The short answer is “no”. However, it’s important to more fully understand the relationship of “MU2 document types” and “C-CDA document templates”.

MU2 C-CDA Document Types
Refer to the article What are MU2 “document types”?, for a brief overview of the seven types of C-CDA documents defined by MU2.

The MU2 requirements guide to the use of valid C-CDA documents for these seven MU2 C-CDA document types, but allow for the use of any defined C-CDA document template that makes sense for any given MU2 C-CDA document.

MU2 Document Types Are Not Defined As CDA Templates
The MU2 “document type” serves largely the same purpose as a CDA document template. It provides CDA Header requirements and guides to which C-CDA section templates (and, thus, indirectly, which C-CDA entry templates) are optional or required in the CDA body.

Although they share a great deal in common with CDA document templates, these seven MU2 document types are not actually CDA document templates – they do not have template identifiers and they have not been declared/defined as CDA templates.

The S&I Framework C-CDA Companion Guide provides some recommendations (not requirements) as to which C-CDA document templates are a good fit for various MU2 document types.

MU2 Document Type is Not Declared in the Document
As just noted, MU2 “document types” are not defined as CDA templates and do not have CDA template identifiers. This means that the fact that a document is intended to meet the requirements for a given MU2 “document type” is NOT stated anywhere inside the C-CDA document itself.

Note also that the same C-CDA document instance (XML file) can potentially be valid for multiple MU2 document types.

MU2 C-CDA Validation Notes
When a C-CDA document is validated by the US government’s TTT Validator for MU2 C-CDA documents, it checks for conformance to the C-CDA US Realm Header template.

It does NOT, however, check that a C-CDA document template is used (let alone which C-CDA document template is used).

If conformance with a C-CDA template is asserted in the document (via declaration of the template identifier in ClinicalDocument/templateId) the TTT Validator will validate that the C-CDA template requirements are met. The reason for this is that complying with asserted templates at all levels is “part of being a valid C-CDA document” – it is not due to the fact that the given C-CDA document template is required by MU2.

No Internal MU Identification in a C-CDA
As noted above, nothing inside the C-CDA document indicates which MU2 document type (or types) it is intended to satisfy.

The validation of the C-CDA document against the requirements for a specific MU2 document type is triggered externally to the document – via the user interface of the validation tool or via meta data submitted with the C-CDA document.

There is no way to tell by inspecting a C-CDA document if it is used for MU2 (or MU1) and, if so, for which MU2 document type(s).

Other CDA PRO Know Articles Referenced In This Article

Related CDA PRO Learn Sessions