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
This is an example form generated from the questionnaire. See also the XML or JSON format.
This is an example form generated from the questionnaire. See also the XML or JSON format
Logical id of this artefact |
Metadata about the resource
A set of rules under which this content was created |
language |
Text summary of the resource, for human interpretation
Contained, inline Resources
Globally unique logical id for concept map |
Additional identifier for the concept map
label: | |
system: | |
value: |
Logical id for this version of the concept map |
Informal name for this concept map |
Name of the publisher (Organization or individual) |
May be a web site, an email address, a telephone number (tel:), etc.
xml:id (or equivalent in JSON) |
Name of a individual to contact |
Contact details for individual or publisher
type: | |
value: | |
use: |
Human language description of the concept map |
Why is this needed? |
Use and/or Publishing restrictions |
status |
If for testing purposes, not real usage |
Date for given status |
Identifies the source of the concepts which are being mapped
type |
uri |
ValueSet |
|
Profile |
|
Provides context to the mappings
type |
uri |
ValueSet |
|
Profile |
|
Generally, the ideal is that there would only be one mapping for each concept in the source value set, but a given concept may be mapped mutliple times with different comments or dependencies.
xml:id (or equivalent in JSON) |
Code System (if value set crosses code systems) |
code |
xml:id (or equivalent in JSON) |
Reference to element/field/valueset mapping depends on |
Code System (if necessary) |
Value of the referenced element |
Ideally there would only be one map, with equal or equivalent mapping. But multiple maps are allowed for several narrower options, or to assert that other concepts are unmatched.
xml:id (or equivalent in JSON) |
System of the target (if necessary) |
code |
equivalence |
Description of status/issues in mapping |