| Error | CodeSystem.version | Values for version differ: '2.0.0' vs '3.0.0' |
| Information | CodeSystem.date | Values for date differ: '2025-10-13' vs '2026-02-18' |
| Information | CodeSystem.concept.where(code='metadata').definition | Changed value for definition: 'A versioning policy that allows non-substantive changes to the metadata elements of an artifact without requiring a change to the value of the version element.' vs 'A versioning policy that allows non-substantive changes to the metadata elements of an artifact without requiring a change to the value of the version element. Metadata elements are defined as elements that characterize information about the artifact (e.g. description, publisher, useContext, jurisdiction, approvalDate, etc) as defined by the MetadataResource pattern (including elements inherited by the CanonicalResource pattern), except for identity elements (i.e. url, version, and name). Content that makes use of the metadata versioning policy SHOULD still update the date element when metadata content changes. Repositories that host content using metadata versioning SHOULD use cache control headers to ensure downstream systems are aware of the possibility of changes to the artifact.' |
| Information | CodeSystem.concept.where(code='strict').definition | Changed value for definition: 'A versioning policy that indicates that any change to the content of an artifact, including non-substantive and metadata changes, requires a change to the value of the version element of the artifact.' vs 'A versioning policy that indicates that any change to the content of an artifact, including non-substantive and metadata changes, requires a change to the value of the version element, with the exception of the `id` and `meta` elements (consistent with FHIR signature requirements) as well as the `status` (to allow for active content to be marked retired), and `lastReviewDate` (to allow for last review date to be communicated) elements. Repositories that host content using strict versioning SHOULD use cache control headers to ensure downstream systems are aware of the possibility of changes to the artifact.' |
| Information | CodeSystem.concept.where(code='loose').definition | Changed value for definition: 'A versioning policy that indicates that only breaking changes require a change to the value of the version element of the artifact.' vs 'A versioning policy that indicates that only breaking changes require a change to the value of the version element of the artifact. Content that makes use of the loose versioning policy SHOULD update the date element when content changes. Repositories that host content using loose versioning SHOULD use cache control headers to ensure downstream systems are aware of the possibility of changes to the artifact.' |
caseSensitive