AssertionManagerGui

Id scheme	Assertion id	Status	Testable?	#Coverage	#Applies to	Predicate	Page	Tags	Last changed
1 2 3 4 5
ccdamu2	MU2-001	reviewed	Testable	0	0	MU2 prohibits the use of an unstructured document	18	Section 2.4	12/23/16 8:59:23 AM by
ccdamu2	MU2-002	reviewed	Testable	0	0	it is recommended to capture the name, identification number, and contact information along with codes to indicate the type of provider and role in the patient’s care	27	Section 3.2.1	12/23/16 8:59:23 AM by
ccdamu2	MU2-003	reviewed	Testable	0	0	it is recommended to capture care team member and provider name and contact information data requirements within participants associated with the clinical encounter or service event detailed in the document	28	Section 3.2.1	12/23/16 8:59:23 AM by
ccdamu2	MU2-004	reviewed	Testable	0	0	The ToC Initiative has determined the following elements within the componentOf/encompassingEncounter header element are recommended to capture Care Team Members, Provider Names and Contact Information, Date of Visit or Hospitalization Admission and Discharge Dates, and Location of Visit or Hospitalization MU2 data requirements	30	Section 3.2.2	12/23/16 8:59:23 AM by
ccdamu2	MU2-005	reviewed	Testable	0	0	The ToC Initiative has determined the following elements within the documentationOf/serviceEvent header element are recommended to capture service event Care Team Members and Provider Names and Contact Information MU2 data requirements	31	Section 3.2.3	12/23/16 8:59:23 AM by
ccdamu2	MU2-006	reviewed	Testable	0	0	MU2 constrains the preferred Language code to be drawn from the ISO 639 Part 2 alpha-3 codes limited to those that also have a corresponding alpha-2 code in ISO 639 Part 1. Use of codes with both alpha-3 and alpha-2 codes from the Language value set specified in Consolidated CDA meets this requirement.	32	Section 3.3.1	12/23/16 8:59:23 AM by
ccdamu2	MU2-007	reviewed	Testable	0	0	vendors are expected to code the “recordTarget/patientRole/Patient/raceCode” element using the following five categories : American Indian or Alaska Native (1002-5) Asian (2028-9) Black or African American (2054-5) Native Hawaiian or Other Pacific Islander (2076-8) White (2106-3).	33	Section 3.3.1	12/23/16 8:59:23 AM by
ccdamu2	MU2-008	reviewed	Testable	0	0	The ToC Initiative has determined the following elements within the recordTarget header element are recommended to capture Patient Name, Sex, Date of Birth, Preferred Language, Race, and Ethnicity MU2 data requirements.	33	Section 3.3.2	12/23/16 8:59:23 AM by
ccdamu2	MU2-009	reviewed	Testable	0	0	To capture the care planning data elements, the recommendation is to use the Plan of Care section	34	Section 3.4.1	12/23/16 8:59:23 AM by
ccdamu2	MU2-010	reviewed	Testable	0	0	In instances where the diagnostic test pending is a laboratory test, the use of LOINC® vocabulary is required for MU2 compliance.	34	Section 3.4.1	12/23/16 8:59:23 AM by
ccdamu2	MU2-011	reviewed	Testable	0	0	Plan of care (2.16.840.1.113883.10.20.22.2.10) is recommended to meet MU2 requirements	0	Section	12/23/16 8:59:23 AM by
ccdamu2	MU2-012	reviewed	Testable	0	0	In Conditions or Concers, Problems must be coded using SNOMED CT® 14 vocabulary	36	Section 3.5.1	12/23/16 8:59:23 AM by
ccdamu2	MU2-013	reviewed	Testable	0	0	In Conditions or Concern, Encounter Diagnoses must be coded using either SNOMED CT® or ICD-10-CM vocabularies	36	Section 3.5.1	12/23/16 8:59:23 AM by
ccdamu2	MU2-014	reviewed	Testable	0	0	Medication Allergies must be coded using RxNorm	36	Section 3.5.1	12/23/16 8:59:23 AM by
ccdamu2	MU2-015	reviewed	Testable	0	0	It is recommended that the Encounters with coded entries required be used in general; however for Hospital Discharge Summary the Hospital Discharge Diagnosis must be used. For the Operative Note and Procedure Note, the Post-operative Diagnosis and Post-procedure Diagnosis could be used respectively.	37	Section 3.5.2	12/23/16 8:59:23 AM by
ccdamu2	MU2-016	reviewed	Testable	0	0	Reason for Visit (2.16.840.1.113883.10.20.22.2.12) is recommended to be used to describe Reason of Visit MU2 Data requirement	38	Section 3.5.2	12/23/16 8:59:23 AM by
ccdamu2	MU2-017	reviewed	Testable	0	0	Immunizations are to be coded using the HL7 Standard Code Set CVX -- Vaccines Administered, with updates through July 11, 2012	40	Section 3.6.1	12/23/16 8:59:23 AM by
ccdamu2	MU2-018	reviewed	Testable	0	0	Medications and medications administered are to be coded using RxNorm, a standardized nomenclature for clinical drugs produced by the United States National Library of Medicine, August 6, 2012 Release	40	Section 3.6.1	12/23/16 8:59:23 AM by
ccdamu2	MU2-019	reviewed	Testable	0	0	Immunizations with coded entries required (2.16.840.1.113883.10.20.22.2.2.1) is recommended by MU2 data requirements	41	Section 3.6.2	12/23/16 8:59:23 AM by
ccdamu2	MU2-020	reviewed	Testable	0	0	Recommended medications sections are Medications Administered, Medications with coded entries required, Hospital Admission Medications, and Hospital Discharge Medications with coded entries required	41	Section 3.6.2	12/23/16 8:59:23 AM by

ccdamu2

MU2-001

reviewed

Testable

0

MU2 prohibits the use of an unstructured document

18

Section 2.4

12/23/16 8:59:23 AM by

ccdamu2

MU2-002

reviewed

Testable

0

it is recommended to capture the name, identification number, and contact information along with codes to indicate the type of provider and role in the patient’s care

27

Section 3.2.1

12/23/16 8:59:23 AM by

ccdamu2

MU2-003

reviewed

Testable

0

it is recommended to capture care team member and provider name and contact information data requirements within participants associated with the clinical encounter or service event detailed in the document

28

Section 3.2.1

12/23/16 8:59:23 AM by

ccdamu2

MU2-004

reviewed

Testable

0

The ToC Initiative has determined the following elements within the componentOf/encompassingEncounter header element are recommended to capture Care Team Members, Provider Names and Contact Information, Date of Visit or Hospitalization Admission and Discharge Dates, and Location of Visit or Hospitalization MU2 data requirements

30

Section 3.2.2

12/23/16 8:59:23 AM by

ccdamu2

MU2-005

reviewed

Testable

0

The ToC Initiative has determined the following elements within the documentationOf/serviceEvent header element are recommended to capture service event Care Team Members and Provider Names and Contact Information MU2 data requirements

31

Section 3.2.3

12/23/16 8:59:23 AM by

ccdamu2

MU2-006

reviewed

Testable

0

MU2 constrains the preferred Language code to be drawn from the ISO 639 Part 2 alpha-3 codes limited to those that also have a corresponding alpha-2 code in ISO 639 Part 1. Use of codes with both alpha-3 and alpha-2 codes from the Language value set specified in Consolidated CDA meets this requirement.

32

Section 3.3.1

12/23/16 8:59:23 AM by

ccdamu2

MU2-007

reviewed

Testable

0

vendors are expected to code the “recordTarget/patientRole/Patient/raceCode” element using the following five categories : American Indian or Alaska Native (1002-5) Asian (2028-9) Black or African American (2054-5) Native Hawaiian or Other Pacific Islander (2076-8) White (2106-3).

33

Section 3.3.1

12/23/16 8:59:23 AM by

ccdamu2

MU2-008

reviewed

Testable

0

The ToC Initiative has determined the following elements within the recordTarget header element are recommended to capture Patient Name, Sex, Date of Birth, Preferred Language, Race, and Ethnicity MU2 data requirements.

33

Section 3.3.2

12/23/16 8:59:23 AM by

ccdamu2

MU2-009

reviewed

Testable

0

To capture the care planning data elements, the recommendation is to use the Plan of Care section

34

Section 3.4.1

12/23/16 8:59:23 AM by

ccdamu2

MU2-010

reviewed

Testable

0

In instances where the diagnostic test pending is a laboratory test, the use of LOINC® vocabulary is required for MU2 compliance.

34

Section 3.4.1

12/23/16 8:59:23 AM by

ccdamu2

MU2-011

reviewed

Testable

0

Plan of care (2.16.840.1.113883.10.20.22.2.10) is recommended to meet MU2 requirements

0

Section

12/23/16 8:59:23 AM by

ccdamu2

MU2-012

reviewed

Testable

0

In Conditions or Concers, Problems must be coded using SNOMED CT® 14 vocabulary

36

Section 3.5.1

12/23/16 8:59:23 AM by

ccdamu2

MU2-013

reviewed

Testable

0

In Conditions or Concern, Encounter Diagnoses must be coded using either SNOMED CT® or ICD-10-CM vocabularies

36

Section 3.5.1

12/23/16 8:59:23 AM by

ccdamu2

MU2-014

reviewed

Testable

0

Medication Allergies must be coded using RxNorm

36

Section 3.5.1

12/23/16 8:59:23 AM by

ccdamu2

MU2-015

reviewed

Testable

0

It is recommended that the Encounters with coded entries required be used in general; however for Hospital Discharge Summary the Hospital Discharge Diagnosis must be used. For the Operative Note and Procedure Note, the Post-operative Diagnosis and Post-procedure Diagnosis could be used respectively.

37

Section 3.5.2

12/23/16 8:59:23 AM by

ccdamu2

MU2-016

reviewed

Testable

0

Reason for Visit (2.16.840.1.113883.10.20.22.2.12) is recommended to be used to describe Reason of Visit MU2 Data requirement

38

Section 3.5.2

12/23/16 8:59:23 AM by

ccdamu2

MU2-017

reviewed

Testable

0

Immunizations are to be coded using the HL7 Standard Code Set CVX -- Vaccines Administered, with updates through July 11, 2012

40

Section 3.6.1

12/23/16 8:59:23 AM by

ccdamu2

MU2-018

reviewed

Testable

0

Medications and medications administered are to be coded using RxNorm, a standardized nomenclature for clinical drugs produced by the United States National Library of Medicine, August 6, 2012 Release

40

Section 3.6.1

12/23/16 8:59:23 AM by

ccdamu2

MU2-019

reviewed

Testable

0

Immunizations with coded entries required (2.16.840.1.113883.10.20.22.2.2.1) is recommended by MU2 data requirements

41

Section 3.6.2

12/23/16 8:59:23 AM by

ccdamu2

MU2-020

reviewed

Testable

0

Recommended medications sections are Medications Administered, Medications with coded entries required, Hospital Admission Medications, and Hospital Discharge Medications with coded entries required

41

Section 3.6.2

12/23/16 8:59:23 AM by

Search Criteria : 242 assertions found for this search Review filtered assertions

Assertion

Applies to

Coverage