R4 Ballot #1 (Mixed Normative/Trial use) Release 4

This page is part of the FHIR Specification (v3.3.0: (v4.0.1: R4 Ballot 2). - Mixed Normative and STU ) in it's permanent home (it will always be available at this URL). The current version which supercedes this version is 5.0.0 . For a full list of available versions, see the Directory of published versions . Page versions: R5 R4B R4 R3 R2

2.26 2.27 DomainResource Resource

http://www.hl7.org/Special/committees/fiwg/index.cfm Maturity Level : 5 N   Normative (from v4.0.0) Compartments : Not linked to any defined compartments
Normative Candidate Note:
This page is candidate normative content for R4 in has been approved as part of an ANSI standard. See the Infrastructure Package . Once normative, it will lose it's Maturity Level, and breaking changes will no longer be made. for further details.

2.26.1 2.27.1 Scope and Usage

A domain resource is an a resource that:

As an abstract resource, this resource is never created directly; instead, one of its descendent descendant resources ( see List of Resources ) is created.

2.26.2 2.27.2 Boundaries and Relationships

This resource extends the base resource Resource . All of the listed Resources except Bundle , Parameters and Binary extend this resource.

2.26.3 2.27.3 Resource Content

Structure

I
Name Flags Card. Type Description & Constraints doco
. . DomainResource I N Resource A resource with narrative, extensions, and contained resources
+ Rule: If the resource is contained in another resource, it SHALL NOT contain nested Resources
+ Rule: If the resource is contained in another resource, it SHALL NOT contain any narrative be referred to from elsewhere in the resource or SHALL refer to the containing resource
+ Rule: If a resource is contained in another resource, it SHALL NOT have a meta.versionId or a meta.lastUpdated
+ Rule: If the a resource is contained in another resource, it SHALL be referred to from elsewhere in the resource or SHALL refer to the containing NOT have a security label
+ Guideline: A resource should have narrative for robust management
Elements defined in Ancestors: id , meta , implicitRules , language
. . . text 0..1 Narrative Text summary of the resource, for human interpretation
. . . contained 0..* Resource Contained, inline Resources
. . . extension 0..* Extension Additional Content content defined by implementations
. . . modifierExtension ?! 0..* Extension Extensions that cannot be ignored

doco Documentation for this format

UML Diagram ( Legend )

DomainResource ( Resource ) A human-readable narrative that contains a summary of the resource and can be used to represent the content of the resource to a human. The narrative need not encode all the structured data, but is required to contain sufficient detail to make it "clinically safe" for a human to just read the narrative. Resource definitions may define what content should be represented in the narrative to ensure clinical safety text : Narrative [0..1] These resources do not have an independent existence apart from the resource that contains them - they cannot be identified independently, and nor can they have their own independent transaction scope contained : Resource [0..*] May be used to represent additional information that is not part of the basic definition of the resource. To make the use of extensions safe and manageable, there is a strict set of governance applied to the definition and use of extensions. Though any implementer can define an extension, there is a set of requirements that SHALL be met as part of the definition of the extension extension : Extension [0..*] May be used to represent additional information that is not part of the basic definition of the resource, resource and that modifies the understanding of the element that contains it. it and/or the understanding of the containing element's descendants. Usually modifier elements provide negation or qualification. To make the use of extensions safe and manageable, there is a strict set of governance applied to the definition and use of extensions. Though any implementer is allowed to define an extension, there is a set of requirements that SHALL be met as part of the definition of the extension. Applications processing a resource are required to check for modifier extensions. Modifier extensions SHALL NOT change the meaning of any elements on Resource or DomainResource (including cannot change the meaning of modifierExtension itself) (this element modifies the meaning of other elements) modifierExtension : Extension [0..*]

XML Template 

<[name] xmlns="http://hl7.org/fhir"> doco
 <!-- from Element: extension -->
 <</text>

 <text><!-- 0..1 Narrative Text summary of the resource, for human interpretation --></text>

 <contained><!-- 0..* Resource Contained, inline Resources --></contained>
 <</extension>
 <</modifierExtension>

 <extension><!-- 0..* Extension Additional content defined by implementations --></extension>
 <modifierExtension><!-- 0..* Extension Extensions that cannot be ignored --></modifierExtension>

</[name]>

Turtle Template 

@prefix fhir: <http://hl7.org/fhir/> .

@prefix fhir: <http://hl7.org/fhir/> .doco


[ a fhir:[name];
  fhir:nodeRole fhir:treeRoot; # if this is the parser root


[

 # from Element: Element.extension
  fhir:DomainResource.text [ Narrative ]; # 0..1 Text summary of the resource, for human interpretation
  fhir:DomainResource.contained [ Resource ], ... ; # 0..* Contained, inline Resources
  fhir:
  fhir:

  fhir:DomainResource.extension [ Extension ], ... ; # 0..* Additional content defined by implementations
  fhir:DomainResource.modifierExtension [ Extension ], ... ; # 0..* Extensions that cannot be ignored

]

Structure

I
Name Flags Card. Type Description & Constraints doco
. . DomainResource I N Resource A resource with narrative, extensions, and contained resources
+ Rule: If the resource is contained in another resource, it SHALL NOT contain nested Resources
+ Rule: If the resource is contained in another resource, it SHALL NOT contain any narrative be referred to from elsewhere in the resource or SHALL refer to the containing resource
+ Rule: If a resource is contained in another resource, it SHALL NOT have a meta.versionId or a meta.lastUpdated
+ Rule: If the a resource is contained in another resource, it SHALL be referred to from elsewhere in the resource or SHALL refer to the containing NOT have a security label
+ Guideline: A resource should have narrative for robust management
Elements defined in Ancestors: id , meta , implicitRules , language
. . . text 0..1 Narrative Text summary of the resource, for human interpretation
. . . contained 0..* Resource Contained, inline Resources
. . . extension 0..* Extension Additional Content content defined by implementations
. . . modifierExtension ?! 0..* Extension Extensions that cannot be ignored

doco Documentation for this format

UML Diagram ( Legend )

DomainResource ( Resource ) A human-readable narrative that contains a summary of the resource and can be used to represent the content of the resource to a human. The narrative need not encode all the structured data, but is required to contain sufficient detail to make it "clinically safe" for a human to just read the narrative. Resource definitions may define what content should be represented in the narrative to ensure clinical safety text : Narrative [0..1] These resources do not have an independent existence apart from the resource that contains them - they cannot be identified independently, and nor can they have their own independent transaction scope contained : Resource [0..*] May be used to represent additional information that is not part of the basic definition of the resource. To make the use of extensions safe and manageable, there is a strict set of governance applied to the definition and use of extensions. Though any implementer can define an extension, there is a set of requirements that SHALL be met as part of the definition of the extension extension : Extension [0..*] May be used to represent additional information that is not part of the basic definition of the resource, resource and that modifies the understanding of the element that contains it. it and/or the understanding of the containing element's descendants. Usually modifier elements provide negation or qualification. To make the use of extensions safe and manageable, there is a strict set of governance applied to the definition and use of extensions. Though any implementer is allowed to define an extension, there is a set of requirements that SHALL be met as part of the definition of the extension. Applications processing a resource are required to check for modifier extensions. Modifier extensions SHALL NOT change the meaning of any elements on Resource or DomainResource (including cannot change the meaning of modifierExtension itself) (this element modifies the meaning of other elements) modifierExtension : Extension [0..*]

XML Template 

<[name] xmlns="http://hl7.org/fhir"> doco
 <!-- from Element: extension -->
 <</text>

 <text><!-- 0..1 Narrative Text summary of the resource, for human interpretation --></text>

 <contained><!-- 0..* Resource Contained, inline Resources --></contained>
 <</extension>
 <</modifierExtension>

 <extension><!-- 0..* Extension Additional content defined by implementations --></extension>
 <modifierExtension><!-- 0..* Extension Extensions that cannot be ignored --></modifierExtension>

</[name]>

Turtle Template 

@prefix fhir: <http://hl7.org/fhir/> .

@prefix fhir: <http://hl7.org/fhir/> .doco


[ a fhir:[name];
  fhir:nodeRole fhir:treeRoot; # if this is the parser root


[

 # from Element: Element.extension
  fhir:DomainResource.text [ Narrative ]; # 0..1 Text summary of the resource, for human interpretation
  fhir:DomainResource.contained [ Resource ], ... ; # 0..* Contained, inline Resources
  fhir:
  fhir:

  fhir:DomainResource.extension [ Extension ], ... ; # 0..* Additional content defined by implementations
  fhir:DomainResource.modifierExtension [ Extension ], ... ; # 0..* Extensions that cannot be ignored

]

2.26.3.1 2.27.3.1 Constraints

dom-1 : If the resource is contained in another resource, it SHALL NOT contain any narrative ( expression
: contained.text.empty() ) id Level Location Description Expression
dom-2 : Rule (base) If the resource is contained in another resource, it SHALL NOT contain nested Resources ( expression : contained.contained.empty() )
dom-3 : Rule (base) If the resource is contained in another resource, it SHALL be referred to from elsewhere in the resource or SHALL refer to the containing resource ( expression : contained.all(('#'+id contained.where((('#'+id in (%resource.descendants().reference | %resource.descendants().as(canonical))) %resource.descendants().as(canonical) | %resource.descendants().as(uri) | %resource.descendants().as(url))) or descendants().where(reference = '#').exists() or descendants().where(as(canonical) = '#').exists()) '#').exists() or descendants().where(as(canonical) = '#').exists()).not()).trace('unmatched', id).empty() )
dom-4 : Rule (base) If a resource is contained in another resource, it SHALL NOT have a meta.versionId or a meta.lastUpdated ( expression : contained.meta.versionId.empty() and contained.meta.lastUpdated.empty() )
dom-5 Rule (base) If a resource is contained in another resource, it SHALL NOT have a security label contained.meta.security.empty()
dom-6 Guideline (base) A resource should have narrative for robust management text.`div`.exists()
This is (only) a best practice guideline because:

When a resource has no narrative, only systems that fully understand the data can display the resource to a human safely. Including a human readable representation in the resource makes for a much more robust eco-system and cheaper handling of resources by intermediary systems. Some ecosystems restrict distribution of resources to only those systems that do fully understand the resources, and as a consequence implementers may believe that the narrative is superfluous. However experience shows that such eco-systems often open up to new participants over time.

2.26.4 2.27.4 Searching Extensions

To search for extensions, define a search parameter SearchParameter for the extension. All other search parameters are named aliases for existing content in the resource. In some cases, though not all, the search parameter name is the same as the element that it searches, but this is not required. Searching for extensions is the same - define a name that identifies the value extension by its URL, and then searches can filter based on the value of the extension.

2.26.5 2.27.5 Search Parameters

Common search parameters defined by this resource. See Searching for more information about searching in REST, messaging, and services.

Name Type Description Paths
_text string Search on the narrative of the resource