UUID as requirement for resource ids necessary?

[skomski]

Is it necessary to restrain resource ids to UUIDs? The FHIR spec is much broader: (http:https://hl7.org/fhir/R4/datatypes.html#id)

Any combination of upper- or lower-case ASCII letters ('A'..'Z', and 'a'..'z', numerals ('0'..'9'), '-' and '.', with a length limit of 64 characters. (This might be an integer, an un-prefixed OID, UUID or any other identifier pattern that meets these constraints.)

medplum/packages/server/src/fhir/repo.ts

Line 472 in c90b03e

if (!validator.isUUID(id)) {

For example we want to use for some resources OIDs.

[codyebberson]

Hi @skomski - Currently the UUID is a requirement. We have plans to support the full ID spec via client assigned IDs. You can see the discussion here: #1175