| ITI31 | ITI31-001 | to be reviewed | Testable |
0
|
3
| | The Patient Encounter Supplier shall support the Basic Subset of messages defined in ITI TF-2b: 3.31.5.1. | 43 | Table 3.31-1 | 1/29/19 2:23:47 PM by Xavier Francois |
|
| ITI31 | ITI31-002 | to be reviewed | Testable |
0
|
3
| | The Patient Encounter Consumer shall support the Basic Subset of messages defined in ITI TF-2b: 3.31.5.1. | 43 | Table 3.31-1 | 1/29/19 2:23:58 PM by Xavier Francois |
|
| ITI31 | ITI31-003 | to be reviewed | Testable |
0
|
6
| | A movement can be updated only if the Historic Movement Management option is supported | 41 | Section 3.31.4 | 1/29/19 2:23:58 PM by Xavier Francois |
|
| ITI31 | ITI31-004 | | Testable |
0
|
4
| | Only the current movement can be cancelled | 41 | Section 3.31.4 | 7/5/21 9:54:13 AM by Clément Lagorce |
|
| ITI31 | ITI31-005 | | Testable |
0
|
4
| | A system implementing either Patient Encounter Supplier or Patient Encounter Consumer, shall support these 5 trigger events and messages :
Admit inpatient, Discharge patient, Register outpatient, Cancel admit/visit, Cancel discharge | 43 | Figure 3.31-1 | 7/5/21 9:54:13 AM by Clément Lagorce |
|
| ITI31 | ITI31-006 | | Testable |
0
|
4
| | A system implementing Inpatient/Outpatient encounter management option shall support these 11 trigger events and messages. | 44 | Table 3.31-2 | 7/5/21 9:54:13 AM by Clément Lagorce |
|
| ITI31 | ITI31-007 | to be reviewed | Testable |
0
|
8
| | The Pending Event Management Option requires the Inpatient/Outpatient Encounter Management Option. | 45 | Figure 3.31.5.3 | 1/29/19 2:23:58 PM by Xavier Francois |
|
| ITI31 | ITI31-008 | to be reviewed | Testable |
0
|
6
| | A system implementing the Pending Event Managament option shall support these 17 trigger events and messages:
Admit inpatient, Register Outpatient, Disscharge Patient, Preadmit patient, Change patient class to inpatient, Change patient class to outpatient, transert patient, Pending admit, Pending transfer, Pending discharge | 45 | Table 3.31-3 | 1/29/19 2:23:47 PM by Xavier Francois |
|
| ITI31 | ITI31-009 | to be reviewed | Testable |
0
|
6
| | A system implementing Advanced Encounter Management Option shall support these 12 trigger events and messages :
Admit inpatient, Register outpatient, Discharge patinent, Change attending doctor, Leave of absence, Return from leave of absence, Move account information | 47 | Table 3.31-4 | 1/29/19 2:23:47 PM by Xavier Francois |
|
| ITI31 | ITI31-010 | to be reviewed | Testable |
0
|
6
| | A system implementing Temporary Patient Transfers Tracking Option shall support these 9 trigger events and messages :
Admit inpatient, Register outpatient, Discharge patient, Patient departing - tracking, Patient arriving - tracking | 47 | Section 3.31-5 | 1/29/19 2:23:47 PM by Xavier Francois |
|
| ITI31 | ITI31-011 | | Testable |
0
|
4
| | The movement updated can either be the current movement or a movement in the past (historic movement) | 48 | Section 3.31.5.6 | 7/5/21 9:54:13 AM by Clément Lagorce |
|
| ITI31 | ITI31-012 | | Testable |
0
|
4
| | The ZBE segment is required for the following trigger events : A01, A02, A03, A04, A05, A06, A07, A11, A12, A13, A14, A15, A16, A21, 1115 A22, A25, A26, A27, A38, A52, A53, A54, A55, Z99 if the historic movement management option is supported | 48 | Section 3.31.5.6 | 7/5/21 9:54:13 AM by Clément Lagorce |
|
| ITI31 | ITI31-013 | to be reviewed | Testable |
0
|
6
| | This Historic Movement Management option may apply to any combination of the previous subsets, except Temporary Patient Transfers Tracking (Temporary Patient Transfers do not need to be uniquely identified). | 48 | Section 3.31.5.6 | 1/29/19 2:23:47 PM by Xavier Francois |
|
| ITI31 | ITI31-014 | to be reviewed | Testable |
0
|
5
| | If 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. | 49 | Section 3.31.5.8 | 1/29/19 2:23:47 PM by Xavier Francois |
|
| ITI31 | ITI31-015 | to be reviewed | Testable |
0
|
6
| | 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 | 50 | Section 3.31.5.9 | 1/29/19 2:23:47 PM by Xavier Francois |
|