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

Capability Statement format mimetype validations #380

Open
brianpos opened this issue Oct 15, 2024 · 0 comments
Open

Capability Statement format mimetype validations #380

brianpos opened this issue Oct 15, 2024 · 0 comments

Comments

@brianpos
Copy link

brianpos commented Oct 15, 2024

The new validator does not pass CapabilityStatement instances that have the format xml or json without the application/ prefix.
Refer to spec for this...
https://build.fhir.org/capabilitystatement-definitions.html#CapabilityStatement.format

https://build.fhir.org/valueset-capability-format-type.html

Should also review the set that are referenced here too:
https://hl7.org/fhir/r4b/valueset-mimetypes.html
(Gino is logging this against the spec to work out if the core spec should be clarified here, as there are differences - and I'll rechcek the java validator to see if that has a rule around these specific values too)

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

No branches or pull requests

1 participant