View source for PCC-8

=== <span ID='PCC-8'>Request Guideline Data</span> ===
This section corresponds to Transaction PCC-8 of the IHE Patient Care Coordination Technical Framework.  Transaction PCC-8 is used by the Care Manager and/or Clinical Data Source Actors to request Guideline Data from a Guideline Manager Actor.  Transaction PCC-8 is similar in structure to Transaction [[PCC-1]].  The difference between PCC-8 and PCC-1 is that where PCC-1 requests clinical information matching the query parameters for a specific patient, the PCC-8 transaction requests a specific care record activating a clinical guideline identified in the query parameters.

==== Use Case Roles ====
{{Use Case Roles
|Care Manager or Clinical Data Source|Requests the data required to implement a guideline.
:;Cooresponding HL7 Version 3 Application Roles:Care Record Query Placer ([http://www.hl7.org/v3ballot/html/domains/uvpc/uvpc_CareRecordQuery.htm#QUPC_AR004030UV-ar QUPC_AR004030UV])<br/>Query by Parameter Placer ([http://www.hl7.org/v3ballot/html/domains/uvqi/uvqi_QueryByParameter.htm#QUQI_AR000001UV01-ar QUQI_AR000001UV01])
|Guideline Manager|Returns the guideline data required to implement a guideline. 
:;Cooresponding HL7 Version 3 Application Roles: Care Record Query Fulfiller  ([http://www.hl7.org/v3ballot/html/domains/uvpc/uvpc_CareRecordQuery.htm#QUPC_AR004040UV-ar QUPC_AR004040UV])<br/>Query by Parameter Fulfiller ([http://www.hl7.org/v3ballot/html/domains/uvqi/uvqi_QueryByParameter.htm#QUQI_AR000002UV01-ar QUQI_AR000002UV01])
|Tx=Request Guideline Data}}

==== <span ID="PCC-8_referenced_standards">Referenced Standards</span> ====
{|
{{Std|CareRecord}}
{{Std|CareQuery}}
{{Std|HL7QI|HL7 Version 3 Standard: Infrastructure Management – Query Infrastrucure|http://www.hl7.org/v3ballot/html/domains/uvqi/uvqi.htm}}
{{Std|HL7WS}}
{{Std|SOAP}}
{{Std|SOAP12}}
|}

==== <span ID="PCC-8_Interaction Diagrams">Interaction Diagrams</span> ====
[[Image:Qcdpmo.png]]
==== Get Care Record Query ====
===== Trigger Events =====
When a Clinical Data Source actor needs to understand the data needed to respond to a query from a Care Manager, or a Care Manager actor needs to refresh its knowledge about a guideline (e.g., to determine how to update a query for a replaced guideline) it will trigger a Get Care Record Query event.  This cooresponds to the HL7 trigger event: [http://www.hl7.org/v3ballot/html/domains/uvpc/uvpc_CareRecordQuery.htm#QUPC_TE040100UV-te QUPC_TE040100UV]

===== Message Semantics =====
The Query Care Record Event Get Query corresponds to the HL7 Interaction 
[http://www.hl7.org/v3ballot/html/domains/uvpc/uvpc_CareRecordQuery.htm#QUPC_IN040100UV-int QUPC_IN040100UV]. 

A schema for this interaction can be found at: http://www.hl7.org/v3ballot2007may/html/processable/multicacheschemas/QUPC_IN040100UV.xsd.  This schema includes:
* the transmission wrapper MCCI_MT000100UV01,
* the control act wrapper QUQI_MT020001UV01, and 
* the message payload QUPC_MT040100UV. 
These components of the interaction are specified in the HL7 standards described above.
===== Transmission Wrapper =====
The transmission wrapper MCCI_MT000100UV01 provides information about the message transmission and routing.  Transmission wrappers are further described in ITI TF-2: Appendix O.
An example transmission wrapper is given below for this interaction.  Items marked in dark gray are transmitted as specified in ITI TF-2: Appendix O.   Items in bold black text are further constrained by this profile in this interaction.
 
 <font color='#808080'><font color='black'>'''<QUPC_IN040100UV xmlns="urn:hl7-org:v3" ITSVersion="XML_1.0"'''
                  '''xmlns:xsi="<nowiki>http://www.w3.org/2001/XMLSchema-instance</nowiki>">'''</font>
  <id root=' ' extension=' '/>
  <creationTime value=' '/>
  <font color='black'>'''<interactionId extension='QUPC_IN040100UV' root='2.16.840.1.113883.5'/>'''</font>
  <processingCode code='D|P|T'/>
  <font color='black'>'''<processingModeCode code='T'/>'''
  '''<acceptAckCode code='AL'/>'''</font>
  <receiver typeCode="RCV">
    <device determinerCode="INSTANCE">
      <id/>
      <name/>
      <telecom value=' ' />
      <manufacturerModelName/>
      <softwareName/>
    </device>
  </receiver>
  <sender typeCode="SND">
    <device determinerCode="INSTANCE">
      <id/>
      <name/>
      <telecom value=' ' />
      <manufacturerModelName/>
      <softwareName/>
    </device>
  </sender>
  <controlActProcess>
   <font color='black'>''See Control Act Wrapper below''</font>
  </controlActProcess>
 </QUPC_IN040100UV></font>

====== <QUPC_IN040100UV xmlns="urn:hl7-org:v3" ITSVersion="XML_1.0" xmlns:xsi="<nowiki>http://www.w3.org/2001/XMLSchema-instance</nowiki>"> ====== 
The HL7 Interaction being sent will control the name of the root element in the message. The namespace of this message shall be urn:hl7-org:v3, and the ITSVersion attribute shall be "XML_1.0". 
====== <interactionId extension='QUPC_IN040100UV' root='2.16.840.1.113883.5'/> ====== 
The identifer for the interaction shall be sent as shown above.
====== <processingModeCode code='T'/> ====== 
The processingModeCode distinguishes the type of processing being performed. This element shall be present and have the value shown above to indicate that this message is for current processing. 
====== <acceptAckCode code='AL'/> ====== 
The acceptAckCode indicates whether the sender wants to recieve an acknowledgement, and shall be sent as shown above.

===== Control Act Wrapper =====
The control act wrapper QUQI_MT020001UV01 provides information about the business actors related to the transaction, including the author or performer of the act.  Control act wrappers are further described in ITI TF-2: Appendix O.
An example transmission wrapper is given below for this interaction.  Items marked in dark gray are transmitted as specified in ITI TF-2: Appendix O.   Items in bold black text are further constrained by this profile in this interaction.
 <font style='color: black'>'''<controlActProcess moodCode="RQO">'''
   <font color='#808080'><id root=' ' extension=' '/></font>
   '''<code code='QUPC_TE040100UV'/>'''
   <font color='#808080'><effectiveTime value=' '/>
   <languageCode code=' '/>
   <authorOrPerformer typeCode=' '></authorOrPerformer></font>
   <font style='font-weight: bold'><!-- Performing a Query -->
   <queryByParameter>
     <id root='&nbsp;' extension='&nbsp;'/>
     <statusCode code='new'/>
     <responseModalityCode code='R'/>
     <responsePriorityCode code='I'/>
     <initialQuantity value=''/>
     <initialQuantityCode code='REPC_RM000100UV' codeSystem='2.16.840.1.113883'>
     <parameterList>
       <font style='font-weight: normal'>''see Query Parameter List below''</font>
     </parameterList>
   </queryByParameter>
 </controlActProcess></font></font>
====== <controlActProcess moodCode="RQO"> ====== 
The controlActProcess element is where information about the business act being performed is recorded. The moodCode is set to "RQO" by the sender to indicate a request to perform an action, in this case, a query.  
====== <code code='QUPC_TE040100UV'/> ====== 
The trigger event which caused the act to be transmitted is recorded in the code element is recorded as shown above.
====== <queryByParameter> ====== 
HL7 Version 3 messages that perform a query specify the details of it in the <queryByParameter> element. 
====== <id root='&nbsp;' extension='&nbsp;'/> ====== 
The sending system shall specify the identifier of the query.  This is the identifier that is used in subsequent continuation or cancel messages.
====== <statusCode code='new'/> ====== 
When passing the parameter list, the <statusCode> element shall be recorded as above to indicate that this is a new query. 
====== <responseModalityCode code='R'/> ====== 
The query response shall always be in real-time.
====== <responsePriorityCode code='I'/> ====== 
The query response shall always be immediate.
====== <initialQuantityCode code='REPC_RM000100UV' codeSystem='2.16.840.1.113883.5'> ====== 
The <initialQuantityCode> shall be sent when <initialQuantity> is sent. The code shall be the identifier of the HL7 artifact that is to be counted (e.g., R-MIM or C-MET identifer). In this profile what is being counted is clinical statements, so the code to use shall be REPC_RM000100UV. 
===== Parameter List ===== 
The message supports specification of the data items listed in the table below as query 
parameters.  The first column of this table provides the name of the parameter.  The next column indicates the number of times it may occur in the query.  The next column indicates the type of data expected for the query parameter.  The next column indicates the vocabulary domain used for coded values.  The Sender column indicates whether the message sender (a Care Manager or Clinical Data Source actor) must send this parameter.  The Reciever column indicates whether the reciever (a Guideline Manager Actor) must support this parameter.  If these last two columns contain the value R, then this parameter SHALL be send by actor, and if it is X, then this parameter SHALL NOT be sent by the actor.  In this profile, all parameters not explicitly required are prohibited.

{| border='1' cellspacing='0'
|-align='center' bgcolor='#D9D9D9'
! Parameter Name!!Cardinality!!Data Type!!Vocabulary Domain!!Sender!!Reciever
|+Query Parameters
|- 
|[[#careRecordId|careRecordId]]||1..1||II||&nbsp;||R||R
|- 
|patientId||0..0||CD||&nbsp;||X||X
|- 
|versionTimeStamp||0..0||TS||&nbsp;||X||X
|- 
|[[#includeCarePlanAttachment|includeCarePlanAttachment]]||1..1||BL||&nbsp;||R||R
|- 
|maxHistoryClincialStatements||0..0||INT||&nbsp;||X||X
|- 
|}

An example of the query specification is described in the figure below.

<pre>
  <parameterList>
    <careRecordId>
      <value code='' displayName='' codeSystem='' codeSystemName=''/>
    </careRecordId>
    <includeCarePlanAttachment><value value='true'/></includeCarePlanAttachment>
  </parameterList>
</pre>

====== <parameterList> ======
The <parameterList> element shall be present, and contains the set of query parameters being used in this query.


====== <span id='careRecordId'><careRecordId><value root='&nbsp;' extension='&nbsp;'/></careRecordId></span>======
The identifier of the care record event that activated the guideline shall be specified in this element.  The root and extension attributes shall be present.

====== <span id='includeCarePlanAttachment'><includeCarePlanAttachment><value value='true'/></includeCarePlanAttachment></span> ======
The <includeCarePlanAttachment> element shall be sent and the value shall be true.  As guidelines always appear in a Care Record message under the Care Plan, the Care Plan must be present in the response.

===== Expected Actions -- Care Manager or Clinical Data Source =====
The clinical data consumer shall send a query as specified in the QUPC_IN040100UV  interaction.   The message shall be sent using web services as specified in the ITI-TF: Appendix V.

The name of the query response message shall be QUPC_IN040100UV_Message in the WSDL.
The following WSDL snippet defines the type for this message:
{|
|+Query Message Type Definition
|-
|
<pre>
<types>
   <xsd:schema elementFormDefault="qualified" 
      targetNamespace="urn:hl7-org:v3" xmlns:hl7="urn:hl7-org:v3">
    <!-- Include the message schema -->
    <xsd:include namespace="urn:hl7-org:v3" schemaLocation="QUPC_IN040100UV.xsd"/>
  </xsd:schema>
</types>
</pre>
|}

The message type is declared to be of the appropriate type by the following WSDL snippet:
{|
|+Query Message WSDL Declaration
|-
|
<pre>
<message name='QUPC_IN040100UV_Message'>
  <part element='hl7:QUPC_IN040100UV' name="Body"/>
</message>
</pre>
|}
Other WSDL declarations required for this transaction are defined under the Domain Content section.

==== Get Care Record Profile Response ====
===== Trigger Events =====
This message is triggered upon reciept of a Query Care Record Event Get Query.  This corresponds to HL7 trigger event: [http://www.hl7.org/v3ballot/html/domains/uvpc/uvpc_CareRecordQuery.htm#QUPC_TE040200UV-te QUPC_TE043200UV]

===== Message Semantics =====
The Query Care Record Event Get Query Response corresponds to the HL7 Interaction [http://www.hl7.org/v3ballot/html/domains/uvpc/uvpc_CareRecordQuery.htm#QUPC_IN040200UV-int QUPC_IN040200UV].   A schema for this interaction can be found at: http://www.hl7.org/v3ballot2007may/html/processable/multicacheschemas/QUPC_IN040200UV.xsd.  This schema includes:
* the transmission wrapper MCCI_MT000300UV01,
* the control act wrapper MFMI_MT700712UV01, and 
* the message payload REPC_MT004000UV. 
These components of the interaction are specified in the HL7 standards described above.
===== Transmission Wrapper =====
The transmission wrapper MCCI_MT000300UV01 provides information about the message transmission and routing.  Transmission wrappers are further described in ITI TF-2: Appendix O.

An example transmission wrapper is given below for this interaction.  Items marked in dark gray are transmitted as specified in ITI TF-2: Appendix O.   Items in bold black text are further constrained by this profile in this interaction.

 <font color='#808080'><font color='black'>'''<QUPC_IN040200UV xmlns="urn:hl7-org:v3" ITSVersion="XML_1.0"'''
                 '''xmlns:xsi="<nowiki>http://www.w3.org/2001/XMLSchema-instance</nowiki>">'''</font>
  <id root=' ' extension=' '/>
  <creationTime value=' '/>
  <font color='black'>'''<interactionId extension='QUPC_IN040200UV' root='2.16.840.1.113883.5'/>'''</font>
  <processingCode code='D|P|T'/>
  <font color='black'>'''<processingModeCode code='T'/>'''
  '''<acceptAckCode code='NE'/>'''</font>
  <receiver typeCode="RCV">
    <device determinerCode="INSTANCE"> 
      <id/>
      <name/>
      <telecom value=' ' />
      <manufacturerModelName/>
      <softwareName/>
    </device>
  </receiver>
  <sender typeCode="SND">
    <device determinerCode="INSTANCE">
      <id/>
      <name/>
      <telecom value=' ' />
      <manufacturerModelName/>
      <softwareName/>
    </device>
  </sender>
  <controlActProcess>
   ''See Control Act Wrapper below''
  </controlActProcess>
 </QUPC_IN040200UV></font>
====== <QUPC_IN040200UV xmlns="urn:hl7-org:v3" ITSVersion="XML_1.0" xmlns:xsi="<nowiki>http://www.w3.org/2001/XMLSchema-instance</nowiki>"> ====== 
The HL7 Interaction being sent will control the name of the root element in the message. The namespace of this message shall be urn:hl7-org:v3, and the ITSVersion attribute shall be "XML_1.0". 
====== <interactionId extension='QUPC_IN040200UV' root='2.16.840.1.113883.5'/> ====== 
The identifer for the interaction shall be sent as shown above.
====== <processingModeCode code='T'/> ====== 
The processingModeCode distinguishes the type of processing being performed. This element shall be present and have the value shown above to indicate that this message is for current processing. 
====== <acceptAckCode code='NE'/> ====== 
The acceptAckCode indicates whether the reciever wants to recieve an acknowledgement, and shall be sent as shown above.  Query responses shall not require acknowledgements.
===== Control Act Wrapper===== 
The control act wrapper MFMI_MT700712UV01 provides information about the business actors related to the transaction, including the author or performer of the act.  Control act wrappers are further described in ITI TF-2: Appendix O.
An example transmission wrapper is given below for this interaction.  Items marked in dark gray are transmitted as specified in ITI TF-2: Appendix O.   Items in bold black text are further constrained by this profile in this interaction.

 <font style='color:black; font-weight:bold'><controlActProcess moodCode="EVN">=
   <font style='color: #808080; font-weight: normal'><id root=' ' extension=' '/></font>
   <code code='QUPC_TE040200UV'/>
   <font style='color: #808080; font-weight: normal'><effectiveTime value=' '/>
   <languageCode code=' '/>
   <authorOrPerformer typeCode=' '></authorOrPerformer></font>
   <!-- Returning Results -->
   <subject>
      See Query Response below
   </subject>
   <queryAck>
     <queryId root=' ' extension=' '/>
     <statusCode code=' '/>
     <queryResponseCode code=' '/>
     <resultTotalQuantity value=' '/>
     <resultCurrentQuantity value=' '/>
     <resultRemainingQuantity value=' '/>
   </queryAck>
 </controlActProcess></font>

====== <controlActProcess moodCode="EVN"> ====== 
The controlActProcess element is where information about the business act being performed is recorded. The moodCode is set to "EVN" by the sender to indicate a response to a query.  
====== <code code='QUPC_TE040200UV'/> ====== 
The trigger event which caused the act to be transmitted is recorded in the code element is recorded as shown above.
====== <subject> ====== 
The <subject> element shall be present to record the responses in a query request.
====== <queryAck> ====== 
The queryAck element is transmitted in any message that is a response to a query, query continuation or query cancellation message. 
====== <queryId root=' ' extension=' '/> ====== 
The <queryId> element shall be transmitted in a queryAck element. It shall contain an identifier that was used in the original query message. 
====== <statusCode code=' '/> ====== 
The statusCode element in the queryAck element indicates the status of the query. It may contain the value 'deliveredResponse' or 'aborted'. 
====== <queryResponseCode code=' '/> ====== 
The queryResponseCode element indicates at a high level the results of performing the query. It may have the value 'OK' to indicate that the query was performed and has results. It may have the value 'NF' to indicate that the query was performed, but no record was found. It may have the value 'QE' to indicate that an error was detected in the incoming query message, or 'AE' to indicate some other application error occurred. 
====== <resultTotalQuantity value=' '/> ====== 
The resultTotalQuantity element shall be present and enumerates the number of results found (1). This element gives the count of the total number of results located by the query. 
{{Note|For this use of the query, the resultTotalQuantity value should always be 1}}
====== <resultCurrentQuantity value=' '/> ====== 
The resultCurrentQuantity element shall be present, and shall enumerate number of results returned in the current response. 
{{Note|For this use of the query, the resultCurrentQuantity value should always be 1}}
====== <resultRemainingQuantity value=' '/> ====== 
This resultRemainingQuantity element shall be present. It shall enumerate the number of results that follow the results currently returned (0). 
{{Note|For this use of the query, the resultRemainingQuantity value should always be 0}}
===== Query Response =====
The <subject> element of the <controlActProcess> element shall appear as shown in the example below.  
<pre>
<subject>
  <registrationEvent>
    <statusCode code='active|obsolete'/>
    <custodian>
      <assignedEntity>
        <id root='' extension=''/>
        <addr></addr>
        <telecom></telecom>
        <assignedOrganization>
          <name></name>
        </assignedOrganization>
      </assignedEntity>
    </custodian>
    <subject2>
      <careProvisionEvent classCode='PCPR' moodCode='EVN'>
        <!-- Message Body -->
      </careProvisionEvent>
      <parameterList>
      </parameterList>
    </subject2>
  </registrationEvent>
</subject>
</pre>

====== <subject>====== 
The <subject> element shall be present, and is where the results are returned.
====== <registrationEvent>====== 
Only one <registrationEvent> element shall be be present.  

The <registrationEvent> is used to record the information about how the <careProvisionEvent> being returned was recorded or "registered" in the custodial system (the Guideline Manager actor) .

====== <statusCode code='active|obsolete'/>====== 
The <statusCode> element records the status of the data records.  Queries return active and obsolete (replaced) records.
====== <custodian>====== 
The <custodian> element records the custodian, or "owner", of the guideline.  A Guideline Manager actor may return records from multiple custodians. 
====== <assignedEntity>====== 
The <assignedEntity> element shall be present, and provides contact and identification information about the <custodian>.
====== <id root='&nbsp;' extension='&nbsp;'/>====== 
The <id> element shall be present, and shall uniquely identify the custodian of the guideline.
====== <addr></addr>====== 
The <addr> element shall be present, and shall provide a postal address for the custodian of the guideline.
====== <telecom></telecom>====== 
At least one <telecom> element shall be present that provides a telephone number to contact the custodian of the guideline.
A <telecom> element may be present that provides the web service end-point address of the custodian of the guideline.
{{Note|How might the web service end-point address be used?  Is it a good idea to include it, or should we omit this from the profile?|For Public Comment}}
====== <assignedOrganization><br/>&nbsp;<name></name><br/></assignedOrganization>====== 
The name of the organization that is the custodian of the guideline shall be provided.
====== <subject2>======
The <subject2> element provides the data content requested from the query.
{{Note|The following content for careProvisionEvent is identical to that found in [[PCC-7]].}}

{{:PCC-7/careProvisionEvent}}



====== <parameterList>====== 
The <parameterList> shall be present, and shall contain content that is identical to the <parameterList> passed in the query.

===== Expected Actions -- Data Repository =====
The Data Repository shall send a response as specified in the QUPC_IN043200UV  interaction.   The message shall be sent using web services as specified in the ITI-TF: Appendix V.  
The name of the query response message shall be QUPC_IN043200UV_Message in the WSDL.
The following WSDL snippet defines the type for this message:
{|
|+Query Response Message Type Definition
|-
|
  <types>
    <xsd:schema elementFormDefault="qualified" 
      targetNamespace="urn:hl7-org:v3" xmlns:hl7="urn:hl7-org:v3">
      <!-- Include the message schema -->
      <xsd:import namespace="urn:hl7-org:v3"
        schemaLocation="QUPC_IN043200UV.xsd"/>
      <xsd:element name="QUPC_IN043200UV"/>
    </xsd:schema>
  </types>
|}

The message type is declared to be of the appropriate type by the following WSDL snippet:
{|
|+Query Respone Message WSDL Declaration
|-
|
  <message name='QUPC_IN040200UV_Message'>
    <part element='hl7:QUPC_IN040200UV' name="Body"/>
  </message>
|}
Other WSDL declarations required for this transaction are defined under the Domain Content section.

====== Response to a New Query ======
The Guideline Manager, shall:
# Recieve and validate the query message.
# Create the response message.
# Add an ILLEGAL detected issue alert to the response message if the content is invalid (e.g., does not pass schema validation or is otherwise malformed), and immediately return a response indicating the error, and that the query was aborted.  Set the text of the alert to the name of the first data element that is not valid.  The Guideline Manager may send more than one ILLEGAL detected issue alert if it is able to determine that multiple data elements in the query are not valid.
# Add a NAT detected issue alert to the response message if the requesting party is not authorized to perform the query, and immediately return a response indicating the error, and that the query was aborted.
# Add a ILLEGAL detected issue alert to the response message if the the data repository does not recognize the identity domain used to identify the guideline.  Set the text value on the alert to careRecordId.
# If any issues were detected, Set queryAck/statusCode/@code to aborted, and queryAct/queryResponse/@code to QE, and return the response.
# Add an ISSUE alert to the response message if at any time during response generation, an application error occurs that prevents further processing.  Set the text of the alert to the reason for the application error (e.g., a stack trace or exception message).  Set queryAct/statusCode/@code to aborted, and queryAct/responseCode/@code to AE, and return the response.
# Query for the guideline requested by the query.
# If results are found, set queryAct/queryResponse/@code to OK, otherwise set it to NF.
# Set queryAck/statusCode/@code to deliveredResponse.
# Add the result to the response.

====== Raising Alerts ======
If the content of the request is not valid (e.g., according to the Schema or the rules of this profile), at least on ILLEGAL alert shall be raised indicating the data element that was invalid.  A response will be sent indicating that the request was invalid, and no further processing shall be performed.

If the requesting party is not authorized to perform the query, the minimum response shall be sent indicating only that the requested is not authorized to perform the query.  

In other cases, all possible alerts shall be accumulated before returning a response to the caller.  

This enables Clinical Data Consumer actors to send a test query that will enable them to verify the vocabulary and other request parameters that are desired.

An alert is raised by sending a response containing one or more <reasonOf> elements, coded as shown below.
<pre>
<reasonOf>
  <detectedIssueEvent>
    <code code='' displayName='' codeSystem='' codeSystemName=''/>
    <text></text>
    <mitigatedBy>
      <detectedIssueManagement moodCode="RQO">
        <code code='' displayName='' codeSystem='' codeSystemName=''/>
        <text></text>
      </detectedIssueManagement>
    </mitigatedBy>
  </detectedIssueEvent>>
</reasonOf>
</pre>

====== <reasonOf> ======
The <reasonOf> element is required to indicate that an alert has occured.

====== <detectedIssueEvent> ======
The details of the alert shall be present in the <detectedIssueEvent> element.

====== &lt;code code='&nbsp;' displayName='&nbsp;' codeSystem='2.16.840.1.113883.5.4' codeSystemName='ActCode'/> ======
The &lt;code> element shall contain ISSUE or one of its descendants from the HL7 [http://www.hl7.org/v3ballot/html/infrastructure/ActCode.htm#ISSUE ActCode] vocabulary.

====== <text></text> ======
If a validation or other business rule error occurred, the erroneous parameter shall be identified in <text> element using the element name, and nothing else should be present.

If an application error occured, the <text> element shall contain diagnostic information (e.g., stack trace or exception message).

If the reason for the alert was an unrecognized code (CODE_INVALID), the text element shall contain the name of the erroneous parameter, and may contain a space separated list of OIDs identifying value sets which would be valid.

If the reason for the alert was an unrecognized identifier (KEY204) for the vocabulary used in the careProvisionCode or careProvisionReason element, the text element shall contain the name of the erroneous paramater, and may contain a space separated list of the OIDs for code systems which would be valid.

===== Expected Actions -- Clinical Data Consumer =====
The Care Manager or Clinical Data Source processes the query response data.  No additional data other than the single requested guideline will be returned, so no provision is made in this profile for continuations or canceling the query.

==== WSDL Declarations ====
{{:PCC-1/WSDL|8|GuidelineManger|Guideline Manger}}