HL7 FHIR Implementation Guide: minimal Common Oncology Data Elements (mCODE) Release 1 - US Realm | STU Ballot 1

HL7 FHIR Implementation Guide: minimal Common Oncology Data Elements (mCODE) Release 1 - US Realm | STU Ballot 1 - Local Development build (v0.9.1). See the Directory of published versions

Laterality

 

The official URL for this extension is:

http://hl7.org/fhir/us/mcode/StructureDefinition/obf-datatype-Laterality-extension

Body side of the body location, if needed to distinguish from a similar location on the other side of the body.

The laterality element is part of BodyLocation, a flexible structure that allows the location to be determined by a single code, or a code plus laterality and/or orientation. The body location can also be specified in relation to one or more body landmarks. SNOMED CT is used in all cases.

  • Code only: The code should include (precoordinate) laterality and/orientation to the degree necessary to completely specify the body location.
  • Code plus laterality and/or orientation: The basic code augmented by codes specifying the body side and/or anatomical orientation.
  • Relation to landmark: The location relative to a landmark is specified by:
    1. Establishing the location and type of landmark using a body site code and optional laterality/orientation, and
    2. Specifying the direction and distance from the landmark to the body location.

Note that BodyLocation is a data type (a reusable structure), not a stand-alone entity. The concept is similar to how a postal address can apply to a person, location, or organization. This contrasts with FHIR’s stand-alone BodySite (aka BodyStructure in r4) which ‘is not … intended for describing the type of anatomical location but rather a specific body site on a specific patient’ (FHIR 3.5).

This extension was published on Thu Aug 01 00:00:00 EDT 2019 as a draft by HL7 International Clinical Interoperability Council.

Summary

Mandatory: 0 element (1 nested mandatory element)
Fixed Value: 1 element
Prohibited: 1 element

NameFlagsCard.TypeDescription & Constraintsdoco
.. Extension 0..*Laterality
... extension 0..0
... url uri"http://hl7.org/fhir/us/mcode/StructureDefinition/obf-datatype-Laterality-extension"
... valueCodeableConcept 1..CodeableConceptBinding: Laterality (extensible)

doco Documentation for this format
NameFlagsCard.TypeDescription & Constraintsdoco
.. Extension I0..*Laterality
ext-1: Must have either extensions or value[x], not both
... id 0..1stringUnique id for inter-element referencing
... extension 0..0
... url 1..1uri"http://hl7.org/fhir/us/mcode/StructureDefinition/obf-datatype-Laterality-extension"
... valueCodeableConcept 1..1CodeableConceptValue of extension
Binding: Laterality (extensible)

doco Documentation for this format

Summary

Mandatory: 0 element (1 nested mandatory element)
Fixed Value: 1 element
Prohibited: 1 element

Differential View

NameFlagsCard.TypeDescription & Constraintsdoco
.. Extension 0..*Laterality
... extension 0..0
... url uri"http://hl7.org/fhir/us/mcode/StructureDefinition/obf-datatype-Laterality-extension"
... valueCodeableConcept 1..CodeableConceptBinding: Laterality (extensible)

doco Documentation for this format

Snapshot View

NameFlagsCard.TypeDescription & Constraintsdoco
.. Extension I0..*Laterality
ext-1: Must have either extensions or value[x], not both
... id 0..1stringUnique id for inter-element referencing
... extension 0..0
... url 1..1uri"http://hl7.org/fhir/us/mcode/StructureDefinition/obf-datatype-Laterality-extension"
... valueCodeableConcept 1..1CodeableConceptValue of extension
Binding: Laterality (extensible)

doco Documentation for this format

Downloads: StructureDefinition: (XML, JSON, TTL), Schema: XML Schematron

 

Terminology Bindings

PathConformanceValueSet
Extension.valueCodeableConceptextensibleLaterality

 

Constraints

IdPathDetailsRequirements
ele-1ExtensionAll FHIR elements must have a @value or children
: hasValue() or (children().count() > id.count())
ext-1ExtensionMust have either extensions or value[x], not both
: extension.exists() != value.exists()

 

Usage

This extension is used in the following profiles:

This extension is used in the following complex extensions: