FHIR © HL7.org  |  Server Home  |  Health Intersections FHIR Server v1.0.329  |  FHIR Version 1.0.2  | User: ANONYMOUS (Unknown)  

Resource "client" Version "1" (Conformance)

Tags:

XML or JSON representation . provenance for this resource

Argonaut Data Query Implemenation Guide Client

FHIR Version: 1.0.2
Supported formats: xml , json
Published: 2016-10-18
Published by: Argonaut Project

This Conformance instance defines the expected capabilities of a client when conforming to the Argonaut Data Query Implementation Guide.


RESTful Behavior



Description:

The Argonaut client SHOULD:

  1. Support fetching and querying of one or more Argonaut profile(s), using the supported RESTful interactions and search parameters declared in the Argonaut Server Conformance Statement

Security:

Argonaut Data Query clients SHALL implement the security requirements documented in this guide


Supported Operations: SHALL Support docref

Resource  Details:


  1. Resource Type: Patient

    Supported Profiles:  Argonaut Data Query Patient Profile

    Summary of Argonaut Search Criteria for StructureDefinition-us-core-patient

    • A client has connected to a server and fetched a patient using GET [base]/Patient/[id].
    • A client has connected to a server and searched through available Patients using at least 2 (example name and gender) of the following search parameters:
      • name
      • gender
      • birthdate

    To limit overly broad search results, a client search with gender SHOULD include family and given name search parameters.


  2. Resource Type: AllergyIntolerance

    Supported Profiles:  Argonaut Data Query AllergyIntolerance Profile

    Summary of Argonaut Search Criteria for StructureDefinition-us-core-allergintolerance

    • A client has connected to a server and fetched a patient's allergies using GET /AllergyIntolerance?patient=[id].


  3. Resource Type: CarePlan

    Supported Profiles:  Argonaut Data Query CarePlan Profile
    Argonaut Data Query CareTeam Profile

    Summary of Argonaut Search Criteria for StructureDefinition-us-core-careplan

    • c of a patient's Assessment and Plan of Treatment information using GET /CarePlan?patient=[id]&category=assess-plan.
    • A client has connected to a server and fetched all of a patient's Assessment and Plan of Treatment information over a specified time period using GET /CarePlan?patient=[id]&category=assess-plan&date=[date].
    • A client SHOULD be capable of connecting to a server and fetching all of a patient's active Assessment and Plan of Treatment information using GET /CarePlan?patient=[id]&category=assess-plan&status=active.
    • A client SHOULD be capable of connecting to a server and fetching all of a patient's active Assessment and Plan of Treatment information over a specified time period using GET /CarePlan?patient=[id]&category=assess-plan&status=active&date=[date].

    Summary of Argonaut Search Criteria for StructureDefinition-argo-careteam

    • A client has connected to a server and fetched a patients current care team members using GET[base]/CarePlan?patient=[id]&category=careteam&status=active


  4. Resource Type: Condition

    Supported Profiles:  Argonaut Data Query Condition Profile

    Summary of Argonaut Search Criteria for StructureDefinition-us-core-condition

    • A client connected to a server and fetched all problems and health concerns for a patient, including current as well as historical problems and health concerns using GET/Condition?patient=[id]


  5. Resource Type: Device

    Supported Profiles:  Argonaut Data Query Device Profile

    Summary of Argonaut Search Criteria for StructureDefinition-us-core-device

    • A client has connected to a server and fetched all Unique device identifier(s)(UDI)for a patient's implantable device(s)using GET /Device?patient=[id].


  6. Resource Type: DocumentReference

    Supported Profiles:  Argonaut Data Query Document Reference Profile

    Search Criteria for StructureDefinition-argo-documentreference

    The Server SHALL support fetching document references using either the direct query for DocumentReference resources as described here or the $docref operation. The Client SHALL support both methods.

    A client has connected to a server and fetches document references for a patient:

    • GET [base]/DocumentReference/$docref?patient=[id]

    A client SHOULD be capable of connecting to a server and fetching references for a patient searched by type and/or date using:

    • GET [base]/DocumentReference/$docref?patient=[id]{&type=[type]}{&period=[date]}

    Supported Search Combinations: patient + type + period


  7. Resource Type: Goal

    Supported Profiles:  Argonaut Data Query Goal Profile

    Summary of US Core Search Criteria for StructureDefinition-us-core-goal

    • A client has connected to a server and fetched all of a patient's goals using GET [base]/Goal?patient=[id].
    • A client has connected to a server and fetched all of a patient's goals over a specified time period using GET [base]/Goal?patient=[id]&date=[date]{&date=[date]}.


  8. Resource Type: Immunization

    Supported Profiles:  Argonaut Data Query Immunization Profile

    Summary of Argonaut Search Criteria for StructureDefinition-us-core-immunization

    • A client has connected to a server and fetched all immunizations for a patient using GET /Immunization?patient=[id].


  9. Resource Type: DiagnosticReport

    Supported Profiles:  Argonaut Data Query DiagnosticReport Profile

    Summary of Argonaut Search Criteria for StructureDefinition-us-core-diagnosticreport

    • A client has connected to a server and fetched all of a patient's laboratory diagnostic reports by searching by category using GET [base]/DiagnosticReport?patient=[id]&category=LAB.
    • A client has connected to a server and fetched all of a patient's laboratory diagnostic reports searching by category code and date range using GET [base]/DiagnosticReport?patient=[id]&category=LAB&date=[date]{&date=[date]}.
    • A client has connected to a server and fetched all of all of a patient's laboratory diagnostic reports searching by category and code using GET [base]/DiagnosticReport?patient=[id]&category=LAB&code=[LOINC].
    • A client SHOULD be capable of connecting to a server and fetching any of a patient's laboratory diagnostic reports searching by category and one or more codes and date range using GET [base]/DiagnosticReport?patient=[id]&category=LAB&code=[LOINC1{,LOINC2,LOINC3,...}]&date=[date]{&date=[date]}.


  10. Resource Type: Observation

    Supported Profiles:  Argonaut Data Query Result Observation Profile
    Argonaut Data Query Vital Signs Profile
    Argonaut Data Query Smoking Status Observation Profile

    Summary of Argonaut Search Criteria for StructureDefinition-us-core-observationresults

    • A client has connected to a server and fetched all of a patient's laboratory results by searching by category using GET [base]/Observation?patient=[id]&category=laboratory.
    • A client has connected to a server and fetched all of a patient's laboratory results searching by category code and date range using GET [base]/Observation?patient=[id]&category=laboratory&date=[date]{&date=[date]}.
    • A client has connected to a server and fetched all of all of a patient's laboratory results searching by category and code using GET [base]/Observation?patient=[id]&category=laboratory&code=[LOINC].
    • A client SHOULD be capable of connecting to a server and fetching any of a patient's laboratory results searching by category and one or more codes and date range using GET [base]/Observation?patient=[id]&category=laboratory&code=[LOINC1{,LOINC2,LOINC3,...}]&date=[date]{&date=[date]}.

    Summary of Argonaut Search Criteria for StructureDefinition-us-core-smokingstatus

    • A client has connected to a server and fetched a patient's smoking status using GET [base]/Observation?patient=[id]&code=72166-2.

    Summary of Argonaut Search Criteria for StructureDefinition-us-core-vitalsigns

    • A client has connected to a server and fetched all of a patient's vital signs by searching by category using GET [base]/Observation?patient=[id]&category=vital-signs.
    • A client has connected to a server and fetched all of a patient's vital signs searching by category code and date range using GET [base]/Observation?patient=[id]&category=vital-signs&date=[date]{&date=[date]}.
    • A client has connected to a server and fetched any of a patient's vital signs by searching by one or more of the codes listed below using GET [base]/Observation?patient=[id]&code[vital sign LOINC{,LOINC2,LOINC3,...}].
    • A client SHOULD be capable of connecting to a server and fetching any of a patient's vital signs searching by one or more of the codes listed below and date range using GET [base]/Observation?patient=[id]&code=[LOINC{,LOINC2...}]vital-signs&date=[date]{&date=[date]}.


  11. Resource Type: Medication

    Supported Profiles:  Argonaut Data Query Medication Profile

    The MedicationStatement and MedicationOrder resources can represent a medication, using either a code or refer to a [Medication] resource. If the Medication Resource is used in a MedicationStatement or a MedicationOrder, then the READ and SEARCH Criteria SHALL be supported.


  12. Resource Type: MedicationStatement

    Supported Profiles:  Argonaut Data Query MedicationStatement Profile

    Summary of US Core Search Criteria for StructureDefinition-us-core-medicationstatement

    The MedicationStatement and MedicationOrder resources can represent a medication, using either a code or refer to a Medication resource. When referencing a Medication resource, the resource may be contained or an external resource. The server application can choose any one way or more than one method, but IF the an external reference to Medication is used, the server SHALL support the include parameter for searching this element. The client application SHALL support both methods.

    • A client has connected to a server and fetched a patient's medications using:
    1. GET /MedicationStatement?patient=[id]
    2. GET /MedicationStatement?patient=[id]&_include=MedicationStatement:medication


  13. Resource Type: MedicationOrder

    Supported Profiles:  Argonaut Data Query MedicationOrder Profile

    Summary of US Core Search Criteria for StructureDefinition-us-core-medicationorder

    The MedicationStatement and MedicationOrder resources can represent a medication, using either a code or refer to a Medication resource. When referencing a Medication resource, the resource may be contained or an external resource. The server application can choose any one way or more than one method, but IF the an external reference to Medication is used, the server SHALL support the include parameter for searching this element. The client application SHALL support both methods.

    • A client has connected to a server and fetched a patient's medications using:
    1. GET /MedicationOrder?patient=[id]
    2. GET /MedicationOrder?patient=[id]&_include=MedicationOrder:medication


  14. Resource Type: Procedure

    Supported Profiles:  Argonaut Data Query Procedure Profile

    Summary of US Core Search Criteria for StructureDefinition-us-core-procedure

    • A client connected to a server and fetched all procedures for a patient, including current as well as historical Procedures GET/Procedure?patient=[id].
    • A client has connected to a server and fetched all of a patient's procedures over a specified time period using GET /Procedure?patient=[id]&date=[date]{&date=[date]}.






<?xml version="1.0" encoding="UTF-8"?>
<Conformance xmlns="http://hl7.org/fhir">
  <id value="client"/>
  <meta>
    <versionId value="1"/>
    <lastUpdated value="2018-10-08T18:34:03.143Z"/>
  </meta>
  <text>
    <status value="generated"/>
    <div xmlns="http://www.w3.org/1999/xhtml">
      <span style="font-size:larger font-weight:bold ">Argonaut Data Query Implemenation Guide Client</span>
      <hr/>
      <p>
        <span>FHIR Version: </span>
        <span>1.0.2</span>
        <br/>
        <span>Supported formats: </span>
        <span>xml</span>
        <span>, </span>
        <span>json</span>
        <br/>
        <span>Published: </span>
        <span>2016-10-18</span>
        <br/>
        <span>Published by: </span>
        <span>Argonaut Project</span> </p>
      <p>
        <span>This Conformance instance defines the expected capabilities of a client when conforming to the Argonaut Data Query Implementation Guide.</span> </p>
      <br/>
      <h4>
        <span style="font-size:larger font-weight:bold ">RESTful Behavior</span> </h4>
      <br/>
      <hr/>
      <div>
        <span>Description: </span>
        <p>
          <strong>The Argonaut client SHOULD:</strong>
        </p>
        <ol>
          <li>Support fetching and querying of one or more Argonaut profile(s), using the supported RESTful interactions and search parameters declared in the
            <a href="Conformance-server.html">Argonaut Server Conformance Statement</a>
          </li> </ol>
        <br/>
      </div>
      <div>
        <span>Security: </span>
        <p>
          <strong>Argonaut Data Query clients SHALL</strong>implement the
          <a href="index.html#security">security requirements</a>documented in this guide </p>
        <br/>
      </div>
      <span>Supported Operations: </span>
      <span style="font-weight:bold">SHALL</span>
      <span>Support </span>
      <a href="http://fhir.org/guides/argonaut/OperationDefinition/docref">
        <span>docref</span> </a>
      <h4>
        <span style="font-weight:bold ">Resource&#160; Details:</span> </h4>
      <br/>
      <ol>
        <li>
          <span style="font-weight:bold ">Resource Type: </span>
          <a name="Patient">
            <span style="font-weight:bold ">Patient</span> </a>
          <p>
            <span>Supported Profiles:&#160; </span>
            <a href="http://fhir.org/guides/argonaut/StructureDefinition-argo-patient.html">
              <span>Argonaut Data Query Patient Profile</span>
              <br/> </a>
            <br/> </p>
          <h4>Summary of Argonaut Search Criteria for StructureDefinition-us-core-patient</h4>
          <ul>
            <li>A client has connected to a server and fetched a patient using GET [base]/Patient/[id].</li>
            <li>A client has connected to a server and searched through available Patients using at least 2 (example name and gender) of the following search parameters:
              <ul>
                <li>name</li>
                <li>gender</li>
                <li>birthdate</li> </ul> </li> </ul>
          <p>To limit overly broad search results, a client search with gender
            <strong>SHOULD</strong>include family and given name search parameters.</p>
          <p/>
          <p/>
          <p/>
          <hr/>
        </li>
        <li>
          <span style="font-weight:bold ">Resource Type: </span>
          <a name="AllergyIntolerance">
            <span style="font-weight:bold ">AllergyIntolerance</span> </a>
          <p>
            <span>Supported Profiles:&#160; </span>
            <a href="http://fhir.org/guides/argonaut/StructureDefinition-argo-allergyintolerance.html">
              <span>Argonaut Data Query AllergyIntolerance Profile</span>
              <br/> </a>
            <br/> </p>
          <h4>Summary of Argonaut Search Criteria for StructureDefinition-us-core-allergintolerance</h4>
          <ul>
            <li>A client has connected to a server and fetched a patient's allergies using GET /AllergyIntolerance?patient=[id].</li> </ul>
          <p/>
          <p/>
          <p/>
          <hr/>
        </li>
        <li>
          <span style="font-weight:bold ">Resource Type: </span>
          <a name="CarePlan">
            <span style="font-weight:bold ">CarePlan</span> </a>
          <p>
            <span>Supported Profiles:&#160; </span>
            <a href="http://fhir.org/guides/argonaut/StructureDefinition-argo-careplan.html">
              <span>Argonaut Data Query CarePlan Profile</span>
              <br/> </a>
            <a href="http://fhir.org/guides/argonaut/StructureDefinition-argo-careteam.html">
              <span>Argonaut Data Query CareTeam Profile</span>
              <br/> </a>
            <br/> </p>
          <h4>Summary of Argonaut Search Criteria for StructureDefinition-us-core-careplan</h4>
          <ul>
            <li>c of a patient's Assessment and Plan of Treatment information using GET /CarePlan?patient=[id]&amp;category=assess-plan.</li>
            <li>A client has connected to a server and fetched all of a patient's Assessment and Plan of Treatment information over a specified time period using GET /CarePlan?patient=[id]&amp;category=assess-plan&amp;date=[date].</li> </ul>
          <ul>
            <li>A client
              <strong>SHOULD</strong>be capable of connecting to a server and fetching all of a patient's active Assessment and Plan of Treatment information using GET /CarePlan?patient=[id]&amp;category=assess-plan&amp;status=active.</li>
            <li>A client
              <strong>SHOULD</strong>be capable of connecting to a server and fetching all of a patient's active Assessment and Plan of Treatment information over a specified time period using GET /CarePlan?patient=[id]&amp;category=assess-plan&amp;status=active&amp;date=[date].</li> </ul>
          <h4 id="summary-of-argonaut-search-criteria-for-structuredefinition-argo-careteam">Summary of Argonaut Search Criteria for StructureDefinition-argo-careteam</h4>
          <ul>
            <li>A client has connected to a server and fetched a patients current care team members using GET[base]/CarePlan?patient=[id]&amp;category=careteam&amp;status=active</li> </ul>
          <p/>
          <p/>
          <p/>
          <hr/>
        </li>
        <li>
          <span style="font-weight:bold ">Resource Type: </span>
          <a name="Condition">
            <span style="font-weight:bold ">Condition</span> </a>
          <p>
            <span>Supported Profiles:&#160; </span>
            <a href="http://fhir.org/guides/argonaut/StructureDefinition-argo-condition.html">
              <span>Argonaut Data Query Condition Profile</span>
              <br/> </a>
            <br/> </p>
          <h4>Summary of Argonaut Search Criteria for StructureDefinition-us-core-condition</h4>
          <ul>
            <li>A client connected to a server and fetched all problems and health concerns for a patient, including current as well as historical problems and health concerns using GET/Condition?patient=[id]</li> </ul>
          <p/>
          <p/>
          <p/>
          <hr/>
        </li>
        <li>
          <span style="font-weight:bold ">Resource Type: </span>
          <a name="Device">
            <span style="font-weight:bold ">Device</span> </a>
          <p>
            <span>Supported Profiles:&#160; </span>
            <a href="http://fhir.org/guides/argonaut/StructureDefinition-argo-device.html">
              <span>Argonaut Data Query Device Profile</span>
              <br/> </a>
            <br/> </p>
          <h4>Summary of Argonaut Search Criteria for StructureDefinition-us-core-device</h4>
          <ul>
            <li>A client has connected to a server and fetched all Unique device identifier(s)(UDI)for a patient's implantable device(s)using GET /Device?patient=[id].</li> </ul>
          <p/>
          <p/>
          <p/>
          <hr/>
        </li>
        <li>
          <span style="font-weight:bold ">Resource Type: </span>
          <a name="DocumentReference">
            <span style="font-weight:bold ">DocumentReference</span> </a>
          <p>
            <span>Supported Profiles:&#160; </span>
            <a href="http://fhir.org/guides/argonaut/StructureDefinition-argo-documentreference.html">
              <span>Argonaut Data Query Document Reference Profile</span>
              <br/> </a>
            <br/> </p>
          <h4>Search Criteria for StructureDefinition-argo-documentreference</h4>
          <p>The Server
            <strong>SHALL</strong>support fetching document references using either the direct query for DocumentReference resources as described here or the
            <a href="OperationDefinition-docref.html">$docref operation</a>. The Client
            <strong>SHALL</strong>support both methods.</p>
          <p>A client has connected to a server and fetches document references for a patient:</p>
          <ul>
            <li>
              <code>GET [base]/DocumentReference/$docref?patient=[id]</code>
            </li>
          </ul>
          <p>A client
            <strong>SHOULD</strong>be capable of connecting to a server and fetching references for a patient searched by type and/or date using:</p>
          <ul>
            <li>
              <code>GET [base]/DocumentReference/$docref?patient=[id]{&amp;type=[type]}{&amp;period=[date]}</code>
            </li>
          </ul>
          <p/>
          <p/>
          <p>
            <span>Supported Search Combinations:</span>
            <span>patient</span>
            <span>+ </span>
            <span>type</span>
            <span>+ </span>
            <span>period</span> </p>
          <p/>
          <hr/>
        </li>
        <li>
          <span style="font-weight:bold ">Resource Type: </span>
          <a name="Goal">
            <span style="font-weight:bold ">Goal</span> </a>
          <p>
            <span>Supported Profiles:&#160; </span>
            <a href="http://fhir.org/guides/argonaut/StructureDefinition-argo-goal.html">
              <span>Argonaut Data Query Goal Profile</span>
              <br/> </a>
            <br/> </p>
          <h4>Summary of US Core Search Criteria for StructureDefinition-us-core-goal</h4>
          <ul>
            <li>A client has connected to a server and fetched all of a patient's goals using GET [base]/Goal?patient=[id].</li>
            <li>A client has connected to a server and fetched all of a patient's goals over a specified time period using GET [base]/Goal?patient=[id]&amp;date=[date]{&amp;date=[date]}.</li> </ul>
          <p/>
          <p/>
          <p/>
          <hr/>
        </li>
        <li>
          <span style="font-weight:bold ">Resource Type: </span>
          <a name="Immunization">
            <span style="font-weight:bold ">Immunization</span> </a>
          <p>
            <span>Supported Profiles:&#160; </span>
            <a href="http://fhir.org/guides/argonaut/StructureDefinition-argo-immunization.html">
              <span>Argonaut Data Query Immunization Profile</span>
              <br/> </a>
            <br/> </p>
          <h4>Summary of Argonaut Search Criteria for StructureDefinition-us-core-immunization</h4>
          <ul>
            <li>A client has connected to a server and fetched all immunizations for a patient using GET /Immunization?patient=[id].</li> </ul>
          <p/>
          <p/>
          <p/>
          <hr/>
        </li>
        <li>
          <span style="font-weight:bold ">Resource Type: </span>
          <a name="DiagnosticReport">
            <span style="font-weight:bold ">DiagnosticReport</span> </a>
          <p>
            <span>Supported Profiles:&#160; </span>
            <a href="http://fhir.org/guides/argonaut/StructureDefinition-argo-diagnosticreport.html">
              <span>Argonaut Data Query DiagnosticReport Profile</span>
              <br/> </a>
            <br/> </p>
          <h4>Summary of Argonaut Search Criteria for StructureDefinition-us-core-diagnosticreport</h4>
          <ul>
            <li>A client has connected to a server and fetched all of a patient's laboratory diagnostic reports by searching by category using GET [base]/DiagnosticReport?patient=[id]&amp;category=LAB.</li>
            <li>A client has connected to a server and fetched all of a patient's laboratory diagnostic reports searching by category code and date range using GET [base]/DiagnosticReport?patient=[id]&amp;category=LAB&amp;date=[date]{&amp;date=[date]}.</li>
            <li>A client has connected to a server and fetched all of all of a patient's laboratory diagnostic reports searching by category and code using GET [base]/DiagnosticReport?patient=[id]&amp;category=LAB&amp;code=[LOINC].</li> </ul>
          <ul>
            <li>A client
              <strong>SHOULD</strong>be capable of connecting to a server and fetching any of a patient's laboratory diagnostic reports searching by category and one or more codes and date range using GET [base]/DiagnosticReport?patient=[id]&amp;category=LAB&amp;code=[LOINC1{,LOINC2,LOINC3,...}]&amp;date=[date]{&amp;date=[date]}.</li> </ul>
          <p/>
          <p/>
          <p/>
          <hr/>
        </li>
        <li>
          <span style="font-weight:bold ">Resource Type: </span>
          <a name="Observation">
            <span style="font-weight:bold ">Observation</span> </a>
          <p>
            <span>Supported Profiles:&#160; </span>
            <a href="http://fhir.org/guides/argonaut/StructureDefinition-argo-observationresults.html">
              <span>Argonaut Data Query Result Observation Profile</span>
              <br/> </a>
            <a href="http://fhir.org/guides/argonaut/StructureDefinition-argo-vitalsigns.html">
              <span>Argonaut Data Query Vital Signs Profile</span>
              <br/> </a>
            <a href="http://fhir.org/guides/argonaut/StructureDefinition-argo-smokingstatus.html">
              <span>Argonaut Data Query Smoking Status Observation Profile</span>
              <br/> </a>
            <br/> </p>
          <h4>Summary of Argonaut Search Criteria for StructureDefinition-us-core-observationresults</h4>
          <ul>
            <li>A client has connected to a server and fetched all of a patient's laboratory results by searching by category using GET [base]/Observation?patient=[id]&amp;category=laboratory.</li>
            <li>A client has connected to a server and fetched all of a patient's laboratory results searching by category code and date range using GET [base]/Observation?patient=[id]&amp;category=laboratory&amp;date=[date]{&amp;date=[date]}.</li>
            <li>A client has connected to a server and fetched all of all of a patient's laboratory results searching by category and code using GET [base]/Observation?patient=[id]&amp;category=laboratory&amp;code=[LOINC].</li> </ul>
          <ul>
            <li>A client
              <strong>SHOULD</strong>be capable of connecting to a server and fetching any of a patient's laboratory results searching by category and one or more codes and date range using GET [base]/Observation?patient=[id]&amp;category=laboratory&amp;code=[LOINC1{,LOINC2,LOINC3,...}]&amp;date=[date]{&amp;date=[date]}.</li> </ul>
          <h4>Summary of Argonaut Search Criteria for StructureDefinition-us-core-smokingstatus</h4>
          <ul>
            <li>A client has connected to a server and fetched a patient's smoking status using GET [base]/Observation?patient=[id]&amp;code=72166-2.</li> </ul>
          <h4>Summary of Argonaut Search Criteria for StructureDefinition-us-core-vitalsigns</h4>
          <ul>
            <li>A client has connected to a server and fetched all of a patient's vital signs by searching by category using GET [base]/Observation?patient=[id]&amp;category=vital-signs.</li>
            <li>A client has connected to a server and fetched all of a patient's vital signs searching by category code and date range using GET [base]/Observation?patient=[id]&amp;category=vital-signs&amp;date=[date]{&amp;date=[date]}.</li>
            <li>A client has connected to a server and fetched any of a patient's vital signs by searching by one or more of the codes listed below using GET [base]/Observation?patient=[id]&amp;code[vital sign LOINC{,LOINC2,LOINC3,...}].</li> </ul>
          <ul>
            <li>A client
              <strong>SHOULD</strong>be capable of connecting to a server and fetching any of a patient's vital signs searching by one or more of the codes listed below and date range using GET [base]/Observation?patient=[id]&amp;code=[LOINC{,LOINC2...}]vital-signs&amp;date=[date]{&amp;date=[date]}.</li> </ul>
          <p/>
          <p/>
          <p/>
          <hr/>
        </li>
        <li>
          <span style="font-weight:bold ">Resource Type: </span>
          <a name="Medication">
            <span style="font-weight:bold ">Medication</span> </a>
          <p>
            <span>Supported Profiles:&#160; </span>
            <a href="http://fhir.org/guides/argonaut/StructureDefinition-argo-medication.html">
              <span>Argonaut Data Query Medication Profile</span>
              <br/> </a>
            <br/> </p>
          <p>The MedicationStatement and MedicationOrder resources can represent a medication, using either a code or refer to a [Medication] resource. If the Medication Resource is used in a MedicationStatement or a MedicationOrder, then the READ and SEARCH Criteria
            <strong>SHALL</strong>be supported.</p>
          <p/>
          <p/>
          <p/>
          <hr/>
        </li>
        <li>
          <span style="font-weight:bold ">Resource Type: </span>
          <a name="MedicationStatement">
            <span style="font-weight:bold ">MedicationStatement</span> </a>
          <p>
            <span>Supported Profiles:&#160; </span>
            <a href="http://fhir.org/guides/argonaut/StructureDefinition-argo-medicationstatement.html">
              <span>Argonaut Data Query MedicationStatement Profile</span>
              <br/> </a>
            <br/> </p>
          <p>
            <strong>Summary of US Core Search Criteria for StructureDefinition-us-core-medicationstatement</strong>
          </p>
          <p>The MedicationStatement and MedicationOrder resources can represent a medication, using either a code or refer to a Medication resource. When referencing a Medication resource, the resource may be
            <a href="http://hl7.org/fhir/2017Jan/references.html#contained">contained</a>or an external resource. The server application can choose any one way or more than one method, but
            <strong>IF</strong>the an external reference to Medication is used, the server
            <strong>SHALL</strong>support the
            <a href="http://hl7.org/fhir/2017Jan/references.html#include">include</a>parameter for searching this element. The client application
            <strong>SHALL</strong>support both methods.</p>
          <ul>
            <li>A client has connected to a server and fetched a patient's medications using:</li> </ul>
          <ol>
            <li>GET /MedicationStatement?patient=[id]</li>
            <li>GET /MedicationStatement?patient=[id]&amp;_include=MedicationStatement:medication</li> </ol>
          <p/>
          <p/>
          <p/>
          <hr/>
        </li>
        <li>
          <span style="font-weight:bold ">Resource Type: </span>
          <a name="MedicationOrder">
            <span style="font-weight:bold ">MedicationOrder</span> </a>
          <p>
            <span>Supported Profiles:&#160; </span>
            <a href="http://fhir.org/guides/argonaut/StructureDefinition-argo-MedicationOrder.html">
              <span>Argonaut Data Query MedicationOrder Profile</span>
              <br/> </a>
            <br/> </p>
          <p>
            <strong>Summary of US Core Search Criteria for StructureDefinition-us-core-medicationorder</strong>
          </p>
          <p>The MedicationStatement and MedicationOrder resources can represent a medication, using either a code or refer to a Medication resource. When referencing a Medication resource, the resource may be
            <a href="http://hl7.org/fhir/references.html#contained">contained</a>or an external resource. The server application can choose any one way or more than one method, but
            <strong>IF</strong>the an external reference to Medication is used, the server
            <strong>SHALL</strong>support the
            <a href="http://hl7.org/fhir/references.html#include">include</a>parameter for searching this element. The client application
            <strong>SHALL</strong>support both methods.</p>
          <ul>
            <li>A client has connected to a server and fetched a patient's medications using:</li> </ul>
          <ol>
            <li>GET /MedicationOrder?patient=[id]</li>
            <li>GET /MedicationOrder?patient=[id]&amp;_include=MedicationOrder:medication</li> </ol>
          <p/>
          <p/>
          <p/>
          <hr/>
        </li>
        <li>
          <span style="font-weight:bold ">Resource Type: </span>
          <a name="Procedure">
            <span style="font-weight:bold ">Procedure</span> </a>
          <p>
            <span>Supported Profiles:&#160; </span>
            <a href="http://fhir.org/guides/argonaut/StructureDefinition-argo-procedure.html">
              <span>Argonaut Data Query Procedure Profile</span>
              <br/> </a>
            <br/> </p>
          <h4>Summary of US Core Search Criteria for StructureDefinition-us-core-procedure</h4>
          <ul>
            <li>A client connected to a server and fetched all procedures for a patient, including current as well as historical Procedures GET/Procedure?patient=[id].</li>
            <li>A client has connected to a server and fetched all of a patient's procedures over a specified time period using GET /Procedure?patient=[id]&amp;date=[date]{&amp;date=[date]}.</li> </ul>
          <p/>
          <p/>
          <p/>
          <hr/>
        </li> </ol>
      <br/>
      <br/>
      <br/> </div>
  </text>
  <url value="http://fhir.org/guides/argonaut/Conformance/client"/>
  <name value="Argonaut Data Query Implemenation Guide Client"/>
  <status value="draft"/>
  <publisher value="Argonaut Project"/>
  <contact>
    <telecom>
      <system value="other"/>
      <value value="http://argonautwiki.hl7.org"/>
    </telecom>
  </contact>
  <date value="2016-10-18"/>
  <description value="This Conformance instance defines the expected capabilities of a client when conforming to the Argonaut Data Query Implementation Guide."/>
  <kind value="requirements"/>
  <fhirVersion value="1.0.2"/>
  <acceptUnknown value="extensions"/>
  <format value="xml"/>
  <format value="json"/>
  <profile>
    <extension url="http://fhir.org/guides/argonaut/StructureDefinition/argo-profile-link">
      <valueCode value="AllergyIntolerance"/>
    </extension>
    <reference value="http://fhir.org/guides/argonaut/StructureDefinition-argo-allergyintolerance.html"/>
    <display value="Argonaut Data Query AllergyIntolerance Profile"/>
  </profile>
  <profile>
    <extension url="http://fhir.org/guides/argonaut/StructureDefinition/argo-profile-link">
      <valueCode value="CarePlan"/>
    </extension>
    <reference value="http://fhir.org/guides/argonaut/StructureDefinition-argo-careplan.html"/>
    <display value="Argonaut Data Query CarePlan Profile"/>
  </profile>
  <profile>
    <extension url="http://fhir.org/guides/argonaut/StructureDefinition/argo-profile-link">
      <valueCode value="CarePlan"/>
    </extension>
    <reference value="http://fhir.org/guides/argonaut/StructureDefinition-argo-careteam.html"/>
    <display value="Argonaut Data Query CareTeam Profile"/>
  </profile>
  <profile>
    <extension url="http://fhir.org/guides/argonaut/StructureDefinition/argo-profile-link">
      <valueCode value="Condition"/>
    </extension>
    <reference value="http://fhir.org/guides/argonaut/StructureDefinition-argo-condition.html"/>
    <display value="Argonaut Data Query Condition Profile"/>
  </profile>
  <profile>
    <extension url="http://fhir.org/guides/argonaut/StructureDefinition/argo-profile-link">
      <valueCode value="DocumentReference"/>
    </extension>
    <reference value="http://fhir.org/guides/argonaut/StructureDefinition-argo-documentreference.html"/>
    <display value="Argonaut Data Query Document Reference Profile"/>
  </profile>
  <profile>
    <extension url="http://fhir.org/guides/argonaut/StructureDefinition/argo-profile-link">
      <valueCode value="Device"/>
    </extension>
    <reference value="http://fhir.org/guides/argonaut/StructureDefinition-argo-device.html"/>
    <display value="Argonaut Data Query Device Profile"/>
  </profile>
  <profile>
    <extension url="http://fhir.org/guides/argonaut/StructureDefinition/argo-profile-link">
      <valueCode value="Goal"/>
    </extension>
    <reference value="http://fhir.org/guides/argonaut/StructureDefinition-argo-goal.html"/>
    <display value="Argonaut Data Query Goal Profile"/>
  </profile>
  <profile>
    <extension url="http://fhir.org/guides/argonaut/StructureDefinition/argo-profile-link">
      <valueCode value="Immunization"/>
    </extension>
    <reference value="http://fhir.org/guides/argonaut/StructureDefinition-argo-immunization.html"/>
    <display value="Argonaut Data Query Immunization Profile"/>
  </profile>
  <profile>
    <extension url="http://fhir.org/guides/argonaut/StructureDefinition/argo-profile-link">
      <valueCode value="DiagnosticReport"/>
    </extension>
    <reference value="http://fhir.org/guides/argonaut/StructureDefinition-argo-diagnosticreport.html"/>
    <display value="Argonaut Data Query DiagnosticReport Profile"/>
  </profile>
  <profile>
    <extension url="http://fhir.org/guides/argonaut/StructureDefinition/argo-profile-link">
      <valueCode value="Observation"/>
    </extension>
    <reference value="http://fhir.org/guides/argonaut/StructureDefinition-argo-observationresults.html"/>
    <display value="Argonaut Data Query Result Observation Profile"/>
  </profile>
  <profile>
    <extension url="http://fhir.org/guides/argonaut/StructureDefinition/argo-profile-link">
      <valueCode value="Medication"/>
    </extension>
    <reference value="http://fhir.org/guides/argonaut/StructureDefinition-argo-medication.html"/>
    <display value="Argonaut Data Query Medication Profile"/>
  </profile>
  <profile>
    <extension url="http://fhir.org/guides/argonaut/StructureDefinition/argo-profile-link">
      <valueCode value="MedicationOrder"/>
    </extension>
    <reference value="http://fhir.org/guides/argonaut/StructureDefinition-argo-MedicationOrder.html"/>
    <display value="Argonaut Data Query MedicationOrder Profile"/>
  </profile>
  <profile>
    <extension url="http://fhir.org/guides/argonaut/StructureDefinition/argo-profile-link">
      <valueCode value="MedicationStatement"/>
    </extension>
    <reference value="http://fhir.org/guides/argonaut/StructureDefinition-argo-medicationstatement.html"/>
    <display value="Argonaut Data Query MedicationStatement Profile"/>
  </profile>
  <profile>
    <extension url="http://fhir.org/guides/argonaut/StructureDefinition/argo-profile-link">
      <valueCode value="Observation"/>
    </extension>
    <reference value="http://fhir.org/guides/argonaut/StructureDefinition-argo-vitalsigns.html"/>
    <display value="Argonaut Data Query Vital Signs Profile"/>
  </profile>
  <profile>
    <extension url="http://fhir.org/guides/argonaut/StructureDefinition/argo-profile-link">
      <valueCode value="Observation"/>
    </extension>
    <reference value="http://fhir.org/guides/argonaut/StructureDefinition-argo-smokingstatus.html"/>
    <display value="Argonaut Data Query Smoking Status Observation Profile"/>
  </profile>
  <profile>
    <extension url="http://fhir.org/guides/argonaut/StructureDefinition/argo-profile-link">
      <valueCode value="Patient"/>
    </extension>
    <reference value="http://fhir.org/guides/argonaut/StructureDefinition-argo-patient.html"/>
    <display value="Argonaut Data Query Patient Profile"/>
  </profile>
  <profile>
    <extension url="http://fhir.org/guides/argonaut/StructureDefinition/argo-profile-link">
      <valueCode value="Procedure"/>
    </extension>
    <reference value="http://fhir.org/guides/argonaut/StructureDefinition-argo-procedure.html"/>
    <display value="Argonaut Data Query Procedure Profile"/>
  </profile>
  <rest>
    <mode value="client"/>
    <documentation value=" &lt;p&gt;&lt;strong&gt;The Argonaut client SHOULD:&lt;/strong&gt;&lt;/p&gt; &lt;ol&gt; &lt;li&gt;Support fetching and querying of one or more Argonaut profile(s), using the supported RESTful interactions and search parameters declared in the &lt;a href=&quot;Conformance-server.html&quot;&gt;Argonaut Server Conformance Statement&lt;/a&gt;&lt;/li&gt; &lt;/ol&gt; "/>
    <security>
      <description value=" &lt;p&gt;&lt;strong&gt;Argonaut Data Query clients SHALL&lt;/strong&gt; implement the &lt;a href=&quot;index.html#security&quot;&gt;security requirements&lt;/a&gt; documented in this guide &lt;/p&gt; "/>
    </security>
    <resource>
      <extension url="http://fhir.org/guides/argonaut/StructureDefinition/argo-resource-documentation">
        <valueMarkdown value=" &lt;h4&gt;Summary of Argonaut Search Criteria for StructureDefinition-us-core-patient&lt;/h4&gt; &lt;ul&gt; &lt;li&gt;A client has connected to a server and fetched a patient using GET [base]/Patient/[id].&lt;/li&gt; &lt;li&gt;A client has connected to a server and searched through available Patients using at least 2 (example name and gender) of the following search parameters: &lt;ul&gt; &lt;li&gt;name&lt;/li&gt; &lt;li&gt;gender&lt;/li&gt; &lt;li&gt;birthdate&lt;/li&gt; &lt;/ul&gt; &lt;/li&gt; &lt;/ul&gt; &lt;p&gt;To limit overly broad search results, a client search with gender &lt;strong&gt;SHOULD&lt;/strong&gt; include family and given name search parameters.&lt;/p&gt; "/>
      </extension>
      <type value="Patient"/>
      <interaction>
        <extension url="http://hl7.org/fhir/StructureDefinition/conformance-expectation">
          <valueCode value="SHOULD"/>
        </extension>
        <code value="search-type"/>
        <documentation value="Allows discovery of existing Argonaut Data Query patient resources using different search criteria"/>
      </interaction>
      <interaction>
        <extension url="http://hl7.org/fhir/StructureDefinition/conformance-expectation">
          <valueCode value="SHOULD"/>
        </extension>
        <code value="read"/>
        <documentation value="Allows retrieval of a specific Argonaut Data Query patients by id"/>
      </interaction>
      <interaction>
        <extension url="http://hl7.org/fhir/StructureDefinition/conformance-expectation">
          <valueCode value="MAY"/>
        </extension>
        <code value="history-instance"/>
        <documentation value="Allows review of changes to Argonaut Data Query patient instance over time"/>
      </interaction>
      <interaction>
        <extension url="http://hl7.org/fhir/StructureDefinition/conformance-expectation">
          <valueCode value="MAY"/>
        </extension>
        <code value="vread"/>
        <documentation value="Allows retrieval of a historical version of a Argonaut Data Query patient instance"/>
      </interaction>
    </resource>
    <resource>
      <extension url="http://fhir.org/guides/argonaut/StructureDefinition/argo-resource-documentation">
        <valueMarkdown value=" &lt;h4&gt;Summary of Argonaut Search Criteria for StructureDefinition-us-core-allergintolerance&lt;/h4&gt; &lt;ul&gt; &lt;li&gt;A client has connected to a server and fetched a patient&apos;s allergies using GET /AllergyIntolerance?patient=[id].&lt;/li&gt; &lt;/ul&gt; "/>
      </extension>
      <type value="AllergyIntolerance"/>
      <interaction>
        <extension url="http://hl7.org/fhir/StructureDefinition/conformance-expectation">
          <valueCode value="SHOULD"/>
        </extension>
        <code value="search-type"/>
        <documentation value="Allows discovery of existing Argonaut Data Query AllergyIntolerance resources using different search criteria"/>
      </interaction>
      <interaction>
        <extension url="http://hl7.org/fhir/StructureDefinition/conformance-expectation">
          <valueCode value="SHOULD"/>
        </extension>
        <code value="read"/>
        <documentation value="Allows retrieval of a specific Argonaut Data Query AllergyIntolerance by id"/>
      </interaction>
      <interaction>
        <extension url="http://hl7.org/fhir/StructureDefinition/conformance-expectation">
          <valueCode value="MAY"/>
        </extension>
        <code value="history-instance"/>
        <documentation value="Allows review of changes to Argonaut Data Query AllergyIntolerance instance over time"/>
      </interaction>
      <interaction>
        <extension url="http://hl7.org/fhir/StructureDefinition/conformance-expectation">
          <valueCode value="MAY"/>
        </extension>
        <code value="vread"/>
        <documentation value="Allows retrieval of a historical version of a Argonaut Data Query AllergyIntolerance instance"/>
      </interaction>
    </resource>
    <resource>
      <extension url="http://fhir.org/guides/argonaut/StructureDefinition/argo-resource-documentation">
        <valueMarkdown value=" &lt;h4&gt;Summary of Argonaut Search Criteria for StructureDefinition-us-core-careplan&lt;/h4&gt; &lt;ul&gt; &lt;li&gt;c of a patient&apos;s Assessment and Plan of Treatment information using GET /CarePlan?patient=[id]&amp;ampcategory=assess-plan.&lt;/li&gt; &lt;li&gt;A client &lt;strong&gt;SHOULD&lt;/strong&gt; be capable of connecting to a server and fetched all of a patient&apos;s Assessment and Plan of Treatment information over a specified time period using GET /CarePlan?patient=[id]&amp;ampcategory=assess-plan&amp;ampdate=[date].&lt;/li&gt; &lt;/ul&gt; &lt;ul&gt; &lt;li&gt;A client &lt;strong&gt;SHOULD&lt;/strong&gt; be capable of connecting to a server and fetching all of a patient&apos;s active Assessment and Plan of Treatment information using GET /CarePlan?patient=[id]&amp;ampcategory=assess-plan&amp;ampstatus=active.&lt;/li&gt; &lt;li&gt;A client &lt;strong&gt;SHOULD&lt;/strong&gt; be capable of connecting to a server and fetching all of a patient&apos;s active Assessment and Plan of Treatment information over a specified time period using GET /CarePlan?patient=[id]&amp;ampcategory=assess-plan&amp;ampstatus=active&amp;ampdate=[date].&lt;/li&gt; &lt;/ul&gt; &lt;h4 id=&quot;summary-of-argonaut-search-criteria-for-structuredefinition-argo-careteam&quot;&gt;Summary of Argonaut Search Criteria for StructureDefinition-argo-careteam&lt;/h4&gt; &lt;ul&gt; &lt;li&gt;A client has connected to a server and fetched a patients current care team members using GET[base]/CarePlan?patient=[id]&amp;ampcategory=careteam&amp;ampstatus=active&lt;/li&gt; &lt;/ul&gt; "/>
      </extension>
      <type value="CarePlan"/>
      <interaction>
        <extension url="http://hl7.org/fhir/StructureDefinition/conformance-expectation">
          <valueCode value="SHOULD"/>
        </extension>
        <code value="search-type"/>
        <documentation value="Allows discovery of existing Argonaut Data Query careplan resources using different search criteria"/>
      </interaction>
      <interaction>
        <extension url="http://hl7.org/fhir/StructureDefinition/conformance-expectation">
          <valueCode value="SHOULD"/>
        </extension>
        <code value="read"/>
        <documentation value="Allows retrieval of a specific Argonaut Data Query careplan by id"/>
      </interaction>
      <interaction>
        <extension url="http://hl7.org/fhir/StructureDefinition/conformance-expectation">
          <valueCode value="MAY"/>
        </extension>
        <code value="history-instance"/>
        <documentation value="Allows review of changes to Argonaut Data Query careplan instance over time"/>
      </interaction>
      <interaction>
        <extension url="http://hl7.org/fhir/StructureDefinition/conformance-expectation">
          <valueCode value="MAY"/>
        </extension>
        <code value="vread"/>
        <documentation value="Allows retrieval of a historical version of a Argonaut Data Query careplan instance"/>
      </interaction>
    </resource>
    <resource>
      <extension url="http://fhir.org/guides/argonaut/StructureDefinition/argo-resource-documentation">
        <valueMarkdown value=" &lt;h4&gt;Summary of Argonaut Search Criteria for StructureDefinition-us-core-condition&lt;/h4&gt; &lt;ul&gt; &lt;li&gt;A client connected to a server and fetched all problems and health concerns for a patient, including current as well as historical problems and health concerns using GET/Condition?patient=[id]&lt;/li&gt; &lt;/ul&gt; "/>
      </extension>
      <type value="Condition"/>
      <interaction>
        <extension url="http://hl7.org/fhir/StructureDefinition/conformance-expectation">
          <valueCode value="SHOULD"/>
        </extension>
        <code value="search-type"/>
        <documentation value="Allows discovery of existing Argonaut Data Query condition resources using different search criteria"/>
      </interaction>
      <interaction>
        <extension url="http://hl7.org/fhir/StructureDefinition/conformance-expectation">
          <valueCode value="SHOULD"/>
        </extension>
        <code value="read"/>
        <documentation value="Allows retrieval of a specific Argonaut Data Query condition by id"/>
      </interaction>
      <interaction>
        <extension url="http://hl7.org/fhir/StructureDefinition/conformance-expectation">
          <valueCode value="MAY"/>
        </extension>
        <code value="history-instance"/>
        <documentation value="Allows review of changes to Argonaut Data Query condition instance over time"/>
      </interaction>
      <interaction>
        <extension url="http://hl7.org/fhir/StructureDefinition/conformance-expectation">
          <valueCode value="MAY"/>
        </extension>
        <code value="vread"/>
        <documentation value="Allows retrieval of a historical version of a Argonaut Data Query condition instance"/>
      </interaction>
    </resource>
    <resource>
      <extension url="http://fhir.org/guides/argonaut/StructureDefinition/argo-resource-documentation">
        <valueMarkdown value=" &lt;h4&gt;Summary of Argonaut Search Criteria for StructureDefinition-us-core-device&lt;/h4&gt; &lt;ul&gt; &lt;li&gt;A client has connected to a server and fetched all Unique device identifier(s)(UDI)for a patient&apos;s implantable device(s)using GET /Device?patient=[id].&lt;/li&gt; &lt;/ul&gt; "/>
      </extension>
      <type value="Device"/>
      <interaction>
        <extension url="http://hl7.org/fhir/StructureDefinition/conformance-expectation">
          <valueCode value="SHOULD"/>
        </extension>
        <code value="search-type"/>
        <documentation value="Allows discovery of existing Argonaut Data Query device resources using different search criteria"/>
      </interaction>
      <interaction>
        <extension url="http://hl7.org/fhir/StructureDefinition/conformance-expectation">
          <valueCode value="SHOULD"/>
        </extension>
        <code value="read"/>
        <documentation value="Allows retrieval of a specific Argonaut Data Query device by id"/>
      </interaction>
      <interaction>
        <extension url="http://hl7.org/fhir/StructureDefinition/conformance-expectation">
          <valueCode value="MAY"/>
        </extension>
        <code value="history-instance"/>
        <documentation value="Allows review of changes to Argonaut Data Query device instance over time"/>
      </interaction>
      <interaction>
        <extension url="http://hl7.org/fhir/StructureDefinition/conformance-expectation">
          <valueCode value="MAY"/>
        </extension>
        <code value="vread"/>
        <documentation value="Allows retrieval of a historical version of a Argonaut Data Query device instance"/>
      </interaction>
    </resource>
    <resource>
      <extension url="http://fhir.org/guides/argonaut/StructureDefinition/argo-resource-documentation">
        <valueMarkdown value=" &lt;h4&gt;Search Criteria for StructureDefinition-argo-documentreference&lt;/h4&gt; &lt;p&gt; The Server &lt;strong&gt;SHALL&lt;/strong&gt; support fetching document references using either the direct query for DocumentReference resources as described here or the &lt;a href=&quot;OperationDefinition-docref.html&quot;&gt;$docref operation&lt;/a&gt;. The Client &lt;strong&gt;SHALL&lt;/strong&gt; support both methods.&lt;/p&gt; &lt;p&gt;A client has connected to a server and fetches document references for a patient:&lt;/p&gt;&lt;ul&gt;&lt;li&gt;&lt;code&gt;GET [base]/DocumentReference/$docref?patient=[id]&lt;/code&gt;&lt;/li&gt;&lt;/ul&gt;&lt;p&gt;A client &lt;strong&gt;SHOULD&lt;/strong&gt; be capable of connecting to a server and fetching references for a patient searched by type and/or date using:&lt;/p&gt;&lt;ul&gt;&lt;li&gt;&lt;code&gt;GET [base]/DocumentReference/$docref?patient=[id]{&amp;amptype=[type]}{&amp;ampperiod=[date]}&lt;/code&gt;&lt;/li&gt;&lt;/ul&gt; "/>
      </extension>
      <extension url="http://hl7.org/fhir/StructureDefinition/conformance-search-parameter-combination">
        <extension url="required">
          <valueString value="patient"/>
        </extension>
        <extension url="required">
          <valueString value="type"/>
        </extension>
        <extension url="required">
          <valueString value="period"/>
        </extension>
      </extension>
      <type value="DocumentReference"/>
      <interaction>
        <extension url="http://hl7.org/fhir/StructureDefinition/conformance-expectation">
          <valueCode value="SHALL"/>
        </extension>
        <code value="search-type"/>
        <documentation value="Allows discovery of existing Argonaut Document Query DocumentReference resources using different search criteria"/>
      </interaction>
      <interaction>
        <extension url="http://hl7.org/fhir/StructureDefinition/conformance-expectation">
          <valueCode value="SHALL"/>
        </extension>
        <code value="read"/>
        <documentation value="Allows retrieval of a specific Argonaut Document Query DocumentReference by id"/>
      </interaction>
      <interaction>
        <extension url="http://hl7.org/fhir/StructureDefinition/conformance-expectation">
          <valueCode value="SHOULD"/>
        </extension>
        <code value="history-instance"/>
        <documentation value="Allows review of changes to Argonaut Document Query DocumentReference instance over time"/>
      </interaction>
      <interaction>
        <extension url="http://hl7.org/fhir/StructureDefinition/conformance-expectation">
          <valueCode value="SHOULD"/>
        </extension>
        <code value="vread"/>
        <documentation value="Allows retrieval of a historical version of a Argonaut Document Query DocumentReference instance"/>
      </interaction>
    </resource>
    <resource>
      <extension url="http://fhir.org/guides/argonaut/StructureDefinition/argo-resource-documentation">
        <valueMarkdown value=" &lt;h4&gt;Summary of US Core Search Criteria for StructureDefinition-us-core-goal&lt;/h4&gt; &lt;ul&gt; &lt;li&gt;A client has connected to a server and fetched all of a patient&apos;s goals using GET [base]/Goal?patient=[id].&lt;/li&gt; &lt;li&gt;A client has connected to a server and fetched all of a patient&apos;s goals over a specified time period using GET [base]/Goal?patient=[id]&amp;ampdate=[date]{&amp;ampdate=[date]}.&lt;/li&gt; &lt;/ul&gt; "/>
      </extension>
      <type value="Goal"/>
      <interaction>
        <extension url="http://hl7.org/fhir/StructureDefinition/conformance-expectation">
          <valueCode value="SHOULD"/>
        </extension>
        <code value="search-type"/>
        <documentation value="Allows discovery of existing Argonaut Data Query goal resources using different search criteria"/>
      </interaction>
      <interaction>
        <extension url="http://hl7.org/fhir/StructureDefinition/conformance-expectation">
          <valueCode value="SHOULD"/>
        </extension>
        <code value="read"/>
        <documentation value="Allows retrieval of a specific Argonaut Data Query goal by id"/>
      </interaction>
      <interaction>
        <extension url="http://hl7.org/fhir/StructureDefinition/conformance-expectation">
          <valueCode value="MAY"/>
        </extension>
        <code value="history-instance"/>
        <documentation value="Allows review of changes to Argonaut Data Query goal instance over time"/>
      </interaction>
      <interaction>
        <extension url="http://hl7.org/fhir/StructureDefinition/conformance-expectation">
          <valueCode value="MAY"/>
        </extension>
        <code value="vread"/>
        <documentation value="Allows retrieval of a historical version of a Argonaut Data Query goal instance"/>
      </interaction>
    </resource>
    <resource>
      <extension url="http://fhir.org/guides/argonaut/StructureDefinition/argo-resource-documentation">
        <valueMarkdown value=" &lt;h4&gt;Summary of Argonaut Search Criteria for StructureDefinition-us-core-immunization&lt;/h4&gt; &lt;ul&gt; &lt;li&gt;A client has connected to a server and fetched all immunizations for a patient using GET /Immunization?patient=[id].&lt;/li&gt; &lt;/ul&gt; "/>
      </extension>
      <type value="Immunization"/>
      <interaction>
        <extension url="http://hl7.org/fhir/StructureDefinition/conformance-expectation">
          <valueCode value="SHOULD"/>
        </extension>
        <code value="search-type"/>
        <documentation value="Allows discovery of existing Argonaut Data Query immunization resources using different search criteria"/>
      </interaction>
      <interaction>
        <extension url="http://hl7.org/fhir/StructureDefinition/conformance-expectation">
          <valueCode value="SHOULD"/>
        </extension>
        <code value="read"/>
        <documentation value="Allows retrieval of a specific Argonaut Data Query immunization by id"/>
      </interaction>
      <interaction>
        <extension url="http://hl7.org/fhir/StructureDefinition/conformance-expectation">
          <valueCode value="MAY"/>
        </extension>
        <code value="history-instance"/>
        <documentation value="Allows review of changes to Argonaut Data Query immunization instance over time"/>
      </interaction>
      <interaction>
        <extension url="http://hl7.org/fhir/StructureDefinition/conformance-expectation">
          <valueCode value="MAY"/>
        </extension>
        <code value="vread"/>
        <documentation value="Allows retrieval of a historical version of a Argonaut Data Query immunization instance"/>
      </interaction>
    </resource>
    <resource>
      <extension url="http://fhir.org/guides/argonaut/StructureDefinition/argo-resource-documentation">
        <valueMarkdown value=" &lt;h4&gt;Summary of Argonaut Search Criteria for StructureDefinition-us-core-diagnosticreport&lt;/h4&gt; &lt;ul&gt; &lt;li&gt;A client has connected to a server and fetched all of a patient&apos;s laboratory diagnostic reports by searching by category using GET [base]/DiagnosticReport?patient=[id]&amp;ampcategory=LAB.&lt;/li&gt; &lt;li&gt;A client has connected to a server and fetched all of a patient&apos;s laboratory diagnostic reports searching by category code and date range using GET [base]/DiagnosticReport?patient=[id]&amp;ampcategory=LAB&amp;ampdate=[date]{&amp;ampdate=[date]}.&lt;/li&gt; &lt;li&gt;A client has connected to a server and fetched all of all of a patient&apos;s laboratory diagnostic reports searching by category and code using GET [base]/DiagnosticReport?patient=[id]&amp;ampcategory=LAB&amp;ampcode=[LOINC].&lt;/li&gt; &lt;/ul&gt; &lt;ul&gt; &lt;li&gt;A client &lt;strong&gt;SHOULD&lt;/strong&gt; be capable of connecting to a server and fetching any of a patient&apos;s laboratory diagnostic reports searching by category and one or more codes and date range using GET [base]/DiagnosticReport?patient=[id]&amp;ampcategory=LAB&amp;ampcode=[LOINC1{,LOINC2,LOINC3,...}]&amp;ampdate=[date]{&amp;ampdate=[date]}.&lt;/li&gt; &lt;/ul&gt; "/>
      </extension>
      <type value="DiagnosticReport"/>
      <interaction>
        <extension url="http://hl7.org/fhir/StructureDefinition/conformance-expectation">
          <valueCode value="SHOULD"/>
        </extension>
        <code value="search-type"/>
        <documentation value="Allows discovery of existing Argonaut Data Query diagnosticreport resources using different search criteria"/>
      </interaction>
      <interaction>
        <extension url="http://hl7.org/fhir/StructureDefinition/conformance-expectation">
          <valueCode value="SHOULD"/>
        </extension>
        <code value="read"/>
        <documentation value="Allows retrieval of a specific Argonaut Data Query diagnosticreport by id"/>
      </interaction>
      <interaction>
        <extension url="http://hl7.org/fhir/StructureDefinition/conformance-expectation">
          <valueCode value="MAY"/>
        </extension>
        <code value="history-instance"/>
        <documentation value="Allows review of changes to Argonaut Data Query diagnosticreport instance over time"/>
      </interaction>
      <interaction>
        <extension url="http://hl7.org/fhir/StructureDefinition/conformance-expectation">
          <valueCode value="MAY"/>
        </extension>
        <code value="vread"/>
        <documentation value="Allows retrieval of a historical version of a Argonaut Data Query diagnosticreport instance"/>
      </interaction>
    </resource>
    <resource>
      <extension url="http://fhir.org/guides/argonaut/StructureDefinition/argo-resource-documentation">
        <valueMarkdown value=" &lt;h4&gt;Summary of Argonaut Search Criteria for StructureDefinition-us-core-observationresults&lt;/h4&gt; &lt;ul&gt; &lt;li&gt;A client has connected to a server and fetched all of a patient&apos;s laboratory results by searching by category using GET [base]/Observation?patient=[id]&amp;ampcategory=laboratory.&lt;/li&gt; &lt;li&gt;A client has connected to a server and fetched all of a patient&apos;s laboratory results searching by category code and date range using GET [base]/Observation?patient=[id]&amp;ampcategory=laboratory&amp;ampdate=[date]{&amp;ampdate=[date]}.&lt;/li&gt; &lt;li&gt;A client has connected to a server and fetched all of all of a patient&apos;s laboratory results searching by category and code using GET [base]/Observation?patient=[id]&amp;ampcategory=laboratory&amp;ampcode=[LOINC].&lt;/li&gt; &lt;/ul&gt; &lt;ul&gt; &lt;li&gt;A client &lt;strong&gt;SHOULD&lt;/strong&gt; be capable of connecting to a server and fetching any of a patient&apos;s laboratory results searching by category and one or more codes and date range using GET [base]/Observation?patient=[id]&amp;ampcategory=laboratory&amp;ampcode=[LOINC1{,LOINC2,LOINC3,...}]&amp;ampdate=[date]{&amp;ampdate=[date]}.&lt;/li&gt; &lt;/ul&gt; &lt;h4&gt;Summary of Argonaut Search Criteria for StructureDefinition-us-core-smokingstatus&lt;/h4&gt; &lt;ul&gt; &lt;li&gt;A client has connected to a server and fetched a patient&apos;s smoking status using GET [base]/Observation?patient=[id]&amp;ampcode=72166-2.&lt;/li&gt; &lt;/ul&gt; &lt;h4&gt;Summary of Argonaut Search Criteria for StructureDefinition-us-core-vitalsigns&lt;/h4&gt; &lt;ul&gt; &lt;li&gt;A client has connected to a server and fetched all of a patient&apos;s vital signs by searching by category using GET [base]/Observation?patient=[id]&amp;ampcategory=vital-signs.&lt;/li&gt; &lt;li&gt;A client has connected to a server and fetched all of a patient&apos;s vital signs searching by category code and date range using GET [base]/Observation?patient=[id]&amp;ampcategory=vital-signs&amp;ampdate=[date]{&amp;ampdate=[date]}.&lt;/li&gt; &lt;li&gt;A client has connected to a server and fetched any of a patient&apos;s vital signs by searching by one or more of the codes listed below using GET [base]/Observation?patient=[id]&amp;ampcode[vital sign LOINC{,LOINC2,LOINC3,...}].&lt;/li&gt; &lt;/ul&gt; &lt;ul&gt; &lt;li&gt;A client &lt;strong&gt;SHOULD&lt;/strong&gt; be capable of connecting to a server and fetching any of a patient&apos;s vital signs searching by one or more of the codes listed below and date range using GET [base]/Observation?patient=[id]&amp;ampcode=[LOINC{,LOINC2...}]vital-signs&amp;ampdate=[date]{&amp;ampdate=[date]}.&lt;/li&gt; &lt;/ul&gt; "/>
      </extension>
      <type value="Observation"/>
      <interaction>
        <extension url="http://hl7.org/fhir/StructureDefinition/conformance-expectation">
          <valueCode value="SHOULD"/>
        </extension>
        <code value="search-type"/>
        <documentation value="Allows discovery of existing Argonaut Data Query resultobs resources using different search criteria"/>
      </interaction>
      <interaction>
        <extension url="http://hl7.org/fhir/StructureDefinition/conformance-expectation">
          <valueCode value="SHOULD"/>
        </extension>
        <code value="read"/>
        <documentation value="Allows retrieval of a specific Argonaut Data Query resultobs by id"/>
      </interaction>
      <interaction>
        <extension url="http://hl7.org/fhir/StructureDefinition/conformance-expectation">
          <valueCode value="MAY"/>
        </extension>
        <code value="history-instance"/>
        <documentation value="Allows review of changes to Argonaut Data Query resultobs instance over time"/>
      </interaction>
      <interaction>
        <extension url="http://hl7.org/fhir/StructureDefinition/conformance-expectation">
          <valueCode value="MAY"/>
        </extension>
        <code value="vread"/>
        <documentation value="Allows retrieval of a historical version of a Argonaut Data Query resultobs instance"/>
      </interaction>
    </resource>
    <resource>
      <extension url="http://fhir.org/guides/argonaut/StructureDefinition/argo-resource-documentation">
        <valueMarkdown value=" &lt;p&gt;The MedicationStatement and MedicationOrder resources can represent a medication, using either a code or refer to a [Medication] resource. If the Medication Resource is used in a MedicationStatement or a MedicationOrder, then the READ and SEARCH Criteria &lt;strong&gt;SHALL&lt;/strong&gt; be supported.&lt;/p&gt; "/>
      </extension>
      <type value="Medication"/>
      <interaction>
        <extension url="http://hl7.org/fhir/StructureDefinition/conformance-expectation">
          <valueCode value="SHOULD"/>
        </extension>
        <code value="search-type"/>
        <documentation value="Allows discovery of existing Argonaut Data Query medicationstatement resources using different search criteria"/>
      </interaction>
      <interaction>
        <extension url="http://hl7.org/fhir/StructureDefinition/conformance-expectation">
          <valueCode value="SHOULD"/>
        </extension>
        <code value="read"/>
        <documentation value="Allows retrieval of a specific Argonaut Data Query medicationstatement by id"/>
      </interaction>
      <interaction>
        <extension url="http://hl7.org/fhir/StructureDefinition/conformance-expectation">
          <valueCode value="MAY"/>
        </extension>
        <code value="history-instance"/>
        <documentation value="Allows review of changes to Argonaut Data Query medicationstatement instance over time"/>
      </interaction>
      <interaction>
        <extension url="http://hl7.org/fhir/StructureDefinition/conformance-expectation">
          <valueCode value="MAY"/>
        </extension>
        <code value="vread"/>
        <documentation value="Allows retrieval of a historical version of a Argonaut Data Query medicationstatement instance"/>
      </interaction>
    </resource>
    <resource>
      <extension url="http://fhir.org/guides/argonaut/StructureDefinition/argo-resource-documentation">
        <valueMarkdown value=" &lt;p&gt;&lt;strong&gt;Summary of US Core Search Criteria for StructureDefinition-us-core-medicationstatement&lt;/strong&gt;&lt;/p&gt; &lt;p&gt;The MedicationStatement and MedicationOrder resources can represent a medication, using either a code or refer to a Medication resource. When referencing a Medication resource, the resource may be &lt;a href=&quot;http://hl7.org/fhir/2017Jan/references.html#contained&quot;&gt;contained&lt;/a&gt; or an external resource. The server application can choose any one way or more than one method, but &lt;strong&gt;IF&lt;/strong&gt; the an external reference to Medication is used, the server &lt;strong&gt;SHALL&lt;/strong&gt; support the &lt;a href=&quot;http://hl7.org/fhir/2017Jan/references.html#include&quot;&gt;include&lt;/a&gt; parameter for searching this element. The client application &lt;strong&gt;SHALL&lt;/strong&gt; support both methods.&lt;/p&gt; &lt;ul&gt; &lt;li&gt;A client has connected to a server and fetched a patient&apos;s medications using:&lt;/li&gt; &lt;/ul&gt; &lt;ol&gt; &lt;li&gt;GET /MedicationStatement?patient=[id]&lt;/li&gt; &lt;li&gt;GET /MedicationStatement?patient=[id]&amp;amp_include=MedicationStatement:medication&lt;/li&gt; &lt;/ol&gt; "/>
      </extension>
      <type value="MedicationStatement"/>
      <interaction>
        <extension url="http://hl7.org/fhir/StructureDefinition/conformance-expectation">
          <valueCode value="SHOULD"/>
        </extension>
        <code value="search-type"/>
        <documentation value="Allows discovery of existing Argonaut Data Query medicationstatement resources using different search criteria"/>
      </interaction>
      <interaction>
        <extension url="http://hl7.org/fhir/StructureDefinition/conformance-expectation">
          <valueCode value="SHOULD"/>
        </extension>
        <code value="read"/>
        <documentation value="Allows retrieval of a specific Argonaut Data Query medicationstatement by id"/>
      </interaction>
      <interaction>
        <extension url="http://hl7.org/fhir/StructureDefinition/conformance-expectation">
          <valueCode value="MAY"/>
        </extension>
        <code value="history-instance"/>
        <documentation value="Allows review of changes to Argonaut Data Query medicationstatement instance over time"/>
      </interaction>
      <interaction>
        <extension url="http://hl7.org/fhir/StructureDefinition/conformance-expectation">
          <valueCode value="MAY"/>
        </extension>
        <code value="vread"/>
        <documentation value="Allows retrieval of a historical version of a Argonaut Data Query medicationstatement instance"/>
      </interaction>
    </resource>
    <resource>
      <extension url="http://fhir.org/guides/argonaut/StructureDefinition/argo-resource-documentation">
        <valueMarkdown value=" &lt;p&gt;&lt;strong&gt;Summary of US Core Search Criteria for StructureDefinition-us-core-medicationorder&lt;/strong&gt;&lt;/p&gt; &lt;p&gt;The MedicationStatement and MedicationOrder resources can represent a medication, using either a code or refer to a Medication resource. When referencing a Medication resource, the resource may be &lt;a href=&quot;http://hl7.org/fhir/references.html#contained&quot;&gt;contained&lt;/a&gt; or an external resource. The server application can choose any one way or more than one method, but &lt;strong&gt;IF&lt;/strong&gt; the an external reference to Medication is used, the server &lt;strong&gt;SHALL&lt;/strong&gt; support the &lt;a href=&quot;http://hl7.org/fhir/references.html#include&quot;&gt;include&lt;/a&gt; parameter for searching this element. The client application &lt;strong&gt;SHALL&lt;/strong&gt; support both methods.&lt;/p&gt; &lt;ul&gt; &lt;li&gt;A client has connected to a server and fetched a patient&apos;s medications using:&lt;/li&gt; &lt;/ul&gt; &lt;ol&gt; &lt;li&gt;GET /MedicationOrder?patient=[id]&lt;/li&gt; &lt;li&gt;GET /MedicationOrder?patient=[id]&amp;amp_include=MedicationOrder:medication&lt;/li&gt; &lt;/ol&gt; "/>
      </extension>
      <type value="MedicationOrder"/>
      <interaction>
        <extension url="http://hl7.org/fhir/StructureDefinition/conformance-expectation">
          <valueCode value="SHOULD"/>
        </extension>
        <code value="search-type"/>
        <documentation value="Allows discovery of existing Argonaut Data Query medicationorder resources using different search criteria"/>
      </interaction>
      <interaction>
        <extension url="http://hl7.org/fhir/StructureDefinition/conformance-expectation">
          <valueCode value="SHOULD"/>
        </extension>
        <code value="read"/>
        <documentation value="Allows retrieval of a specific Argonaut Data Query medicationorder by id"/>
      </interaction>
      <interaction>
        <extension url="http://hl7.org/fhir/StructureDefinition/conformance-expectation">
          <valueCode value="MAY"/>
        </extension>
        <code value="history-instance"/>
        <documentation value="Allows review of changes to Argonaut Data Query medicationorder instance over time"/>
      </interaction>
      <interaction>
        <extension url="http://hl7.org/fhir/StructureDefinition/conformance-expectation">
          <valueCode value="MAY"/>
        </extension>
        <code value="vread"/>
        <documentation value="Allows retrieval of a historical version of a Argonaut Data Query medicationorder instance"/>
      </interaction>
    </resource>
    <resource>
      <extension url="http://fhir.org/guides/argonaut/StructureDefinition/argo-resource-documentation">
        <valueMarkdown value=" &lt;h4&gt;Summary of US Core Search Criteria for StructureDefinition-us-core-procedure&lt;/h4&gt; &lt;ul&gt; &lt;li&gt;A client connected to a server and fetched all procedures for a patient, including current as well as historical Procedures GET/Procedure?patient=[id].&lt;/li&gt; &lt;li&gt;A client has connected to a server and fetched all of a patient&apos;s procedures over a specified time period using GET /Procedure?patient=[id]&amp;ampdate=[date]{&amp;ampdate=[date]}.&lt;/li&gt; &lt;/ul&gt; "/>
      </extension>
      <type value="Procedure"/>
      <interaction>
        <extension url="http://hl7.org/fhir/StructureDefinition/conformance-expectation">
          <valueCode value="SHOULD"/>
        </extension>
        <code value="search-type"/>
        <documentation value="Allows discovery of existing Argonaut Data Query procedure resources using different search criteria"/>
      </interaction>
      <interaction>
        <extension url="http://hl7.org/fhir/StructureDefinition/conformance-expectation">
          <valueCode value="SHOULD"/>
        </extension>
        <code value="read"/>
        <documentation value="Allows retrieval of a specific Argonaut Data Query procedure by id"/>
      </interaction>
      <interaction>
        <extension url="http://hl7.org/fhir/StructureDefinition/conformance-expectation">
          <valueCode value="MAY"/>
        </extension>
        <code value="history-instance"/>
        <documentation value="Allows review of changes to Argonaut Data Query procedure instance over time"/>
      </interaction>
      <interaction>
        <extension url="http://hl7.org/fhir/StructureDefinition/conformance-expectation">
          <valueCode value="MAY"/>
        </extension>
        <code value="vread"/>
        <documentation value="Allows retrieval of a historical version of a Argonaut Data Query procedure instance"/>
      </interaction>
    </resource>
    <operation>
      <extension url="http://hl7.org/fhir/StructureDefinition/conformance-expectation">
        <valueCode value="SHALL"/>
      </extension>
      <name value="docref"/>
      <definition>
        <reference value="http://fhir.org/guides/argonaut/OperationDefinition/docref"/>
        <display value="Argonaut Get DocumentReferences"/>
      </definition>
    </operation>
  </rest>
</Conformance>