Error | CapabilityStatement.url | Values for url differ: 'http://hl7.org/fhir/uv/ipa/CapabilityStatement/ipa-server' vs 'http://hl7.dk/fhir/smart/CapabilityStatement/dk-smart-server' |
Error | CapabilityStatement.version | Values for version differ: '1.0.0' vs '0.5.0' |
Information | CapabilityStatement.name | Values for name differ: 'InternationalPatientAccessAPI' vs 'DKSmartServer' |
Information | CapabilityStatement.title | Values for title differ: 'International Patient Access Server CapabilityStatement' vs 'Danish SMART Server Capability Statement' |
Information | CapabilityStatement.date | Values for date differ: '2022-12-09' vs '2023-11-09' |
Information | CapabilityStatement.publisher | Values for publisher differ: 'HL7 International - Patient Care Work Group' vs 'HL7 Denmark' |
Information | CapabilityStatement.jurisdiction | Removed the item 'http://unstats.un.org/unsd/methods/m49/m49.htm#001' |
Information | CapabilityStatement.jurisdiction | Added the item 'urn:iso:std:iso:3166#DK' |
Information | CapabilityStatement.implementationGuide | Added the item 'http://hl7.org/fhir/uv/ipa/ImplementationGuide/hl7.fhir.uv.ipa' |
Warning | CapabilityStatement.rest.where(mode='SERVER').documentation | Changed value for documentation: 'The IPA Server **SHALL**:
1. Support the IPA Patient resource profile.
1. Support at least one additional resource profile from the list of IPA Profiles.
1. Implement the RESTful behavior according to the FHIR specification.
1. Return the following response classes:
- (Status 400): invalid parameter
- (Status 401/4xx): unauthorized request
- (Status 403): insufficient scope
- (Status 404): unknown resource
1. Support JSON source formats for all IPA interactions.
1. Declare a CapabilityStatement identifying the list of profiles, operations, and search parameters supported.
The IPA Server **SHOULD**:
1. Support XML source formats for all IPA interactions.' vs 'The server **SHALL**:
1. Implement the RESTful behavior according to the FHIR specification.
1. Support JSON source formats for all interactions.
1. Declare a CapabilityStatement identifying the list of profiles, operations, and search parameters supported.
The server **SHOULD**:
1. Support XML source formats for all interactions.
1. Implement the International Patient Access (IPA) specification.' |
Information | CapabilityStatement.rest.security.security.description | Changed value for security.description: '1. See the [General Security Considerations](security.html) section for requirements and recommendations.
1. A server **SHALL** reject any unauthorized requests by returning an HTTP `401 Unauthorized`, `403 Forbidden`, or `404 Not Found` response code.' vs 'This implementation guide relies heavily on the widely adopted SMART App Launch mechanism. This implementation guide does not define any new security mechanisms. Please familiarize yourself with the securty concepts infroduced in the SMART App Launch specification, and the underlying OpenID Connect and OAuth2 specifications the SMART App Launch specification build on.
1. See the Best Practices outlined in the SMART App Launch specification.
1. See the [FHIR Security](https://www.hl7.org/fhir/security.html) section of the FHIR specification for requirements and recommendations.
1. A server **SHALL** reject any unauthorized requests by returning an HTTP `401 Unauthorized`, `403 Forbidden`, or `404 Not Found` response code.' |