Difference between revisions of "PCC-6"
m (→Use Case Roles) |
m |
||
Line 1: | Line 1: | ||
− | === Query Professional Services === | + | === <span id='PCC-6'>Query Professional Services</span> === |
This section corresponds to Transaction PCC-6 of the IHE Patient Care Coordination Technical Framework. Transaction Query Professional Services is used by the Clinical Data Consumer and Professional Services Data Repository Actors. | This section corresponds to Transaction PCC-6 of the IHE Patient Care Coordination Technical Framework. Transaction Query Professional Services is used by the Clinical Data Consumer and Professional Services Data Repository Actors. | ||
Revision as of 17:27, 12 September 2007
Query Professional Services
This section corresponds to Transaction PCC-6 of the IHE Patient Care Coordination Technical Framework. Transaction Query Professional Services is used by the Clinical Data Consumer and Professional Services Data Repository Actors.
Transaction Query Professional Services 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 Domain Content.
Use Case Roles
Clinical Data Consumer | Professional Services Data Repository | |
- Actor
- Clinical Data Consumer
- Role
- Requests a list of visits or procedures for a given patient matching a minimal set of selection criteria from the Professional Services Data Repository.
- Cooresponding HL7 Version 3 Application Roles
- Care Record Query Placer (QUPC_AR004030UV)
Query by Parameter Placer (QUQI_AR000001UV01)
- Actor
- Professional Services Data Repository
- Role
- Returns procedure or visit entries for a given patient matching the selection criteria supplied by the Clinical Data Consumer.
- Cooresponding HL7 Version 3 Application Roles
- Care Record Query Fulfiller (QUPC_AR004040UV)
Query by Parameter Fulfiller (QUQI_AR000002UV01)
Domain Content
This section lists the requirements specific to the Query Professional Services transaction.
Note: | Implementors of a Professional Services 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. |
Get Care Record Profile Query
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 immunzation records listed in the table below.
Code | Returns | Template Id |
---|---|---|
PSVCCAT | All professional service entries |
A Clinical Data Consumer Actor may make requests using other codes to obtain information about specific visit or procedure. Additional codes for professional services may be found in SNOMED CT (2.16.840.1.113883.6.96), CPT-4 (2.16.840.1.113883.6.12), ICD-9-CM procedure codes (2.16.840.1.113883.6.104), and in other controlled vocabularies.
careProvisionReason
The <value> element of the <careProvisionReason> element may contain a value identifying a the reason for the procedure or visit.
A Professional Services Data Repository Actor that chooses to honor this query parameter shall return only those results that were for the indicated reason. Should the Professional Services Data Repository 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.
Get Care Record Profile Response
A Professional Services Data Repository Actor shall respond to a query request by returning clinical statements matching the query parameter returned within <pertinentInformation3> data elements.
The clinical statements that are returned for codes specified in the table above in the section on careProvisionCode shall conform to the templates shown above. All clinical statements returned shall specify the author or authors of the statement in an <author> element, and may indicate the informants in <informant> elements. A Professional Services Data Repository Actor may respond to query requests using other codes to return information about specific procedure or visit. These entries conform to one of the template identifiers shown above.
WSDL Declarations
The following WSDL naming conventions SHALL apply for this transaction:
WSDL Item | Value |
---|---|
wsdl:definitions/@name | ProfessionalServicesDataSource |
Get Care Record Profile Query | QUPC_IN043100UV_Message |
Get Care Record Profile Response | QUPC_IN043200UV_Message |
General Query Activate Continue / Cancel | QUQI_IN000003UV01_Messsage |
portType | ProfessionalServicesDataSource_PortType |
Query Operation | ProfessionalServicesDataSource_QUPC_IN043100UV |
Continue Operation | ProfessionalServicesDataSource_QUQI_IN000003UV01_Continue |
Cancel Operation | ProfessionalServicesDataSource_QUQI_IN000003UV01_Cancel |
SOAP 1.1 binding | ProfessionalServicesDataSource_Binding_Soap11 |
SOAP 1.1 port | ProfessionalServicesDataSource_Port_Soap11 |
SOAP 1.2 binding | ProfessionalServicesDataSource_Binding_Soap12 |
SOAP 1.2 port | ProfessionalServicesDataSource_Port_Soap12 |
The following WSDL snippets specify the Port Type and Binding definitions, according to the requirements specified in ITI TF-2: Appendix V. A full WSDL example for the Professional Services Data Source actor implementing the QED profile can be found at ftp://ftp.ihe.net/Patient_Care_Coordination/yr3_2007-2008/resources/Query.zip. For a general description of the WSDLs for QED see the Appendix of the same name in this volume.
Port Type
<portType name="ProfessionalServicesDataSource_PortType"> <operation name="ProfessionalServicesDataSource_QUPC_IN043100UV"> <input message="tns:QUPC_IN043100UV_Message" wsaw:Action="urn:hl7-org:v3:QUPC_IN043100UV"/> <output message="tns:QUPC_IN043200UV_Message" wsaw:Action="urn:hl7-org:v3:QUPC_IN043200UV "/> </operation> <operation name="ProfessionalServicesDataSource_QUQI_IN000003UV01_Continue"> <input message="tns:QUQI_IN000003UV01_Message" wsaw:Action="urn:hl7-org:v3:QUQI_IN000003UV01"/> <output message="tns:QUPC_IN043200UV_Message" wsaw:Action="urn:hl7-org:v3:QUPC_IN043200UV "/> </operation> <operation name="ProfessionalServicesDataSource_QUQI_IN000003UV01_Cancel"> <input message="tns:QUQI_IN000003UV01_Message" wsaw:Action="urn:hl7-org:v3:QUQI_IN000003UV01"/> <output message="tns:QUPC_IN043200UV_Message" wsaw:Action="urn:hl7-org:v3:QUPC_IN043200UV "/> </operation> </portType> |
Bindings
<binding name="ProfessionalServicesDataSource_Binding_Soap12" type="ProfessionalServicesDataSource_PortType"> <wsoap12:binding style="document" transport="http://schemas.xmlsoap.org/soap/http"/> <operation name="ProfessionalServicesDataSource_QUPC_IN043100UV"> <wsoap12:operation soapAction="urn:hl7-org:v3:QUPC_IN043100UV"/> <input> <wsoap12:body use="literal"/> </input> <output> <wsoap12:body use="literal"/> </output> </operation> </binding> |
<binding name="ProfessionalServicesDataSource_Binding_Soap11" type="ProfessionalServicesDataSource_PortType"> <wsoap11:binding style="document" transport="http://schemas.xmlsoap.org/soap/http"/> <operation name="ProfessionalServicesDataSource_QUPC_IN043100UV"> <wsoap11:operation soapAction="urn:hl7-org:v3:QUPC_IN043100UV"/> <input> <wsoap11:body use="literal"/> </input> <output> <wsoap11:body use="literal"/> </output> </operation> </binding> |