DSTU2 QA Preview
This page is part of the FHIR Specification (v1.0.0: DSTU 2 Ballot 3). The current version which supercedes this version is 5.0.0. For a full list of available versions, see the Directory of published versions 
StructureDefinition for Profile of BodySite for decision support/quality metrics. Defines the core set of elements and extensions for quality rule and measure authors.
{
"resourceType": "StructureDefinition",
"id": "qicore-bodysite",
"text": {
"status": "generated",
"div": "<div>!-- Snipped for Brevity --></div>"
},
"url": "http://hl7.org/fhir/StructureDefinition/qicore-bodysite",
"name": "QICore-BodySite",
"status": "draft",
"publisher": "Health Level Seven International (Clinical Quality Information - QICore)",
"contact": [
{
"telecom": [
{
"system": "other",
"value": "http://hl7.org/special/committees/CQI"
}
]
}
],
"date": "2015-03-11",
"description": "Profile of BodySite for decision support/quality metrics. Defines the core set of elements and extensions for quality rule and measure authors.",
"mapping": [
{
"identity": "qdm",
"uri": "http://www.healthit.gov/quality-data-model",
"name": "Quality Data Model"
}
],
"kind": "resource",
"constrainedType": "BodySite",
"abstract": false,
"base": "http://hl7.org/fhir/StructureDefinition/BodySite",
"snapshot": {
"element": [
{
"path": "BodySite",
"name": "QICore-BodySite",
"short": "Specific and identified anatomical location",
"definition": "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.",
"alias": [
"anatomical location"
],
"min": 0,
"max": "*",
"base": {
"path": "BodySite",
"min": 0,
"max": "*"
},
"type": [
{
"code": "BodySite"
}
],
"mapping": [
{
"identity": "openehr",
"map": "Archetype ID openEHR-EHR-CLUSTER.anatomical_location.v1 Concept name Anatomical Location Concept description Record details about an anatomical location. Keywords location, site, anatomical Copyright © openEHR Foundation Purpose To record details about anatomical location. Misuse Not for specifiying unilateral/bilateral occurence - this is related to an evaluation which perhaps includes multiple locations. Author Author name: Heather Leslie Organisation: Ocean Informatics Email: heather.leslie@oceaninformatics.com Date of Origination: 2008-11-10 Translator Norwegian Bokmål: Lars Bitsch-Larsen, Haukeland University Hospital of Bergen, Norway, MD, DEAA, MBA, spec in anesthesia, spec in tropical medicine. Arabic (Syria): Mona Saleh Other contributors Heather Leslie, Ocean Informatics, Australia (Editor) Ian McNicoll, freshEHR Clinical Informatics, United Kingdom (Editor) Dunmail Hodkinson, Black Pear Software Ltd, UK References Use cases: - 5LICS, midclavicular line - L forearm, 2cm anterior to the cubital fossa - Right iliac fossa - 5 cm below L tibial tuberosity - 2 cm medial to R nipple - 4 cm below R costal margin in midclavicular line - R femur - midline nose - medial aspect of R great toe nail."
},
{
"identity": "w5",
"map": "clinical.diagnostics"
},
{
"identity": "qdm",
"map": "Device.anatomical location site or Device.anatomical approach site or Procedure.anatomical approach site or Procedure.approach site"
}
]
},
{
"path": "BodySite.id",
"short": "Logical id of this artifact",
"definition": "The logical id of the resource, as used in the url for the resource. Once assigned, this value never changes.",
"comments": "The only time that a resource does not have an id is when it is being submitted to the server using a create operation. Bundles always have an id, though it is usually a generated UUID.",
"min": 0,
"max": "1",
"base": {
"path": "BodySite.id",
"min": 0,
"max": "1"
},
"type": [
{
"code": "id"
}
],
"isSummary": true
},
{
"path": "BodySite.meta",
"short": "Metadata about the resource",
"definition": "The metadata about the resource. This is content that is maintained by the infrastructure. Changes to the content may not always be associated with version changes to the resource.",
"min": 0,
"max": "1",
"base": {
"path": "BodySite.meta",
"min": 0,
"max": "1"
},
"type": [
{
"code": "Meta"
}
],
"isSummary": true
},
{
"path": "BodySite.implicitRules",
"short": "A set of rules under which this content was created",
"definition": "A reference to a set of rules that were followed when the resource was constructed, and which must be understood when processing the content.",
"comments": "Asserting this rule set restricts the content to be only understood by a limited set of trading partners. This inherently limits the usefulness of the data in the long term. However the existing health eco-system is highly fractured, and not yet ready to define, collect, and exchange data in a generally computable sense. Wherever possible, implementers and/or specification writers should avoid using this element as much as possible.",
"min": 0,
"max": "1",
"base": {
"path": "BodySite.implicitRules",
"min": 0,
"max": "1"
},
"type": [
{
"code": "uri"
}
],
"isModifier": true,
"isSummary": true
},
{
"path": "BodySite.language",
"short": "Language of the resource content",
"definition": "The base language in which the resource is written.",
"comments": "Language is provided to support indexing and accessibility (typically, services such as text to speech use the language tag). The html language tag in the narrative applies to the narrative. The language tag on the resource may be used to specify the language of other presentations generated from the data in the resource Not all the content has to be in the base language. The Resource.language should not be assumed to apply to the narrative automatically. If a language is specified, it should it also be specified on the div element in the html (see rules in HTML5 for information about the relationship between xml:lang and the html lang attribute).",
"min": 0,
"max": "1",
"base": {
"path": "BodySite.language",
"min": 0,
"max": "1"
},
"type": [
{
"code": "code"
}
],
"binding": {
"strength": "required",
"description": "A human language",
"valueSetUri": "http://tools.ietf.org/html/bcp47"
}
},
{
"path": "BodySite.text",
"short": "Text summary of the resource, for human interpretation",
"definition": "A human-readable narrative that contains a summary of the resource, and may be used to represent the content of the resource to a human. The narrative need not encode all the structured data, but is required to contain sufficient detail to make it \"clinically safe\" for a human to just read the narrative. Resource definitions may define what content should be represented in the narrative to ensure clinical safety.",
"comments": "Contained resources do not have narrative. Resources that are not contained SHOULD have a narrative.",
"alias": [
"narrative",
"html",
"xhtml",
"display"
],
"min": 0,
"max": "1",
"base": {
"path": "BodySite.text",
"min": 0,
"max": "1"
},
"type": [
{
"code": "Narrative"
}
],
"condition": [
"dom-1"
],
"mapping": [
{
"identity": "rim",
"map": "Act.text?"
}
]
},
{
"path": "BodySite.contained",
"short": "Contained, inline Resources",
"definition": "These resources do not have an independent existence apart from the resource that contains them - they cannot be identified independently, and nor can they have their own independent transaction scope.",
"comments": "This should never be done when the content can be identified properly, as once identification is lost, it is extremely difficult (and context dependent) to restore it again.",
"alias": [
"inline resources",
"anonymous resources",
"contained resources"
],
"min": 0,
"max": "*",
"base": {
"path": "BodySite.contained",
"min": 0,
"max": "*"
},
"type": [
{
"code": "Resource"
}
],
"mapping": [
{
"identity": "rim",
"map": "N/A"
}
]
},
{
"path": "BodySite.extension",
"short": "Additional Content defined by implementations",
"definition": "May be used to represent additional information that is not part of the basic definition of the resource. In order 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 is allowed to define an extension, there is a set of requirements that SHALL be met as part of the definition of the extension.",
"comments": "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": [
"extensions",
"user content"
],
"min": 0,
"max": "*",
"base": {
"path": "BodySite.extension",
"min": 0,
"max": "*"
},
"type": [
{
"code": "Extension"
}
],
"mapping": [
{
"identity": "rim",
"map": "N/A"
}
]
},
{
"path": "BodySite.modifierExtension",
"short": "Extensions that cannot be ignored",
"definition": "May be used to represent additional information that is not part of the basic definition of the resource, and that modifies the understanding of the element that contains it. Usually modifier elements provide negation or qualification. In order 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 is allowed to define an extension, there is a set of requirements that SHALL be met as part of the definition of the extension. Applications processing a resource are required to check for modifier extensions.",
"comments": "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": [
"extensions",
"user content"
],
"min": 0,
"max": "*",
"base": {
"path": "BodySite.modifierExtension",
"min": 0,
"max": "*"
},
"type": [
{
"code": "Extension"
}
],
"isModifier": true,
"mapping": [
{
"identity": "rim",
"map": "N/A"
}
]
},
{
"path": "BodySite.patient",
"short": "Patient",
"definition": "The person to which the body site belongs.",
"min": 1,
"max": "1",
"base": {
"path": "BodySite.patient",
"min": 1,
"max": "1"
},
"type": [
{
"code": "Reference",
"profile": [
"http://hl7.org/fhir/StructureDefinition/Patient"
]
}
],
"mustSupport": true,
"isSummary": true
},
{
"path": "BodySite.identifier",
"short": "Bodysite identifier",
"definition": "Identifier for this instance of the anatomical location.",
"min": 0,
"max": "*",
"base": {
"path": "BodySite.identifier",
"min": 0,
"max": "*"
},
"type": [
{
"code": "Identifier"
}
],
"isSummary": true,
"mapping": [
{
"identity": "openehr",
"map": "Specific location Cluster Optional (0..1) Cardinality: Mandatory, repeating, unordered (1..*)"
}
]
},
{
"path": "BodySite.code",
"short": "Named anatomical location",
"definition": "Named anatomical location - ideally would be coded where possible.",
"min": 0,
"max": "1",
"base": {
"path": "BodySite.code",
"min": 0,
"max": "1"
},
"type": [
{
"code": "CodeableConcept"
}
],
"mustSupport": true,
"isSummary": true,
"binding": {
"strength": "example",
"description": "Codes describing anatomical locations. May include laterality",
"valueSetReference": {
"reference": "http://hl7.org/fhir/ValueSet/body-site"
}
},
"mapping": [
{
"identity": "openehr",
"map": "Name of location"
}
]
},
{
"path": "BodySite.modifier",
"short": "Modification to location code",
"definition": "Modifier to refine the anatomical location. These include modifiers for laterality, relative location, directionality, number, and plane.",
"min": 0,
"max": "*",
"base": {
"path": "BodySite.modifier",
"min": 0,
"max": "*"
},
"type": [
{
"code": "CodeableConcept"
}
],
"mustSupport": true,
"binding": {
"strength": "example",
"description": "Concepts modifying the anatomic location",
"valueSetReference": {
"reference": "http://hl7.org/fhir/ValueSet/bodysite-relative-location"
}
},
"mapping": [
{
"identity": "openehr",
"map": "Combines Side, Numerical identifier, Anatomical plane,and Aspect"
}
]
},
{
"path": "BodySite.description",
"short": "The Description of anatomical location",
"definition": "Description of anatomical location.",
"comments": "This Description could include any visual markings used to orientate the viewer e.g external reference points, special sutures, ink markings.",
"min": 0,
"max": "1",
"base": {
"path": "BodySite.description",
"min": 0,
"max": "1"
},
"type": [
{
"code": "string"
}
],
"isSummary": true,
"mapping": [
{
"identity": "openehr",
"map": "Description of anatomical location/Visual markings/orientation"
}
]
},
{
"path": "BodySite.image",
"short": "Attached images",
"definition": "Image or images used to identify a location.",
"min": 0,
"max": "*",
"base": {
"path": "BodySite.image",
"min": 0,
"max": "*"
},
"type": [
{
"code": "Attachment"
}
],
"mapping": [
{
"identity": "openehr",
"map": "Image"
}
]
}
]
},
"differential": {
"element": [
{
"path": "BodySite",
"name": "QICore-BodySite",
"min": 0,
"max": "*",
"type": [
{
"code": "BodySite"
}
],
"mapping": [
{
"identity": "qdm",
"map": "Device.anatomical location site or Device.anatomical approach site or Procedure.anatomical approach site or Procedure.approach site"
}
]
},
{
"path": "BodySite.patient",
"mustSupport": true
},
{
"path": "BodySite.code",
"mustSupport": true
},
{
"path": "BodySite.modifier",
"mustSupport": true
}
]
}
}
© HL7.org 2011+. FHIR DSTU2 (v1.0.0-6850) generated on Tue, Sep 1, 2015 14:42+1000.
Links: What's a DSTU? |
Version History |
Table of Contents |
Compare to DSTU1 |
|
Propose a change