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

Appearance

T.4 Supporting Guidance and Terminology Relationships ​

This section directs readers to the specifications that establish implementation requirements and to supporting material that illustrates the terminology. Definitions establish meaning; they do not silently create new obligations or supersede the governing standards.

T.4.1 Relationship to Normative Requirements ​

Chapter 3 establishes common transaction architecture and technical requirements. Governed Generalized Transaction Definitions (GenTXDefs) in the Reusable Transaction Catalog (RTC) and the applicable Use Case Transaction Definitions (UCTXDefs) specify additional or constrained requirements. Chapter 2 applies the T.3 distinctions among business entities, grouped technical actors, Routing Targets, and provenance agents when describing exchanges and diagrams. Terms defined here do not turn conditional reporting or use case-specific processing into universal requirements.

T.4.2 Relationship to Vocabulary and Code Systems ​

The vocabulary chapter and applicable terminology packages identify code systems, value sets, and bindings. A conceptual term in Chapter T does not by itself establish a binding, cardinality, or encoded field requirement. Authors must use exact terminology and field names when establishing conformance rules.

Appendix A explains standardized document concepts; Appendix B covers identity and context; Appendix C covers document classification metadata; Appendix D explains structured payload packaging mappings; and Appendix E explains document lifecycle, status, and provenance. Additional appendices cover demographic representation, Direct transport, and intermediated exchange. All appendices are collected under Chapter 7.