Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

More constraints on identifiers necessary #93

Closed
simoneOnFhir opened this issue Sep 23, 2021 · 2 comments
Closed

More constraints on identifiers necessary #93

simoneOnFhir opened this issue Sep 23, 2021 · 2 comments
Assignees

Comments

@simoneOnFhir
Copy link

simoneOnFhir commented Sep 23, 2021

In order to ascertain the proper usage of identifiers, identifier.system and identifier.value should be mandatory in general.
Where UUIDs or OIDs are required, system should be fixed to urn:ietf:rfc:3986, see: http://hl7.org/fhir/identifier-registry.html

Example: A List with

<identifier>
  <use value = "official"/>
</identifier>
<identifier>
  <use value = "usual"/>
</identifier>

...would currently validate against https://profiles.ihe.net/ITI/MHD/StructureDefinition-IHE.MHD.UnContained.Comprehensive.SubmissionSet.html

@JohnMoehrke
Copy link
Contributor

so add to the MHD profiles where there are identifiers that the identifier.system and identifier.value are 1..
right?

@JohnMoehrke JohnMoehrke added the Discussion Committee Discussion needed label Oct 21, 2021
@simoneOnFhir
Copy link
Author

Yes. I don't see how an identifier without a value or a system would make any sense, if the identifier itself is mandatory.
Also, where OIDs or UUIDs are required, identifier,system should have a fixed value of urn:ietf:rfc:3986.
It is my observation, that that's something implementers often get wrong when using OIDs/UUIDs

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

3 participants