STU 3 Ballot

This page is part of the FHIR Specification (v1.6.0: STU 3 Ballot 4). 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

10.6 Resource BodySite - Content

Orders and Observations

Work Group

Maturity Level: 0

Compartments: Patient

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

10.6.1 Scope and Usage

DSTU Note: Feedback is welcome on whether BodySite should be an independent resource or a datatype to be used when a resource element is an anatomic location (for example Observation.bodySite)

Feedback is welcome here .

The BodySite resource contains details about the anatomical location of a specimen or body part, including patient information, identifiers, as well as text descriptons and images. It provides for the addition of modifiers such as laterality and directionality to the anatomic location for those use cases where precoordination of codes is not possible. The BodySite resource supports recording and tracking of an anatomic location or structure on a patient outside the context of another resource. For example it can be the target of a Procedure resource or Observation resource.

10.6.2 Boundaries and Relationships

The BodySite resource is not intended to substitute for precoordination of codes. If precoordination of codes is supported by an implementation and a resource element has a choice of codeableConcept or BodySite, the codeableConcept should be used. This resource is not intended for describing the type of anatomical location but rather a specific body site on a specific patient.

This resource is referenced by DeviceUseStatement, MedicationAdministration, MedicationDispense, MedicationOrder and MedicationStatement

Structure

Name	Flags	Card.	Type	Description & Constraints
BodySite			DomainResource	Specific and identified anatomical location
patient	Σ	1..1	Reference(Patient)	Patient
identifier	Σ	0..*	Identifier	Bodysite identifier
code	Σ	0..1	CodeableConcept	Named anatomical location SNOMED CT Body Structures (Example)
modifier		0..*	CodeableConcept	Modification to location code Bodysite Location Modifier (Example)
description	Σ	0..1	string	The Description of anatomical location
image		0..*	Attachment	Attached images
Documentation for this format

UML Diagram (Legend)

XML Template

<BodySite xmlns="http://hl7.org/fhir"> 
 <!-- from Resource: id, meta, implicitRules, and language -->
 <!-- from DomainResource: text, contained, extension, and modifierExtension -->
 <patient><!-- 1..1 Reference(Patient) Patient --></patient>
 <identifier><!-- 0..* Identifier Bodysite identifier --></identifier>
 <code><!-- 0..1 CodeableConcept Named anatomical location --></code>
 <modifier><!-- 0..* CodeableConcept Modification to location code --></modifier>
 <description value="[string]"/><!-- 0..1 The Description of anatomical location -->
 <image><!-- 0..* Attachment Attached images --></image>
</BodySite>

JSON Template

{
  "resourceType" : "BodySite",
  // from Resource: id, meta, implicitRules, and language
  // from DomainResource: text, contained, extension, and modifierExtension
  "patient" : { Reference(Patient) }, // R!  Patient
  "identifier" : [{ Identifier }], // Bodysite identifier
  "code" : { CodeableConcept }, // Named anatomical location
  "modifier" : [{ CodeableConcept }], // Modification to location code
  "description" : "<string>", // The Description of anatomical location
  "image" : [{ Attachment }] // Attached images
}

Turtle Template

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


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

  # from Resource: .id, .meta, .implicitRules, and .language
  # from DomainResource: .text, .contained, .extension, and .modifierExtension
  fhir:BodySite.patient [ Reference(Patient) ]; # 1..1 Patient
  fhir:BodySite.identifier [ Identifier ], ... ; # 0..* Bodysite identifier
  fhir:BodySite.code [ CodeableConcept ]; # 0..1 Named anatomical location
  fhir:BodySite.modifier [ CodeableConcept ], ... ; # 0..* Modification to location code
  fhir:BodySite.description [ string ]; # 0..1 The Description of anatomical location
  fhir:BodySite.image [ Attachment ], ... ; # 0..* Attached images
]

Changes since DSTU2

BodySite

No Changes

See the Full Difference for further information

Structure

Name	Flags	Card.	Type	Description & Constraints
BodySite			DomainResource	Specific and identified anatomical location
patient	Σ	1..1	Reference(Patient)	Patient
identifier	Σ	0..*	Identifier	Bodysite identifier
code	Σ	0..1	CodeableConcept	Named anatomical location SNOMED CT Body Structures (Example)
modifier		0..*	CodeableConcept	Modification to location code Bodysite Location Modifier (Example)
description	Σ	0..1	string	The Description of anatomical location
image		0..*	Attachment	Attached images
Documentation for this format

UML Diagram (Legend)

XML Template

<BodySite xmlns="http://hl7.org/fhir"> 
 <!-- from Resource: id, meta, implicitRules, and language -->
 <!-- from DomainResource: text, contained, extension, and modifierExtension -->
 <patient><!-- 1..1 Reference(Patient) Patient --></patient>
 <identifier><!-- 0..* Identifier Bodysite identifier --></identifier>
 <code><!-- 0..1 CodeableConcept Named anatomical location --></code>
 <modifier><!-- 0..* CodeableConcept Modification to location code --></modifier>
 <description value="[string]"/><!-- 0..1 The Description of anatomical location -->
 <image><!-- 0..* Attachment Attached images --></image>
</BodySite>

JSON Template

{
  "resourceType" : "BodySite",
  // from Resource: id, meta, implicitRules, and language
  // from DomainResource: text, contained, extension, and modifierExtension
  "patient" : { Reference(Patient) }, // R!  Patient
  "identifier" : [{ Identifier }], // Bodysite identifier
  "code" : { CodeableConcept }, // Named anatomical location
  "modifier" : [{ CodeableConcept }], // Modification to location code
  "description" : "<string>", // The Description of anatomical location
  "image" : [{ Attachment }] // Attached images
}

Turtle Template

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


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

  # from Resource: .id, .meta, .implicitRules, and .language
  # from DomainResource: .text, .contained, .extension, and .modifierExtension
  fhir:BodySite.patient [ Reference(Patient) ]; # 1..1 Patient
  fhir:BodySite.identifier [ Identifier ], ... ; # 0..* Bodysite identifier
  fhir:BodySite.code [ CodeableConcept ]; # 0..1 Named anatomical location
  fhir:BodySite.modifier [ CodeableConcept ], ... ; # 0..* Modification to location code
  fhir:BodySite.description [ string ]; # 0..1 The Description of anatomical location
  fhir:BodySite.image [ Attachment ], ... ; # 0..* Attached images
]

Changes since DSTU2

BodySite

No Changes

See the Full Difference for further information

Alternate definitions: Master Definition (XML, JSON), XML Schema/Schematron (for ) + JSON Schema, ShEx (for Turtle)

10.6.3.1 Terminology Bindings

Path	Definition	Type	Reference
BodySite.code	Codes describing anatomical locations. May include laterality	Example	SNOMED CT Body Structures
BodySite.modifier	Concepts modifying the anatomic location	Example	Bodysite Location Modifier

Path

Definition

Type

Reference

BodySite.code

Codes describing anatomical locations. May include laterality

Example

SNOMED CT Body Structures

BodySite.modifier

Concepts modifying the anatomic location

Example

Bodysite Location Modifier

10.6.4 Search Parameters

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

Name	Type	Description	Paths
code	token	Named anatomical location	BodySite.code
identifier	token	Identifier for this instance of the anatomical location	BodySite.identifier
patient	reference	Patient to whom bodysite belongs	BodySite.patient (Patient)