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

MimeTypeTerminologyService should handle STU3 canonical for MimeType ValueSet #2504

Closed
alexzautke opened this issue Jun 16, 2023 · 0 comments · Fixed by #2506
Closed

MimeTypeTerminologyService should handle STU3 canonical for MimeType ValueSet #2504

alexzautke opened this issue Jun 16, 2023 · 0 comments · Fixed by #2506
Assignees

Comments

@alexzautke
Copy link
Member

In STU3 the canonical for the MimeType ValueSet, e.g. in Attachment.contentType is "http://www.rfc-editor.org/bcp/bcp13.txt" not "http://hl7.org/fhir/ValueSet/mimetypes". This should be handled by the the terminology service as an additional canonical. Note that this is a bit more tricky as there is not a ValueSet resource defined by the spec itself. It's just a binding on the datatype itself as far as I can see. This might cause some issues in the VS resolver.

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

Successfully merging a pull request may close this issue.

3 participants