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

Extension Associates the profile with a collection of Data Elements - Definition

URL for this extension: 

http://hl7.org/fhir/ExtensionDefinition/datadictionary

Status: draft

This extension associates a profile with a data dictionary - a collection of data elements that any instance of data that conforms to the profile must also conform to. The value of the extension is a uri the defines a query that identifies the collection of relevant data elements

This extension can be used on any profile of the resource types Observation and Questionnaire. THe profile specifies which elements are mandatory etc, but any elements in a resource that conforms to the profile must also conform to one of the defined data elements.

For Observation: * Observation.code must be associated with a matching Data Element by DataElement.code. * The profile should bind Observation.code to a value set that has the same codes as the collection of data elements (though it can be narrower) * the units and the quantity value should conform to the rules laid down in the matching Data Element

For Questionnaire: * todo.

Health Level Seven, Inc. - FHIR Core WG

usage info: todo

Extension Content

Structure

NameFlagsCard.TypeDescription & Constraintsdoco
.. extensionExtensionURL = http://hl7.org/fhir/ExtensionDefinition/datadictionary
Associates the profile with a collection of Data Elements: This extension associates a profile with a data dictionary - a collection of data elements that any instance of data that conforms to the profile must also conform to. The value of the extension is a uri the defines a query that identifies the collection of relevant data elements This extension can be used on any profile of the resource types Observation and Questionnaire. THe profile specifies which elements are mandatory etc, but any elements in a resource that conforms to the profile must also conform to one of the defined data elements. For Observation: * Observation.code must be associated with a matching Data Element by DataElement.code. * The profile should bind Observation.code to a value set that has the same codes as the collection of data elements (though it can be narrower) * the units and the quantity value should conform to the rules laid down in the matching Data Element For Questionnaire: * todo.
Use on element: Profile
..valueString 0..1stringAssociates the profile with a collection of Data Elements
Use on element: Profile

XML Template

<!-- Associates the profile with a collection of Data Elements -->doco

<extension xmlns="http://hl7.org/fhir"
     url="http://hl7.org/fhir/ExtensionDefinition/datadictionary" >
 <!-- from Element: extension -->
 <valueString value="[string]"/>
</extension>

JSON Template

// extension added to existing objectdoco

  "http://hl7.org/fhir/ExtensionDefinition/datadictionary" : { // Associates the profile with a collection of Data Elements
    "valueString" : ["<string>"] //Associates the profile with a collection of Data Elements
  }

Structure

NameFlagsCard.TypeDescription & Constraintsdoco
.. extensionExtensionURL = http://hl7.org/fhir/ExtensionDefinition/datadictionary
Associates the profile with a collection of Data Elements: This extension associates a profile with a data dictionary - a collection of data elements that any instance of data that conforms to the profile must also conform to. The value of the extension is a uri the defines a query that identifies the collection of relevant data elements This extension can be used on any profile of the resource types Observation and Questionnaire. THe profile specifies which elements are mandatory etc, but any elements in a resource that conforms to the profile must also conform to one of the defined data elements. For Observation: * Observation.code must be associated with a matching Data Element by DataElement.code. * The profile should bind Observation.code to a value set that has the same codes as the collection of data elements (though it can be narrower) * the units and the quantity value should conform to the rules laid down in the matching Data Element For Questionnaire: * todo.
Use on element: Profile
..valueString 0..1stringAssociates the profile with a collection of Data Elements
Use on element: Profile

XML Template

<!-- Associates the profile with a collection of Data Elements -->doco

<extension xmlns="http://hl7.org/fhir"
     url="http://hl7.org/fhir/ExtensionDefinition/datadictionary" >
 <!-- from Element: extension -->
 <valueString value="[string]"/>
</extension>

JSON Template

to do