 |
Return to detail page at www.hitsp.org | HITSP/SC113 |
| 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/SC113 |
| Prev TOC Next |
The HITSP Query for Existing Data Service Collaboration provides the capability to query and retrieve data from another clinical system, and the capability to respond to same queries. The Service Collaboration applies the necessary Security and Privacy constructs. The Service Collaboration supports all the queries found in HITSP/TP21 Query for Existing Data, including:
Vital Signs
Problems and Allergies
Diagnostic Data
Medications
Immunizations
Professional Services
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 |
Transaction or Data |
Transaction or Data Optionality [1] |
|
HITSP/SC113 - Query for Existing Data |
Requests existing patient data from another clinical system |
Request Existing Patient Data |
R |
|
HITSP/SC113 - Query for Existing Data |
Provides data for another clinical system |
Respond to Existing Patient Data |
R |
Figure 1-1 Query for Existing Data External View diagram
Table 1-2 List of Constructs
|
Construct |
|
HITSP/SC108 - Access Control |
|
HITSP/SC109 - Security Audit |
|
HITSP/SC110 - Patient Identification Management |
|
HITSP/T17 - Secured Communication Channel |
|
HITSP/TP21 - Query for Existing Data |
Figure 1-2 Request Existing Data Internal View
Table 1-3 Sequence of Constructs Pre-Conditions
|
Pre-condition |
Uses SC, T, TP or C |
Interface |
Purpose |
|
None |
|
|
|
Table 1-4 Sequence of Constructs
|
Step Number |
Uses SC, T, TP or C |
Interface |
Purpose |
|
1 |
HITSP/SC110 - Patient Identification Management |
Request Patient Identification |
To resolve the patient identity into the identity that the Clinical Data Service requires |
|
2 |
HITSP/SC108 - Access Control Service |
Request Access Control Decision |
To ensure that the user of this Service Collaboration has the right to use the HITSP/TP21 Transaction for this patient and this purpose |
|
3 |
HITSP/T17 - Secured Communication Channel |
Secure Node |
To open a secure communications channel for HITSP/TP21 to transmit clinical data |
|
4 |
HITSP/C19 - Entity Identity Assertion |
|
To provide the identity and attributes about the requestor of the HITSP/TP21 Transaction |
|
5 |
HITSP/TP21 - Query for Existing Data |
Clinical Data Consumer |
To request and receive the existing data |
|
6 |
HITSP/SC109 - Security Audit |
Send Security Audit Event |
To record the success or failure of the relevant information about the HITSP/TP21 Transaction |
Table 1-5 Sequence of Constructs Post-Conditions
|
Post-conditions |
Uses SC, T, TP or C |
Interface |
Purpose |
|
None |
|
|
|
Figure 1-3 Respond Existing Patient Data Internal View
Table 1-6 Sequence of Constructs Pre-Conditions
|
Pre-condition |
Uses SC, T, TP or C |
Interface |
Purpose |
|
None |
|
|
|
Table 1-7 Sequence of Constructs
|
Step Number |
Uses SC, T, TP or C |
Interface |
Purpose |
|
1 |
HITSP/ T17 - Secured Communication Channel |
Secure Node |
To receive a secure communications channel for HITSP/TP21 to transmit clinical data |
|
2 |
HITSP/ C19 - Entity Identity Assertion |
|
To receive the identity and attributes about the requestor of the HITSP/TP21 Transaction |
|
3 |
HITSP/ TP21 - Query for Existing Data |
Depends on payload. |
Receive the request for existing Data |
|
4 |
HITSP/ SC110 - Patient Identification Management |
Request Patient Identification |
If required, resolve the patient identity into the identity that the Clinical Data Service requires |
|
5 |
HITSP/ SC108 - Access Control Service |
Request Access Control Decision |
To ensure that the user of this Service Collaboration has the right to use the data for this patient and this purpose |
|
6 |
(Internal) |
|
Lookup the requested data |
|
7 |
HITSP/ SC109 - Security Audit |
Send Security Audit Event |
To record the success or failure of the relevant information about the HITSP/TP21 Transaction |
|
8 |
HITSP/ TP21 - Query for Existing Data |
Depends on payload. |
Return the requested Data |
Table 1-8 Sequence of Constructs Post-Conditions
|
Post-conditions |
Uses SC, T, TP or C |
Interface |
Purpose |
|
None |
|
|
|
|
Return to detail page at www.hitsp.org | HITSP/SC113 |
| Prev TOC Next |