Difference between revisions of "PCC-3"
m |
|||
| Line 1: | Line 1: | ||
| − | == Query Diagnostic Data == | + | === Query Diagnostic Data === |
This section corresponds to Transaction PCC-3 of the IHE Patient Care Coordination Technical Framework. Transaction Query Diagnostic Data is used by the Clinical Data Consumer and Diagnostic Data Repository Actors. | This section corresponds to Transaction PCC-3 of the IHE Patient Care Coordination Technical Framework. Transaction Query Diagnostic Data is used by the Clinical Data Consumer and Diagnostic Data Repository Actors. | ||
Transaction Query Diagnostic Data uses the same pattern as transaction {{ILink|PCC-3|PCC-1}}. Therefore, the {{ILink|PCC-3|PCC-1_referenced_standards|Referenced Standards}} and {{ILink|PCC-3|PCC-1_interaction_diagrams|Interaction Diagrams}} sections of that transaction also serve to document the standards and interactions used in this transaction. Information specific to this transaction is described in futher detail below in the section on [[#Domain Content|Domain Content]]. | Transaction Query Diagnostic Data uses the same pattern as transaction {{ILink|PCC-3|PCC-1}}. Therefore, the {{ILink|PCC-3|PCC-1_referenced_standards|Referenced Standards}} and {{ILink|PCC-3|PCC-1_interaction_diagrams|Interaction Diagrams}} sections of that transaction also serve to document the standards and interactions used in this transaction. Information specific to this transaction is described in futher detail below in the section on [[#Domain Content|Domain Content]]. | ||
| − | === Use Case Roles === | + | ==== Use Case Roles ==== |
{{Use Case Roles | {{Use Case Roles | ||
|Clinical Data Consumer|Requests a list of diagnostic results for a given patient matching a minimal set of selection criteria from the Diagnostic Data Repository. | |Clinical Data Consumer|Requests a list of diagnostic results for a given patient matching a minimal set of selection criteria from the Diagnostic Data Repository. | ||
| Line 10: | Line 10: | ||
|Tx=Query Diagnostic Data}} | |Tx=Query Diagnostic Data}} | ||
| − | === Domain Content === | + | ==== Domain Content ==== |
This section lists the requirements specific to the Query Diagnostic Data transaction. | This section lists the requirements specific to the Query Diagnostic Data transaction. | ||
| Line 17: | Line 17: | ||
{{Note|Diagnostic results include any observations made using specific diagnostic procedures or equipment, including laboratory, imaging, or assessment scales}} | {{Note|Diagnostic results include any observations made using specific diagnostic procedures or equipment, including laboratory, imaging, or assessment scales}} | ||
| − | ====careProvisionCode==== | + | =====careProvisionCode===== |
A Clinical Data Consumer may specify the following values from the HL7 ActCode vocabulary (2.16.840.1.113883.5.4) to obtain the observations listed in the table below. | A Clinical Data Consumer may specify the following values from the HL7 ActCode vocabulary (2.16.840.1.113883.5.4) to obtain the observations listed in the table below. | ||
| Line 30: | Line 30: | ||
A Diagnostic Data Repository Actor shall respond with <observation> elements cooresponding the specified results. The results shall be returned in the form of clinical statements that conform to the {{ILink|PCC-3|1.3.6.1.4.1.19376.1.5.3.1.4.13|Simple Observation}} template. | A Diagnostic Data Repository Actor shall respond with <observation> elements cooresponding the specified results. The results shall be returned in the form of clinical statements that conform to the {{ILink|PCC-3|1.3.6.1.4.1.19376.1.5.3.1.4.13|Simple Observation}} template. | ||
| − | ====careProvisionReason==== | + | =====careProvisionReason===== |
The <value> element of the <careProvisionReason> element may contain a value identifying a specific problem that was the reason for obtaining the result. | The <value> element of the <careProvisionReason> element may contain a value identifying a specific problem that was the reason for obtaining the result. | ||
A Diagnostic Data Repository Actor that chooses to honor this query parameter shall return only those results that were for the indicated reason. Should the Diagnostic Data Repository Actor not support the use of the <careProvisionReason> element, it shall indicate this by raising the appropriate alert as decribed in the expected actions recorded in {{ILink|PCC-3|PCC-1}}. | A Diagnostic Data Repository Actor that chooses to honor this query parameter shall return only those results that were for the indicated reason. Should the Diagnostic Data Repository Actor not support the use of the <careProvisionReason> element, it shall indicate this by raising the appropriate alert as decribed in the expected actions recorded in {{ILink|PCC-3|PCC-1}}. | ||
Revision as of 21:12, 14 June 2007
Query Diagnostic Data
This section corresponds to Transaction PCC-3 of the IHE Patient Care Coordination Technical Framework. Transaction Query Diagnostic Data is used by the Clinical Data Consumer and Diagnostic Data Repository Actors.
Transaction Query Diagnostic Data uses the same pattern as transaction PCC-1. Therefore, the Referenced Standards and Interaction Diagrams sections of that transaction also serve to document the standards and interactions used in this transaction. Information specific to this transaction is described in futher detail below in the section on Domain Content.
Use Case Roles
| Clinical Data Consumer | Diagnostic Data Repository | |
 Query Diagnostic Data | ||
- Actor
- Clinical Data Consumer
- Role
- Requests a list of diagnostic results for a given patient matching a minimal set of selection criteria from the Diagnostic Data Repository.
- Actor
- Diagnostic Data Repository
- Role
- Returns diagnostic results for a given patient matching the selection criteria supplied by the Clinical Data Consumer.
Domain Content
This section lists the requirements specific to the Query Diagnostic Data transaction.
| Note: | Implementors of a Diagnostic Data Repository Actor, or a Clinical Data Consumer Actor shall publish an HL7 Conformance Profile that indicates the vocabularies and code sets that they support for this transaction. |
| Note: | Diagnostic results include any observations made using specific diagnostic procedures or equipment, including laboratory, imaging, or assessment scales |
careProvisionCode
A Clinical Data Consumer may specify the following values from the HL7 ActCode vocabulary (2.16.840.1.113883.5.4) to obtain the observations listed in the table below.
| Code | Returns | Template Id |
|---|---|---|
| LABCAT | All Lab Results | Simple Observations |
| DICAT | All Imaging Results | Simple Observations |
A Clinical Data Consumer Actor may set the <value> element of the <careProvisionCode> element to identify a specific diagnostic result using LOINC, or it may select a class of diagnostic results using the LOINC values specified in the XD*-Lab profile.
A Diagnostic Data Repository Actor shall respond with <observation> elements cooresponding the specified results. The results shall be returned in the form of clinical statements that conform to the Simple Observation template.
careProvisionReason
The <value> element of the <careProvisionReason> element may contain a value identifying a specific problem that was the reason for obtaining the result. A Diagnostic Data Repository Actor that chooses to honor this query parameter shall return only those results that were for the indicated reason. Should the Diagnostic Data Repository Actor not support the use of the <careProvisionReason> element, it shall indicate this by raising the appropriate alert as decribed in the expected actions recorded in PCC-1.