| Error | CapabilityStatement.url | Values for url differ: 'http://hl7.org/fhir/uv/ips/CapabilityStatement/ips-server' vs 'http://hl7.org/fhir/us/core/CapabilityStatement/us-core-server' |
| Error | CapabilityStatement.version | Values for version differ: '2.0.0' vs '9.0.0-ballot' |
| Information | CapabilityStatement.name | Values for name differ: 'IpsServerCapabilityStatement' vs 'UsCoreServerCapabilityStatement' |
| Information | CapabilityStatement.title | Values for title differ: 'IPS Server Capability Statement' vs 'US Core Server CapabilityStatement' |
| Information | CapabilityStatement.date | Values for date differ: '2022-01-05T13:15:56.964-00:00' vs '2025-10-13T13:24:36.607377-08:00' |
| Information | CapabilityStatement.publisher | Values for publisher differ: 'HL7 International / Patient Care' vs 'HL7 International / Cross-Group Projects' |
| 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#US' |
| Information | CapabilityStatement.format | Removed the item 'application/fhir+xml' |
| Information | CapabilityStatement.format | Removed the item 'application/fhir+json' |
| Information | CapabilityStatement.patchFormat | Added the item 'application/json-patch+json' |
| Information | CapabilityStatement.implementationGuide | Added the item 'http://hl7.org/fhir/smart-app-launch/ImplementationGuide/hl7.fhir.uv.smart-app-launch' |
| Information | CapabilityStatement.rest.resource.documentation | Changed value for documentation: 'Some systems may only support MedicationRequest(IPS) or MedicationStatement(IPS).' vs '* This Profile can represent a medication using a code or reference a Medication resource.
* The Server systems are not required to support both a code and a reference, but **SHALL** support at least one of these methods.
* The Client application **SHALL** support all methods.
* Systems that primarily rely on NDC codes instead of RxNorm to represent medications can use the National Library of Medicine's (NLM) NDC to RxNorm mappings to aid in additional codings.
* When referencing a Medication resource in `.medicationReference`, the resource may be contained or an external resource. If an external reference to a Medication resource is used, the Server **SHALL** support the `_include` parameter for searching this element.
* The MedicationRequest resource can represent that information is from a secondary source using either a boolean flag or reference in `MedicationRequest.reportedBoolean`, or a reference using `MedicationRequest.reportedReference` to Practitioner or other resource.
* Although both are marked as must support, the server systems are not required to support both a boolean and a reference, but **SHALL** choose to support at least one of these elements.
* The client application **SHALL** support both elements.
* When recording “self-prescribed” medication, requester **SHOULD** be used to indicate the Patient or RelatedPerson as the prescriber. (See the Medication List section for guidance on accessing a patient medications including over the counter (OTC) medication and other substances taken for medical and recreational use.)
* The MedicationRequest resource can communicate the reason or indication for treatment using either a code in MedicationRequest.reasonCode or a reference using MedicationRequest.reasonReference.
* Although both `MedicationRequest.reasonCode` and `MedicationRequest.reasonReference` are marked as Additional USCDI Requirements. The certifying server system is not required to support both but **SHALL** support at least one of these elements. The certifying client application **SHALL** support both elements.
* when using MedicationRequest.reasonReference:
* Servers **SHALL** support at least one target resource in `MedicationRequest.reasonReference`. Clients **SHALL** support all target resources.
* The referenced resources **SHOULD** be a US Core Profile as documented in Referencing US Core Profiles.' |