Appearance
Vocabulary
DirectTrust value sets
This catalog lists the 19 ValueSet resources in the DirectTrust Terminology and Artifacts Package V5.1 dated October 12, 2026. Use the names and canonical URL suffixes to locate their definitions in the package. Each description is reproduced exactly from the corresponding ValueSet definition. Applicable terminology bindings are specified in the guide and transaction requirements.
| ValueSet name and canonical URL suffix | Description |
|---|---|
DTContextTypeCodeValueSet DTContextTypeCodeVS | This value set includes all codes defined in the DTContextTypeCodeCS code system and selected IHE-defined CXi identifier type URNs for accession numbers, referrals, orders, DICOM studies, and encounters. The IHE URNs are represented using urn:ietf:rfc:3986 as specified by IHE ITI TF Volume 2 Appendix Z, Section Z.9.1.2. |
DTEndpointConnectionTypeValueSet DTEndpointConnectionTypeVS | This value set includes all codes defined in the DTEndpointConnectionTypeCS code system. |
DTFormatCodeValueSet DTFormatCodeVS | This value set includes all codes defined in the DTFormatCodeCS code system. |
DTTemporaryCodeValueSet DTTemporaryCodeVS | This value set includes all codes defined in the DTTemporaryCodeCS code system. |
FacetValueSet FacetVS | This value set includes all codes in the FacetCS code system. |
HispIDValueSet HispIdVS | This value set includes all codes defined in the HispIdCS code system. |
IalCodeValueSet IalCodeVS | This value set includes all codes defined in the IalCodeCS code system. |
LocationTypeExtensionalValueSet LocationTypeExtensionalVS | This extensionally defined value set includes all codes defined in the Service Delivery Location Role Type, Healthcare Service Location Type Combined, and CMS Place of Service value sets. These concepts are intended to be used to classify the type of Facility Location. |
LocationTypeValueSet LocationTypeVS | This intensionally defined value set includes all codes defined in the Service Delivery Location Role Type, Healthcare Service Location Type Combined, and CMS Place of Service value sets. These concepts are intended to be used to classify the type of Facility Location. |
MAPFailureReasonVS map-failure-reason | Initial shared MAP failure reasons for TX8 workflow status updates. Intended for an extensible binding in the consuming MAP specification or profile; binding strength is not a property of this ValueSet. |
MAPPatientChangeActionVS map-patient-change-action | The two permitted TX7 patient change actions. |
MetadataTypeValueSet MetadataTypeVS | This value set includes all codes defined in the MetadataTypeCS code system. |
OrgTypeValueSet OrgTypeVS | This value set includes DirectTrust Entity Type classification codes for organizational entities. It does not include, for example, the entity type for entities classified as an individual person acting in a personal capacity. |
ProvenanceActivityValueSet ProvenanceActivityVS | Twenty-one provenance activities: fifteen DirectTrust base-verb concepts and six externally defined concepts. External codes and source displays are preserved; DirectTrust designations use base verbs. |
ProvenanceAgentTypeValueSet ProvenanceAgentTypeVS | Fifteen agent participation types permitted by the DirectTrust provenance terminology model: twelve HL7 concepts and three DirectTrust concepts. Concepts are explicitly enumerated to support implementations that do not perform terminology-server expansion. |
ServDescValueSet ServDescVS | All codes from the ServDescCS Code System. |
SuffixValueSet SuffixVS | This value set includes all codes defined in the SuffixCS code system. |
| TaskInputVS | The four common MAP Task input type codes defined in TaskInputCS. Intended for an extensible binding to common Task.input.type in the consuming specification. Context-specific input types continue to use their established Context terminology. Binding strength is not encoded as a ValueSet property. |
TransactionTypesValueSet TransactionTypesVS | The value set of canonical DirectTrust transaction types. Concepts are enumerated extensionally to support implementations that do not perform terminology-server expansion. |