cc-maternal-health-birth Use Case Guide

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

Skip to content

Main Navigation Use Case Overview Implementation Guidance Appendices DirectTrust Technical Docs Home

Appearance

Sidebar Navigation

About this Guide

0.2 What This Guide Defines and Reuses

0.3 How to Use This Guide

Use Case Overview

1.2 Information Exchange Objectives

1.3 Technical Feasibility and Scope

1.4 Approach Principles

Actors and Transactions

2.2 Transaction Participants and Participation Roles

2.3 Technology Components Supporting Transactions

2.4 Reusable Transaction Catalog

2.5 Objective-to-Transaction Matrix

2.6 Actor Transaction Diagrams

Transaction Framework

3.2 Transaction Model and Identifiers

3.3 Technical Actor Roles and Accountability

3.4 Transaction Processing Lifecycle and the Message to Payload Handoff

3.5 Workflow Unit and Structured Payload Architecture

3.6 Patient Identity Context and Information Classification

3.7 XD Metadata Requirements and Terminology Bindings

3.8 Message and Transport Requirements

3.9 Workflow Status and Processing Anomalies

3.10 Provenance Across the Transaction Lifecycle

3.11 Putting the Framework Together

Transaction Definitions

TX1: send-outpatient-visit-notification

TX2: send-admission-notification

TX3: send-birth-notification

TX4: send-discharge-notification

TX5: send-documents

TX6: query-for-documents

TX7: send-patient-update

TX8: send-workflow-status

Endpoint Capability Statement

4.2 MAP Endpoint CapabilityStatement Profile

4.3 Endpoint and Organization Identification

4.4 Supported Use Cases

4.5 Transaction Capabilities and Technical Actor Roles

4.6 Structured Payload Metadata Representation Capabilities

4.7 Metadata Representation Selection

4.8 Information Object and Human-Readable Communication Capabilities

4.9 Direct Message Delivery and Structured Payload Workflow Status

4.10 TX8 Workflow Status Capability

4.11 Identifier Capabilities

4.12 Terminology Capabilities

4.13 Intended Workflow

4.14 Endpoint Discovery and Capability Resolution

4.15 Testing and Operational Support

Implementation Guidance

5.2 Normative Boundary

5.3 Progressive Structuring and Narrative Interoperability

5.4 Implementation Roadmap

5.5 Implementing a Reusable Transaction

5.6 Endpoint Capability and Representation Selection

5.7 AI-Assisted and Autonomous Implementation Considerations

5.8 Conformance and Testing

5.9 Implementation Artifacts, Examples, and Tools

5.10 Implementation Checklist

5.11 Where to Go Next

Terms

T.2 Document Terminology

T.3 Workflow Transaction and Routing Terminology

T.4 Supporting Guidance

Appendices

Appendix A: Understanding Standardized Clinical Documents

Appendix B: Understanding Identity Context and Status

Appendix C: Understanding XD Classification Metadata

Appendix D: FHIR Collection Bundle Packaging

Appendix E: Understanding Document Lifecycle and Status

References

Vocabulary

Examples

Version History

On this page

4.4 Supported Use Cases

Explicitly declare support for cc-maternal-health-birth when the endpoint asserts conformance to this guide. A single endpoint MAY support multiple use cases. Use-case support does not imply support for every transaction or direction; those capabilities are declared separately.

Pager

Previous page4.3 Endpoint and Organization Identification

Next page4.5 Transaction Capabilities and Technical Actor Roles