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


Applies to

Applied to
Not applied to


Covered by
Not covered by
Id scheme
Assertion id
#Applies to
Last changed
ITI31ITI31-004validatedTestable 0 2 Both the Patient Encounter Supplier and Patient Encounter Consumer actors shall be able to cancel only a current movement.43Section 3.31.44/4/16 12:24:34 PM by aberge
ITI31ITI31-005validatedTestable 0 1 A system implementing either Patient Encounter Supplier or Patient Encounter Consumer, shall support these 5 trigger events: Admit inpatient, Discharge patient, Register outpatient, Cancel admit/visit, Cancel discharge44Figure 3.31-14/4/16 12:24:36 PM by aberge
ITI31ITI31-006validatedTestable 0 2 A system implementing Inpatient/Outpatient encounter management option shall support the 11 trigger events and messages defined in table 3.31-2.45Table 3.31-24/4/16 12:26:39 PM by aberge
ITI31ITI31-008validatedTestable 0 2 A system implementing the Pending Event Managament option shall support the 17 trigger events and messages defined in table 3.31-346Table 3.31-34/4/16 11:48:34 AM by aberge
ITI31ITI31-009validatedTestable 0 2 A system implementing Advanced Encounter Management Option shall support the12 trigger events and messages defined in table 3.31-447Table 3-31-44/4/16 12:31:47 PM by aberge
ITI31ITI31-010validatedTestable 0 2 A system implementing Temporary Patient Transfers Tracking Option shall support the 9 trigger events and messages defined in table 3.31-548Section 3.31-54/4/16 11:48:40 AM by aberge
ITI31ITI31-012validatedTestable 0 2 The ZBE segment is required for the following trigger events : A01, A02, A03, A04, A05, A06, A07, A11, A12, A13, A14, A15, A16, A21, A22, A25, A26, A27, A38, A52, A53, A54, A55, Z99 if the historic movement management option is supported49Section 12:25:24 PM by aberge
ITI31ITI31-014validatedTestable 0 2 I don't think we are testing this option in 2016 cycle, might be out of scopeIf the Patient Encounter Supplier supports the Ambulatory Patient Data Option, it SHALL supply: the patient address in field PID-11 for ambulatory patients whenever this address is known the referring doctor in field PV1-8, if known, when registering an outpatient (MSH-9 Message Type is ADT^A04) or when pre-registering a patient (MSH-9 Message Type is ADT^A05) the ambulatory status of the patient into field PV1-15 if this information is known.50Section 11:48:47 AM by aberge
ITI31ITI31-015validatedTestable 0 1 A Patient Encounter Supplier or Patient Encounter Consumer supporting the Maintain Demographics Option shall support these 7 trigger events and messages : Admit inpatient, register outpatient, discharge patient, update patient information, merge patient identifier list, Cancel admission, Cancel Discharge51Section 12:27:29 PM by aberge