Appearance
Message Metadata
Metadata in the SMTP Message Header
The derivative IG will set the values for:
x-direct-metadata-payload-versionIdentifier
x-direct-purpose
x-direct-useCase
x-direct-formatCode
x-direct-metadataTypeCode
x-direct-payloadMimeType
These elements are carried in the SMTP message header so that HISPs can report on transaction traffic based on this information and route or process messages more effectively.
| Metadata Element | Cardinality | Binding Strength | ValueSet (or Fixed Value) |
| x-direct-metadata-payload-versionIdentifier | 1..1 | n/a | Use the Version number of the Metadata and Payload Framework which the use case messages will conform to. |
| x-direct-purpose | 0..1 | Extensional | Purpose Code from either: Or Or |
| x-direct-useCase | 1...1 | Extensional | DirectTrust SERV_DESCVS |
| x-direct-formatCode | 0..1 | Extensional | Or |
| x-direct-metadataTypeCode | 1..1 | Extensional | DirectTrust Metadata Type Codes |
| x-direct-payloadMimeType | 0..* | Extensional | HL7 EndpointFHIRMimeTypes |
How to Comply to Minimum Requirements
When following the Metadata and Payloads Framework, the following table provides guidance on one way to meet the minimum requirements for messages that don’t conform to a specific derivative IG.
| Metadata Element | Cardinality | Binding Strength | ValueSet (or Fixed Value) |
| x-direct-metadata-payload-versionIdentifier | 1..1 | n/a | Use 1.0 |
| x-direct-useCase | 1..1 | Extensional | Use “any-all” |
| x-direct-metadataTypeCode | 1..1 | Extensional | Use urn:dt-org:dsm:map:SMTP+XD:1.0 for XD metadata Use “urn:dt-org:dsm:map:SMTP+CIG:1.0" for Context IG metadata. |