 |
Return to detail page at www.hitsp.org | HITSP/SC110 |
| Prev TOC Next |
| HOME | ABOUT | MEMBERSHIP | NEWS & ANNOUNCEMENTS | MEETINGS | FAQ | CONTACT US | | Powered by American National Standards Institute |
|
Return to detail page at www.hitsp.org | HITSP/SC110 |
| Prev TOC Next |
The Patient Identification Management Service Collaboration provides the ability to lookup and/or cross-reference patient identities. This Service Collaboration utilizes the following constructs or applicable:
HITSP/TP22 Patient ID Cross-Referencing Transaction Package to deal with identifying and cross-referencing different attributes for the same patient
HITSP/T23 Patient Demographics Query Transaction to provide a list of patients and their demographics query and patient(s) and their demographics identified response message pair (QBP^Q22, RSP^K22) for use wherever such needs exist
HITSP/T24 Pseudonymize to provide access to use specific pseudonyms for patients
Necessary Security and Privacy constructs to assure appropriate access control and enforcement of privacy policies
For more information about the underlying capabilities, pre-conditions, post-conditions, data flows and other detailed information, please refer to the constructs that are used by this Service Collaboration.
The Service Collaboration document illustrates one internal view diagram and sequence table for each service interface. The diagrams are descriptive and the sequences are not mandatory. They may be affected by policy, chosen architecture, and implementation details. Conformance is measured against the underlying constructs.
Table 1-1 Service Collaboration Transactions and Data
|
Service Collaboration |
Service Collaboration Description |
Interface |
Interface Optionality [1] |
|
HITSP/SC110 - Patient Identification Management
|
Provides the ability to request identity lookup and/or cross-reference |
Request Patient Identification |
R |
There is one example diagram included for each service interface. The diagrams are descriptive and the sequences are not mandatory. They may be affected by policy, chosen architecture, and implementation details. Conformance is measured against the underlying constructs.
Figure 1-1 Patient Identity Management External View Diagram
Table 1-2 List of Constructs
|
Construct |
Required/Optional [2] |
|
HITSP/T17 - Secured Communication Channel |
R |
|
HITSP/TP22 - Patient ID Cross-Referencing |
O [C1] |
|
HITSP/T23 - Patient Demographics Query |
O [C1] |
|
HITSP/T24 - Pseudonymize |
O[C1] |
|
HITSP/SC108 - Access Control |
R |
|
HITSP /SC109 - Security Audit |
R |
[C1]: Implementation choice must be made to select at least on of the following HITSP constructs: HITSP/TP22 Patient ID Cross Referencing, HITSP/T23 Patient Demographics Query, or HITSP/T24 Pseudonymize.
Figure 1-2 Request Patient Management Identification Internal View
Table 1-3 Request Patient Identification Pre-conditions
|
Pre-conditions |
Uses SC, T, TP or C |
Interface |
Purpose |
|
Patient Identities among which cross-referencing may be performed, have been communicated to the PIX Manager Interface |
HITSP/TP22 - Patient ID Cross-Referencing |
PIX Consumer |
Patient identities have been cross-referenced |
Table 1-4 Request Patient Identification Sequence of Constructs
|
Step Number |
Uses SC, T, TP or C |
Interface |
Transaction |
Purpose |
|
1 |
HITSP/SC108 - Access Control |
Request Access Control Decision |
To assure that the user has authorization to request patient identification |
|
|
2 |
HITSP/TP22 - Patient Identity Cross-Reference |
Patient Identifier Cross-Reference Consumer |
PIX Query [ITI-9] |
If cross-referencing is desired this step is used to cross-reference the provided patient identifier into the requested patient identity domain |
|
3 |
HITSP/T23 - Patient Demographics Query |
Patient Demographics Consumer |
Patient Demographics Query [ITI-21] |
If demographics are needed or if demographics are provided this step is used to lookup the patient by/with demographics |
|
4 |
HITSP/T24 - Pseudonymize |
Patient Identifier Cross-Reference Consumer |
PIX Query [ITI-9] |
If cross-referencing to/from a pseudonym identity domain this step is used to cross-reference the provided patient identifier into/out of the requested pseudonym identity domain |
|
5 |
HITSP/SC109 - Security Audit |
Send Security Audit Event |
Record the success/failure of the patient identification |
Table 1-5 Request Patient Identification Post-conditions
|
Post-conditions |
Uses SC, T, TP or C |
Actor |
Purpose |
|
None |
|
|
|
Return to detail page at www.hitsp.org | HITSP/SC110 |
| Prev TOC Next |