DRAFT Working draft of an upcoming version. Not the published standard. View the current published version

Skip to content

Main Navigation About This Framework Transaction Framework Implementation Guidance Appendices DirectTrust Technical Docs Home

Appearance

Sidebar Navigation

About this Guide

0.2 What This Framework Defines and Reuses

0.3 How to Use This Framework

0.4 Framework Evolution and Development History

0.5 Open Issues and Resolution Tracking

Overview

1-1-purpose

1-2-objectives

1.3 Feasibility and Scope

1.4 Foundational Principles

1-5-requirements-and-conformance

Actors and Transactions

2.1 Business Entities and Information Exchange Roles

2.2 Technical Actors and System Actor Roles

2.3 Actor Formations and Organizational Relationships

2.4 Transaction Interactions and Information Flow

2.5 Transaction Listing (Reusable Transactions Catalog)

2.6 Diagrams and Examples

Common Transaction Architecture and Requirements

3.1 Transaction Definition Architecture

3.2 Transaction Model and Identification

3.3 Transaction Actors and Responsibilities

3.4 Transaction Processing and Information Exchange

3.5 Direct Message Packaging, Structured Payload, and Metadata Architecture

MAP Reusable Transactions Catalog

send-documents

send-patient-update

send-visit-notification

send-workflow-status — Generalized Transaction Definition

Endpoint Capability and Discovery

4.1 Purpose and Scope

4.2 Human-Readable Endpoint Capability Descriptions

4.3 Recommended Capability Description Content

4.4 Endpoint Discovery and Capability Interpretation

4.5 Optional Machine-Processable CapabilityStatements

4.6 Relationship to Transaction Requirements and Conformance

Implementation Guidance

5.1 Applying the MAP Framework

5.2 Implementation and Verification Approach

5.3 Supporting Resources

Terms

T.2 Document and Information Terminology

T.3 Use Case, Transaction, Workflow, and Routing Terminology

T.4 Supporting Guidance and Terminology Relationships

T.5 Acronyms and Abbreviations

Appendices

Appendix D — FHIR Metadata and Payload Mapping

D.1 Core Packaging Pattern

D.2 Bundle Requirements

D.3 SubmissionSet to FHIR List Mapping

D.4 DocumentEntry to FHIR DocumentReference Mapping

D.5 Representing the Payload Objects

D.6 Provenance Collection Bundles and Target Resolution

D.7 Mapping Constraints and Conformance

References

Vocabulary

Examples

Templates

Version History

On this page

Chapter 09 — Vocabulary

This chapter provides a landing place for shared code systems, value sets, and terminology bindings used by the MAP Framework. Binding requirements remain governed by the applicable technical specifications and transaction definitions; no new bindings are established by this landing page.

Pager

Previous pageReferences

Next pageExamples