| Attribute | Schema Datatype or Enumeration | Usage | Definition | Business Rules |
|---|---|---|---|---|
| Type | text | Required | Categorization of external resources. Examples include: "ODM", "HL7-FHIR", "HL7-CDA", "HL7-v2", "OpenEHR-extract" | Extensible controlled terminology may be developed and published in the future. |
| Name | name | Required | The human readable identifier of the element or field in the external resource. Examples include : "ItemGroupDef" (for Type="ODM"), "Observation" (for Type="HL7-FHIR"), "substanceAdministration.doseQuantity" (for Type="HL7-CDA"), "OBX-5" (for field 5 ("Observation Result") for Type="HL7-v2"). | The value must be an existing element name or field name for the specific document or message type provided in the Type attribute. |
| Attribute | name | Optional | Field provided by the Name attribute where the data or information can be obtained. Examples are "valueQuantity.value" or "valueQuantity.unit" for the case of an HL7-FHIR "Observation", "Repeating" for the case of an ODM ItemGroupDef element, "unit" for the case of an HL7-CDA doseQuantity, "Code" or "Name" for the case of field 5 (which is composite) of an HL7-v2 OBX message. | The Name and Attribute attributes are are meant to provide traceability documentation. The Selection child element is meant to provide machine-executable instructions for extracting the information from the resource. |
.