FHIR Extensions Pack
5.2.0-ballot - 5.2.0 Ballot - September 2024)
FHIR Extensions Pack
5.2.0-ballot - 5.2.0 Ballot - September 2024)
FHIR Extensions Pack, published by HL7 International / FHIR Infrastructure. This guide is not an authorized publication; it is the continuous build for version 5.2.0-ballot built by the FHIR (HL7® FHIR® Standard) CI Build. This version is based on the current content of https://github.com/HL7/fhir-extensions/ and changes regularly. See the Directory of published versions
| Page standards status: Trial-use | Maturity Level: 1 |
<CodeSystem xmlns="http://hl7.org/fhir">
<id value="obligation"/>
<text>
<status value="generated"/>
<div xmlns="http://www.w3.org/1999/xhtml"><p class="res-header-id"><b>Generated Narrative: CodeSystem obligation</b></p><a name="obligation"> </a><a name="hcobligation"> </a><a name="obligation-en-US"> </a><p><b>Properties</b></p><p><b>This code system defines the following properties for its concepts</b></p><table class="grid"><tr><td><b>Name</b></td><td><b>Code</b></td><td><b>URI</b></td><td><b>Type</b></td><td><b>Description</b></td></tr><tr><td>Not Selectable</td><td>not-selectable</td><td>http://hl7.org/fhir/concept-properties#notSelectable</td><td>boolean</td><td>Codes with this property set are not intended to appear in instances. They are for grouping/subsetting purposes only.</td></tr><tr><td>Parent</td><td>parent</td><td>http://hl7.org/fhir/concept-properties#parent</td><td>code</td><td/></tr><tr><td>qualifier</td><td>qualifier</td><td>http://hl7.org/fhir/CodeSystem/obligation#qualifier</td><td>code</td><td>Indicates the level of adherence expected to the obligation concept</td></tr><tr><td>converse</td><td>converse</td><td>http://hl7.org/fhir/CodeSystem/obligation#converse</td><td>code</td><td>Indicates another obligation code with an opposite meaning to this one. A single obligation cannot list two converse codes and an application cannot satisfy both a code and its coverse (though if the obligation strength for both is SHOULD or MAY, an application could conform with both obligations by adhering to one and not the other).</td></tr><tr><td>security-dependent</td><td>security-dependent</td><td>http://hl7.org/fhir/CodeSystem/obligation#security-dependent</td><td>boolean</td><td>Obligation codes with this property set to true may be overridden by policies and regulations related to privacy and security, including patient consent. Testing of such obligations will need to take such considerations into account.</td></tr></table><p><b>Concepts</b></p><p>This case-sensitive code system <code>http://hl7.org/fhir/CodeSystem/obligation</code> defines the following codes in a Is-A hierarchy:</p><table class="codes"><tr><td style="white-space:nowrap"><b>Code</b></td><td><b>Display</b></td><td><b>Definition</b></td><td><b>Not Selectable</b></td><td><b>Parent</b></td></tr><tr><td style="white-space:nowrap">SHALL<a name="obligation-SHALL"> </a></td><td>SHALL</td><td><div><p>The functional requirement is mandatory. Applications that do not implement this functional behavior are considered non-conformant.</p>
</div></td><td>true</td><td/></tr><tr><td style="white-space:nowrap">SHOULD<a name="obligation-SHOULD"> </a></td><td>SHOULD</td><td><div><p>The functional requirement is a recommendation. Applications are strongly encouraged to implement this functional behavior, but are still conformant if they do not.</p>
</div></td><td>true</td><td/></tr><tr><td style="white-space:nowrap">MAY<a name="obligation-MAY"> </a></td><td>MAY</td><td><div><p>The functional requirement is an option worthy of consideration but there is no expectation or recommendation associated with its use. NOTE: Elements not flagged with any obligation are intrinsically still 'MAY' (unless constraints dictate otherwise), but have not specifically been called out by the author as worthy of consideration.</p>
</div></td><td>true</td><td/></tr><tr><td style="white-space:nowrap">ResourceProducerObligations<a name="obligation-ResourceProducerObligations"> </a></td><td>ResourceProducerObligations</td><td><div><p>Resource producers are applications that assembles resources in the first place. Resource producers may be a server, client, sender, receiver or some middleware device, and they may store the resource, or merely hand it on.</p>
</div></td><td>true</td><td/></tr><tr><td style="white-space:nowrap">ResourceExchangerObligations<a name="obligation-ResourceExchangerObligations"> </a></td><td>ResourceExchangerObligations</td><td><div><p>Exchangers do not produce or consume resources; they only pass the resource on. They may store the resource in a persistent store between reception and subsequent transfer. The generic FHIR servers are exchangers, as are most middleware systems. Note that Exchanger obligations may also be taken on by Producers or Consumers if they act as intermediaries between other systems or between systems and users.</p>
</div></td><td>true</td><td/></tr><tr><td style="white-space:nowrap">ResourceConsumerObligations<a name="obligation-ResourceConsumerObligations"> </a></td><td>ResourceConsumerObligations</td><td><div><p>Resource Consumers are applications that consume resources and do something with them, either displaying them to humans, transferring them to some other format for further re-use, or using them to drive some kind of application logic process AKA decision support. Resource Consumers often store resources, but do not need to, and whether resources are stored or not between receiving them and using them doesn't make any difference to the obligations</p>
</div></td><td>true</td><td/></tr><tr><td style="white-space:nowrap">able-to-populate<a name="obligation-able-to-populate"> </a></td><td>be able to populate</td><td><div><p>Conformant applications producing resources SHALL/SHOULD/MAY be able to correctly populate this element.
Notes: Typically, this means that an application needs to demonstrate during some conformance testing process that there are some conditions under which it populates the element with a correct value. (i.e. not a data-absent-reason or equivalent.) This obligation does not impose expectations on the circumstances in which the element will be sent, only that it can be in at least some situations.</p>
</div></td><td>true</td><td><a href="#obligation-ResourceProducerObligations">ResourceProducerObligations</a></td></tr><tr><td style="white-space:nowrap">populate-if-known<a name="obligation-populate-if-known"> </a></td><td>populate if known</td><td><div><p>Conformant applications producing resources SHALL/SHOULD correctly populate this element if they know a value for the element, but it is acceptable if the system is unable to ever know a value for the element.
Notes: This obligation does not impose a requirement to be able to know a value, unlike populate and able-to-populate which do. 'Knowing' an element means that a value for the element is available in memory, persistent store, or is otherwise available within the system claiming conformance.</p>
</div></td><td>true</td><td><a href="#obligation-ResourceProducerObligations">ResourceProducerObligations</a></td></tr><tr><td style="white-space:nowrap">populate<a name="obligation-populate"> </a></td><td>populate</td><td><div><p>Conformant applications producing resources SHALL/SHOULD include this element if a value is known and allowed to be shared.
Notes: This implementation obligation means that whenever the producer knows the correct value for an element, it populates it. This is NOT the same as cardinality, as a 'populate' element can be omitted if no data exists or the data that exists is prohibited from being shared.</p>
</div></td><td>true</td><td><a href="#obligation-populate-if-known">populate-if-known</a>, <a href="#obligation-able-to-populate">able-to-populate</a></td></tr><tr><td style="white-space:nowrap">in-narrative<a name="obligation-in-narrative"> </a></td><td>include in narrative</td><td><div><p>Conformant applications SHALL/SHOULD/MAY ensure that this data element is represented in any human readable representation of a resource.
Notes: When no value for an element is known, the producer populates the narrative with the content of any nested <a href="http://hl7.org/fhir/R5/elementdefinition-definitions.html#ElementDefinition.valueAlternatives">ElementDefinition.valueAlternatives</a> extensions such as <a href="StructureDefinition-data-absent-reason.html">DataAbsentReason</a>. If no particular reason is known or reportable, the element can simply be indicated as 'unknown' in the narrative.</p>
</div></td><td>true</td><td><a href="#obligation-ResourceProducerObligations">ResourceProducerObligations</a></td></tr><tr><td style="white-space:nowrap">exclude-narrative<a name="obligation-exclude-narrative"> </a></td><td>exclude from narrative</td><td><div><p>Conformant applications SHALL/SHOULD ensure that this data element is NOT represented in any human readable representation of a resource.
Notes: This may be useful for profiles related to de-identified records</p>
</div></td><td>true</td><td><a href="#obligation-ResourceProducerObligations">ResourceProducerObligations</a></td></tr><tr><td style="white-space:nowrap">user-input<a name="obligation-user-input"> </a></td><td>allow user input</td><td><div><p>Conformant applications SHALL/SHOULD/MAY ensure that users can enter a value for this element during data input/capture.
Notes: Exactly what form the input takes is not specified, but the expectation is that this is a value that comes from the user, and not implied internally by the application.</p>
</div></td><td>true</td><td><a href="#obligation-ResourceProducerObligations">ResourceProducerObligations</a></td></tr><tr><td style="white-space:nowrap">explain<a name="obligation-explain"> </a></td><td>populate or document irrelevance</td><td><div><p>Documentation applicable to Conformant applications SHALL/SHOULD explain how this element is handled.
Notes: this is really a rule about specifications, implying that another specification (which might be application documentation) either makes this element <code>populate</code>, or explains how the use cases that involve this element do not arise, or how they are handled. An example: IPA marks Patient.active must-handle and must-explain. Client applications must process Patient.active correctly if they see it, but many (though <em>not all</em>) specifications and/or applications ensure that Patient.active will never be false, and so it will never be populated e.g. MedMij in Netherlands prohibits use of Patient.active, and explains that it is never false.</p>
</div></td><td>true</td><td><a href="#obligation-ResourceProducerObligations">ResourceProducerObligations</a></td></tr><tr><td style="white-space:nowrap">persist<a name="obligation-persist"> </a></td><td>persist</td><td><div><p>Conformant applications SHALL/SHOULD/MAY ensure that the value for this element is stored in a persistent data store.
Notes: Exactly what the data store is not specified, nor how long it is stored for, but it is understood that the same value will be available in later exchanges</p>
</div></td><td>true</td><td><a href="#obligation-ResourceConsumerObligations">ResourceConsumerObligations</a>, <a href="#obligation-ResourceProducerObligations">ResourceProducerObligations</a></td></tr><tr><td style="white-space:nowrap">no-alter<a name="obligation-no-alter"> </a></td><td>not alter</td><td><div><p>Conformant applications SHALL/SHOULD ensure that this element does not change between receiving and transfer.
Notes: This does not mean that the element value cannot change, only that changing the element value for an element marked with this obligation moves an application from being an exchanger to a Consumer and a Producer, and those obligations apply</p>
</div></td><td>true</td><td><a href="#obligation-ResourceExchangerObligations">ResourceExchangerObligations</a></td></tr><tr><td style="white-space:nowrap">no-error<a name="obligation-no-error"> </a></td><td>not error if present</td><td><div><p>Conformant applications SHALL/SHOULD accept resources containing any valid value for the element without error.
Notes: Applications are still able to inform the user that a value cannot be processed correctly and may ignore the data, but applications aren't able to reject an instance merely because the element is present (which would be allowed for elements that do not have this obligation). A system MAY raise an error if the value provided is not valid or violates specific business rules. This obligation also applies to elements that only contain an extension in place of a value where (or equivalent), should either of these be allowed on the consumer obligations</p>
</div></td><td>true</td><td><a href="#obligation-ResourceConsumerObligations">ResourceConsumerObligations</a></td></tr><tr><td style="white-space:nowrap">reject-invalid<a name="obligation-reject-invalid"> </a></td><td>reject invalid</td><td><div><p>Conformant applications SHALL/SHOULD check that values for this element meet all data constraints asserted within the profile declaring this obligation. If validity issues are found, the system SHALL/SHOULD not accept the instance.
Notes: This applies to validating the element with the obligation, but not resources referenced by it.</p>
</div></td><td>true</td><td><a href="#obligation-ResourceConsumerObligations">ResourceConsumerObligations</a></td></tr><tr><td style="white-space:nowrap">accept-invalid<a name="obligation-accept-invalid"> </a></td><td>accept invalid</td><td><div><p>Conformant applications SHALL/SHOULD accept data that does not meet all data constraints asserted within the profile declaring this obligation.
This applies to non-valid constraints, not to non-valid syntax or failure to meet base resource validity expectations. Typically used when a system needs to be able to handle data that does not adhere to desired expectations (legacy data, test data, data undergoing authorship that is not yet complete, etc.)</p>
</div></td><td>true</td><td><a href="#obligation-ResourceConsumerObligations">ResourceConsumerObligations</a></td></tr><tr><td style="white-space:nowrap">handle<a name="obligation-handle"> </a></td><td>correctly handle</td><td><div><p>Conformant applications SHALL/SHOULD handle the meaning of this element correctly.
Notes: this rule is vague in that doesn't specify any particular handling of the element. But it's important because an application that ignores this element is non-conformant. A good example would be a status code of 'entered-in-error' - how exactly a Resource Consumer handles this depends on the use case etc., but the application can never simply ignore such a status code. Note that whether the resource or information from it is stored for later use is irrelevant - when the resource or information in it is processed, the consequences of the element are considered. That may mean not retaining the information for later use, or informing the user, etc. Typically, this obligation marks that there are known patient safety issues that can arise if the element is ignored. Implementers should pay particular attention to the possible range of values for the element from a safety perspective.</p>
</div></td><td>true</td><td><a href="#obligation-ResourceConsumerObligations">ResourceConsumerObligations</a></td></tr><tr><td style="white-space:nowrap">display<a name="obligation-display"> </a></td><td>display</td><td><div><p>Conformant applications SHALL/SHOULD/MAY display the value of this element when presenting the data from the resource to a human user.
Notes: exactly how it is displayed is not specified, but it means that a human looking at the content of the resource is made aware of the value of the element so that they can consider the meaning of the resource</p>
</div></td><td>true</td><td><a href="#obligation-handle">handle</a></td></tr><tr><td style="white-space:nowrap">process<a name="obligation-process"> </a></td><td>process</td><td><div><p>Conformant applications SHALL/SHOULD/MAY consider the value of this element when processing the resource as specified by the IG.
Notes: this implies that the IG that specifies this obligation provides details about what processing is to be performed, and the obligation specifially relates to the processing specified in the IG of any <a href="http://hl7.org/fhir/R5/elementdefinition-definitions.html#ElementDefinition.valueAlternatives">ElementDefinition.valueAlternatives</a> extensions as well as the value (or other extensions explicitly declared beneath the element in the profile containing the obligation. Examples might include consideration in decision support, consideration in claims evaluation, etc.</p>
</div></td><td>true</td><td><a href="#obligation-handle">handle</a></td></tr><tr><td style="white-space:nowrap">print<a name="obligation-print"> </a></td><td>print</td><td><div><p>Conformant applications SHALL/SHOULD/MAY print the value of this element somewhere.
Notes: The form of the printing is not specified. A profile using this value SHALL explain the nature of the printing requirement somehow</p>
</div></td><td>true</td><td><a href="#obligation-handle">handle</a></td></tr><tr><td style="white-space:nowrap">ignore<a name="obligation-ignore"> </a></td><td>ignore</td><td><div><p>Conformant applications SHALL/SHOULD/MAY not make any use of the value of this element if received.</p>
</div></td><td>true</td><td><a href="#obligation-ResourceConsumerObligations">ResourceConsumerObligations</a></td></tr><tr><td style="white-space:nowrap">SHALL:able-to-populate<a name="obligation-SHALL.58able-to-populate"> </a></td><td>SHALL be able to populate</td><td><div><p>Conformant applications producing resources SHALL be able to correctly populate this element.
Notes: Typically, this means that an application needs to demonstrate during some conformance testing process that there are some conditions under which it populates the element with a correct value. (i.e. not a data-absent-reason or equivalent.) This obligation does not impose expectations on the circumstances in which the element will be sent, only that it can be in at least some situations.</p>
</div></td><td/><td><a href="#obligation-able-to-populate">able-to-populate</a></td></tr><tr><td style="white-space:nowrap">SHOULD:able-to-populate<a name="obligation-SHOULD.58able-to-populate"> </a></td><td>SHOULD be able to populate</td><td><div><p>Conformant applications producing resources SHOULD be able to correctly populate this element.
Notes: Typically, this means that an application needs to demonstrate during some conformance testing process that there are some conditions under which it populates the element with a correct value. (i.e. not a data-absent-reason or equivalent.) This obligation does not impose expectations on the circumstances in which the element will be sent, only that it shold be in at least some situations.</p>
</div></td><td/><td><a href="#obligation-able-to-populate">able-to-populate</a></td></tr><tr><td style="white-space:nowrap">MAY:able-to-populate<a name="obligation-MAY.58able-to-populate"> </a></td><td>MAY be able to populate</td><td><div><p>Conformant applications producing resources MAY be able to correctly populate this element.
Notes: Typically, this means that an application needs to demonstrate during some conformance testing process that there are some conditions under which it populates the element with a correct value. (i.e. not a data-absent-reason or equivalent.) This obligation does not impose expectations on the circumstances in which the element will be sent, only that it may be in at least some situations. This is a null statement and is the default behavior for originating systems if other obligations are not specified.</p>
</div></td><td/><td><a href="#obligation-able-to-populate">able-to-populate</a></td></tr><tr><td style="white-space:nowrap">SHALL:populate-if-known<a name="obligation-SHALL.58populate-if-known"> </a></td><td>SHALL populate if known</td><td><div><p>Conformant applications producing resources SHALL correctly populate this element if they know a value for the element, but it is acceptable if the system is unable to ever know a value for the element.
Notes: This obligation does not impose a requirement to be able to know a value, unlike populate and able-to-populate which do. 'Knowing' an element means that a value for the element is available in memory, persistent store, or is otherwise available within the system claiming conformance.</p>
</div></td><td/><td><a href="#obligation-populate-if-known">populate-if-known</a></td></tr><tr><td style="white-space:nowrap">SHOULD:populate-if-known<a name="obligation-SHOULD.58populate-if-known"> </a></td><td>SHOULD populate if known</td><td><div><p>Conformant applications producing resources SHOULD correctly populate this element if they know a value for the element, but it is acceptable if the system is unable to ever know a value for the element.
Notes: This obligation does not impose a requirement to be able to know a value, unlike populate and able-to-populate which do. 'Knowing' an element means that a value for the element is available in memory, persistent store, or is otherwise available within the system claiming conformance.</p>
</div></td><td/><td><a href="#obligation-populate-if-known">populate-if-known</a></td></tr><tr><td style="white-space:nowrap">SHALL:populate<a name="obligation-SHALL.58populate"> </a></td><td>SHALL populate</td><td><div><p>Conformant applications producing resources SHALL include this element if a value is known and allowed to be shared.
Notes: This implementation obligation means that whenever the producer knows the correct value for an element, it populates it. This is NOT the same as cardinality, as a 'populate' element can be omitted if no data exists or the data that exists is prohibited from being shared.</p>
</div></td><td/><td><a href="#obligation-SHALL.58able-to-populate">SHALL:able-to-populate</a>, <a href="#obligation-populate">populate</a></td></tr><tr><td style="white-space:nowrap">SHOULD:populate<a name="obligation-SHOULD.58populate"> </a></td><td>SHOULD populate</td><td><div><p>Conformant applications producing resources SHOULD include this element if a value is known and allowed to be shared.
Notes: This implementation obligation means that whenever the producer knows the correct value for an element, it should populate it. This is NOT the same as cardinality, as a 'populate' element can be omitted if no data exists or the data that exists is prohibited from being shared.</p>
</div></td><td/><td><a href="#obligation-SHOULD.58able-to-populate">SHOULD:able-to-populate</a>, <a href="#obligation-populate">populate</a></td></tr><tr><td style="white-space:nowrap">SHALL:in-narrative<a name="obligation-SHALL.58in-narrative"> </a></td><td>SHALL include in narrative</td><td><div><p>Conformant applications SHALL ensure that this data element is represented in any human readable representation of a resource.
Notes: When no value for an element is known, the producer populates the narrative with the content of any nested <a href="http://hl7.org/fhir/R5/elementdefinition-definitions.html#ElementDefinition.valueAlternatives">ElementDefinition.valueAlternatives</a> extensions such as <a href="StructureDefinition-data-absent-reason.html">DataAbsentReason</a>. If no particular reason is known or reportable, the element can simply be indicated as 'unknown' in the narrative.</p>
</div></td><td/><td><a href="#obligation-in-narrative">in-narrative</a></td></tr><tr><td style="white-space:nowrap">SHOULD:in-narrative<a name="obligation-SHOULD.58in-narrative"> </a></td><td>SHOULD include in narrative</td><td><div><p>Conformant applications SHOULD ensure that this data element is represented in any human readable representation of a resource.
Notes: When no value for an element is known, the producer populates the narrative with the content of any nested <a href="http://hl7.org/fhir/R5/elementdefinition-definitions.html#ElementDefinition.valueAlternatives">ElementDefinition.valueAlternatives</a> extensions such as <a href="StructureDefinition-data-absent-reason.html">DataAbsentReason</a>. If no particular reason is known or reportable, the element can simply be indicated as 'unknown' in the narrative.</p>
</div></td><td/><td><a href="#obligation-in-narrative">in-narrative</a></td></tr><tr><td style="white-space:nowrap">MAY:in-narrative<a name="obligation-MAY.58in-narrative"> </a></td><td>MAY include in narrative</td><td><div><p>Conformant applications MAY ensure that this data element is represented in any human readable representation of a resource.
Notes: When no value for an element is known, the producer populates the narrative with the content of any nested <a href="http://hl7.org/fhir/R5/elementdefinition-definitions.html#ElementDefinition.valueAlternatives">ElementDefinition.valueAlternatives</a> extensions such as <a href="StructureDefinition-data-absent-reason.html">DataAbsentReason</a>. If no particular reason is known or reportable, the element can simply be indicated as 'unknown' in the narrative.</p>
</div></td><td/><td><a href="#obligation-in-narrative">in-narrative</a></td></tr><tr><td style="white-space:nowrap">SHALL:exclude-narrative<a name="obligation-SHALL.58exclude-narrative"> </a></td><td>SHALL exclude from narrative</td><td><div><p>Conformant applications SHALL ensure that this data element is NOT represented in any human readable representation of a resource.
Notes: This may be useful for profiles related to de-identified records</p>
</div></td><td/><td><a href="#obligation-exclude-narrative">exclude-narrative</a></td></tr><tr><td style="white-space:nowrap">SHOULD:exclude-narrative<a name="obligation-SHOULD.58exclude-narrative"> </a></td><td>SHOULD exclude from narrative</td><td><div><p>Conformant applications SHOULD ensure that this data element is NOT represented in any human readable representation of a resource.
Notes: This may be useful for profiles related to de-identified records</p>
</div></td><td/><td><a href="#obligation-exclude-narrative">exclude-narrative</a></td></tr><tr><td style="white-space:nowrap">SHALL:user-input<a name="obligation-SHALL.58user-input"> </a></td><td>SHALL allow user input</td><td><div><p>Conformant applications SHALL ensure that users can enter a value for this element during data input/capture.
Notes: Exactly what form the input takes is not specified, but the expectation is that this is a value that comes from the user, and not implied internally by the application.</p>
</div></td><td/><td><a href="#obligation-user-input">user-input</a></td></tr><tr><td style="white-space:nowrap">SHOULD:user-input<a name="obligation-SHOULD.58user-input"> </a></td><td>SHOULD allow user input</td><td><div><p>Conformant applications SHOULD ensure that users can enter a value for this element during data input/capture.
Notes: Exactly what form the input takes is not specified, but the expectation is that this is a value that comes from the user, and not implied internally by the application.</p>
</div></td><td/><td><a href="#obligation-user-input">user-input</a></td></tr><tr><td style="white-space:nowrap">MAY:user-input<a name="obligation-MAY.58user-input"> </a></td><td>MAY allow user input</td><td><div><p>Conformant applications MAY ensure that users can enter a value for this element during data input/capture.
Notes: Exactly what form the input takes is not specified, but the expectation is that this is a value that comes from the user, and not implied internally by the application.</p>
</div></td><td/><td><a href="#obligation-user-input">user-input</a></td></tr><tr><td style="white-space:nowrap">SHALL:explain<a name="obligation-SHALL.58explain"> </a></td><td>SHALL populate or document irrelevance</td><td><div><p>Documentation applicable to Conformant applications SHALL explain how this element is handled.
Notes: this is really a rule about specifications, implying that another specification (which might be application documentation) either makes this element <code>populate</code>, or explains how the use cases that involve this element do not arise, or how they are handled. An example: IPA marks Patient.active must-handle and must-explain. Client applications must process Patient.active correctly if they see it, but many (though <em>not all</em>) specifications and/or applications ensure that Patient.active will never be false, and so it will never be populated e.g. MedMij in Netherlands prohibits use of Patient.active, and explains that it is never false.</p>
</div></td><td/><td><a href="#obligation-explain">explain</a></td></tr><tr><td style="white-space:nowrap">SHOULD:explain<a name="obligation-SHOULD.58explain"> </a></td><td>SHOULD populate or document irrelevance</td><td><div><p>Documentation applicable to Conformant applications SHOULD explain how this element is handled.
Notes: this is really a rule about specifications, implying that another specification (which might be application documentation) either makes this element <code>populate</code>, or explains how the use cases that involve this element do not arise, or how they are handled. An example: IPA marks Patient.active must-handle and must-explain. Client applications must process Patient.active correctly if they see it, but many (though <em>not all</em>) specifications and/or applications ensure that Patient.active will never be false, and so it will never be populated e.g. MedMij in Netherlands prohibits use of Patient.active, and explains that it is never false.</p>
</div></td><td/><td><a href="#obligation-explain">explain</a></td></tr><tr><td style="white-space:nowrap">SHALL:persist<a name="obligation-SHALL.58persist"> </a></td><td>SHALL persist</td><td><div><p>Conformant applications SHALL ensure that the value for this element is stored in a persistent data store.
Notes: Exactly what the data store is not specified, nor how long it is stored for, but it is understood that the same value will be available in later exchanges</p>
</div></td><td/><td><a href="#obligation-persist">persist</a></td></tr><tr><td style="white-space:nowrap">SHOULD:persist<a name="obligation-SHOULD.58persist"> </a></td><td>SHOULD persist</td><td><div><p>Conformant applications SHOULD ensure that the value for this element is stored in a persistent data store.
Notes: Exactly what the data store is not specified, nor how long it is stored for, but it is understood that the same value will be available in later exchanges</p>
</div></td><td/><td><a href="#obligation-persist">persist</a></td></tr><tr><td style="white-space:nowrap">MAY:persist<a name="obligation-MAY.58persist"> </a></td><td>MAY persist</td><td><div><p>Conformant applications MAY ensure that the value for this element is stored in a persistent data store.
Notes: Exactly what the data store is not specified, nor how long it is stored for, but it is understood that the same value will be available in later exchanges</p>
</div></td><td/><td><a href="#obligation-persist">persist</a></td></tr><tr><td style="white-space:nowrap">SHALL:no-alter<a name="obligation-SHALL.58no-alter"> </a></td><td>SHALL not alter</td><td><div><p>Conformant applications SHALL ensure that this element does not change between receiving and transfer.
Notes: This does not mean that the element value cannot change, only that changing the element value for an element marked with this obligation moves an application from being an exchanger to a Consumer and a Producer, and those obligations apply</p>
</div></td><td/><td><a href="#obligation-no-alter">no-alter</a></td></tr><tr><td style="white-space:nowrap">SHOULD:no-alter<a name="obligation-SHOULD.58no-alter"> </a></td><td>SHOULD not alter</td><td><div><p>Conformant applications SHOULD ensure that this element does not change between receiving and transfer.
Notes: This does not mean that the element value cannot change, only that changing the element value for an element marked with this obligation moves an application from being an exchanger to a Consumer and a Producer, and those obligations apply</p>
</div></td><td/><td><a href="#obligation-no-alter">no-alter</a></td></tr><tr><td style="white-space:nowrap">MAY:alter<a name="obligation-MAY.58alter"> </a></td><td>MAY alter</td><td><div><p>Conformant applications MAY choose to alter this element value.
Notes: this is really a null-statement - it's the default rule for an application. It's defined here to allow a specification to be explicit that it isn't conveying obligations for resource producers</p>
</div></td><td/><td><a href="#obligation-ResourceExchangerObligations">ResourceExchangerObligations</a></td></tr><tr><td style="white-space:nowrap">SHALL:no-error<a name="obligation-SHALL.58no-error"> </a></td><td>SHALL not error if present</td><td><div><p>Conformant applications SHALL accept resources containing any valid value for the element without error.
Notes: Applications are still able to inform the user that a value cannot be processed correctly and may ignore the data, but applications aren't able to reject an instance merely because the element is present (which would be allowed for elements that do not have this obligation). A system MAY raise an error if the value provided is not valid or violates specific business rules. This obligation also applies to elements that only contain an extension in place of a value where (or equivalent), should either of these be allowed on the consumer obligations</p>
</div></td><td/><td><a href="#obligation-no-error">no-error</a></td></tr><tr><td style="white-space:nowrap">SHOULD:no-error<a name="obligation-SHOULD.58no-error"> </a></td><td>SHOULD not error if present</td><td><div><p>Conformant applications SHOULD accept resources containing any valid value for the element without error.
Notes: Applications are still able to inform the user that a value cannot be processed correctly and may ignore the data, but applications aren't able to reject an instance merely because the element is present (which would be allowed for elements that do not have this obligation). A system MAY raise an error if the value provided is not valid or violates specific business rules. This obligation also applies to elements that only contain an extension in place of a value where (or equivalent), should either of these be allowed on the consumer obligations</p>
</div></td><td/><td><a href="#obligation-no-error">no-error</a></td></tr><tr><td style="white-space:nowrap">SHALL:reject-invalid<a name="obligation-SHALL.58reject-invalid"> </a></td><td>SHALL reject invalid</td><td><div><p>Conformant applications SHALL check that values for this element meet all data constraints asserted within the profile declaring this obligation. If validity issues are found, the system SHALL not accept the instance.
Notes: This applies to validating the element with the obligation, but not resources referenced by it.</p>
</div></td><td/><td><a href="#obligation-reject-invalid">reject-invalid</a></td></tr><tr><td style="white-space:nowrap">SHOULD:reject-invalid<a name="obligation-SHOULD.58reject-invalid"> </a></td><td>SHOULD reject invalid</td><td><div><p>Conformant applications SHOULD check that values for this element meet all data constraints asserted within the profile declaring this obligation. If validity issues are found, the system SHOULD not accept the instance.
Notes: This applies to validating the element with the obligation, but not resources referenced by it.</p>
</div></td><td/><td><a href="#obligation-reject-invalid">reject-invalid</a></td></tr><tr><td style="white-space:nowrap">SHALL:accept-invalid<a name="obligation-SHALL.58accept-invalid"> </a></td><td>SHALL accept invalid</td><td><div><p>Conformant applications SHALL accept data that does not meet all data constraints asserted within the profile declaring this obligation.
This applies to non-valid constraints, not to non-valid syntax or failure to meet base resource validity expectations. Typically used when a system needs to be able to handle data that does not adhere to desired expectations (legacy data, test data, data undergoing authorship that is not yet complete, etc.)</p>
</div></td><td/><td><a href="#obligation-accept-invalid">accept-invalid</a></td></tr><tr><td style="white-space:nowrap">SHOULD:accept-invalid<a name="obligation-SHOULD.58accept-invalid"> </a></td><td>SHOULD accept invalid</td><td><div><p>Conformant applications SHOULD accept data that does not meet all data constraints asserted within the profile declaring this obligation.
This applies to non-valid constraints, not to non-valid syntax or failure to meet base resource validity expectations. Typically used when a system ought to be able to handle data that does not adhere to desired expectations (legacy data, test data, data undergoing authorship that is not yet complete, etc.)</p>
</div></td><td/><td><a href="#obligation-accept-invalid">accept-invalid</a></td></tr><tr><td style="white-space:nowrap">SHALL:handle<a name="obligation-SHALL.58handle"> </a></td><td>SHALL correctly handle</td><td><div><p>Conformant applications SHALL handle the meaning of this element correctly.
Notes: this rule is vague in that doesn't specify any particular handling of the element. But it's important because an application that ignores this element is non-conformant. A good example would be a status code of 'entered-in-error' - how exactly a Resource Consumer handles this depends on the use case etc., but the application can never simply ignore such a status code. Note that whether the resource or information from it is stored for later use is irrelevant - when the resource or information in it is processed, the consequences of the element are considered. That may mean not retaining the information for later use, or informing the user, etc. Typically, this obligation marks that there are known patient safety issues that can arise if the element is ignored. Implementers should pay particular attention to the possible range of values for the element from a safety perspective.</p>
</div></td><td/><td><a href="#obligation-handle">handle</a></td></tr><tr><td style="white-space:nowrap">SHOULD:handle<a name="obligation-SHOULD.58handle"> </a></td><td>SHOULD correctly handle</td><td><div><p>Conformant applications SHOULD handle the meaning of this element correctly.
Notes: this rule is vague in that doesn't specify any particular handling of the element. But it's important because an application that ignores this element is non-conformant. A good example would be a status code of 'entered-in-error' - how exactly a Resource Consumer handles this depends on the use case etc., but the application can never simply ignore such a status code. Note that whether the resource or information from it is stored for later use is irrelevant - when the resource or information in it is processed, the consequences of the element are considered. That may mean not retaining the information for later use, or informing the user, etc. Typically, this obligation marks that there are known patient safety issues that can arise if the element is ignored. Implementers should pay particular attention to the possible range of values for the element from a safety perspective.</p>
</div></td><td/><td><a href="#obligation-handle">handle</a></td></tr><tr><td style="white-space:nowrap">SHALL:display<a name="obligation-SHALL.58display"> </a></td><td>SHALL display</td><td><div><p>Conformant applications SHALL display the value of this element when presenting the data from the resource to a human user.
Notes: exactly how it is displayed is not specified, but it means that a human looking at the content of the resource is made aware of the value of the element so that they can consider the meaning of the resource</p>
</div></td><td/><td><a href="#obligation-SHALL.58handle">SHALL:handle</a>, <a href="#obligation-display">display</a></td></tr><tr><td style="white-space:nowrap">SHOULD:display<a name="obligation-SHOULD.58display"> </a></td><td>SHOULD display</td><td><div><p>Conformant applications SHOULD display the value of this element when presenting the data from the resource to a human user.
Notes: exactly how it is displayed is not specified, but it means that a human looking at the content of the resource is made aware of the value of the element so that they can consider the meaning of the resource</p>
</div></td><td/><td><a href="#obligation-SHOULD.58handle">SHOULD:handle</a>, <a href="#obligation-display">display</a></td></tr><tr><td style="white-space:nowrap">MAY:display<a name="obligation-MAY.58display"> </a></td><td>MAY display</td><td><div><p>Conformant applications MAY display the value of this element when presenting the data from the resource to a human user.
Notes: exactly how it is displayed is not specified, but it means that a human looking at the content of the resource is made aware of the value of the element so that they can consider the meaning of the resource</p>
</div></td><td/><td><a href="#obligation-display">display</a></td></tr><tr><td style="white-space:nowrap">SHALL:process<a name="obligation-SHALL.58process"> </a></td><td>SHALL process</td><td><div><p>Conformant applications SHALL consider the value of this element when processing the resource as specified by the IG.
Notes: this implies that the IG that specifies this obligation provides details about what processing is to be performed, and the obligation specifially relates to the processing specified in the IG of any <a href="http://hl7.org/fhir/R5/elementdefinition-definitions.html#ElementDefinition.valueAlternatives">ElementDefinition.valueAlternatives</a> extensions as well as the value (or other extensions explicitly declared beneath the element in the profile containing the obligation. Examples might include consideration in decision support, consideration in claims evaluation, etc.</p>
</div></td><td/><td><a href="#obligation-SHALL.58handle">SHALL:handle</a>, <a href="#obligation-process">process</a></td></tr><tr><td style="white-space:nowrap">SHOULD:process<a name="obligation-SHOULD.58process"> </a></td><td>SHOULD process</td><td><div><p>Conformant applications SHOULD consider the value of this element when processing the resource as specified by the IG.
Notes: this implies that the IG that specifies this obligation provides details about what processing is to be performed, and the obligation specifially relates to the processing specified in the IG of any <a href="http://hl7.org/fhir/R5/elementdefinition-definitions.html#ElementDefinition.valueAlternatives">ElementDefinition.valueAlternatives</a> extensions as well as the value (or other extensions explicitly declared beneath the element in the profile containing the obligation. Examples might include consideration in decision support, consideration in claims evaluation, etc.</p>
</div></td><td/><td><a href="#obligation-SHOULD.58handle">SHOULD:handle</a>, <a href="#obligation-process">process</a></td></tr><tr><td style="white-space:nowrap">MAY:process<a name="obligation-MAY.58process"> </a></td><td>MAY process</td><td><div><p>Conformant applications MAY consider the value of this element when processing the resource as specified by the IG.
Notes: this implies that the IG that specifies this obligation provides details about what processing is to be performed, and the obligation specifially relates to the processing specified in the IG of any <a href="http://hl7.org/fhir/R5/elementdefinition-definitions.html#ElementDefinition.valueAlternatives">ElementDefinition.valueAlternatives</a> extensions as well as the value (or other extensions explicitly declared beneath the element in the profile containing the obligation. Examples might include consideration in decision support, consideration in claims evaluation, etc.</p>
</div></td><td/><td><a href="#obligation-process">process</a></td></tr><tr><td style="white-space:nowrap">SHALL:print<a name="obligation-SHALL.58print"> </a></td><td>SHALL print</td><td><div><p>Conformant applications SHALL print the value of this element somewhere.
Notes: The form of the printing is not specified. A profile using this value SHALL explain the nature of the printing requirement somehow</p>
</div></td><td/><td><a href="#obligation-SHALL.58handle">SHALL:handle</a>, <a href="#obligation-print">print</a></td></tr><tr><td style="white-space:nowrap">SHOULD:print<a name="obligation-SHOULD.58print"> </a></td><td>SHOULD print</td><td><div><p>Conformant applications SHOULD print the value of this element somewhere.
Notes: The form of the printing is not specified. A profile using this value SHALL explain the nature of the printing requirement somehow</p>
</div></td><td/><td><a href="#obligation-SHOULD.58handle">SHOULD:handle</a>, <a href="#obligation-print">print</a></td></tr><tr><td style="white-space:nowrap">MAY:print<a name="obligation-MAY.58print"> </a></td><td>MAY print</td><td><div><p>Conformant applications MAY print the value of this element somewhere.
Notes: The form of the printing is not specified. A profile using this value SHALL explain the nature of the printing requirement somehow</p>
</div></td><td/><td><a href="#obligation-print">print</a></td></tr><tr><td style="white-space:nowrap">SHALL:ignore<a name="obligation-SHALL.58ignore"> </a></td><td>SHALL ignore</td><td><div><p>Conformant applications SHALL not make any use of the value of this element if received.</p>
</div></td><td/><td><a href="#obligation-ignore">ignore</a></td></tr><tr><td style="white-space:nowrap">SHOULD:ignore<a name="obligation-SHOULD.58ignore"> </a></td><td>SHOULD ignore</td><td><div><p>Conformant applications SHOULD not make any use of the value of this element if received.</p>
</div></td><td/><td><a href="#obligation-ignore">ignore</a></td></tr><tr><td style="white-space:nowrap">MAY:ignore<a name="obligation-MAY.58ignore"> </a></td><td>MAY ignore</td><td><div><p>Conformant applications MAY not make any use of the value of this element if received. This is a null statement and is the default behavior or consuming systems if other obligations are not specified.</p>
</div></td><td/><td><a href="#obligation-ignore">ignore</a></td></tr><tr><td style="white-space:nowrap">v2-re<a name="obligation-v2-re"> </a></td><td>V2 RE (required but may be empty)</td><td><div><p>RE as defined in chapter 2 of the v2 specification</p>
</div></td><td/><td><a href="#obligation-SHALL.58able-to-populate">SHALL:able-to-populate</a>, <a href="#obligation-SHALL.58display">SHALL:display</a>, <a href="#obligation-SHOULD.58persist">SHOULD:persist</a>, <a href="#obligation-SHOULD.58populate">SHOULD:populate</a>, <a href="#obligation-SHALL.58no-error">SHALL:no-error</a></td></tr><tr><td style="white-space:nowrap">ihe-r2<a name="obligation-ihe-r2"> </a></td><td>IHE R2</td><td><div><p>R2 as defined in IHE Appendix Z</p>
</div></td><td/><td><a href="#obligation-SHALL.58populate">SHALL:populate</a>, <a href="#obligation-MAY.58ignore">MAY:ignore</a>, <a href="#obligation-SHALL.58no-error">SHALL:no-error</a></td></tr><tr><td style="white-space:nowrap">std<a name="obligation-std"> </a></td><td>Standard obligations</td><td><div><p>The standard recommended set of obligations for IGs to use unless they know they want something different. Note that the standard codes don't include use-dar, use-dar-nf, use-dar-if-allowed / use-reason - that gets put on specific elements that justify this handling</p>
</div></td><td/><td><a href="#obligation-SHALL.58populate">SHALL:populate</a>, <a href="#obligation-SHALL.58display">SHALL:display</a>, <a href="#obligation-SHALL.58no-error">SHALL:no-error</a></td></tr></table></div>
</text>
<extension
url="http://hl7.org/fhir/StructureDefinition/structuredefinition-standards-status">
<valueCode value="trial-use"/>
</extension>
<extension
url="http://hl7.org/fhir/StructureDefinition/structuredefinition-wg">
<valueCode value="fhir"/>
</extension>
<extension
url="http://hl7.org/fhir/StructureDefinition/structuredefinition-fmm">
<valueInteger value="1">
<extension
url="http://hl7.org/fhir/StructureDefinition/structuredefinition-conformance-derivedFrom">
<valueCanonical
value="http://hl7.org/fhir/extensions/ImplementationGuide/hl7.fhir.uv.extensions"/>
</extension>
</valueInteger>
</extension>
<url value="http://hl7.org/fhir/CodeSystem/obligation"/>
<identifier>
<system value="urn:ietf:rfc:3986"/>
<value value="urn:oid:2.16.840.1.113883.4.642.4.2123"/>
</identifier>
<version value="5.2.0-ballot"/>
<name value="ObligationCodes"/>
<title value="Obligation Codes"/>
<status value="active"/>
<experimental value="false"/>
<date value="2024-10-09T18:10:55+00:00"/>
<publisher value="HL7 International / FHIR Infrastructure"/>
<contact>
<telecom>
<system value="url"/>
<value value="http://www.hl7.org/Special/committees/fiwg"/>
</telecom>
</contact>
<description
value="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."/>
<jurisdiction>
<coding>
<system value="http://unstats.un.org/unsd/methods/m49/m49.htm"/>
<code value="001"/>
</coding>
</jurisdiction>
<caseSensitive value="true"/>
<hierarchyMeaning value="is-a"/>
<compositional value="true"/>
<content value="complete"/>
<property>
<code value="not-selectable"/>
<uri value="http://hl7.org/fhir/concept-properties#notSelectable"/>
<description
value="Codes with this property set are not intended to appear in instances. They are for grouping/subsetting purposes only."/>
<type value="boolean"/>
</property>
<property>
<code value="parent"/>
<uri value="http://hl7.org/fhir/concept-properties#parent"/>
<type value="code"/>
</property>
<property>
<code value="qualifier"/>
<uri value="http://hl7.org/fhir/CodeSystem/obligation#qualifier"/>
<description
value="Indicates the level of adherence expected to the obligation concept"/>
<type value="code"/>
</property>
<property>
<code value="converse"/>
<uri value="http://hl7.org/fhir/CodeSystem/obligation#converse"/>
<description
value="Indicates another obligation code with an opposite meaning to this one. A single obligation cannot list two converse codes and an application cannot satisfy both a code and its coverse (though if the obligation strength for both is SHOULD or MAY, an application could conform with both obligations by adhering to one and not the other)."/>
<type value="code"/>
</property>
<property>
<code value="security-dependent"/>
<uri
value="http://hl7.org/fhir/CodeSystem/obligation#security-dependent"/>
<description
value="Obligation codes with this property set to true may be overridden by policies and regulations related to privacy and security, including patient consent. Testing of such obligations will need to take such considerations into account."/>
<type value="boolean"/>
</property>
<concept>
<code value="SHALL"/>
<display value="SHALL"/>
<definition
value="The functional requirement is mandatory. Applications that do not implement this functional behavior are considered non-conformant."/>
<property>
<code value="not-selectable"/>
<valueBoolean value="true"/>
</property>
</concept>
<concept>
<code value="SHOULD"/>
<display value="SHOULD"/>
<definition
value="The functional requirement is a recommendation. Applications are strongly encouraged to implement this functional behavior, but are still conformant if they do not."/>
<property>
<code value="not-selectable"/>
<valueBoolean value="true"/>
</property>
</concept>
<concept>
<code value="MAY"/>
<display value="MAY"/>
<definition
value="The functional requirement is an option worthy of consideration but there is no expectation or recommendation associated with its use. NOTE: Elements not flagged with any obligation are intrinsically still 'MAY' (unless constraints dictate otherwise), but have not specifically been called out by the author as worthy of consideration."/>
<property>
<code value="not-selectable"/>
<valueBoolean value="true"/>
</property>
</concept>
<concept>
<code value="ResourceProducerObligations"/>
<display value="ResourceProducerObligations"/>
<definition
value="Resource producers are applications that assembles resources in the first place. Resource producers may be a server, client, sender, receiver or some middleware device, and they may store the resource, or merely hand it on."/>
<property>
<code value="not-selectable"/>
<valueBoolean value="true"/>
</property>
</concept>
<concept>
<code value="ResourceExchangerObligations"/>
<display value="ResourceExchangerObligations"/>
<definition
value="Exchangers do not produce or consume resources; they only pass the resource on. They may store the resource in a persistent store between reception and subsequent transfer. The generic FHIR servers are exchangers, as are most middleware systems. Note that Exchanger obligations may also be taken on by Producers or Consumers if they act as intermediaries between other systems or between systems and users."/>
<property>
<code value="not-selectable"/>
<valueBoolean value="true"/>
</property>
</concept>
<concept>
<code value="ResourceConsumerObligations"/>
<display value="ResourceConsumerObligations"/>
<definition
value="Resource Consumers are applications that consume resources and do something with them, either displaying them to humans, transferring them to some other format for further re-use, or using them to drive some kind of application logic process AKA decision support. Resource Consumers often store resources, but do not need to, and whether resources are stored or not between receiving them and using them doesn't make any difference to the obligations"/>
<property>
<code value="not-selectable"/>
<valueBoolean value="true"/>
</property>
</concept>
<concept>
<code value="able-to-populate"/>
<display value="be able to populate"/>
<definition
value="Conformant applications producing resources SHALL/SHOULD/MAY be able to correctly populate this element.
Notes: Typically, this means that an application needs to demonstrate during some conformance testing process that there are some conditions under which it populates the element with a correct value. (i.e. not a data-absent-reason or equivalent.) This obligation does not impose expectations on the circumstances in which the element will be sent, only that it can be in at least some situations."/>
<property>
<code value="not-selectable"/>
<valueBoolean value="true"/>
</property>
<property>
<code value="parent"/>
<valueCode value="ResourceProducerObligations"/>
</property>
</concept>
<concept>
<code value="populate-if-known"/>
<display value="populate if known"/>
<definition
value="Conformant applications producing resources SHALL/SHOULD correctly populate this element if they know a value for the element, but it is acceptable if the system is unable to ever know a value for the element.
Notes: This obligation does not impose a requirement to be able to know a value, unlike populate and able-to-populate which do. 'Knowing' an element means that a value for the element is available in memory, persistent store, or is otherwise available within the system claiming conformance."/>
<property>
<code value="not-selectable"/>
<valueBoolean value="true"/>
</property>
<property>
<code value="parent"/>
<valueCode value="ResourceProducerObligations"/>
</property>
<property>
<code value="security-dependent"/>
<valueBoolean value="true"/>
</property>
</concept>
<concept>
<code value="populate"/>
<display value="populate"/>
<definition
value="Conformant applications producing resources SHALL/SHOULD include this element if a value is known and allowed to be shared.
Notes: This implementation obligation means that whenever the producer knows the correct value for an element, it populates it. This is NOT the same as cardinality, as a 'populate' element can be omitted if no data exists or the data that exists is prohibited from being shared."/>
<property>
<code value="not-selectable"/>
<valueBoolean value="true"/>
</property>
<property>
<code value="parent"/>
<valueCode value="populate-if-known"/>
</property>
<property>
<code value="parent"/>
<valueCode value="able-to-populate"/>
</property>
<property>
<code value="security-dependent"/>
<valueBoolean value="true"/>
</property>
</concept>
<concept>
<code value="in-narrative"/>
<display value="include in narrative"/>
<definition
value="Conformant applications SHALL/SHOULD/MAY ensure that this data element is represented in any human readable representation of a resource.
Notes: When no value for an element is known, the producer populates the narrative with the content of any nested [ElementDefinition.valueAlternatives](http://hl7.org/fhir/R5/elementdefinition-definitions.html#ElementDefinition.valueAlternatives) extensions such as [DataAbsentReason](StructureDefinition-data-absent-reason.html). If no particular reason is known or reportable, the element can simply be indicated as 'unknown' in the narrative."/>
<property>
<code value="not-selectable"/>
<valueBoolean value="true"/>
</property>
<property>
<code value="parent"/>
<valueCode value="ResourceProducerObligations"/>
</property>
<property>
<code value="security-dependent"/>
<valueBoolean value="true"/>
</property>
</concept>
<concept>
<code value="exclude-narrative"/>
<display value="exclude from narrative"/>
<definition
value="Conformant applications SHALL/SHOULD ensure that this data element is NOT represented in any human readable representation of a resource.
Notes: This may be useful for profiles related to de-identified records"/>
<property>
<code value="not-selectable"/>
<valueBoolean value="true"/>
</property>
<property>
<code value="parent"/>
<valueCode value="ResourceProducerObligations"/>
</property>
</concept>
<concept>
<code value="user-input"/>
<display value="allow user input"/>
<definition
value="Conformant applications SHALL/SHOULD/MAY ensure that users can enter a value for this element during data input/capture.
Notes: Exactly what form the input takes is not specified, but the expectation is that this is a value that comes from the user, and not implied internally by the application."/>
<property>
<code value="not-selectable"/>
<valueBoolean value="true"/>
</property>
<property>
<code value="parent"/>
<valueCode value="ResourceProducerObligations"/>
</property>
</concept>
<concept>
<code value="explain"/>
<display value="populate or document irrelevance"/>
<definition
value="Documentation applicable to Conformant applications SHALL/SHOULD explain how this element is handled.
Notes: this is really a rule about specifications, implying that another specification (which might be application documentation) either makes this element `populate`, or explains how the use cases that involve this element do not arise, or how they are handled. An example: IPA marks Patient.active must-handle and must-explain. Client applications must process Patient.active correctly if they see it, but many (though *not all*) specifications and/or applications ensure that Patient.active will never be false, and so it will never be populated e.g. MedMij in Netherlands prohibits use of Patient.active, and explains that it is never false."/>
<property>
<code value="not-selectable"/>
<valueBoolean value="true"/>
</property>
<property>
<code value="parent"/>
<valueCode value="ResourceProducerObligations"/>
</property>
</concept>
<concept>
<code value="persist"/>
<display value="persist"/>
<definition
value="Conformant applications SHALL/SHOULD/MAY ensure that the value for this element is stored in a persistent data store.
Notes: Exactly what the data store is not specified, nor how long it is stored for, but it is understood that the same value will be available in later exchanges"/>
<property>
<code value="not-selectable"/>
<valueBoolean value="true"/>
</property>
<property>
<code value="parent"/>
<valueCode value="ResourceConsumerObligations"/>
</property>
<property>
<code value="parent"/>
<valueCode value="ResourceProducerObligations"/>
</property>
</concept>
<concept>
<code value="no-alter"/>
<display value="not alter"/>
<definition
value="Conformant applications SHALL/SHOULD ensure that this element does not change between receiving and transfer.
Notes: This does not mean that the element value cannot change, only that changing the element value for an element marked with this obligation moves an application from being an exchanger to a Consumer and a Producer, and those obligations apply"/>
<property>
<code value="not-selectable"/>
<valueBoolean value="true"/>
</property>
<property>
<code value="parent"/>
<valueCode value="ResourceExchangerObligations"/>
</property>
<property>
<code value="converse"/>
<valueCode value="may-alter"/>
</property>
</concept>
<concept>
<code value="no-error"/>
<display value="not error if present"/>
<definition
value="Conformant applications SHALL/SHOULD accept resources containing any valid value for the element without error.
Notes: Applications are still able to inform the user that a value cannot be processed correctly and may ignore the data, but applications aren't able to reject an instance merely because the element is present (which would be allowed for elements that do not have this obligation). A system MAY raise an error if the value provided is not valid or violates specific business rules. This obligation also applies to elements that only contain an extension in place of a value where (or equivalent), should either of these be allowed on the consumer obligations"/>
<property>
<code value="not-selectable"/>
<valueBoolean value="true"/>
</property>
<property>
<code value="parent"/>
<valueCode value="ResourceConsumerObligations"/>
</property>
</concept>
<concept>
<code value="reject-invalid"/>
<display value="reject invalid"/>
<definition
value="Conformant applications SHALL/SHOULD check that values for this element meet all data constraints asserted within the profile declaring this obligation. If validity issues are found, the system SHALL/SHOULD not accept the instance.
Notes: This applies to validating the element with the obligation, but not resources referenced by it."/>
<property>
<code value="not-selectable"/>
<valueBoolean value="true"/>
</property>
<property>
<code value="parent"/>
<valueCode value="ResourceConsumerObligations"/>
</property>
<property>
<code value="converse"/>
<valueCode value="accept-invalid"/>
</property>
</concept>
<concept>
<code value="accept-invalid"/>
<display value="accept invalid"/>
<definition
value="Conformant applications SHALL/SHOULD accept data that does not meet all data constraints asserted within the profile declaring this obligation.
This applies to non-valid constraints, not to non-valid syntax or failure to meet base resource validity expectations. Typically used when a system needs to be able to handle data that does not adhere to desired expectations (legacy data, test data, data undergoing authorship that is not yet complete, etc.)"/>
<property>
<code value="not-selectable"/>
<valueBoolean value="true"/>
</property>
<property>
<code value="parent"/>
<valueCode value="ResourceConsumerObligations"/>
</property>
<property>
<code value="converse"/>
<valueCode value="reject-invalid"/>
</property>
</concept>
<concept>
<code value="handle"/>
<display value="correctly handle"/>
<definition
value="Conformant applications SHALL/SHOULD handle the meaning of this element correctly.
Notes: this rule is vague in that doesn't specify any particular handling of the element. But it's important because an application that ignores this element is non-conformant. A good example would be a status code of 'entered-in-error' - how exactly a Resource Consumer handles this depends on the use case etc., but the application can never simply ignore such a status code. Note that whether the resource or information from it is stored for later use is irrelevant - when the resource or information in it is processed, the consequences of the element are considered. That may mean not retaining the information for later use, or informing the user, etc. Typically, this obligation marks that there are known patient safety issues that can arise if the element is ignored. Implementers should pay particular attention to the possible range of values for the element from a safety perspective."/>
<property>
<code value="not-selectable"/>
<valueBoolean value="true"/>
</property>
<property>
<code value="parent"/>
<valueCode value="ResourceConsumerObligations"/>
</property>
</concept>
<concept>
<code value="display"/>
<display value="display"/>
<definition
value="Conformant applications SHALL/SHOULD/MAY display the value of this element when presenting the data from the resource to a human user.
Notes: exactly how it is displayed is not specified, but it means that a human looking at the content of the resource is made aware of the value of the element so that they can consider the meaning of the resource"/>
<property>
<code value="not-selectable"/>
<valueBoolean value="true"/>
</property>
<property>
<code value="parent"/>
<valueCode value="handle"/>
</property>
<property>
<code value="security-dependent"/>
<valueBoolean value="true"/>
</property>
</concept>
<concept>
<code value="process"/>
<display value="process"/>
<definition
value="Conformant applications SHALL/SHOULD/MAY consider the value of this element when processing the resource as specified by the IG.
Notes: this implies that the IG that specifies this obligation provides details about what processing is to be performed, and the obligation specifially relates to the processing specified in the IG of any [ElementDefinition.valueAlternatives](http://hl7.org/fhir/R5/elementdefinition-definitions.html#ElementDefinition.valueAlternatives) extensions as well as the value (or other extensions explicitly declared beneath the element in the profile containing the obligation. Examples might include consideration in decision support, consideration in claims evaluation, etc."/>
<property>
<code value="not-selectable"/>
<valueBoolean value="true"/>
</property>
<property>
<code value="parent"/>
<valueCode value="handle"/>
</property>
<property>
<code value="security-dependent"/>
<valueBoolean value="true"/>
</property>
</concept>
<concept>
<code value="print"/>
<display value="print"/>
<definition
value="Conformant applications SHALL/SHOULD/MAY print the value of this element somewhere.
Notes: The form of the printing is not specified. A profile using this value SHALL explain the nature of the printing requirement somehow"/>
<property>
<code value="not-selectable"/>
<valueBoolean value="true"/>
</property>
<property>
<code value="parent"/>
<valueCode value="handle"/>
</property>
<property>
<code value="security-dependent"/>
<valueBoolean value="true"/>
</property>
</concept>
<concept>
<code value="ignore"/>
<display value="ignore"/>
<definition
value="Conformant applications SHALL/SHOULD/MAY not make any use of the value of this element if received."/>
<property>
<code value="not-selectable"/>
<valueBoolean value="true"/>
</property>
<property>
<code value="parent"/>
<valueCode value="ResourceConsumerObligations"/>
</property>
<property>
<code value="converse"/>
<valueCode value="handle"/>
</property>
</concept>
<concept>
<code value="SHALL:able-to-populate"/>
<display value="SHALL be able to populate"/>
<definition
value="Conformant applications producing resources SHALL be able to correctly populate this element.
Notes: Typically, this means that an application needs to demonstrate during some conformance testing process that there are some conditions under which it populates the element with a correct value. (i.e. not a data-absent-reason or equivalent.) This obligation does not impose expectations on the circumstances in which the element will be sent, only that it can be in at least some situations."/>
<property>
<code value="qualifier"/>
<valueCode value="SHALL"/>
</property>
<property>
<code value="parent"/>
<valueCode value="able-to-populate"/>
</property>
</concept>
<concept>
<code value="SHOULD:able-to-populate"/>
<display value="SHOULD be able to populate"/>
<definition
value="Conformant applications producing resources SHOULD be able to correctly populate this element.
Notes: Typically, this means that an application needs to demonstrate during some conformance testing process that there are some conditions under which it populates the element with a correct value. (i.e. not a data-absent-reason or equivalent.) This obligation does not impose expectations on the circumstances in which the element will be sent, only that it shold be in at least some situations."/>
<property>
<code value="qualifier"/>
<valueCode value="SHOULD"/>
</property>
<property>
<code value="parent"/>
<valueCode value="able-to-populate"/>
</property>
</concept>
<concept>
<code value="MAY:able-to-populate"/>
<display value="MAY be able to populate"/>
<definition
value="Conformant applications producing resources MAY be able to correctly populate this element.
Notes: Typically, this means that an application needs to demonstrate during some conformance testing process that there are some conditions under which it populates the element with a correct value. (i.e. not a data-absent-reason or equivalent.) This obligation does not impose expectations on the circumstances in which the element will be sent, only that it may be in at least some situations. This is a null statement and is the default behavior for originating systems if other obligations are not specified."/>
<property>
<code value="qualifier"/>
<valueCode value="MAY"/>
</property>
<property>
<code value="parent"/>
<valueCode value="able-to-populate"/>
</property>
</concept>
<concept>
<code value="SHALL:populate-if-known"/>
<display value="SHALL populate if known"/>
<definition
value="Conformant applications producing resources SHALL correctly populate this element if they know a value for the element, but it is acceptable if the system is unable to ever know a value for the element.
Notes: This obligation does not impose a requirement to be able to know a value, unlike populate and able-to-populate which do. 'Knowing' an element means that a value for the element is available in memory, persistent store, or is otherwise available within the system claiming conformance."/>
<property>
<code value="qualifier"/>
<valueCode value="SHALL"/>
</property>
<property>
<code value="parent"/>
<valueCode value="populate-if-known"/>
</property>
<property>
<code value="security-dependent"/>
<valueBoolean value="true"/>
</property>
</concept>
<concept>
<code value="SHOULD:populate-if-known"/>
<display value="SHOULD populate if known"/>
<definition
value="Conformant applications producing resources SHOULD correctly populate this element if they know a value for the element, but it is acceptable if the system is unable to ever know a value for the element.
Notes: This obligation does not impose a requirement to be able to know a value, unlike populate and able-to-populate which do. 'Knowing' an element means that a value for the element is available in memory, persistent store, or is otherwise available within the system claiming conformance."/>
<property>
<code value="qualifier"/>
<valueCode value="SHOULD"/>
</property>
<property>
<code value="parent"/>
<valueCode value="populate-if-known"/>
</property>
<property>
<code value="security-dependent"/>
<valueBoolean value="true"/>
</property>
</concept>
<concept>
<code value="SHALL:populate"/>
<display value="SHALL populate"/>
<definition
value="Conformant applications producing resources SHALL include this element if a value is known and allowed to be shared.
Notes: This implementation obligation means that whenever the producer knows the correct value for an element, it populates it. This is NOT the same as cardinality, as a 'populate' element can be omitted if no data exists or the data that exists is prohibited from being shared."/>
<property>
<code value="qualifier"/>
<valueCode value="SHALL"/>
</property>
<property>
<code value="parent"/>
<valueCode value="SHALL:able-to-populate"/>
</property>
<property>
<code value="parent"/>
<valueCode value="populate"/>
</property>
<property>
<code value="security-dependent"/>
<valueBoolean value="true"/>
</property>
</concept>
<concept>
<code value="SHOULD:populate"/>
<display value="SHOULD populate"/>
<definition
value="Conformant applications producing resources SHOULD include this element if a value is known and allowed to be shared.
Notes: This implementation obligation means that whenever the producer knows the correct value for an element, it should populate it. This is NOT the same as cardinality, as a 'populate' element can be omitted if no data exists or the data that exists is prohibited from being shared."/>
<property>
<code value="qualifier"/>
<valueCode value="SHOULD"/>
</property>
<property>
<code value="parent"/>
<valueCode value="SHOULD:able-to-populate"/>
</property>
<property>
<code value="parent"/>
<valueCode value="populate"/>
</property>
<property>
<code value="security-dependent"/>
<valueBoolean value="true"/>
</property>
</concept>
<concept>
<code value="SHALL:in-narrative"/>
<display value="SHALL include in narrative"/>
<definition
value="Conformant applications SHALL ensure that this data element is represented in any human readable representation of a resource.
Notes: When no value for an element is known, the producer populates the narrative with the content of any nested [ElementDefinition.valueAlternatives](http://hl7.org/fhir/R5/elementdefinition-definitions.html#ElementDefinition.valueAlternatives) extensions such as [DataAbsentReason](StructureDefinition-data-absent-reason.html). If no particular reason is known or reportable, the element can simply be indicated as 'unknown' in the narrative."/>
<property>
<code value="qualifier"/>
<valueCode value="SHALL"/>
</property>
<property>
<code value="parent"/>
<valueCode value="in-narrative"/>
</property>
<property>
<code value="security-dependent"/>
<valueBoolean value="true"/>
</property>
</concept>
<concept>
<code value="SHOULD:in-narrative"/>
<display value="SHOULD include in narrative"/>
<definition
value="Conformant applications SHOULD ensure that this data element is represented in any human readable representation of a resource.
Notes: When no value for an element is known, the producer populates the narrative with the content of any nested [ElementDefinition.valueAlternatives](http://hl7.org/fhir/R5/elementdefinition-definitions.html#ElementDefinition.valueAlternatives) extensions such as [DataAbsentReason](StructureDefinition-data-absent-reason.html). If no particular reason is known or reportable, the element can simply be indicated as 'unknown' in the narrative."/>
<property>
<code value="qualifier"/>
<valueCode value="SHOULD"/>
</property>
<property>
<code value="parent"/>
<valueCode value="in-narrative"/>
</property>
<property>
<code value="security-dependent"/>
<valueBoolean value="true"/>
</property>
</concept>
<concept>
<code value="MAY:in-narrative"/>
<display value="MAY include in narrative"/>
<definition
value="Conformant applications MAY ensure that this data element is represented in any human readable representation of a resource.
Notes: When no value for an element is known, the producer populates the narrative with the content of any nested [ElementDefinition.valueAlternatives](http://hl7.org/fhir/R5/elementdefinition-definitions.html#ElementDefinition.valueAlternatives) extensions such as [DataAbsentReason](StructureDefinition-data-absent-reason.html). If no particular reason is known or reportable, the element can simply be indicated as 'unknown' in the narrative."/>
<property>
<code value="qualifier"/>
<valueCode value="MAY"/>
</property>
<property>
<code value="parent"/>
<valueCode value="in-narrative"/>
</property>
<property>
<code value="security-dependent"/>
<valueBoolean value="true"/>
</property>
</concept>
<concept>
<code value="SHALL:exclude-narrative"/>
<display value="SHALL exclude from narrative"/>
<definition
value="Conformant applications SHALL ensure that this data element is NOT represented in any human readable representation of a resource.
Notes: This may be useful for profiles related to de-identified records"/>
<property>
<code value="qualifier"/>
<valueCode value="SHALL"/>
</property>
<property>
<code value="parent"/>
<valueCode value="exclude-narrative"/>
</property>
</concept>
<concept>
<code value="SHOULD:exclude-narrative"/>
<display value="SHOULD exclude from narrative"/>
<definition
value="Conformant applications SHOULD ensure that this data element is NOT represented in any human readable representation of a resource.
Notes: This may be useful for profiles related to de-identified records"/>
<property>
<code value="qualifier"/>
<valueCode value="SHOULD"/>
</property>
<property>
<code value="parent"/>
<valueCode value="exclude-narrative"/>
</property>
</concept>
<concept>
<code value="SHALL:user-input"/>
<display value="SHALL allow user input"/>
<definition
value="Conformant applications SHALL ensure that users can enter a value for this element during data input/capture.
Notes: Exactly what form the input takes is not specified, but the expectation is that this is a value that comes from the user, and not implied internally by the application."/>
<property>
<code value="qualifier"/>
<valueCode value="SHALL"/>
</property>
<property>
<code value="parent"/>
<valueCode value="user-input"/>
</property>
</concept>
<concept>
<code value="SHOULD:user-input"/>
<display value="SHOULD allow user input"/>
<definition
value="Conformant applications SHOULD ensure that users can enter a value for this element during data input/capture.
Notes: Exactly what form the input takes is not specified, but the expectation is that this is a value that comes from the user, and not implied internally by the application."/>
<property>
<code value="qualifier"/>
<valueCode value="SHOULD"/>
</property>
<property>
<code value="parent"/>
<valueCode value="user-input"/>
</property>
</concept>
<concept>
<code value="MAY:user-input"/>
<display value="MAY allow user input"/>
<definition
value="Conformant applications MAY ensure that users can enter a value for this element during data input/capture.
Notes: Exactly what form the input takes is not specified, but the expectation is that this is a value that comes from the user, and not implied internally by the application."/>
<property>
<code value="qualifier"/>
<valueCode value="MAY"/>
</property>
<property>
<code value="parent"/>
<valueCode value="user-input"/>
</property>
</concept>
<concept>
<code value="SHALL:explain"/>
<display value="SHALL populate or document irrelevance"/>
<definition
value="Documentation applicable to Conformant applications SHALL explain how this element is handled.
Notes: this is really a rule about specifications, implying that another specification (which might be application documentation) either makes this element `populate`, or explains how the use cases that involve this element do not arise, or how they are handled. An example: IPA marks Patient.active must-handle and must-explain. Client applications must process Patient.active correctly if they see it, but many (though *not all*) specifications and/or applications ensure that Patient.active will never be false, and so it will never be populated e.g. MedMij in Netherlands prohibits use of Patient.active, and explains that it is never false."/>
<property>
<code value="qualifier"/>
<valueCode value="SHALL"/>
</property>
<property>
<code value="parent"/>
<valueCode value="explain"/>
</property>
</concept>
<concept>
<code value="SHOULD:explain"/>
<display value="SHOULD populate or document irrelevance"/>
<definition
value="Documentation applicable to Conformant applications SHOULD explain how this element is handled.
Notes: this is really a rule about specifications, implying that another specification (which might be application documentation) either makes this element `populate`, or explains how the use cases that involve this element do not arise, or how they are handled. An example: IPA marks Patient.active must-handle and must-explain. Client applications must process Patient.active correctly if they see it, but many (though *not all*) specifications and/or applications ensure that Patient.active will never be false, and so it will never be populated e.g. MedMij in Netherlands prohibits use of Patient.active, and explains that it is never false."/>
<property>
<code value="qualifier"/>
<valueCode value="SHOULD"/>
</property>
<property>
<code value="parent"/>
<valueCode value="explain"/>
</property>
</concept>
<concept>
<code value="SHALL:persist"/>
<display value="SHALL persist"/>
<definition
value="Conformant applications SHALL ensure that the value for this element is stored in a persistent data store.
Notes: Exactly what the data store is not specified, nor how long it is stored for, but it is understood that the same value will be available in later exchanges"/>
<property>
<code value="qualifier"/>
<valueCode value="SHALL"/>
</property>
<property>
<code value="parent"/>
<valueCode value="persist"/>
</property>
</concept>
<concept>
<code value="SHOULD:persist"/>
<display value="SHOULD persist"/>
<definition
value="Conformant applications SHOULD ensure that the value for this element is stored in a persistent data store.
Notes: Exactly what the data store is not specified, nor how long it is stored for, but it is understood that the same value will be available in later exchanges"/>
<property>
<code value="qualifier"/>
<valueCode value="SHOULD"/>
</property>
<property>
<code value="parent"/>
<valueCode value="persist"/>
</property>
</concept>
<concept>
<code value="MAY:persist"/>
<display value="MAY persist"/>
<definition
value="Conformant applications MAY ensure that the value for this element is stored in a persistent data store.
Notes: Exactly what the data store is not specified, nor how long it is stored for, but it is understood that the same value will be available in later exchanges"/>
<property>
<code value="qualifier"/>
<valueCode value="MAY"/>
</property>
<property>
<code value="parent"/>
<valueCode value="persist"/>
</property>
</concept>
<concept>
<code value="SHALL:no-alter"/>
<display value="SHALL not alter"/>
<definition
value="Conformant applications SHALL ensure that this element does not change between receiving and transfer.
Notes: This does not mean that the element value cannot change, only that changing the element value for an element marked with this obligation moves an application from being an exchanger to a Consumer and a Producer, and those obligations apply"/>
<property>
<code value="qualifier"/>
<valueCode value="SHALL"/>
</property>
<property>
<code value="parent"/>
<valueCode value="no-alter"/>
</property>
<property>
<code value="converse"/>
<valueCode value="may-alter"/>
</property>
</concept>
<concept>
<code value="SHOULD:no-alter"/>
<display value="SHOULD not alter"/>
<definition
value="Conformant applications SHOULD ensure that this element does not change between receiving and transfer.
Notes: This does not mean that the element value cannot change, only that changing the element value for an element marked with this obligation moves an application from being an exchanger to a Consumer and a Producer, and those obligations apply"/>
<property>
<code value="qualifier"/>
<valueCode value="SHOULD"/>
</property>
<property>
<code value="parent"/>
<valueCode value="no-alter"/>
</property>
<property>
<code value="converse"/>
<valueCode value="may-alter"/>
</property>
</concept>
<concept>
<code value="MAY:alter"/>
<display value="MAY alter"/>
<definition
value="Conformant applications MAY choose to alter this element value.
Notes: this is really a null-statement - it's the default rule for an application. It's defined here to allow a specification to be explicit that it isn't conveying obligations for resource producers"/>
<property>
<code value="qualifier"/>
<valueCode value="MAY"/>
</property>
<property>
<code value="parent"/>
<valueCode value="ResourceExchangerObligations"/>
</property>
<property>
<code value="converse"/>
<valueCode value="no-alter"/>
</property>
</concept>
<concept>
<code value="SHALL:no-error"/>
<display value="SHALL not error if present"/>
<definition
value="Conformant applications SHALL accept resources containing any valid value for the element without error.
Notes: Applications are still able to inform the user that a value cannot be processed correctly and may ignore the data, but applications aren't able to reject an instance merely because the element is present (which would be allowed for elements that do not have this obligation). A system MAY raise an error if the value provided is not valid or violates specific business rules. This obligation also applies to elements that only contain an extension in place of a value where (or equivalent), should either of these be allowed on the consumer obligations"/>
<property>
<code value="qualifier"/>
<valueCode value="SHALL"/>
</property>
<property>
<code value="parent"/>
<valueCode value="no-error"/>
</property>
</concept>
<concept>
<code value="SHOULD:no-error"/>
<display value="SHOULD not error if present"/>
<definition
value="Conformant applications SHOULD accept resources containing any valid value for the element without error.
Notes: Applications are still able to inform the user that a value cannot be processed correctly and may ignore the data, but applications aren't able to reject an instance merely because the element is present (which would be allowed for elements that do not have this obligation). A system MAY raise an error if the value provided is not valid or violates specific business rules. This obligation also applies to elements that only contain an extension in place of a value where (or equivalent), should either of these be allowed on the consumer obligations"/>
<property>
<code value="qualifier"/>
<valueCode value="SHOULD"/>
</property>
<property>
<code value="parent"/>
<valueCode value="no-error"/>
</property>
</concept>
<concept>
<code value="SHALL:reject-invalid"/>
<display value="SHALL reject invalid"/>
<definition
value="Conformant applications SHALL check that values for this element meet all data constraints asserted within the profile declaring this obligation. If validity issues are found, the system SHALL not accept the instance.
Notes: This applies to validating the element with the obligation, but not resources referenced by it."/>
<property>
<code value="qualifier"/>
<valueCode value="SHALL"/>
</property>
<property>
<code value="parent"/>
<valueCode value="reject-invalid"/>
</property>
<property>
<code value="converse"/>
<valueCode value="accept-invalid"/>
</property>
</concept>
<concept>
<code value="SHOULD:reject-invalid"/>
<display value="SHOULD reject invalid"/>
<definition
value="Conformant applications SHOULD check that values for this element meet all data constraints asserted within the profile declaring this obligation. If validity issues are found, the system SHOULD not accept the instance.
Notes: This applies to validating the element with the obligation, but not resources referenced by it."/>
<property>
<code value="qualifier"/>
<valueCode value="SHOULD"/>
</property>
<property>
<code value="parent"/>
<valueCode value="reject-invalid"/>
</property>
<property>
<code value="converse"/>
<valueCode value="accept-invalid"/>
</property>
</concept>
<concept>
<code value="SHALL:accept-invalid"/>
<display value="SHALL accept invalid"/>
<definition
value="Conformant applications SHALL accept data that does not meet all data constraints asserted within the profile declaring this obligation.
This applies to non-valid constraints, not to non-valid syntax or failure to meet base resource validity expectations. Typically used when a system needs to be able to handle data that does not adhere to desired expectations (legacy data, test data, data undergoing authorship that is not yet complete, etc.)"/>
<property>
<code value="qualifier"/>
<valueCode value="SHALL"/>
</property>
<property>
<code value="parent"/>
<valueCode value="accept-invalid"/>
</property>
<property>
<code value="converse"/>
<valueCode value="reject-invalid"/>
</property>
</concept>
<concept>
<code value="SHOULD:accept-invalid"/>
<display value="SHOULD accept invalid"/>
<definition
value="Conformant applications SHOULD accept data that does not meet all data constraints asserted within the profile declaring this obligation.
This applies to non-valid constraints, not to non-valid syntax or failure to meet base resource validity expectations. Typically used when a system ought to be able to handle data that does not adhere to desired expectations (legacy data, test data, data undergoing authorship that is not yet complete, etc.)"/>
<property>
<code value="qualifier"/>
<valueCode value="SHOULD"/>
</property>
<property>
<code value="parent"/>
<valueCode value="accept-invalid"/>
</property>
<property>
<code value="converse"/>
<valueCode value="reject-invalid"/>
</property>
</concept>
<concept>
<code value="SHALL:handle"/>
<display value="SHALL correctly handle"/>
<definition
value="Conformant applications SHALL handle the meaning of this element correctly.
Notes: this rule is vague in that doesn't specify any particular handling of the element. But it's important because an application that ignores this element is non-conformant. A good example would be a status code of 'entered-in-error' - how exactly a Resource Consumer handles this depends on the use case etc., but the application can never simply ignore such a status code. Note that whether the resource or information from it is stored for later use is irrelevant - when the resource or information in it is processed, the consequences of the element are considered. That may mean not retaining the information for later use, or informing the user, etc. Typically, this obligation marks that there are known patient safety issues that can arise if the element is ignored. Implementers should pay particular attention to the possible range of values for the element from a safety perspective."/>
<property>
<code value="qualifier"/>
<valueCode value="SHALL"/>
</property>
<property>
<code value="parent"/>
<valueCode value="handle"/>
</property>
</concept>
<concept>
<code value="SHOULD:handle"/>
<display value="SHOULD correctly handle"/>
<definition
value="Conformant applications SHOULD handle the meaning of this element correctly.
Notes: this rule is vague in that doesn't specify any particular handling of the element. But it's important because an application that ignores this element is non-conformant. A good example would be a status code of 'entered-in-error' - how exactly a Resource Consumer handles this depends on the use case etc., but the application can never simply ignore such a status code. Note that whether the resource or information from it is stored for later use is irrelevant - when the resource or information in it is processed, the consequences of the element are considered. That may mean not retaining the information for later use, or informing the user, etc. Typically, this obligation marks that there are known patient safety issues that can arise if the element is ignored. Implementers should pay particular attention to the possible range of values for the element from a safety perspective."/>
<property>
<code value="qualifier"/>
<valueCode value="SHOULD"/>
</property>
<property>
<code value="parent"/>
<valueCode value="handle"/>
</property>
</concept>
<concept>
<code value="SHALL:display"/>
<display value="SHALL display"/>
<definition
value="Conformant applications SHALL display the value of this element when presenting the data from the resource to a human user.
Notes: exactly how it is displayed is not specified, but it means that a human looking at the content of the resource is made aware of the value of the element so that they can consider the meaning of the resource"/>
<property>
<code value="qualifier"/>
<valueCode value="SHALL"/>
</property>
<property>
<code value="parent"/>
<valueCode value="SHALL:handle"/>
</property>
<property>
<code value="parent"/>
<valueCode value="display"/>
</property>
<property>
<code value="security-dependent"/>
<valueBoolean value="true"/>
</property>
</concept>
<concept>
<code value="SHOULD:display"/>
<display value="SHOULD display"/>
<definition
value="Conformant applications SHOULD display the value of this element when presenting the data from the resource to a human user.
Notes: exactly how it is displayed is not specified, but it means that a human looking at the content of the resource is made aware of the value of the element so that they can consider the meaning of the resource"/>
<property>
<code value="qualifier"/>
<valueCode value="SHOULD"/>
</property>
<property>
<code value="parent"/>
<valueCode value="SHOULD:handle"/>
</property>
<property>
<code value="parent"/>
<valueCode value="display"/>
</property>
<property>
<code value="security-dependent"/>
<valueBoolean value="true"/>
</property>
</concept>
<concept>
<code value="MAY:display"/>
<display value="MAY display"/>
<definition
value="Conformant applications MAY display the value of this element when presenting the data from the resource to a human user.
Notes: exactly how it is displayed is not specified, but it means that a human looking at the content of the resource is made aware of the value of the element so that they can consider the meaning of the resource"/>
<property>
<code value="qualifier"/>
<valueCode value="MAY"/>
</property>
<property>
<code value="parent"/>
<valueCode value="display"/>
</property>
<property>
<code value="security-dependent"/>
<valueBoolean value="true"/>
</property>
</concept>
<concept>
<code value="SHALL:process"/>
<display value="SHALL process"/>
<definition
value="Conformant applications SHALL consider the value of this element when processing the resource as specified by the IG.
Notes: this implies that the IG that specifies this obligation provides details about what processing is to be performed, and the obligation specifially relates to the processing specified in the IG of any [ElementDefinition.valueAlternatives](http://hl7.org/fhir/R5/elementdefinition-definitions.html#ElementDefinition.valueAlternatives) extensions as well as the value (or other extensions explicitly declared beneath the element in the profile containing the obligation. Examples might include consideration in decision support, consideration in claims evaluation, etc."/>
<property>
<code value="qualifier"/>
<valueCode value="SHALL"/>
</property>
<property>
<code value="parent"/>
<valueCode value="SHALL:handle"/>
</property>
<property>
<code value="parent"/>
<valueCode value="process"/>
</property>
<property>
<code value="security-dependent"/>
<valueBoolean value="true"/>
</property>
</concept>
<concept>
<code value="SHOULD:process"/>
<display value="SHOULD process"/>
<definition
value="Conformant applications SHOULD consider the value of this element when processing the resource as specified by the IG.
Notes: this implies that the IG that specifies this obligation provides details about what processing is to be performed, and the obligation specifially relates to the processing specified in the IG of any [ElementDefinition.valueAlternatives](http://hl7.org/fhir/R5/elementdefinition-definitions.html#ElementDefinition.valueAlternatives) extensions as well as the value (or other extensions explicitly declared beneath the element in the profile containing the obligation. Examples might include consideration in decision support, consideration in claims evaluation, etc."/>
<property>
<code value="qualifier"/>
<valueCode value="SHOULD"/>
</property>
<property>
<code value="parent"/>
<valueCode value="SHOULD:handle"/>
</property>
<property>
<code value="parent"/>
<valueCode value="process"/>
</property>
<property>
<code value="security-dependent"/>
<valueBoolean value="true"/>
</property>
</concept>
<concept>
<code value="MAY:process"/>
<display value="MAY process"/>
<definition
value="Conformant applications MAY consider the value of this element when processing the resource as specified by the IG.
Notes: this implies that the IG that specifies this obligation provides details about what processing is to be performed, and the obligation specifially relates to the processing specified in the IG of any [ElementDefinition.valueAlternatives](http://hl7.org/fhir/R5/elementdefinition-definitions.html#ElementDefinition.valueAlternatives) extensions as well as the value (or other extensions explicitly declared beneath the element in the profile containing the obligation. Examples might include consideration in decision support, consideration in claims evaluation, etc."/>
<property>
<code value="qualifier"/>
<valueCode value="MAY"/>
</property>
<property>
<code value="parent"/>
<valueCode value="process"/>
</property>
<property>
<code value="security-dependent"/>
<valueBoolean value="true"/>
</property>
</concept>
<concept>
<code value="SHALL:print"/>
<display value="SHALL print"/>
<definition
value="Conformant applications SHALL print the value of this element somewhere.
Notes: The form of the printing is not specified. A profile using this value SHALL explain the nature of the printing requirement somehow"/>
<property>
<code value="qualifier"/>
<valueCode value="SHALL"/>
</property>
<property>
<code value="parent"/>
<valueCode value="SHALL:handle"/>
</property>
<property>
<code value="parent"/>
<valueCode value="print"/>
</property>
<property>
<code value="security-dependent"/>
<valueBoolean value="true"/>
</property>
</concept>
<concept>
<code value="SHOULD:print"/>
<display value="SHOULD print"/>
<definition
value="Conformant applications SHOULD print the value of this element somewhere.
Notes: The form of the printing is not specified. A profile using this value SHALL explain the nature of the printing requirement somehow"/>
<property>
<code value="qualifier"/>
<valueCode value="SHOULD"/>
</property>
<property>
<code value="parent"/>
<valueCode value="SHOULD:handle"/>
</property>
<property>
<code value="parent"/>
<valueCode value="print"/>
</property>
<property>
<code value="security-dependent"/>
<valueBoolean value="true"/>
</property>
</concept>
<concept>
<code value="MAY:print"/>
<display value="MAY print"/>
<definition
value="Conformant applications MAY print the value of this element somewhere.
Notes: The form of the printing is not specified. A profile using this value SHALL explain the nature of the printing requirement somehow"/>
<property>
<code value="qualifier"/>
<valueCode value="MAY"/>
</property>
<property>
<code value="parent"/>
<valueCode value="print"/>
</property>
<property>
<code value="security-dependent"/>
<valueBoolean value="true"/>
</property>
</concept>
<concept>
<code value="SHALL:ignore"/>
<display value="SHALL ignore"/>
<definition
value="Conformant applications SHALL not make any use of the value of this element if received."/>
<property>
<code value="qualifier"/>
<valueCode value="SHALL"/>
</property>
<property>
<code value="parent"/>
<valueCode value="ignore"/>
</property>
<property>
<code value="converse"/>
<valueCode value="handle"/>
</property>
</concept>
<concept>
<code value="SHOULD:ignore"/>
<display value="SHOULD ignore"/>
<definition
value="Conformant applications SHOULD not make any use of the value of this element if received."/>
<property>
<code value="qualifier"/>
<valueCode value="SHOULD"/>
</property>
<property>
<code value="parent"/>
<valueCode value="ignore"/>
</property>
<property>
<code value="converse"/>
<valueCode value="handle"/>
</property>
</concept>
<concept>
<code value="MAY:ignore"/>
<display value="MAY ignore"/>
<definition
value="Conformant applications MAY not make any use of the value of this element if received. This is a null statement and is the default behavior or consuming systems if other obligations are not specified."/>
<property>
<code value="qualifier"/>
<valueCode value="MAY"/>
</property>
<property>
<code value="parent"/>
<valueCode value="ignore"/>
</property>
<property>
<code value="converse"/>
<valueCode value="handle"/>
</property>
</concept>
<concept>
<code value="v2-re"/>
<display value="V2 RE (required but may be empty)"/>
<definition value="RE as defined in chapter 2 of the v2 specification"/>
<property>
<code value="parent"/>
<valueCode value="SHALL:able-to-populate"/>
</property>
<property>
<code value="parent"/>
<valueCode value="SHALL:display"/>
</property>
<property>
<code value="parent"/>
<valueCode value="SHOULD:persist"/>
</property>
<property>
<code value="parent"/>
<valueCode value="SHOULD:populate"/>
</property>
<property>
<code value="parent"/>
<valueCode value="SHALL:no-error"/>
</property>
</concept>
<concept>
<code value="ihe-r2"/>
<display value="IHE R2"/>
<definition value="R2 as defined in IHE Appendix Z"/>
<property>
<code value="parent"/>
<valueCode value="SHALL:populate"/>
</property>
<property>
<code value="parent"/>
<valueCode value="MAY:ignore"/>
</property>
<property>
<code value="parent"/>
<valueCode value="SHALL:no-error"/>
</property>
</concept>
<concept>
<code value="std"/>
<display value="Standard obligations"/>
<definition
value="The standard recommended set of obligations for IGs to use unless they know they want something different. Note that the standard codes don't include use-dar, use-dar-nf, use-dar-if-allowed / use-reason - that gets put on specific elements that justify this handling"/>
<property>
<code value="parent"/>
<valueCode value="SHALL:populate"/>
</property>
<property>
<code value="parent"/>
<valueCode value="SHALL:display"/>
</property>
<property>
<code value="parent"/>
<valueCode value="SHALL:no-error"/>
</property>
</concept>
</CodeSystem>
IG © 2022+ HL7 International / FHIR Infrastructure. Package hl7.fhir.uv.extensions#5.2.0-ballot based on FHIR 5.0.0. Generated 2024-10-09
Links: Table of Contents |
QA Report
| Version History |
|
Propose a change