Generated Narrative: StructureDefinition ext-R4B-DocumentReference.context Name Flags Card. Type Description & Constraints Extension 0..1 Extension(5.0.0) Clinical context of document #xD; Slices for extension 0..* Extension Extension Slice: Unordered, Closed by value:url #xD; extension:encounter 0..* Extension Context of the document content #xD; url 1..1 uri "encounter" #xD; value[x] 0..1 Reference() Context of the document content #xD; <a href="StructureDefinition-ext-R4B-DocumentReference.context-definitions.html#Extension.extension:event" title="Slice event: This list of codes represents the main clinical acts, such as a colonoscopy or an appendectomy, being documented. In some cases, the event is inherent in the type Code, such as a "History and Physical Report" in which the procedure being documented is necessarily a "History and Physical" act.">extension:event 0..* Extension Main clinical acts documented #xD; url 1..1 uri "event" #xD; <a href="StructureDefinition-ext-R4B-DocumentReference.context-definitions.html#Extension.extension:event.value[x]" title="This list of codes represents the main clinical acts, such as a colonoscopy or an appendectomy, being documented. In some cases, the event is inherent in the type Code, such as a "History and Physical Report" in which the procedure being documented is necessarily a "History and Physical" act.">value[x] 0..1 CodeableConcept Main clinical acts documented Binding: http://terminology.hl7.org/ValueSet/v3-ActCode|2.0.0 (example): This list of codes represents the main clinical acts being documented. #xD; extension:period 0..1 Extension Time of service that is being documented #xD; url 1..1 uri "period" #xD; value[x] 0..1 Period Time of service that is being documented #xD; extension:facilityType 0..1 Extension Kind of facility where patient was seen #xD; url 1..1 uri "facilityType" #xD; value[x] 0..1 CodeableConcept Kind of facility where patient was seen Binding: R4B_c80_facilitycodes_for_R5 (0.0.1-snapshot-2) (example): XDS Facility Type. #xD; extension:practiceSetting 0..1 Extension Additional details about where the content was created (e.g. clinical specialty) #xD; url 1..1 uri "practiceSetting" #xD; value[x] 0..1 CodeableConcept Additional details about where the content was created (e.g. clinical specialty) Binding: R4B_c80_practice_codes_for_R5 (0.0.1-snapshot-2) (example): Additional details about where the content was created (e.g. clinical specialty). #xD; extension:sourcePatientInfo 0..1 Extension Patient demographics from source #xD; url 1..1 uri "sourcePatientInfo" #xD; value[x] 0..1 Reference() Patient demographics from source #xD; extension:related 0..* Extension Related identifiers or resources #xD; url 1..1 uri "related" #xD; value[x] 0..1 Reference() Related identifiers or resources #xD; url 1..1 uri "http://hl7.org/fhir/4.3/StructureDefinition/extension-DocumentReference.context" #xD; Documentation for this format
Cross-version Extension for R4B.DocumentReference.context for use in FHIR R5
This cross-version extension represents DocumentReference.context from http://hl7.org/fhir/StructureDefinition/DocumentReference|4.3.0 for use in FHIR R5.
The clinical context in which the document was prepared.
`DocumentReference.context` maps to R5 `DocumentReference.context`. Has no type mapping Changed from a single value to an array (max cardinality from 1 to *). So is mapped as RelatedTo.
All FHIR elements must have a @value or children
hasValue() or (children().count() > id.count())
Must have either extensions or value[x], not both
Unique id for the element within a resource (for internal references). This may be any string value that does not contain spaces.
Extensions are always sliced by (at least) url
Describes the clinical encounter or type of care that the document content is associated with.
Additional content defined by implementations
May be used to represent additional information that is not part of the basic definition of the element. To make the use of extensions safe and managable, there is a strict set of governance applied to the definition and use of extensions. Though any implementer can define an extension, there is a set of requirements that SHALL be met as part of the definition of the extension.
There can be no stigma associated with the use of extensions by any application, project, or standard - regardless of the institution or jurisdiction that uses or defines the extensions. The use of extensions is what allows the FHIR specification to retain a core level of simplicity for everyone.
Source of the definition for the extension code - a logical name or a URL.
The definition may point directly to a computable or human-readable definition of the extensibility codes, or it may be a logical URI as declared in some other specification. The definition SHALL be a URI for the Structure Definition defining the extension.
This list of codes represents the main clinical acts, such as a colonoscopy or an appendectomy, being documented. In some cases, the event is inherent in the type Code, such as a "History and Physical Report" in which the procedure being documented is necessarily a "History and Physical" act.
This list of codes represents the main clinical acts being documented.
Time of service that is being documented
The time period over which the service that is described by the document was provided.
The kind of facility where the patient was seen.
Additional details about where the content was created (e.g. clinical specialty)
This property may convey specifics about the practice setting where the content was created, often reflecting the clinical specialty.
Additional details about where the content was created (e.g. clinical specialty).
The Patient Information as known when the document was published. May be a reference to a version specific, or contained.
Related identifiers or resources associated with the DocumentReference.
Value of extension - must be one of a constrained set of the data types (see [Extensibility](http://hl7.org/fhir/R5/extensibility.html) for a list).