This page is part of the Breast Radiology Report (v0.1.0: Comment Draft) based on FHIR R4. . For a full list of available versions, see the Directory of published versions
<StructureDefinition xmlns="http://hl7.org/fhir"> <id value="obf-datatype-LandmarkLocation-extension"/> <text> <status value="generated"/> <div xmlns="http://www.w3.org/1999/xhtml"> <p><b>LandmarkLocation Extension</b></p> <p>The body location of the landmark, specified by a location code and optional laterality and orientation.</p> </div> </text> <url value="http://hl7.org/fhir/us/breast-radiology/StructureDefinition/obf-datatype-LandmarkLocation-extension"/> <version value="0.1.0"/> <name value="LandmarkLocation"/> <title value="obf-datatype-LandmarkLocation"/> <status value="draft"/> <date value="2019-08-02T00:00:00-04:00"/> <publisher value="Hl7 - Clinical Interoperability Council"/> <contact> <telecom> <system value="url"/> <value value="http://www.hl7.org/Special/committees/cic"/> </telecom> </contact> <description value="The body location of the landmark, specified by a location code and optional laterality and orientation."/> <fhirVersion value="4.0.0"/> <kind value="complex-type"/> <abstract value="false"/> <context> <type value="element"/> <expression value="*"/> </context> <type value="Extension"/> <baseDefinition value="http://hl7.org/fhir/StructureDefinition/Extension"/> <derivation value="constraint"/> <snapshot> <element id="Extension"> <path value="Extension"/> <short value="LandmarkLocation"/> <definition value="The body location of the landmark, specified by a location code and optional laterality and orientation."/> <min value="0"/> <max value="*"/> <base> <path value="Extension"/> <min value="0"/> <max value="*"/> </base> <condition value="ele-1"/> <constraint> <key value="ele-1"/> <severity value="error"/> <human value="All FHIR elements must have a @value or children"/> <expression value="hasValue() or (children().count() > id.count())"/> <xpath value="@value|f:*|h:div"/> <source value="Element"/> </constraint> <constraint> <key value="ext-1"/> <severity value="error"/> <human value="Must have either extensions or value[x], not both"/> <expression value="extension.exists() != value.exists()"/> <xpath value="exists(f:extension)!=exists(f:*[starts-with(local-name(.), 'value')])"/> </constraint> <isModifier value="false"/> <mapping> <identity value="rim"/> <map value="n/a"/> </mapping> <mapping> <identity value="rim"/> <map value="N/A"/> </mapping> </element> <element id="Extension.id"> <path value="Extension.id"/> <representation value="xmlAttr"/> <short value="Unique id for inter-element referencing"/> <definition value="Unique id for the element within a resource (for internal references). This may be any string value that does not contain spaces."/> <min value="0"/> <max value="1"/> <base> <path value="Element.id"/> <min value="0"/> <max value="1"/> </base> <type> <code value="string"/> </type> <isModifier value="false"/> <isSummary value="false"/> <mapping> <identity value="rim"/> <map value="n/a"/> </mapping> </element> <element id="Extension.extension"> <path value="Extension.extension"/> <slicing> <discriminator> <type value="value"/> <path value="url"/> </discriminator> <description value="Extensions are always sliced by (at least) url"/> <rules value="open"/> </slicing> <short value="Additional content defined by implementations"/> <definition value="May be used to represent additional information that is not part of the basic definition of the element. To make the use of extensions safe and manageable, there is a strict set of governance applied to the definition and use of extensions. Though any implementer can define an extension, there is a set of requirements that SHALL be met as part of the definition of the extension."/> <comment value="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."/> <alias value="extensions"/> <alias value="user content"/> <min value="0"/> <max value="*"/> <base> <path value="Element.extension"/> <min value="0"/> <max value="*"/> </base> <type> <code value="Extension"/> </type> <isModifier value="false"/> <isSummary value="false"/> <mapping> <identity value="rim"/> <map value="n/a"/> </mapping> </element> <element id="Extension.extension:code"> <path value="Extension.extension"/> <sliceName value="code"/> <definition value="The main type identifier for a lab, procedure, condition, etc., usually drawn from a controlled vocabulary."/> <min value="0"/> <max value="1"/> <base> <path value="Element.extension"/> <min value="0"/> <max value="*"/> </base> <type> <code value="Extension"/> <profile value="http://hl7.org/fhir/us/breast-radiology/StructureDefinition/obf-datatype-Code-extension"/> </type> <isModifier value="false"/> <isSummary value="false"/> <mapping> <identity value="rim"/> <map value="n/a"/> </mapping> </element> <element id="Extension.extension:laterality"> <path value="Extension.extension"/> <sliceName value="laterality"/> <definition value="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)."/> <min value="0"/> <max value="1"/> <base> <path value="Element.extension"/> <min value="0"/> <max value="*"/> </base> <type> <code value="Extension"/> <profile value="http://hl7.org/fhir/us/breast-radiology/StructureDefinition/obf-datatype-Laterality-extension"/> </type> <isModifier value="false"/> <isSummary value="false"/> <mapping> <identity value="rim"/> <map value="n/a"/> </mapping> </element> <element id="Extension.extension:anatomicalorientation"> <path value="Extension.extension"/> <sliceName value="anatomicalorientation"/> <definition value="AnatomicalOrientation of the body location, if needed to distinguish from a similar location in another orientation. The orientation 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)."/> <min value="0"/> <max value="1"/> <base> <path value="Element.extension"/> <min value="0"/> <max value="*"/> </base> <type> <code value="Extension"/> <profile value="http://hl7.org/fhir/us/breast-radiology/StructureDefinition/obf-datatype-AnatomicalOrientation-extension"/> </type> <isModifier value="false"/> <isSummary value="false"/> <mapping> <identity value="rim"/> <map value="n/a"/> </mapping> </element> <element id="Extension.url"> <path value="Extension.url"/> <representation value="xmlAttr"/> <short value="identifies the meaning of the extension"/> <definition value="Source of the definition for the extension code - a logical name or a URL."/> <comment value="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."/> <min value="1"/> <max value="1"/> <base> <path value="Extension.url"/> <min value="1"/> <max value="1"/> </base> <type> <code value="uri"/> </type> <fixedUri value="http://hl7.org/fhir/us/breast-radiology/StructureDefinition/obf-datatype-LandmarkLocation-extension"/> <isModifier value="false"/> <isSummary value="false"/> <mapping> <identity value="rim"/> <map value="N/A"/> </mapping> </element> <element id="Extension.value[x]"> <path value="Extension.value[x]"/> <short value="Value of extension"/> <definition value="Value of extension - must be one of a constrained set of the data types (see [Extensibility](extensibility.html) for a list)."/> <min value="0"/> <max value="0"/> <base> <path value="Extension.value[x]"/> <min value="0"/> <max value="1"/> </base> <type> <code value="base64Binary"/> </type> <type> <code value="boolean"/> </type> <type> <code value="canonical"/> </type> <type> <code value="code"/> </type> <type> <code value="date"/> </type> <type> <code value="dateTime"/> </type> <type> <code value="decimal"/> </type> <type> <code value="id"/> </type> <type> <code value="instant"/> </type> <type> <code value="integer"/> </type> <type> <code value="markdown"/> </type> <type> <code value="oid"/> </type> <type> <code value="positiveInt"/> </type> <type> <code value="string"/> </type> <type> <code value="time"/> </type> <type> <code value="unsignedInt"/> </type> <type> <code value="uri"/> </type> <type> <code value="url"/> </type> <type> <code value="uuid"/> </type> <type> <code value="Address"/> </type> <type> <code value="Age"/> </type> <type> <code value="Annotation"/> </type> <type> <code value="Attachment"/> </type> <type> <code value="CodeableConcept"/> </type> <type> <code value="Coding"/> </type> <type> <code value="ContactPoint"/> </type> <type> <code value="Count"/> </type> <type> <code value="Distance"/> </type> <type> <code value="Duration"/> </type> <type> <code value="HumanName"/> </type> <type> <code value="Identifier"/> </type> <type> <code value="Money"/> </type> <type> <code value="Period"/> </type> <type> <code value="Quantity"/> </type> <type> <code value="Range"/> </type> <type> <code value="Ratio"/> </type> <type> <code value="Reference"/> </type> <type> <code value="SampledData"/> </type> <type> <code value="Signature"/> </type> <type> <code value="Timing"/> </type> <type> <code value="ContactDetail"/> </type> <type> <code value="Contributor"/> </type> <type> <code value="DataRequirement"/> </type> <type> <code value="Expression"/> </type> <type> <code value="ParameterDefinition"/> </type> <type> <code value="RelatedArtifact"/> </type> <type> <code value="TriggerDefinition"/> </type> <type> <code value="UsageContext"/> </type> <type> <code value="Dosage"/> </type> <isModifier value="false"/> <isSummary value="false"/> <mapping> <identity value="rim"/> <map value="N/A"/> </mapping> </element> </snapshot> <differential> <element id="Extension"> <path value="Extension"/> <short value="LandmarkLocation"/> <definition value="The body location of the landmark, specified by a location code and optional laterality and orientation."/> <min value="0"/> <max value="*"/> </element> <element id="Extension.extension:code"> <path value="Extension.extension"/> <sliceName value="code"/> <definition value="The main type identifier for a lab, procedure, condition, etc., usually drawn from a controlled vocabulary."/> <min value="0"/> <max value="1"/> <base> <path value="Element.extension"/> <min value="0"/> <max value="*"/> </base> <type> <code value="Extension"/> <profile value="http://hl7.org/fhir/us/breast-radiology/StructureDefinition/obf-datatype-Code-extension"/> </type> <isModifier value="false"/> <isSummary value="false"/> <mapping> <identity value="rim"/> <map value="n/a"/> </mapping> </element> <element id="Extension.extension:laterality"> <path value="Extension.extension"/> <sliceName value="laterality"/> <definition value="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)."/> <min value="0"/> <max value="1"/> <base> <path value="Element.extension"/> <min value="0"/> <max value="*"/> </base> <type> <code value="Extension"/> <profile value="http://hl7.org/fhir/us/breast-radiology/StructureDefinition/obf-datatype-Laterality-extension"/> </type> <isModifier value="false"/> <isSummary value="false"/> <mapping> <identity value="rim"/> <map value="n/a"/> </mapping> </element> <element id="Extension.extension:anatomicalorientation"> <path value="Extension.extension"/> <sliceName value="anatomicalorientation"/> <definition value="AnatomicalOrientation of the body location, if needed to distinguish from a similar location in another orientation. The orientation 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)."/> <min value="0"/> <max value="1"/> <base> <path value="Element.extension"/> <min value="0"/> <max value="*"/> </base> <type> <code value="Extension"/> <profile value="http://hl7.org/fhir/us/breast-radiology/StructureDefinition/obf-datatype-AnatomicalOrientation-extension"/> </type> <isModifier value="false"/> <isSummary value="false"/> <mapping> <identity value="rim"/> <map value="n/a"/> </mapping> </element> <element id="Extension.url"> <path value="Extension.url"/> <type> <code value="uri"/> </type> <fixedUri value="http://hl7.org/fhir/us/breast-radiology/StructureDefinition/obf-datatype-LandmarkLocation-extension"/> </element> <element id="Extension.value[x]"> <path value="Extension.value[x]"/> <min value="0"/> <max value="0"/> </element> </differential> </StructureDefinition>