The jira specification file appears to be out of date with the versions, artifacts and pages currently defined in the IG. A proposed revised file to be reviewed and, if appropriate, submitted as a pull request against the XML folder in https://github.com/HL7/JIRA-Spec-Artifacts. To see the differences, perform a file compare on 'template/jira-current.xml' (a normalized view of what is in Github) and 'template/jira-new.xml' (reflects current IG content)
CodeSystem-obligation.html
information
The html source contains the word 'SHALL' but it is not in a text phrase marked as a conformance clause: ' Codes that describe application obligations for handling FHIR content. There are five kinds of codes in this code system: Categorizer codes: ResourceProducerObligations, ResourcesExchangerObligations, and ResourceConsumerObligations which are used to construct value sets and indicate the contexts in which the obligations apply. Note that many applications will be producers, consumers, and potentially exchangers simultaneously, so there is no need to limit obligations to only one category. These are abstract and cannot be declared as obligations. Qualifier codes: SHALL/SHOULD/MAY which convey the 'strength' of an obligation. These are also abstract and cannot be declared as obligations. Generic codes - these describe abstract functional obligation behaviors applications may implement, but do not specify a specific strength. They may be organized in a hierarchy where one generic code specializes another. These are also abstract cannot be declared as obligations. Leaf obligation codes - these are specific qualified obligations that can be declared by a data element and represent leaf-level obligations. They always inherit from a qualification concept and usually inherit from a functional code concept. These codes can be declared as obligations. Composite codes - these specialise Leaf obligation codes, inheriting the expectations of multiple concrete obligations. They represent common or externally defined combinations of obligations for ease of reference. These codes can also be declared as obligations. 'CONFORMANCE_STATEMENT_WORD
StructureDefinition-additionalIdentifier.html
information
The html source contains the word 'SHALL' but it is not in a text phrase marked as a conformance clause: 'An additional identifier for the target resource. This is used when there is no way to reference the other resource directly, either because the entity it represents is not available through a FHIR server, or because there is no way for the author of the resource to convert a known identifier to an actual location. There is no requirement that a Reference.identifier point to something that is actually exposed as a FHIR instance, but it SHALL point to a business concept that would be expected to be exposed as a FHIR instance, and that instance would need to be of a FHIR resource type allowed by the reference.'CONFORMANCE_STATEMENT_WORD
The html source contains the word 'SHALL' but it is not in a text phrase marked as a conformance clause: 'The 'substanceExposureRisk' extension is a structured and more flexible alternative to AllergyIntolerance.code for making positive or negative allergy or intolerance statements. This extension provides the capability to make "no known allergy" (or "no risk of adverse reaction") statements regarding any coded substance/product (including cases when a pre-coordinated "no allergy to x" concept for that substance/product does not exist). If the 'substanceExposureRisk' extension is present, the AllergyIntolerance.code element SHALL be omitted.'CONFORMANCE_STATEMENT_WORD
StructureDefinition-alternate-codes.html
information
The html source contains the word 'SHALL' but it is not in a text phrase marked as a conformance clause: 'Indicates alternate codings and/or original text for the concept represented by the code. Codings or text provided SHALL convey equivalent meaning to the meaning of the code being extended (though with potential differences in level of detail conveyed).'CONFORMANCE_STATEMENT_WORD
StructureDefinition-artifact-jurisdiction.html
information
The html source contains the word 'SHALL' but it is not in a text phrase marked as a conformance clause: 'A legal or geographic region in which the authority that maintains the resource is operating. In general, the jurisdiction is also found in the Artifact use context for the resource. The useContext may reference additional jurisdictions because the defining jurisdiction does not necessarily limit the jurisdictions of use. This extension SHALL not be used on any resource that has a defined jurisdiction element.'CONFORMANCE_STATEMENT_WORD
StructureDefinition-artifact-url.html
information
The html source contains the word 'SHALL' but it is not in a text phrase marked as a conformance clause: 'An absolute URI that is used to identify this artifact when it is referenced in a specification, model, design or an instance; also called its canonical identifier. This SHOULD be globally unique and SHOULD be a literal address at which an authoritative instance of this artifact is (or will be) published. This URL can be the target of a canonical reference. It SHALL remain the same when the artifact is stored on different servers.'CONFORMANCE_STATEMENT_WORD
The html source contains the word 'SHALL' but it is not in a text phrase marked as a conformance clause: 'An expression that defines the criteria for group membership. This extension can only be used on a Group resource with a membership of definitional. When this expression is used, the Group resource cannot have any characteristic elements; this mechanism is exclusive with characteristics. The result of the expression SHALL be boolean-valued. The expression SHALL be parameterized with a %context variable that represents the subject being tested for membership. If evaluation of the expression results in true, the subject is considered a member of the group.'CONFORMANCE_STATEMENT_WORD
StructureDefinition-codeOptions.html
information
The html source contains the word 'SHALL NOT' but it is not in a text phrase marked as a conformance clause: 'This extension SHALL NOT be used when an appropriate higher level concept code exists.'CONFORMANCE_STATEMENT_WORD
The html source contains the word 'SHOULD' but it is not in a text phrase marked as a conformance clause: 'Indicates that a ContactPoint has the intended use of the combination of the use and multiple use e.g. Mobile Business, or Temporary Home. Systems SHOULD populate a primary use in ContactPoint.use and then populate all applicable uses in this extension.'CONFORMANCE_STATEMENT_WORD
StructureDefinition-cqf-citation.html
information
The html source contains the word 'SHOULD' but it is not in a text phrase marked as a conformance clause: 'A bibliographic citation for the resource. This text SHOULD be formatted according to an accepted citation format.'CONFORMANCE_STATEMENT_WORD
The html source contains the word 'SHALL' but it is not in a text phrase marked as a conformance clause: 'This acts as an overall 'required' binding for an element that already has a less restrictive binding. It is used when there is a desire to have a 'small' enumerable binding that meets most needs and where the overall value set that the codes must be drawn from is 'infinite'. The the base less restrictive binding SHALL be a proper subset of the max binding valueset. In most cases, this extension is used where the base binding is 'extensible'. DEPRECATED: Use additionalBinding extension or element instead'CONFORMANCE_STATEMENT_WORD
The html source contains the word 'SHALL' but it is not in a text phrase marked as a conformance clause: 'The minimum allowable value set, for use when the binding strength is 'required' or 'extensible'. This value set is the minimum value set that any conformant system SHALL support. DEPRECATED: Use additionalBinding extension or element instead'CONFORMANCE_STATEMENT_WORD
StructureDefinition-feature-assertion.html
information
The html source contains the word 'SHOULD' but it is not in a text phrase marked as a conformance clause: 'As an example of the kind of use this extension might support, an application could choose to only use value set expansions that are explicitly labeled as 'prepared under the conformance rules defined in the CRMI implementation guide. This extension is a statement about the provenance of a particular version of the resource that it is describing; as such, it should be made in a Provenance resource referring to that particular version. Alternatively, the extension can be placed in the resource about which the assertion is made (in Resource.meta); in this case, the assertion SHOULD be removed when the resource data is altered (it may be replaced by a new assertion).'CONFORMANCE_STATEMENT_WORD
StructureDefinition-obligations-profile.html
information
The html source contains the word 'SHOULD' but it is not in a text phrase marked as a conformance clause: 'As an example of the kind of use this extension might support, an application could decide, while reading the contents of a resource, that an element was available for data entry and the fact that it is mising implies 'no value exists' as opposed to 'creating system was unable to provide a value'. This extension is a statement about the provenance of a particular version of the resource that it is describing; as such, it should be made in a Provenance resource referring to that particular version. Alternatively, the extension can be placed in the resource about which the declaration is made (in Resource.meta); in this case, the declaration SHOULD be removed when the resource data is altered (it may be replaced by a new declaration).'CONFORMANCE_STATEMENT_WORD
The html source contains the word 'SHALL' but it is not in a text phrase marked as a conformance clause: 'Identifies a profile structure or implementation Guide that applies to the datatype this element refers to. If any profiles are specified, then the content must conform to at least one of them. The URL can be a local reference - to a contained StructureDefinition, or a reference to another StructureDefinition or Implementation Guide by a canonical URL. When an implementation guide is specified, the type SHALL conform to at least one profile defined in the implementation guide.'CONFORMANCE_STATEMENT_WORD
The html source contains the word 'SHOULD' but it is not in a text phrase marked as a conformance clause: 'Indicates the terminology server(s) that are known to be capable of returning and potentially expanding the value set(s) associated with the resource or a particular portion of the resource (depending on where the extension appears). If a full URL is not provided AND the requested query is a terminology operation (e.g. $lookup or $expand) the client SHOULD execute the operation against (one of) the preferredTerminologyServer(s) rather than the local repository. Systems SHOULD evaluate value sets using terminology servers as follows: First, try any terminology servers declared on the element in question. If there are more then one, try them in the order they appear. Then try any servers that appear on ancestor elements in order of closest ancestor up to any on the resource root If there are no declared servers or none of the ones listed provide a useful response, the form filler may then try any of the typical servers it would normally use. A 'useful response' means a response that provides a valid (though potentially empty) expansion. Clients MAY wish to log/report errors returned by terminology servers.'CONFORMANCE_STATEMENT_WORD
The html source contains the word 'SHOULD' but it is not in a text phrase marked as a conformance clause: 'An extension (or if multiple, a collection of alternative extensions) that SHOULD be used in the event a value element is not present.'CONFORMANCE_STATEMENT_WORD
StructureDefinition-profile-mapping.html
information
The html source contains the word 'SHALL' but it is not in a text phrase marked as a conformance clause: 'This extension defines a relationship between a search string and a profile. Any resource that meets a given search string will be expected to conform to the particular profile. If more than one profile is nominated for a search string, resources SHALL conform to all the listed profiles. The last extension can be without a search matches and remaining resources'CONFORMANCE_STATEMENT_WORD
StructureDefinition-quantity-accuracy.html
information
The html source contains the word 'SHOULD' but it is not in a text phrase marked as a conformance clause: 'Accuracy is usually in the same units as the reported value. Accuracy valueQuantity units SHOULD be provided for clarity; if omitted, they are implied to be the same as the reported value's units (or the DeviceMetric units).'CONFORMANCE_STATEMENT_WORD
The html source contains the word 'SHOULD' but it is not in a text phrase marked as a conformance clause: 'The reported value need not be at the center of the confidence interval; for example, if the values don't follow a normal distribution. The context Observation.value SHOULD be present when this extension is used, due to the risk that systems unfamiliar with (or ignoring) this extension may be unable to process a valueless quantity.'CONFORMANCE_STATEMENT_WORD
StructureDefinition-questionnaire-unit.html
information
The html source contains the word 'SHOULD' but it is not in a text phrase marked as a conformance clause: 'Provides a computable unit of measure associated with numeric questions to support subsequent computation on responses. This is for use on items of type integer and decimal, and its purpose is to support converting the integer or decimal answer into a Quantity when extracting the data into a resource. If a 'display' value is provided for valueCoding of this extension and the associated question item does not have a child 'display' item with an itemControl extension of 'unit', then form fillers SHOULD take the display value of this extension and use it as as the unit display.'CONFORMANCE_STATEMENT_WORD
StructureDefinition-timezone.html
information
The html source contains the word 'SHALL' but it is not in a text phrase marked as a conformance clause: 'An IANA timezone code for the timezone offset per BCP 175. For data types allowing the offset (all except date and time), this extension SHALL agree with the offset if provided and cannot be used in place of the offset if the precision expressed requires an offset. Where an offset is provided, this extension provides a more legible display of the zone associated with the offset. Where an offset is not present, this extension can be used to provide zone information not otherwise available.'CONFORMANCE_STATEMENT_WORD
StructureDefinition-translation.html
information
The html source contains the word 'SHOULD' but it is not in a text phrase marked as a conformance clause: 'Language translation from base language of resource to another language, used to provide translations for strings, including markdown. Generally, the type of the translation extension SHOULD match that of the element being extended.'CONFORMANCE_STATEMENT_WORD
StructureDefinition-valueset-caseSensitive.html
information
The html source contains the word 'SHALL NOT' but it is not in a text phrase marked as a conformance clause: 'An assertion of whether the code is case sensitive or not. This assertion SHALL be based on how the code system is defined. If the server generating the expansion does not know how the code system defined case sensitivity of codes, this extension SHALL NOT be used.'CONFORMANCE_STATEMENT_WORD
The html source contains the word 'SHALL NOT' but it is not in a text phrase marked as a conformance clause: 'A definition that describes the meaning of this code when used as part of this value set. Use of this extension SHALL NOT result in a definition for a concept that changes the meaning of the concept as described in the code system. This SHALL only be used to further clarify or provide additional nuances to the meaning.'CONFORMANCE_STATEMENT_WORD
StructureDefinition-valueset-expirationDate.html
information
The html source contains the word 'SHALL' but it is not in a text phrase marked as a conformance clause: 'The date when the value set version is no longer expected to be used to create new content. This is the first date-time when the value set version becomes Inactive, so this value SHALL present on all Inactive value set versions. The start Date_time is expected to be as of 0001 UTC of the Expiration Date.'CONFORMANCE_STATEMENT_WORD
StructureDefinition-valueset-unclosed.html
information
The html source contains the word 'SHALL' but it is not in a text phrase marked as a conformance clause: 'Marks that the expansion is incomplete, and values other than those listed may be valid. This may be used when technical limitations prevent a full expansion, or when post-coordinated codes are allowed, and no complete expansion can be produced. This extension SHALL only be used when the client specifies that it will recognize and process an incomplete expansion. If the client has not specified it will recognize and process an incomplete expansion, the server SHALL return an error.'CONFORMANCE_STATEMENT_WORD
deprecated.html
information
The html source contains the word 'SHOULD' but it is not in a text phrase marked as a conformance clause: 'Such an IG SHOULD allow both the old extension and the new inter-version extension to be transmitted for a period of time for compatibility reasons and to reduce the pain of the breaking change.'CONFORMANCE_STATEMENT_WORD
'Fetus' is no longer considered a correct display for code '83418008' (status = inactive). The correct display is one of "Entire fetus" (from https://tx.fhir.org/r5, see log, or see the servers logic) INACTIVE_DISPLAY_FOUND
Constraint failed: sdf-9: 'In any snapshot or differential, no label, code or requirements on an element without a "." in the path (e.g. the first element) (children().element.where(path.contains('.').not()).label.empty() and children().element.where(path.contains('.').not()).code.empty() and children().element.where(path.contains('.').not()).requirements.empty())' (defined in http://hl7.org/fhir/StructureDefinition/StructureDefinition)http://hl7.org/fhir/StructureDefinition/StructureDefinition#sdf-9
The property 'deprecated' is not known for the system 'http://terminology.hl7.org/CodeSystem/v2-0066', so may not be understood by the terminology ecosystem. Known properties for this system: concept,code,status,inactive,effectiveDate,deprecationDate,retirementDate,notSelectable,synonym,comment,itemWeight,parent,child,partOf,v2-table-deprecated
ValueSet 'true' Filter by property 'http://hl7.org/fhir/ValueSet/practitionerrole-employmentStatus|5.3.0-ballot-tc1' and op 'deprecated' is not supported yet (and Error from https://tx.fhir.org/r5: The filter "deprecated = 2.9" from the value set http://hl7.org/fhir/ValueSet/practitionerrole-employmentStatus was not understood in the context of http://terminology.hl7.org/CodeSystem/v2-0066 (4))
Conformance resource /scratch/repo/input/definitions/Resource/StructureDefinition-entered-in-error-status.xml - the canonical URL (http://hl7.org/fhir/extensions/StructureDefinition/entered-in-error-status) does not match the URL (http://hl7.org/fhir/tools/StructureDefinition/entered-in-error-status). Use the special-url parameter if you really mean for it not to matchRESOURCE_CANONICAL_MISMATCH
URL Mismatch http://hl7.org/fhir/extensions/StructureDefinition/entered-in-error-status vs http://hl7.org/fhir/tools/StructureDefinition/entered-in-error-status
The concepts in the value set include have not been validated because the code system is not known, and no terminology service supports itVALUESET_INC_CS_NO_SUPPORT
ValueSet.where(id = 'value-filter-comparator')
error
Error from https://tx.fhir.org/r5: A definition for CodeSystem 'http://hl7.org/fhir/search-comparator' version '4.0.1' could not be found, so the value set cannot be expanded. Valid versions: 5.0.0,5.0.0 (from server, see log)
The System URI could not be determined for the code '6.0' in the ValueSet 'http://hl7.org/fhir/ValueSet/major-fhir-version|5.3.0-ballot-tc1'UNABLE_TO_INFER_CODESYSTEM
The value provided ('6.0') was not found in the value set 'Major FHIR Versions' (http://hl7.org/fhir/ValueSet/major-fhir-version|5.3.0-ballot-tc1), and a code is required from this value set (error message = The System URI could not be determined for the code '6.0' in the ValueSet 'http://hl7.org/fhir/ValueSet/major-fhir-version|5.3.0-ballot-tc1'; The provided code '#6.0' was not found in the value set 'http://hl7.org/fhir/ValueSet/major-fhir-version|5.3.0-ballot-tc1')Terminology_TX_NoValid_16
Wrong Display Name 'goat' for http://snomed.info/sct#125097000. Valid display is 'Capra hircus' (en) (for the language(s) 'en, en-US'). Note that the display in the ValueSet does not have to match; this check exists to help check that it's not accidentally the wrong codeVALUESET_CODE_CONCEPT_HINT
Wrong Display Name 'cow' for http://snomed.info/sct#34618005. Valid display is 'Bos taurus' (en) (for the language(s) 'en, en-US'). Note that the display in the ValueSet does not have to match; this check exists to help check that it's not accidentally the wrong codeVALUESET_CODE_CONCEPT_HINT
Wrong Display Name 'turkey' for http://snomed.info/sct#425134008. Valid display is 'Subfamily Meleagridinae (organism)' (en) (for the language(s) 'en, en-US'). Note that the display in the ValueSet does not have to match; this check exists to help check that it's not accidentally the wrong codeVALUESET_CODE_CONCEPT_HINT
Wrong Display Name 'goose' for http://snomed.info/sct#15778005. Valid display is 'Anser' (en) (for the language(s) 'en, en-US'). Note that the display in the ValueSet does not have to match; this check exists to help check that it's not accidentally the wrong codeVALUESET_CODE_CONCEPT_HINT
'horse' is no longer considered a correct display for code '388445009' (status = inactive). The correct display is one of "Genus Equus (organism)" (from https://tx.fhir.org/r5, see log) INACTIVE_DISPLAY_FOUND
This element does not match any known slice defined in the profile http://hl7.org/fhir/StructureDefinition/shareablecodesystem|5.0.0 (125 uses)
This element does not match any known slice defined in the profile http://hl7.org/fhir/StructureDefinition/shareablevalueset|5.0.0 (215 uses)
FMG has decided to address these issues in a future release
HL7 Defined CodeSystems should ensure that every concept has a definition (1 uses)
Most code systems defined in HL7 IGs will need to move to THO later during the process. Consider giving this code system a THO URL now (See https://confluence.hl7.org/display/TSMG/Terminology+Play+Book, and/or talk to TSMG) (49 uses)
SD_ED_EXPERIMENTAL_BINDING (28 uses)
These codes properties are intended to be internal codes
INFORMATION: CodeSystem/obligation: CodeSystem.property[2]: The type of property 'code' is 'code', but no ValueSet information was found, so the codes will be validated as internal codes (1 uses)
INFORMATION: CodeSystem/obligation: CodeSystem.property[3]: The type of property 'code' is 'code', but no ValueSet information was found, so the codes will be validated as internal codes (1 uses)
These extensions really should have a context of 'element' (checked with FMG)
This code sytstem is wrongly labelled experimental in R5 - will be fixed in R6
Reference to experimental CodeSystem http://hl7.org/fhir/guide-parameter-code|5.0.0 (16 uses)
This is OK by a recent decision of the TI workgroup, but the validator hasn't yet been updated for the decision
Pinned the version of http://hl7.org/fhir/ValueSet/value-filter-comparator to 5.3.0-ballot from choices of 5.0.0 (hl7.fhir.r5.core#5.0.0), 5.3.0-ballot (hl7.fhir.uv.extensions#5.3.0-ballot) (0 uses)
The property 'status' has no definition in CodeSystem.property. Many terminology tools won't know what to do with it (1 uses)
This is actually caused by an error in the definition of the CodeSystem in THO. We've created a task to fix that
Pinned the version of http://hl7.org/fhir/ValueSet/value-filter-comparator to 5.3.0-ballot-tc1 from choices of 5.0.0 (hl7.fhir.r5.core#5.0.0), 5.3.0-ballot-tc1 (hl7.fhir.uv.extensions#5.3.0-ballot-tc1)
Pinned the version of http://hl7.org/fhir/ValueSet/value-filter-comparator to 5.3.0-ballot-tc1 from choices of 5.0.0 (hl7.fhir.r5.core#5.0.0), 5.3.0-ballot-tc1 (hl7.fhir.uv.extensions#5.3.0-ballot-tc1)
Conformance resource /scratch/repo/input/definitions/Resource/StructureDefinition-entered-in-error-status.xml - the canonical URL (http://hl7.org/fhir/extensions/StructureDefinition/entered-in-error-status) does not match the URL (http://hl7.org/fhir/tools/StructureDefinition/entered-in-error-status). Use the special-url parameter if you really mean for it not to match
The value provided ('6.0') was not found in the value set 'Major FHIR Versions' (http://hl7.org/fhir/ValueSet/major-fhir-version|5.3.0-ballot-tc1), and a code is required from this value set (error message = The System URI could not be determined for the code '6.0' in the ValueSet 'http://hl7.org/fhir/ValueSet/major-fhir-version|5.3.0-ballot-tc1'; The provided code '#6.0' was not found in the value set 'http://hl7.org/fhir/ValueSet/major-fhir-version|5.3.0-ballot-tc1')
Wrong Display Name 'Prefix Family Given Suffix' for http://terminology.hl7.org/CodeSystem/v2-0444#F. Valid display is 'Prefix Family Middle Given Suffix' (for the language(s) 'en, en-US'). Note that the display in the ValueSet does not have to match; this check exists to help check that it's not accidentally the wrong code
Wrong Display Name 'Prefix Given Family Suffix' for http://terminology.hl7.org/CodeSystem/v2-0444#G. Valid display is 'Prefix Given Middle Family Suffix' (for the language(s) 'en, en-US'). Note that the display in the ValueSet does not have to match; this check exists to help check that it's not accidentally the wrong code
Wrong Display Name 'Call me' for http://terminology.hl7.org/CodeSystem/v3-EntityNamePartQualifierR2#CL. Valid display is 'callme' (en) (for the language(s) 'en, en-US'). Note that the display in the ValueSet does not have to match; this check exists to help check that it's not accidentally the wrong code
Wrong Display Name 'milliseconds' for http://unitsofmeasure.org#ms. Valid display is 'ms' (for the language(s) 'en, en-US'). Note that the display in the ValueSet does not have to match; this check exists to help check that it's not accidentally the wrong code
Wrong Display Name 'seconds' for http://unitsofmeasure.org#s. Valid display is 's' (for the language(s) 'en, en-US'). Note that the display in the ValueSet does not have to match; this check exists to help check that it's not accidentally the wrong code
Wrong Display Name 'minutes' for http://unitsofmeasure.org#min. Valid display is 'min' (for the language(s) 'en, en-US'). Note that the display in the ValueSet does not have to match; this check exists to help check that it's not accidentally the wrong code
Wrong Display Name 'hours' for http://unitsofmeasure.org#h. Valid display is 'h' (for the language(s) 'en, en-US'). Note that the display in the ValueSet does not have to match; this check exists to help check that it's not accidentally the wrong code
Wrong Display Name 'days' for http://unitsofmeasure.org#d. Valid display is 'd' (for the language(s) 'en, en-US'). Note that the display in the ValueSet does not have to match; this check exists to help check that it's not accidentally the wrong code
Wrong Display Name 'months' for http://unitsofmeasure.org#mo. Valid display is 'mo' (for the language(s) 'en, en-US'). Note that the display in the ValueSet does not have to match; this check exists to help check that it's not accidentally the wrong code
Wrong Display Name 'years' for http://unitsofmeasure.org#a. Valid display is 'a' (for the language(s) 'en, en-US'). Note that the display in the ValueSet does not have to match; this check exists to help check that it's not accidentally the wrong code
Wrong Display Name 'goat' for http://snomed.info/sct#125097000. Valid display is 'Capra hircus' (en) (for the language(s) 'en, en-US'). Note that the display in the ValueSet does not have to match; this check exists to help check that it's not accidentally the wrong code
Wrong Display Name 'cow' for http://snomed.info/sct#34618005. Valid display is 'Bos taurus' (en) (for the language(s) 'en, en-US'). Note that the display in the ValueSet does not have to match; this check exists to help check that it's not accidentally the wrong code
Wrong Display Name 'turkey' for http://snomed.info/sct#425134008. Valid display is 'Subfamily Meleagridinae (organism)' (en) (for the language(s) 'en, en-US'). Note that the display in the ValueSet does not have to match; this check exists to help check that it's not accidentally the wrong code
Wrong Display Name 'goose' for http://snomed.info/sct#15778005. Valid display is 'Anser' (en) (for the language(s) 'en, en-US'). Note that the display in the ValueSet does not have to match; this check exists to help check that it's not accidentally the wrong code
No definition can be found for the system urn:iso:std:iso:11073:10101, and the property 'partition' is not a generally known property, so the property might not be valid, or understood by the terminology ecosystem. In case it's useful, the list of generally known properties for all systems is concept,code,status,inactive,effectiveDate,deprecationDate,retirementDate,notSelectable,synonym,comment,itemWeight
hl7.fhir.uv.extensions
hl7.fhir.uv.extensions.r5