abstractbaseDefinitioncopyrightdate- Values Differ
descriptionexperimentalfhirVersion- Values Differ
jurisdiction
jurisdiction[0]kindnamepublisherpurposestatustitletypeurlversion- Values Differ
| Left: | Danish Core Condition Profile (http://hl7.dk/fhir/core/StructureDefinition/dk-core-condition) |
| Right: | Danish Core Condition Profile (http://hl7.dk/fhir/core/StructureDefinition/dk-core-condition) |
| Error | StructureDefinition.version | Values for version differ: '3.2.0' vs '1.0.0' |
| Information | StructureDefinition.date | Values for date differ: '2024-05-06T15:21:43+02:00' vs '2024-11-18T13:05:29+00:00' |
| Warning | StructureDefinition.fhirVersion | Values for fhirVersion differ: '4.0.1' vs '5.0.0' |
| Information | StructureDefinition.comment | Values for comment differ: 'The only time that a resource does not have an id is when it is being submitted to the server using a create operation.' vs 'Within the context of the FHIR RESTful interactions, the resource has an id except for cases like the create and conditional update. Otherwise, the use of the resouce id depends on the given use case.' |
| Information | StructureDefinition.comment | Values for comment differ: 'Asserting this rule set restricts the content to be only understood by a limited set of trading partners. This inherently limits the usefulness of the data in the long term. However, the existing health eco-system is highly fractured, and not yet ready to define, collect, and exchange data in a generally computable sense. Wherever possible, implementers and/or specification writers should avoid using this element. Often, when used, the URL is a reference to an implementation guide that defines these special rules as part of it's narrative along with other profiles, value sets, etc.' vs 'Asserting this rule set restricts the content to be only understood by a limited set of trading partners. This inherently limits the usefulness of the data in the long term. However, the existing health eco-system is highly fractured, and not yet ready to define, collect, and exchange data in a generally computable sense. Wherever possible, implementers and/or specification writers should avoid using this element. Often, when used, the URL is a reference to an implementation guide that defines these special rules as part of its narrative along with other profiles, value sets, etc.' |
| Information | StructureDefinition.comment | Values for comment differ: 'Contained resources do not have narrative. Resources that are not contained SHOULD have a narrative. In some cases, a resource may only have text with little or no additional discrete data (as long as all minOccurs=1 elements are satisfied). This may be necessary for data from legacy systems where information is captured as a 'text blob' or where text is additionally entered raw or narrated and encoded information is added later.' vs 'Contained resources do not have a narrative. Resources that are not contained SHOULD have a narrative. In some cases, a resource may only have text with little or no additional discrete data (as long as all minOccurs=1 elements are satisfied). This may be necessary for data from legacy systems where information is captured as a 'text blob' or where text is additionally entered raw or narrated and encoded information is added later.' |
| Information | StructureDefinition.definition | Values for definition differ: 'These resources do not have an independent existence apart from the resource that contains them - they cannot be identified independently, and nor can they have their own independent transaction scope.' vs 'These resources do not have an independent existence apart from the resource that contains them - they cannot be identified independently, nor can they have their own independent transaction scope. This is allowed to be a Parameters resource if and only if it is referenced by a resource that provides context/meaning.' |
| Information | StructureDefinition.comment | Values for comment differ: 'This should never be done when the content can be identified properly, as once identification is lost, it is extremely difficult (and context dependent) to restore it again. Contained resources may have profiles and tags In their meta elements, but SHALL NOT have security labels.' vs 'This should never be done when the content can be identified properly, as once identification is lost, it is extremely difficult (and context dependent) to restore it again. Contained resources may have profiles and tags in their meta elements, but SHALL NOT have security labels.' |
| Information | StructureDefinition.definition | Values for definition differ: 'May be used to represent additional information that is not part of the basic definition of the resource and that modifies the understanding of the element that contains it and/or the understanding of the containing element's descendants. Usually modifier elements provide negation or qualification. To make the use of extensions safe and manageable, there is a strict set of governance applied to the definition and use of extensions. Though any implementer is allowed to define an extension, there is a set of requirements that SHALL be met as part of the definition of the extension. Applications processing a resource are required to check for modifier extensions. Modifier extensions SHALL NOT change the meaning of any elements on Resource or DomainResource (including cannot change the meaning of modifierExtension itself).' vs 'May be used to represent additional information that is not part of the basic definition of the resource and that modifies the understanding of the element that contains it and/or the understanding of the containing element's descendants. Usually modifier elements provide negation or qualification. To make the use of extensions safe and managable, there is a strict set of governance applied to the definition and use of extensions. Though any implementer is allowed to define an extension, there is a set of requirements that SHALL be met as part of the definition of the extension. Applications processing a resource are required to check for modifier extensions. Modifier extensions SHALL NOT change the meaning of any elements on Resource or DomainResource (including cannot change the meaning of modifierExtension itself).' |
| Information | StructureDefinition.requirements | Values for requirements differ: 'Modifier extensions allow for extensions that *cannot* be safely ignored to be clearly distinguished from the vast majority of extensions which can be safely ignored. This promotes interoperability by eliminating the need for implementers to prohibit the presence of extensions. For further information, see the [definition of modifier extensions](http://hl7.org/fhir/R4/extensibility.html#modifierExtension).' vs 'Modifier extensions allow for extensions that *cannot* be safely ignored to be clearly distinguished from the vast majority of extensions which can be safely ignored. This promotes interoperability by eliminating the need for implementers to prohibit the presence of extensions. For further information, see the [definition of modifier extensions](http://hl7.org/fhir/R5/extensibility.html#modifierExtension).' |
| Information | StructureDefinition.comment | Values for comment differ: 'This is a business identifier, not a resource identifier (see [discussion](http://hl7.org/fhir/R4/resource.html#identifiers)). It is best practice for the identifier to only appear on a single resource instance, however business practices may occasionally dictate that multiple resource instances with the same identifier can exist - possibly even with different resource types. For example, multiple Patient and a Person resource instance might share the same social insurance number.' vs 'This is a business identifier, not a resource identifier (see [discussion](http://hl7.org/fhir/R5/resource.html#identifiers)). It is best practice for the identifier to only appear on a single resource instance, however business practices may occasionally dictate that multiple resource instances with the same identifier can exist - possibly even with different resource types. For example, multiple Patient and a Person resource instance might share the same social insurance number.' |
| Information | StructureDefinition.short | Values for short differ: 'active | recurrence | relapse | inactive | remission | resolved' vs 'active | recurrence | relapse | inactive | remission | resolved | unknown' |
| Information | StructureDefinition.comment | Values for comment differ: 'The data type is CodeableConcept because clinicalStatus has some clinical judgment involved, such that there might need to be more specificity than the required FHIR value set allows. For example, a SNOMED coding might allow for additional specificity.' vs 'The data type is CodeableConcept because clinicalStatus has some clinical judgment involved, such that there might need to be more specificity than the required FHIR value set allows. For example, a SNOMED coding might allow for additional specificity. clinicalStatus is required since it is a modifier element. For conditions that are problems list items, the clinicalStatus should not be unknown. For conditions that are not problem list items, the clinicalStatus may be unknown. For example, conditions derived from a claim are point in time, so those conditions may have a clinicalStatus of unknown' |
| Information | Condition.clinicalStatus | Element minimum cardinalities differ: '0' vs '1' |
| Information | StructureDefinition.definition | Values for definition differ: 'The verification status to support the clinical status of the condition.' vs 'The verification status to support the clinical status of the condition. The verification status pertains to the condition, itself, not to any specific condition attribute.' |
| Information | StructureDefinition.definition | Values for definition differ: 'May be used to represent additional information that is not part of the basic definition of the element. To make the use of extensions safe and manageable, there is a strict set of governance applied to the definition and use of extensions. Though any implementer can define an extension, there is a set of requirements that SHALL be met as part of the definition of the extension.' vs 'May be used to represent additional information that is not part of the basic definition of the element. To make the use of extensions safe and managable, there is a strict set of governance applied to the definition and use of extensions. Though any implementer can define an extension, there is a set of requirements that SHALL be met as part of the definition of the extension.' |
| Information | StructureDefinition.comment | Values for comment differ: 'Only used if not implicit in code found in Condition.code. If the use case requires attributes from the BodySite resource (e.g. to identify and track separately) then use the standard extension [bodySite](http://hl7.org/fhir/R4/extension-bodysite.html). May be a summary code, or a reference to a very precise definition of the location, or both.' vs 'Only used if not implicit in code found in Condition.code. If the use case requires attributes from the BodyStructure resource (e.g. to identify and track separately) then use the standard extension [http://hl7.org/fhir/StructureDefinition/bodySite](http://hl7.org/fhir/extensions/StructureDefinition-bodySite.html). May be a summary code, or a reference to a very precise definition of the location, or both.' |
| Information | StructureDefinition.short | Values for short differ: 'Encounter created as part of' vs 'The Encounter during which this Condition was created' |
| Information | StructureDefinition.comment | Values for comment differ: 'Age is generally used when the patient reports an age at which the Condition began to occur.' vs 'Age is generally used when the patient reports an age at which the Condition began to occur. Period is generally used to convey an imprecise onset that occurred within the time period. For example, Period is not intended to convey the transition period before the chronic bronchitis or COPD condition was diagnosed, but Period can be used to convey an imprecise diagnosis date. Range is generally used to convey an imprecise age range (e.g. 4 to 6 years old). Because a Condition.code can represent multiple levels of granularity and can be modified over time, the onset and abatement dates can have ambiguity whether those dates apply to the current Condition.code or an earlier representation of that Condition.code. For example, if the Condition.code was initially documented as severe asthma, then it is ambiguous whether the onset and abatement dates apply to asthma (overall in that subject's lifetime) or when asthma transitioned to become severe.' |
| Information | StructureDefinition.definition | Values for definition differ: 'The date or estimated date that the condition resolved or went into remission. This is called 'abatement' because of the many overloaded connotations associated with 'remission' or 'resolution' - Conditions are never really resolved, but they can abate.' vs 'The date or estimated date that the condition resolved or went into remission. This is called 'abatement' because of the many overloaded connotations associated with 'remission' or 'resolution' - Some conditions, such as chronic conditions, are never really resolved, but they can abate.' |
| Information | StructureDefinition.comment | Values for comment differ: 'There is no explicit distinction between resolution and remission because in many cases the distinction is not clear. Age is generally used when the patient reports an age at which the Condition abated. If there is no abatement element, it is unknown whether the condition has resolved or entered remission; applications and users should generally assume that the condition is still valid. When abatementString exists, it implies the condition is abated.' vs 'There is no explicit distinction between resolution and remission because in many cases the distinction is not clear. Age is generally used when the patient reports an age at which the Condition abated. If there is no abatement element, it is unknown whether the condition has resolved or entered remission; applications and users should generally assume that the condition is still valid. When abatementString exists, it implies the condition is abated. Because a Condition.code can represent multiple levels of granularity and can be modified over time, the onset and abatement dates can have ambiguity whether those dates apply to the current Condition.code or an earlier representation of that Condition.code. For example, if the Condition.code was initially documented as severe asthma, then it is ambiguous whether the onset and abatement dates apply to asthma (overall in that subject's lifetime) or when asthma transitioned to become severe.' |
| Information | StructureDefinition.short | Values for short differ: 'Date record was first recorded' vs 'Date condition was first recorded' |
| Information | StructureDefinition.definition | Values for definition differ: 'Clinical stage or grade of a condition. May include formal severity assessments.' vs 'A simple summary of the stage such as 'Stage 3' or 'Early Onset'. The determination of the stage is disease-specific, such as cancer, retinopathy of prematurity, kidney diseases, Alzheimer's, or Parkinson disease.' |
| Information | StructureDefinition.definition | Values for definition differ: 'May be used to represent additional information that is not part of the basic definition of the element. To make the use of extensions safe and manageable, there is a strict set of governance applied to the definition and use of extensions. Though any implementer can define an extension, there is a set of requirements that SHALL be met as part of the definition of the extension.' vs 'May be used to represent additional information that is not part of the basic definition of the element. To make the use of extensions safe and managable, there is a strict set of governance applied to the definition and use of extensions. Though any implementer can define an extension, there is a set of requirements that SHALL be met as part of the definition of the extension.' |
| Information | StructureDefinition.definition | Values for definition differ: 'May be used to represent additional information that is not part of the basic definition of the element and that modifies the understanding of the element in which it is contained and/or the understanding of the containing element's descendants. Usually modifier elements provide negation or qualification. To make the use of extensions safe and manageable, there is a strict set of governance applied to the definition and use of extensions. Though any implementer can define an extension, there is a set of requirements that SHALL be met as part of the definition of the extension. Applications processing a resource are required to check for modifier extensions. Modifier extensions SHALL NOT change the meaning of any elements on Resource or DomainResource (including cannot change the meaning of modifierExtension itself).' vs 'May be used to represent additional information that is not part of the basic definition of the element and that modifies the understanding of the element in which it is contained and/or the understanding of the containing element's descendants. Usually modifier elements provide negation or qualification. To make the use of extensions safe and managable, there is a strict set of governance applied to the definition and use of extensions. Though any implementer can define an extension, there is a set of requirements that SHALL be met as part of the definition of the extension. Applications processing a resource are required to check for modifier extensions. Modifier extensions SHALL NOT change the meaning of any elements on Resource or DomainResource (including cannot change the meaning of modifierExtension itself).' |
| Information | StructureDefinition.requirements | Values for requirements differ: 'Modifier extensions allow for extensions that *cannot* be safely ignored to be clearly distinguished from the vast majority of extensions which can be safely ignored. This promotes interoperability by eliminating the need for implementers to prohibit the presence of extensions. For further information, see the [definition of modifier extensions](http://hl7.org/fhir/R4/extensibility.html#modifierExtension).' vs 'Modifier extensions allow for extensions that *cannot* be safely ignored to be clearly distinguished from the vast majority of extensions which can be safely ignored. This promotes interoperability by eliminating the need for implementers to prohibit the presence of extensions. For further information, see the [definition of modifier extensions](http://hl7.org/fhir/R5/extensibility.html#modifierExtension).' |
| Information | StructureDefinition.definition | Values for definition differ: 'A simple summary of the stage such as 'Stage 3'. The determination of the stage is disease-specific.' vs 'A simple summary of the stage such as 'Stage 3' or 'Early Onset'. The determination of the stage is disease-specific, such as cancer, retinopathy of prematurity, kidney diseases, Alzheimer's, or Parkinson disease.' |
| Information | StructureDefinition.short | Values for short differ: 'Supporting evidence' vs 'Supporting evidence for the verification status' |
| Information | StructureDefinition.comment | Values for comment differ: 'The evidence may be a simple list of coded symptoms/manifestations, or references to observations or formal assessments, or both.' vs 'If the condition was confirmed, but subsequently refuted, then the evidence can be cumulative including all evidence over time. The evidence may be a simple list of coded symptoms/manifestations, or references to observations or formal assessments, or both. For example, if the Condition.code is pneumonia, then there could be an evidence list where Condition.evidence.concept = fever (CodeableConcept), Condition.evidence.concept = cough (CodeableConcept), and Condition.evidence.reference = bronchitis (reference to Condition).' |
| Name | Value | Comments | |
|---|---|---|---|
| abstract | false | ||
| baseDefinition | http://hl7.org/fhir/StructureDefinition/Condition | ||
| copyright | |||
| date | 2024-05-06T15:21:43+02:00 | 2024-11-18T13:05:29+00:00 |
|
| description | HL7 Denmark core profile for professionally asserted conditions, as specified by danish health and social care organizations | ||
| experimental | |||
| fhirVersion | 4.0.1 | 5.0.0 |
|
| jurisdiction | |||
| jurisdiction[0] | urn:iso:std:iso:3166#DK | ||
| kind | resource | ||
| name | DkCoreCondition | ||
| publisher | HL7 Denmark | ||
| purpose | |||
| status | active | ||
| title | Danish Core Condition Profile | ||
| type | Condition | ||
| url | http://hl7.dk/fhir/core/StructureDefinition/dk-core-condition | ||
| version | 3.2.0 | 1.0.0 |
|
| Name | L Flags | L Card. | L Type | L Description & Constraints | R Flags | R Card. | R Type | R Description & Constraints | Comments | ||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
 Condition | C | 0..* | Condition | Detailed information about conditions, problems or diagnoses con-3: Condition.clinicalStatus SHALL be present if verificationStatus is not entered-in-error and category is problem-list-item con-4: If condition is abated, then clinicalStatus must be either inactive, resolved, or remission con-5: Condition.clinicalStatus SHALL NOT be present if verification Status is entered-in-error | C | 0..* | Condition | Detailed information about conditions, problems or diagnoses con-2: If category is problems list item, the clinicalStatus should not be unknown con-3: If condition is abated, then clinicalStatus must be either inactive, resolved, or remission. | |||||||||
 id | Σ | 0..1 | id | Logical id of this artifact | Σ | 0..1 | id | Logical id of this artifact | |||||||||
| meta | Σ | 0..1 | Meta | Metadata about the resource | Σ | 0..1 | Meta | Metadata about the resource | |||||||||
| implicitRules | ?!Σ | 0..1 | uri | A set of rules under which this content was created | ?!Σ | 0..1 | uri | A set of rules under which this content was created | |||||||||
| language | 0..1 | code | Language of the resource content Binding: ?? (preferred): A human language.
| 0..1 | code | Language of the resource content Binding: ?? (required): IETF language tag for a human language
| |||||||||||
| text | 0..1 | Narrative | Text summary of the resource, for human interpretation | 0..1 | Narrative | Text summary of the resource, for human interpretation | |||||||||||
| contained | 0..* | Resource | Contained, inline Resources | 0..* | Resource | Contained, inline Resources | |||||||||||
 Slices for extension | 0..* | Extension | Extension Slice: Unordered, Open by value:url | 0..* | Extension | Extension Slice: Unordered, Open by value:url | |||||||||||
 modifierExtension | ?! | 0..* | Extension | Extensions that cannot be ignored | ?!Σ | 0..* | Extension | Extensions that cannot be ignored | |||||||||
| identifier | Σ | 0..* | Identifier | External Ids for this condition | Σ | 0..* | Identifier | External Ids for this condition | |||||||||
| clinicalStatus | ?!ΣC | 0..1 | CodeableConcept | active | recurrence | relapse | inactive | remission | resolved Binding: ?? (required): The clinical status of the condition or diagnosis. | ?!ΣC | 1..1 | CodeableConcept | active | recurrence | relapse | inactive | remission | resolved | unknown Binding: ?? (required): The clinical status of the condition or diagnosis. |
| ||||||||
| verificationStatus | ?!ΣC | 0..1 | CodeableConcept | unconfirmed | provisional | differential | confirmed | refuted | entered-in-error Binding: ?? (required): The verification status to support or decline the clinical status of the condition or diagnosis. | ?!Σ | 0..1 | CodeableConcept | unconfirmed | provisional | differential | confirmed | refuted | entered-in-error Binding: ?? (required): The verification status to support or decline the clinical status of the condition or diagnosis. | |||||||||
| category | 0..* | CodeableConcept | problem-list-item | encounter-diagnosis Binding: ?? (extensible): A category assigned to the condition. | C | 0..* | CodeableConcept | problem-list-item | encounter-diagnosis Binding: ?? (preferred): A category assigned to the condition. | ||||||||||
| severity | 0..1 | CodeableConcept | Subjective severity of condition Binding: ?? (preferred): A subjective assessment of the severity of the condition as evaluated by the clinician. | 0..1 | CodeableConcept | Subjective severity of condition Binding: ?? (preferred): A subjective assessment of the severity of the condition as evaluated by the clinician. | |||||||||||
 code | Σ | 0..1 | CodeableConcept | Identification of the condition, problem or diagnosis Binding: ?? (example): Identification of the condition or diagnosis. | Σ | 0..1 | CodeableConcept | Identification of the condition, problem or diagnosis Binding: ?? (example): Identification of the condition or diagnosis. | |||||||||
 id | 0..1 | string | Unique id for inter-element referencing | 0..1 | id | Unique id for inter-element referencing | |||||||||||
| Slices for extension | 0..* | Extension | Additional content defined by implementations Slice: Unordered, Open by value:url | 0..* | Extension | Additional content defined by implementations Slice: Unordered, Open by value:url | |||||||||||
| Slices for coding | Σ | 0..* | Coding | Condition code, [DA] tilstandskode Slice: Unordered, Open by value:system | Σ | 0..* | Coding | Condition code, [DA] tilstandskode Slice: Unordered, Open by value:system | |||||||||
| text | Σ | 0..1 | string | Plain text representation of the concept | Σ | 0..1 | string | Plain text representation of the concept | |||||||||
| bodySite | Σ | 0..* | CodeableConcept | Anatomical location, if relevant Binding: ?? (example): Codes describing anatomical locations. May include laterality. | Σ | 0..* | CodeableConcept | Anatomical location, if relevant Binding: ?? (example): SNOMED CT Body site concepts | |||||||||
| subject | Σ | 1..1 | Reference(Danish Core Patient Profile) | Who has the condition? | Σ | 1..1 | Reference(Danish Core Patient Profile) | Who has the condition? | |||||||||
| encounter | Σ | 0..1 | Reference(Encounter) | Encounter created as part of | Σ | 0..1 | Reference(Encounter) | The Encounter during which this Condition was created | |||||||||
| onset[x] | Σ | 0..1 | dateTime, Age, Period, Range, string | Estimated or actual date, date-time, or age | Σ | 0..1 | dateTime, Age, Period, Range, string | Estimated or actual date, date-time, or age | |||||||||
| abatement[x] | C | 0..1 | dateTime, Age, Period, Range, string | When in resolution/remission | C | 0..1 | dateTime, Age, Period, Range, string | When in resolution/remission | |||||||||
| recordedDate | Σ | 0..1 | dateTime | Date record was first recorded | Σ | 0..1 | dateTime | Date condition was first recorded | |||||||||
| recorder | Σ | 0..1 | Reference(Danish Core Practitioner Profile | PractitionerRole | Danish Core Patient Profile | Danish Core Related Person Profile) | Who recorded the condition |
| ||||||||||||
| asserter | Σ | 0..1 | Reference(Danish Core Practitioner Profile | PractitionerRole) | Person who asserts this condition |
| ||||||||||||
| stage | C | 0..* | BackboneElement | Stage/grade, usually assessed formally con-1: Stage SHALL have summary or assessment | C | 0..* | BackboneElement | Stage/grade, usually assessed formally con-1: Stage SHALL have summary or assessment | |||||||||
| id | 0..1 | string | Unique id for inter-element referencing | 0..1 | string | Unique id for inter-element referencing | |||||||||||
| extension | 0..* | Extension | Additional content defined by implementations | 0..* | Extension | Additional content defined by implementations | |||||||||||
| modifierExtension | ?!Σ | 0..* | Extension | Extensions that cannot be ignored even if unrecognized | ?!Σ | 0..* | Extension | Extensions that cannot be ignored even if unrecognized | |||||||||
| summary | C | 0..1 | CodeableConcept | Simple summary (disease specific) Binding: ?? (example): Codes describing condition stages (e.g. Cancer stages). | C | 0..1 | CodeableConcept | Simple summary (disease specific) Binding: ?? (example): Codes describing condition stages (e.g. Cancer stages). | |||||||||
| assessment | C | 0..* | Reference(ClinicalImpression | DiagnosticReport | Observation) | Formal record of assessment | C | 0..* | Reference(ClinicalImpression | DiagnosticReport | Observation) | Formal record of assessment | |||||||||
| type | 0..1 | CodeableConcept | Kind of staging Binding: ?? (example): Codes describing the kind of condition staging (e.g. clinical or pathological). | 0..1 | CodeableConcept | Kind of staging Binding: ?? (example): Codes describing the kind of condition staging (e.g. clinical or pathological). | |||||||||||
| evidence | C | 0..* | BackboneElement | Supporting evidence con-2: evidence SHALL have code or details | Σ | 0..* | CodeableReference(Resource) | Supporting evidence for the verification status Binding: ?? (example) | |||||||||
| id | 0..1 | string | Unique id for inter-element referencing |
| |||||||||||||
| extension | 0..* | Extension | Additional content defined by implementations |
| |||||||||||||
| modifierExtension | ?!Σ | 0..* | Extension | Extensions that cannot be ignored even if unrecognized |
| ||||||||||||
| code | ΣC | 0..* | CodeableConcept | Manifestation/symptom Binding: ?? (example): Codes that describe the manifestation or symptoms of a condition. |
| ||||||||||||
| detail | ΣC | 0..* | Reference(Resource) | Supporting information found elsewhere |
| ||||||||||||
| note | 0..* | Annotation | Additional information about the Condition | 0..* | Annotation | Additional information about the Condition | |||||||||||
| Slices for participant | Σ | 0..* | BackboneElement | Who or what participated in the activities related to the condition and how they were involved Slice: Unordered, Open by value:function.coding.code |
| ||||||||||||
| Documentation for this format | |||||||||||||||||