2nd DSTU Draft For Comment

This page is part of the FHIR Specification (v0.4.0: DSTU 2 Draft). 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: R3 R2

4.2 Resource BodySite - Content

This resource maintained by the Orders and Observations Work Group

Record details about the anatomical location of a specimen or body part, including precise localisation information. This resource may be used when a coded concept does not provide the necessary detail needed for the use case.

4.2.1 Scope and Usage

Record details about the anatomical location of a specimen or body part, including precise localisation information. This resource may be used when a coded concept does not provide the necessary detail needed for the use case.

4.2.2 Boundaries and Relationships

Todo

4.2.3 Background and Context

This resource is based upon the openEHR-EHR-CLUSTER.anatomical_location.v1 archetype. copyright openEHR Foundation. (openEHR Foundation is licensed under a Commons Attribution-ShareAlike 3.0 Unported License. ) ( EH todo :need to make the attribution is correct )

This resource is referenced by DeviceUseRequest, DeviceUseStatement, DiagnosticOrder, Observation, ProcedureRequest and Specimen

4.2.4 Resource Content

Structure

NameFlagsCard.TypeDescription & Constraintsdoco
.. BodySite DomainResourceSpecific and identified anatomical location
... identifier 0..*IdentifierBodysite identifier
... specificLocation 0..1ElementSpecific anatomical location
.... name 0..1CodeableConceptNamed anatomical location
BodySite (Example)
.... side 0..1CodeableConceptLaterality
Laterality (Example)
.... number 0..1integerWhich instance of many
.... anatomicalPlane 0..1CodeableConceptDescription of anatomical plane
AnatomicPlane (Example)
... relativeLocation 0..*ElementRelative anatomical location(s)
.... landmark 0..1CodeableConceptIdentified landmark Identified landmark Identified landmark
BodySite (Example)
.... aspect 0..1CodeableConceptRelative position to landmark
RelativeLocation (Example)
.... distance 0..1QuantityDistance from Landmark
... description 0..1stringThe Description of anatomical location
... image 0..*AttachmentAttached images

UML Diagram

BodySite (DomainResource)Identifier for this instance of the anatomical locationidentifier : Identifier 0..*Description of anatomical locationdescription : string 0..1Image or images used to identify a locationimage : Attachment 0..*SpecificLocationNamed anatomical location - ideally would be coded where possiblename : CodeableConcept 0..1 « (Codes describing anatomical locations. May include lateralityBodySite) »Specify lateraility of the anatomical locationside : CodeableConcept 0..1 « (Specify lateraility of the anatomical location.Laterality) »Identify the specific anatomical site out of multiple eg tenth rib; fourth vertebra; second toenumber : integer 0..1Line describing the position of a vertical anatomical plane in the bodyanatomicalPlane : CodeableConcept 0..1 « (Concepts describing anatomical plane in the bodyAnatomicPlane) »RelativeLocationIdentified anatomical landmark from which to specify relative anatomical locationlandmark : CodeableConcept 0..1 « (Codes describing anatomical locations. May include lateralityBodySite) »Qualifier to identify which direction the anatomical location is in relation to the identified landmarkaspect : CodeableConcept 0..1 « (Concepts describing the relative locatiion in relation to an identified anatomical landmarkRelativeLocation) »Distance of location from the identified landmarkdistance : Quantity 0..1The Specific and identified anatomical locationspecificLocation0..1Qualifiers to identify non-specific location eg 5cm (distance) inferior (aspect) to the tibial tuberosity (landmark). There may be more than one relative location required to provide a cross referencerelativeLocation0..*

XML Template

<BodySite xmlns="http://hl7.org/fhir"> doco
 <!-- from Resource: id, meta, implicitRules, and language -->
 <!-- from DomainResource: text, contained, extension, and modifierExtension -->
 <identifier><!-- 0..* Identifier Bodysite identifier --></identifier>
 <specificLocation>  <!-- 0..1 Specific anatomical location -->
  <name><!-- 0..1 CodeableConcept Named anatomical location --></name>
  <side><!-- 0..1 CodeableConcept Laterality --></side>
  <number value="[integer]"/><!-- 0..1 Which instance of many -->
  <anatomicalPlane><!-- 0..1 CodeableConcept Description of anatomical plane --></anatomicalPlane>
 </specificLocation>
 <relativeLocation>  <!-- 0..* Relative anatomical location(s) -->
  <landmark><!-- 0..1 CodeableConcept Identified landmark
Identified landmark
Identified landmark --></landmark>
  <aspect><!-- 0..1 CodeableConcept Relative position to landmark --></aspect>
  <distance><!-- 0..1 Quantity Distance from Landmark --></distance>
 </relativeLocation>
 <description value="[string]"/><!-- 0..1 The Description of anatomical location -->
 <image><!-- 0..* Attachment Attached images --></image>
</BodySite>

JSON Template

{doco
  "resourceType" : "BodySite",
  // from Resource: id, meta, implicitRules, and language
  // from DomainResource: text, contained, extension, and modifierExtension
  "identifier" : [{ Identifier }], // Bodysite identifier
  "specificLocation" : { // Specific anatomical location
    "name" : { CodeableConcept }, // Named anatomical location
    "side" : { CodeableConcept }, // Laterality
    "number" : <integer>, // Which instance of many
    "anatomicalPlane" : { CodeableConcept } // Description of anatomical plane
  },
  "relativeLocation" : [{ // Relative anatomical location(s)
    "landmark" : { CodeableConcept }, // Identified landmark
Identified landmark
Identified landmark
    "aspect" : { CodeableConcept }, // Relative position to landmark
    "distance" : { Quantity } // Distance from Landmark
  }],
  "description" : "<string>", // The Description of anatomical location
  "image" : [{ Attachment }] // Attached images
}

Structure

NameFlagsCard.TypeDescription & Constraintsdoco
.. BodySite DomainResourceSpecific and identified anatomical location
... identifier 0..*IdentifierBodysite identifier
... specificLocation 0..1ElementSpecific anatomical location
.... name 0..1CodeableConceptNamed anatomical location
BodySite (Example)
.... side 0..1CodeableConceptLaterality
Laterality (Example)
.... number 0..1integerWhich instance of many
.... anatomicalPlane 0..1CodeableConceptDescription of anatomical plane
AnatomicPlane (Example)
... relativeLocation 0..*ElementRelative anatomical location(s)
.... landmark 0..1CodeableConceptIdentified landmark Identified landmark Identified landmark
BodySite (Example)
.... aspect 0..1CodeableConceptRelative position to landmark
RelativeLocation (Example)
.... distance 0..1QuantityDistance from Landmark
... description 0..1stringThe Description of anatomical location
... image 0..*AttachmentAttached images

UML Diagram

BodySite (DomainResource)Identifier for this instance of the anatomical locationidentifier : Identifier 0..*Description of anatomical locationdescription : string 0..1Image or images used to identify a locationimage : Attachment 0..*SpecificLocationNamed anatomical location - ideally would be coded where possiblename : CodeableConcept 0..1 « (Codes describing anatomical locations. May include lateralityBodySite) »Specify lateraility of the anatomical locationside : CodeableConcept 0..1 « (Specify lateraility of the anatomical location.Laterality) »Identify the specific anatomical site out of multiple eg tenth rib; fourth vertebra; second toenumber : integer 0..1Line describing the position of a vertical anatomical plane in the bodyanatomicalPlane : CodeableConcept 0..1 « (Concepts describing anatomical plane in the bodyAnatomicPlane) »RelativeLocationIdentified anatomical landmark from which to specify relative anatomical locationlandmark : CodeableConcept 0..1 « (Codes describing anatomical locations. May include lateralityBodySite) »Qualifier to identify which direction the anatomical location is in relation to the identified landmarkaspect : CodeableConcept 0..1 « (Concepts describing the relative locatiion in relation to an identified anatomical landmarkRelativeLocation) »Distance of location from the identified landmarkdistance : Quantity 0..1The Specific and identified anatomical locationspecificLocation0..1Qualifiers to identify non-specific location eg 5cm (distance) inferior (aspect) to the tibial tuberosity (landmark). There may be more than one relative location required to provide a cross referencerelativeLocation0..*

XML Template

<BodySite xmlns="http://hl7.org/fhir"> doco
 <!-- from Resource: id, meta, implicitRules, and language -->
 <!-- from DomainResource: text, contained, extension, and modifierExtension -->
 <identifier><!-- 0..* Identifier Bodysite identifier --></identifier>
 <specificLocation>  <!-- 0..1 Specific anatomical location -->
  <name><!-- 0..1 CodeableConcept Named anatomical location --></name>
  <side><!-- 0..1 CodeableConcept Laterality --></side>
  <number value="[integer]"/><!-- 0..1 Which instance of many -->
  <anatomicalPlane><!-- 0..1 CodeableConcept Description of anatomical plane --></anatomicalPlane>
 </specificLocation>
 <relativeLocation>  <!-- 0..* Relative anatomical location(s) -->
  <landmark><!-- 0..1 CodeableConcept Identified landmark
Identified landmark
Identified landmark --></landmark>
  <aspect><!-- 0..1 CodeableConcept Relative position to landmark --></aspect>
  <distance><!-- 0..1 Quantity Distance from Landmark --></distance>
 </relativeLocation>
 <description value="[string]"/><!-- 0..1 The Description of anatomical location -->
 <image><!-- 0..* Attachment Attached images --></image>
</BodySite>

JSON Template

{doco
  "resourceType" : "BodySite",
  // from Resource: id, meta, implicitRules, and language
  // from DomainResource: text, contained, extension, and modifierExtension
  "identifier" : [{ Identifier }], // Bodysite identifier
  "specificLocation" : { // Specific anatomical location
    "name" : { CodeableConcept }, // Named anatomical location
    "side" : { CodeableConcept }, // Laterality
    "number" : <integer>, // Which instance of many
    "anatomicalPlane" : { CodeableConcept } // Description of anatomical plane
  },
  "relativeLocation" : [{ // Relative anatomical location(s)
    "landmark" : { CodeableConcept }, // Identified landmark
Identified landmark
Identified landmark
    "aspect" : { CodeableConcept }, // Relative position to landmark
    "distance" : { Quantity } // Distance from Landmark
  }],
  "description" : "<string>", // The Description of anatomical location
  "image" : [{ Attachment }] // Attached images
}

 

Alternate definitions: Schema/Schematron, Resource Profile (XML, JSON), Questionnaire

4.2.4.1 Terminology Bindings

PathDefinitionTypeReference
BodySite.specificLocation.name
BodySite.relativeLocation.landmark 		Codes describing anatomical locations. May include lateralityExamplehttp://hl7.org/fhir/vs/body-site
BodySite.specificLocation.side Specify lateraility of the anatomical location.Examplehttp://hl7.org/fhir/vs/bodysite-laterality
BodySite.specificLocation.anatomicalPlane Concepts describing anatomical plane in the bodyExamplehttp://hl7.org/fhir/vs/bodysite-anatomic-plane
BodySite.relativeLocation.aspect Concepts describing the relative locatiion in relation to an identified anatomical landmarkExamplehttp://hl7.org/fhir/vs/bodysite-relative-location

4.2.5 Search Parameters

Search parameters for this resource. The common parameters also apply. See Searching for more information about searching in REST, messaging, and services.

NameTypeDescriptionPaths
nametokenNamed anatomical locationBodySite.specificLocation.name