Page History

...

This implementation guide uses existing standards and specifications to enable the sharing of clinical content and the minimal workflow information for the closed-loop referral use case.

...

The following XDM data types represent a single value, and can be referenced directly from within a field in a given attribute, or they can be components of a complex data type. When viewing the attribute descriptions below, the expansion stops at a base data type.

6.1.2 Submission Set Requirements

...

Data and Section requirements for 360x: 360X requires a valid CCDA C-CDA per HL7 C-CDA R2.1 IG and, therefore, the section conventions that that IG defines take precedence. The only requirement that 360X levies on the referral request and the request closure documents beyond the HL7 CCDA C-CDA R2.1 IG is that:

• Every referral request must have a non-null reason for referral section (R)
• Every closure of a request must have a non-null response to the question asked in the reason for referral and the recommendation is to include that content in the Results section.

Data and Section information: We have provided an Appendix provided Appendix B for document types and sections in support of your development to 360X and comparison of it to any development toward the ONC 2015 Edition specifications. This is for information only. Three document types are reviewed:

...

For the Consultation note, only 2 two columns are provided; HL7 IG and AMA input, since the ONC 2015 Edition does not define a Consultation Note as a required document template.

...

The complete specification for the HL7 Version 2.x messages is in Appendix C. The following is a summary of the messages used in the various transactions. This section contains the required content according to this implementation guide. It is intended as a summary reference.

Proposal (Hans Buitendijk): Change MSH-4 and MSH-6 optional; pre-adopt MSH-22 and MSH-23 where MSH-22 is R and MSH-23 is RE.  This will allow distinction between physical facility vs. organization where we know organization to send the request/etc., but not the facility.

6.3.1 Base Data Types

The following data types represent a single value, and can be referenced directly from within a field in a given segment, or they can be components of a complex data type. When viewing the message and segment descriptions below, the expansion stops at a base data type.

...