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

History Record

XML or JSON representation

Links: First Previous Next Last  (7 found). Search: http://tx.fhir.org/r2/Conformance/_history?&_prior=2019-09-15T20:38:15.434Z&_format=text/xhtml&history-id=735558a5-0353-4e3a-b561-749f9d4faa 

Unknown message Conformance "server" Version "1"

Tags: (no tags)  +

This Resource , XML or JSON representation, or the full version history.. provenance for this resource
Updated: by

Argonaut Data Query Implementation Guide Server

FHIR Version: 1.0.2
Supported formats: xml , json
Published: 2016-12-15
Published by: Argonaut Project

This profile defines the expected capabilities of a Argonaut Data Query server when conforming to the Argonaut Data Query IG The conformance resource includes the complete list of actual profiles, RESTful operations, and search parameters supported by Argonaut Data Query Servers. Servers have the option of choosing from this list to access necessary data based on their local use cases and other contextual requirements.


RESTful Behavior



Description:

The Argonaut Data Query Server SHALL:

  1. Support the Argonaut Data Query Patient resource profile.
  2. Support at least one additional resource profile from the list of Argonaut Data Query Profiles
  3. Implement REST behavior according to the FHIR specification
  4. Support json resource formats for all Argonaut Data Query interactions.
  5. Identify the Argonaut Data Query profile(s) supported as part of the FHIR Meta profile attribute for each instance.
  6. Declare a Conformance identifying the list of profiles, operations, search parameter supported.

The Argonaut Data Query Server SHOULD:

  1. Support xml resource formats for all Argonaut Data Query interactions.

Security:

Argonaut Data Query Servers SHALL

  1. implement the security requirements documented in this guide
  2. A server has ensured that every API request includes a valid Authorization token, supplied via: Authorization: Bearer {server-specific-token-here}
  3. A server has rejected any unauthorized requests by returning an HTTP 401 Unauthorized response code.

Supported Operations: MAY Support docref

Profile Summary:


All servers SHALL make available the read and search-type interactions for the Argonaut Profiles the server chooses to support.
All servers SHOULD make available the vread and history-instance interactions for the Argonaut Profiles the server chooses to support.


Summary of Argonaut Profile search criteria. Specific server search capabilities are described in detail below in each of the resource sections.


Resource Type Supported Profiles Supported Searches Supported Includes
Patient Argonaut Data Query Patient Profile

name , family , given , identifier , gender , birthdate
name + gender , name + birthdate , family + gender , given + gender
 
AllergyIntolerance Argonaut Data Query AllergyIntolerance Profile

patient
 
CarePlan Argonaut Data Query CarePlan Profile
Argonaut Data Query CareTeam Profile

patient , category , status , date
patient + category , patient + category + date , patient + category + status , patient + category + status + date
 
Condition Argonaut Data Query Condition Profile

patient , category , clinicalstatus
patient + clinicalstatus , patient + category
 
Device Argonaut Data Query Device Profile

patient
 
DocumentReference Argonaut Data Query Document Reference Profile

patient , period , type
patient + type + period
 
Goal Argonaut Data Query Goal Profile

patient , date
patient + date
 
Immunization Argonaut Data Query Immunization Profile

patient
 
DiagnosticReport Argonaut Data Query DiagnosticReport Profile

patient , category , code , date
patient + category , patient + category + date , patient + category + code , patient + category + code + date
 
Medication Argonaut Data Query Medication Profile


 
MedicationStatement Argonaut Data Query MedicationStatement Profile

patient
MedicationStatement.medicationReference
MedicationOrder Argonaut Data Query MedicationOrder Profile

patient
MedicationOrder.medicationReference
Observation Argonaut Data Query Result Observation Profile
Argonaut Data Query Vital Signs Profile
Argonaut Data Query Smoking Status Observation Profile

patient , category , code , date
patient + category , patient + category + date , patient + category + code , patient + category + code + date
 
Procedure Argonaut Data Query Procedure Profile

patient , date
patient + date
 

Resource  Details:


  1. Resource Type: Patient

    Supported Profiles:  Argonaut Data Query Patient Profile

    Summary of Argonaut Data Query Search Criteria for StructureDefinition-argo-patient

    • A server is capable of returning a patient using GET [base]/Patient/[id].
    • A server returns valid FHIR Patient resources according to the Data Access Framework (DAF) Patient Profile..
    • A server has exposed a FHIR Patient search endpoint supporting at a minimum the following search parameters:
      • identifier
    • A server has exposed a FHIR Patient search endpoint supporting at a minimum the following search parameters when at least 2 (example name and gender) are present:
      • name
      • gender
      • birthdate

    Search Parameters:
    Conformance Parameter Type Modifiers
    SHALL name string  
    SHALL family string  
    SHALL given string  
    SHALL identifier token  
    SHALL gender token  
    SHALL birthdate date  

    Supported Search Combinations: name + gender , name + birthdate , family + gender , given + gender


  2. Resource Type: AllergyIntolerance

    Supported Profiles:  Argonaut Data Query AllergyIntolerance Profile

    Summary of Argonaut Data Query Search Criteria for StructureDefinition-argo-allergyintolerance

    • A server is capable of returning a patient’s allergies using GET /AllergyIntolerance?patient=[id].

    Search Parameters:
    Conformance Parameter Type Modifiers
    SHALL patient reference  


  3. Resource Type: CarePlan

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

    Summary of Argonaut Data Query Search Criteria for StructureDefinition-argo-careplan

    • A server is capable of returning all of a patient’s Assessment and Plan of Treatment information using GET /CarePlan?patient=[id]&category=assess-plan.
    • A server SHOULD be capable of returning 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 server SHOULD be capable returning all of a patient’s active Assessment and Plan of Treatment information using GET /CarePlan?patient=[id]&category=assess-plan&status=active.
    • A server SHOULD be capable returning 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 server is capable of returning a patients current care team members using GET[base]/CarePlan?patient=[id]&category=careteam&status=active

    Search Parameters:
    Conformance Parameter Type Modifiers
    SHALL patient reference  
    SHALL category token  
    SHOULD status token  
    SHOULD date date

    The server SHALL support the date search modifiers ‘ge’,‘le’,‘gt','lt' for this profile

    Supported Search Combinations: patient + category , patient + category + date , patient + category + status , patient + category + status + date


  4. Resource Type: Condition

    Supported Profiles:  Argonaut Data Query Condition Profile

    Summary of Argonaut Data Query Search Criteria for StructureDefinition-argo-condition

    • A server is capable of returning a patient’s conditions list using GET/Condition?patient=[id].

    • A server SHOULD be capable returning all of a patient’s active problems and health concerns using ‘GET /Condition?patient=[id]&clinicalstatus=active,recurrance,remission’
    • A server SHOULD be capable returning all of a patient’s problems or all of patient’s health concerns using ‘GET /Condition?patient=[id]&category=[problem|health-concern]’

    Search Parameters:
    Conformance Parameter Type Modifiers
    SHALL patient reference  
    SHOULD category token  
    SHOULD clinicalstatus token  

    Supported Search Combinations: patient + clinicalstatus , patient + category


  5. Resource Type: Device

    Supported Profiles:  Argonaut Data Query Device Profile

    Summary of Argonaut Data Query Search Criteria for StructureDefinition-argo-device

    • A server is capable of returning all Unique device identifier(s)(UDI) for a patient’s implanted device(s) using GET /Device?patient=[id].

    Search Parameters:
    Conformance Parameter Type Modifiers
    SHALL patient reference  


  6. Resource Type: DocumentReference

    Supported Profiles:  Argonaut Data Query Document Reference Profile

    Search Criteria for StructureDefinition-argo-documentreference

    • To fetch document references, the Server SHALL support either:
      • a direct query for DocumentReference resources as described here
      • or the $docref operation operation

    The Client SHALL support both methods.

    • If supporting a direct query, a server SHALL be capable of returning at least the most recent CCD document references and MAY provide most recent references to other document types for a patient using:GET [base]/DocumentReference/$docref?patient=[id]
    • If supporting a direct query, A server SHOULD be capable of returning references to CCD documents and MAY provide references to other document types for a patient searched by type and/or date using:GET [base]/DocumentReference/$docref?patient=[id]{&type=[type]}{&period=[date]}

    Search Parameters:
    Conformance Parameter Type Modifiers
    SHALL patient reference  
    SHOULD period date

    The server SHALL support the date search modifiers ‘ge’,‘le’,‘gt','lt' for this profile

    SHOULD type token  

    Supported Search Combinations: patient + type + period


  7. Resource Type: Goal

    Supported Profiles:  Argonaut Data Query Goal Profile

    Summary of Argonaut Data Query Search Criteria for StructureDefinition-argo-device

    • A server is capable of returning all of a patient’s goals using GET [base]/Goal?patient=[id].
    • A server is capable of returning all of all of a patient’s goals over a specified time period using GET [base]/Goal?patient=[id]&date=[date]{&date=[date]}.

    Search Parameters:
    Conformance Parameter Type Modifiers
    SHALL patient reference  
    SHALL date date

    The server SHALL support the date search modifiers ‘ge’,‘le’,‘gt','lt' for this profile

    Supported Search Combinations: patient + date


  8. Resource Type: Immunization

    Supported Profiles:  Argonaut Data Query Immunization Profile

    Summary of Argonaut Data Query Search Criteria for StructureDefinition-argo-immunization

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

    Search Parameters:
    Conformance Parameter Type Modifiers
    SHALL patient reference  


  9. Resource Type: DiagnosticReport

    Supported Profiles:  Argonaut Data Query DiagnosticReport Profile

    Summary of Argonaut Data Query Search Criteria for StructureDefinition-argo-diagnosticreport

    • A server is capable of returning all of a patient’s laboratory diagnostic reports queried by category using GET [base]/DiagnosticReport?patient=[id]&category=LAB.
    • A server is capable of returning all of a patient’s laboratory diagnostic reports queried by category code and date range using GET [base]/DiagnosticReport?patient=[id]&category=LAB&date=[date]{&date=[date]}.
    • A server is capable of returning all of a patient’s laboratory diagnostic reports queried by category and code using GET [base]/DiagnosticReport?patient=[id]&category=LAB&code=[LOINC].

    • A server SHOULD be capable of returning all of a patient’s laboratory diagnostic reports queried 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]}.

    Search Parameters:
    Conformance Parameter Type Modifiers
    SHALL patient reference  
    SHALL category token  
    SHALL code token  
    SHALL date date

    The server SHALL support the date search modifiers ‘ge’,‘le’,‘gt','lt' for this profile

    Supported Search Combinations: patient + category , patient + category + date , patient + category + code , patient + category + code + date


  10. 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.

    Search Parameters:
    Conformance Parameter Type Modifiers


  11. Resource Type: MedicationStatement

    Supported Profiles:  Argonaut Data Query MedicationStatement Profile

    Summary of Argonaut Data Query Search Criteria for StructureDefinition-argo-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 must support both methods.

    • A server is capable of returning a patient’s medications using one of or both
    1. GET /MedicationStatement?patient=[id]
    2. GET /MedicationStatement?patient=[id]&_include=MedicationStatement:medication

    Search Parameters:
    Conformance Parameter Type Modifiers
    SHALL patient reference  

    Supported Includes: MedicationStatement.medicationReference


  12. Resource Type: MedicationOrder

    Supported Profiles:  Argonaut Data Query MedicationOrder Profile

    Summary of Argonaut Data Query Search Criteria for StructureDefinition-argo-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 must support both methods.

    • A server is capable of returning a patient’s medications using one of or both
    1. GET /MedicationOrder?patient=[id]
    2. GET /MedicationOrder?patient=[id]&_include=MedicationOrder:medication

    Search Parameters:
    Conformance Parameter Type Modifiers
    SHALL patient reference  

    Supported Includes: MedicationOrder.medicationReference


  13. 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 Data Query Search Criteria for StructureDefinition-argo-observationresults

    • A server is capable of returning all of a patient's laboratory results queried by category using GET [base]/Observation?patient=[id]&category=laboratory.
    • A server is capable of returning all of a patient's laboratory results queried by category code and date range usingGET [base]/Observation?patient=[id]&category=laboratory&date=[date]{&date=[date]}.
    • A server is capable of returning all of a patient's laboratory results queried by category and code using GET [base]/Observation?patient=[id]&category=laboratory&code=[LOINC].
    • A server SHOULD be capable of returning all of a patient's laboratory results queried 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 Data Query Search Criteria for StructureDefinition-argo-smokingstatus

    • A server is capable of returning a a patient’s smoking status using GET [base]/Observation?patient=[id]&code=72166-2

    Summary of Argonaut Data Query Search Criteria for StructureDefinition-argo-vitalsigns

    • A server is capable of returning all of a patient’s vital signs that it supports using GET [base]/Observation?patient=[id]&category=vital-signs.
    • A server is capable of returning all of a patient’s vital signs queried by date range using GET [base]/Observation?patient=[id]&category=vital-signs&date=[date]{&date=[date]}.
    • A server is capable of returning any of a patient’s vital signs queried by one or more of the codes listed below using GET [base]/Observation?patient=[id]&code[vital sign LOINC{,LOINC2,LOINC3,…}].

    • A server SHOULD be capable of returning any of a patient’s vital signs queried 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]}.

    Search Parameters:
    Conformance Parameter Type Modifiers
    SHALL patient reference  
    SHALL category token  
    SHALL code token  
    SHALL date date

    The server SHALL support the date search modifiers ‘ge’,‘le’,‘gt','lt' for this profile

    Supported Search Combinations: patient + category , patient + category + date , patient + category + code , patient + category + code + date


  14. Resource Type: Procedure

    Supported Profiles:  Argonaut Data Query Procedure Profile

    Summary of Argonaut Data Query Search Criteria for StructureDefinition-argo-procedure

    • A server is capable of returning a patient’s procedures using GET/Procedure?patient=[id].
    • A server is capable of returning all of all of a patient’s procedures over a specified time period using GET /Procedure?patient=[id]&date=[date]{&date=[date]}.

    Search Parameters:
    Conformance Parameter Type Modifiers
    SHALL patient reference  
    SHALL date date

    The server SHALL support the date search modifiers ‘ge’,‘le’,‘gt','lt' for this profile

    Supported Search Combinations: patient + date






<?xml version="1.0" encoding="UTF-8"?>
<Conformance xmlns="http://hl7.org/fhir">
  <id value="server"/>
  <meta>
    <versionId value="1"/>
    <lastUpdated value="2018-10-08T18:34:03.237Z"/>
  </meta>
  <text>
    <status value="generated"/>
    <div xmlns="http://www.w3.org/1999/xhtml">
      <span style="font-size:larger font-weight:bold ">Argonaut Data Query Implementation Guide Server</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-12-15</span>
        <br/>
        <span>Published by: </span>
        <span>Argonaut Project</span> </p>
      <p>
        <span>This profile defines the expected capabilities of a Argonaut Data Query server when conforming to the Argonaut Data Query IG The conformance resource includes the complete list of actual profiles, RESTful operations, and search parameters supported by Argonaut Data Query Servers. Servers have the option of choosing from this list to access necessary data based on their local use cases and other contextual requirements.</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 Data Query Server SHALL:</strong>
        </p>
        <ol>
          <li>Support the Argonaut Data Query Patient resource profile.</li>
          <li>Support at least one additional resource profile from the list of Argonaut Data Query Profiles</li>
          <li>Implement REST behavior according to the FHIR specification</li>
          <li>Support json resource formats for all Argonaut Data Query interactions.</li>
          <li>Identify the Argonaut Data Query profile(s) supported as part of the
            <a href="http://build.fhir.org/resource-definitions.html#Meta.profile">FHIR Meta profile attribute</a>for each instance.</li>
          <li>Declare a Conformance identifying the list of profiles, operations, search parameter supported. </li> </ol>
        <p>
          <strong>The Argonaut Data Query Server SHOULD:</strong> </p>
        <ol>
          <li>Support xml resource formats for all Argonaut Data Query interactions. </li> </ol>
        <br/>
      </div>
      <div>
        <span>Security: </span>
        <p>
          <strong>Argonaut Data Query Servers SHALL</strong>
        </p>
        <ol>
          <li>implement the
            <a href="index.html#security">security requirements</a>documented in this guide</li>
          <li>A server has ensured that every API request includes a valid Authorization token, supplied via:
            <code>Authorization: Bearer {server-specific-token-here}</code>
          </li>
          <li>A server has rejected any unauthorized requests by returning an
            <code>HTTP 401</code>Unauthorized response code.</li> </ol>
        <br/>
      </div>
      <span>Supported Operations: </span>
      <span style="font-weight:bold">MAY</span>
      <span>Support </span>
      <a href="http://fhir.org/guides/argonaut/r2/OperationDefinition-docref.html">
        <span>docref</span> </a>
      <h4>
        <span style="font-weight:bold ">Profile Summary:</span> </h4>
      <p>
        <br/>
        <span>All servers </span>
        <span style="font-weight:bold ">SHALL</span>
        <span>make available the </span>
        <a href="http://build.fhir.org/http.html#read">
          <span>read</span> </a>
        <span>and </span>
        <a href="http://build.fhir.org/http.html#search-type">
          <span>search-type</span> </a>
        <span>interactions for the Argonaut Profiles the server chooses to support.</span>
        <br/>
        <span>All servers </span>
        <span style="font-weight:bold ">SHOULD</span>
        <span>make available the </span>
        <a href="http://build.fhir.org/http.html#vread">
          <span>vread</span> </a>
        <span>and </span>
        <a href="http://build.fhir.org/http.html#history-instance">
          <span>history-instance</span> </a>
        <span>interactions for the Argonaut Profiles the server chooses to support.</span>
        <br/> </p>
      <br/>
      <p>
        <span>Summary of Argonaut Profile search criteria. Specific server search capabilities are described in detail below in each of the resource sections.</span> </p>
      <br/>
      <table border="1">
        <thead>
          <tr>
            <th>
              <span>Resource Type</span> </th>
            <th>
              <span>Supported Profiles</span> </th>
            <th style="text-align:center ">
              <span>Supported Searches</span> </th>
            <th>
              <span>Supported Includes</span> </th> </tr> </thead>
        <tbody>
          <tr style="height:0.36in ">
            <td>
              <a href="#Patient">
                <span>Patient</span> </a> </td>
            <td>
              <span>Argonaut Data Query Patient Profile</span>
              <br/>
              <br/> </td>
            <td style="text-align:center ">
              <span>name</span>
              <span>, </span>
              <span>family</span>
              <span>, </span>
              <span>given</span>
              <span>, </span>
              <span>identifier</span>
              <span>, </span>
              <span>gender</span>
              <span>, </span>
              <span>birthdate</span>
              <br/>
              <span>name</span>
              <span>+ </span>
              <span>gender</span>
              <span>, </span>
              <span>name</span>
              <span>+ </span>
              <span>birthdate</span>
              <span>, </span>
              <span>family</span>
              <span>+ </span>
              <span>gender</span>
              <span>, </span>
              <span>given</span>
              <span>+ </span>
              <span>gender</span> </td>
            <td>&#160;</td> </tr>
          <tr style="height:0.36in ">
            <td>
              <a href="#AllergyIntolerance">
                <span>AllergyIntolerance</span> </a> </td>
            <td>
              <span>Argonaut Data Query AllergyIntolerance Profile</span>
              <br/>
              <br/> </td>
            <td style="text-align:center ">
              <span>patient</span>
              <br/> </td>
            <td>&#160;</td> </tr>
          <tr style="height:0.36in ">
            <td>
              <a href="#CarePlan">
                <span>CarePlan</span> </a> </td>
            <td>
              <span>Argonaut Data Query CarePlan Profile</span>
              <br/>
              <span>Argonaut Data Query CareTeam Profile</span>
              <br/>
              <br/> </td>
            <td style="text-align:center ">
              <span>patient</span>
              <span>, </span>
              <span>category</span>
              <span>, </span>
              <span>status</span>
              <span>, </span>
              <span>date</span>
              <br/>
              <span>patient</span>
              <span>+ </span>
              <span>category</span>
              <span>, </span>
              <span>patient</span>
              <span>+ </span>
              <span>category</span>
              <span>+ </span>
              <span>date</span>
              <span>, </span>
              <span>patient</span>
              <span>+ </span>
              <span>category</span>
              <span>+ </span>
              <span>status</span>
              <span>, </span>
              <span>patient</span>
              <span>+ </span>
              <span>category</span>
              <span>+ </span>
              <span>status</span>
              <span>+ </span>
              <span>date</span> </td>
            <td>&#160;</td> </tr>
          <tr style="height:0.36in ">
            <td>
              <a href="#Condition">
                <span>Condition</span> </a> </td>
            <td>
              <span>Argonaut Data Query Condition Profile</span>
              <br/>
              <br/> </td>
            <td style="text-align:center ">
              <span>patient</span>
              <span>, </span>
              <span>category</span>
              <span>, </span>
              <span>clinicalstatus</span>
              <br/>
              <span>patient</span>
              <span>+ </span>
              <span>clinicalstatus</span>
              <span>, </span>
              <span>patient</span>
              <span>+ </span>
              <span>category</span> </td>
            <td>&#160;</td> </tr>
          <tr style="height:0.36in ">
            <td>
              <a href="#Device">
                <span>Device</span> </a> </td>
            <td>
              <span>Argonaut Data Query Device Profile</span>
              <br/>
              <br/> </td>
            <td style="text-align:center ">
              <span>patient</span>
              <br/> </td>
            <td>&#160;</td> </tr>
          <tr style="height:0.36in ">
            <td>
              <a href="#DocumentReference">
                <span>DocumentReference</span> </a> </td>
            <td>
              <span>Argonaut Data Query Document Reference Profile</span>
              <br/>
              <br/> </td>
            <td style="text-align:center ">
              <span>patient</span>
              <span>, </span>
              <span>period</span>
              <span>, </span>
              <span>type</span>
              <br/>
              <span>patient</span>
              <span>+ </span>
              <span>type</span>
              <span>+ </span>
              <span>period</span> </td>
            <td>&#160;</td> </tr>
          <tr style="height:0.36in ">
            <td>
              <a href="#Goal">
                <span>Goal</span> </a> </td>
            <td>
              <span>Argonaut Data Query Goal Profile</span>
              <br/>
              <br/> </td>
            <td style="text-align:center ">
              <span>patient</span>
              <span>, </span>
              <span>date</span>
              <br/>
              <span>patient</span>
              <span>+ </span>
              <span>date</span> </td>
            <td>&#160;</td> </tr>
          <tr style="height:0.36in ">
            <td>
              <a href="#Immunization">
                <span>Immunization</span> </a> </td>
            <td>
              <span>Argonaut Data Query Immunization Profile</span>
              <br/>
              <br/> </td>
            <td style="text-align:center ">
              <span>patient</span>
              <br/> </td>
            <td>&#160;</td> </tr>
          <tr style="height:0.36in ">
            <td>
              <a href="#DiagnosticReport">
                <span>DiagnosticReport</span> </a> </td>
            <td>
              <span>Argonaut Data Query DiagnosticReport Profile</span>
              <br/>
              <br/> </td>
            <td style="text-align:center ">
              <span>patient</span>
              <span>, </span>
              <span>category</span>
              <span>, </span>
              <span>code</span>
              <span>, </span>
              <span>date</span>
              <br/>
              <span>patient</span>
              <span>+ </span>
              <span>category</span>
              <span>, </span>
              <span>patient</span>
              <span>+ </span>
              <span>category</span>
              <span>+ </span>
              <span>date</span>
              <span>, </span>
              <span>patient</span>
              <span>+ </span>
              <span>category</span>
              <span>+ </span>
              <span>code</span>
              <span>, </span>
              <span>patient</span>
              <span>+ </span>
              <span>category</span>
              <span>+ </span>
              <span>code</span>
              <span>+ </span>
              <span>date</span> </td>
            <td>&#160;</td> </tr>
          <tr style="height:0.36in ">
            <td>
              <a href="#Medication">
                <span>Medication</span> </a> </td>
            <td>
              <span>Argonaut Data Query Medication Profile</span>
              <br/>
              <br/> </td>
            <td style="text-align:center ">
              <br/> </td>
            <td>&#160;</td> </tr>
          <tr style="height:0.36in ">
            <td>
              <a href="#MedicationStatement">
                <span>MedicationStatement</span> </a> </td>
            <td>
              <span>Argonaut Data Query MedicationStatement Profile</span>
              <br/>
              <br/> </td>
            <td style="text-align:center ">
              <span>patient</span>
              <br/> </td>
            <td>
              <span>MedicationStatement.medicationReference</span> </td> </tr>
          <tr style="height:0.36in ">
            <td>
              <a href="#MedicationOrder">
                <span>MedicationOrder</span> </a> </td>
            <td>
              <span>Argonaut Data Query MedicationOrder Profile</span>
              <br/>
              <br/> </td>
            <td style="text-align:center ">
              <span>patient</span>
              <br/> </td>
            <td>
              <span>MedicationOrder.medicationReference</span> </td> </tr>
          <tr style="height:0.36in ">
            <td>
              <a href="#Observation">
                <span>Observation</span> </a> </td>
            <td>
              <span>Argonaut Data Query Result Observation Profile</span>
              <br/>
              <span>Argonaut Data Query Vital Signs Profile</span>
              <br/>
              <span>Argonaut Data Query Smoking Status Observation Profile</span>
              <br/>
              <br/> </td>
            <td style="text-align:center ">
              <span>patient</span>
              <span>, </span>
              <span>category</span>
              <span>, </span>
              <span>code</span>
              <span>, </span>
              <span>date</span>
              <br/>
              <span>patient</span>
              <span>+ </span>
              <span>category</span>
              <span>, </span>
              <span>patient</span>
              <span>+ </span>
              <span>category</span>
              <span>+ </span>
              <span>date</span>
              <span>, </span>
              <span>patient</span>
              <span>+ </span>
              <span>category</span>
              <span>+ </span>
              <span>code</span>
              <span>, </span>
              <span>patient</span>
              <span>+ </span>
              <span>category</span>
              <span>+ </span>
              <span>code</span>
              <span>+ </span>
              <span>date</span> </td>
            <td>&#160;</td> </tr>
          <tr style="height:0.36in ">
            <td>
              <a href="#Procedure">
                <span>Procedure</span> </a> </td>
            <td>
              <span>Argonaut Data Query Procedure Profile</span>
              <br/>
              <br/> </td>
            <td style="text-align:center ">
              <span>patient</span>
              <span>, </span>
              <span>date</span>
              <br/>
              <span>patient</span>
              <span>+ </span>
              <span>date</span> </td>
            <td>&#160;</td> </tr> </tbody> </table>
      <br/>
      <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/r2/StructureDefinition-argo-patient.html">
              <span>Argonaut Data Query Patient Profile</span>
              <br/> </a>
            <br/> </p>
          <p>
            <strong>Summary of Argonaut Data Query Search Criteria for StructureDefinition-argo-patient</strong>
          </p>
          <ul>
            <li>A server is capable of returning a patient using GET [base]/Patient/[id].</li>
            <li>A server returns valid FHIR Patient resources according to the Data Access Framework (DAF) Patient Profile..</li>
            <li>A server has exposed a FHIR Patient search endpoint supporting at a minimum the following search parameters:
              <ul>
                <li>identifier</li> </ul>
            </li>
            <li>A server has exposed a FHIR Patient search endpoint supporting at a minimum the following search parameters when at least 2 (example name and gender) are present:
              <ul>
                <li>name</li>
                <li>gender</li>
                <li>birthdate</li> </ul>
            </li> </ul>
          <p/>
          <span>Search Parameters:</span>
          <table border="1">
            <thead>
              <tr>
                <th style="width:2.71in ">
                  <span>Conformance</span> </th>
                <th>
                  <span>Parameter</span> </th>
                <th style="width:2.11in ">
                  <span>Type</span> </th>
                <th style="width:2.90in ">
                  <span>Modifiers</span> </th> </tr> </thead>
            <tbody>
              <tr>
                <td style="width:2.71in ">
                  <span>SHALL</span> </td>
                <td>
                  <span>name</span> </td>
                <td style="width:2.11in ">
                  <span>string</span> </td>
                <td style="width:2.90in ">&#160;</td> </tr>
              <tr>
                <td style="width:2.71in ">
                  <span>SHALL</span> </td>
                <td>
                  <span>family</span> </td>
                <td style="width:2.11in ">
                  <span>string</span> </td>
                <td style="width:2.90in ">&#160;</td> </tr>
              <tr>
                <td style="width:2.71in ">
                  <span>SHALL</span> </td>
                <td>
                  <span>given</span> </td>
                <td style="width:2.11in ">
                  <span>string</span> </td>
                <td style="width:2.90in ">&#160;</td> </tr>
              <tr>
                <td style="width:2.71in ">
                  <span>SHALL</span> </td>
                <td>
                  <span>identifier</span> </td>
                <td style="width:2.11in ">
                  <span>token</span> </td>
                <td style="width:2.90in ">&#160;</td> </tr>
              <tr>
                <td style="width:2.71in ">
                  <span>SHALL</span> </td>
                <td>
                  <span>gender</span> </td>
                <td style="width:2.11in ">
                  <span>token</span> </td>
                <td style="width:2.90in ">&#160;</td> </tr>
              <tr>
                <td style="width:2.71in ">
                  <span>SHALL</span> </td>
                <td>
                  <span>birthdate</span> </td>
                <td style="width:2.11in ">
                  <span>date</span> </td>
                <td style="width:2.90in ">&#160;</td> </tr> </tbody> </table>
          <p/>
          <p>
            <span>Supported Search Combinations:</span>
            <span>name</span>
            <span>+ </span>
            <span>gender</span>
            <span>, </span>
            <span>name</span>
            <span>+ </span>
            <span>birthdate</span>
            <span>, </span>
            <span>family</span>
            <span>+ </span>
            <span>gender</span>
            <span>, </span>
            <span>given</span>
            <span>+ </span>
            <span>gender</span> </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/r2/StructureDefinition-argo-allergyintolerance.html">
              <span>Argonaut Data Query AllergyIntolerance Profile</span>
              <br/> </a>
            <br/> </p>
          <p>
            <strong>Summary of Argonaut Data Query Search Criteria for StructureDefinition-argo-allergyintolerance</strong>
          </p>
          <ul>
            <li>A server is capable of returning a patient&#8217;s allergies using GET /AllergyIntolerance?patient=[id].</li> </ul>
          <p/>
          <span>Search Parameters:</span>
          <table border="1">
            <thead>
              <tr>
                <th style="width:2.71in ">
                  <span>Conformance</span> </th>
                <th>
                  <span>Parameter</span> </th>
                <th style="width:2.11in ">
                  <span>Type</span> </th>
                <th style="width:2.90in ">
                  <span>Modifiers</span> </th> </tr> </thead>
            <tbody>
              <tr>
                <td style="width:2.71in ">
                  <span>SHALL</span> </td>
                <td>
                  <span>patient</span> </td>
                <td style="width:2.11in ">
                  <span>reference</span> </td>
                <td style="width:2.90in ">&#160;</td> </tr> </tbody> </table>
          <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/r2/StructureDefinition-argo-careplan.html">
              <span>Argonaut Data Query CarePlan Profile</span>
              <br/> </a>
            <a href="http://fhir.org/guides/argonaut/r2/StructureDefinition-argo-careteam.html">
              <span>Argonaut Data Query CareTeam Profile</span>
              <br/> </a>
            <br/> </p>
          <p>
            <strong>Summary of Argonaut Data Query Search Criteria for StructureDefinition-argo-careplan</strong>
          </p>
          <ul>
            <li>A server is capable of returning all of a patient&#8217;s Assessment and Plan of Treatment information using GET /CarePlan?patient=[id]&amp;category=assess-plan.</li>
            <li>
              <p>A server
                <strong>SHOULD</strong>be capable of returning a patient&#8217;s Assessment and Plan of Treatment information over a specified time period using GET /CarePlan?patient=[id]&amp;category=assess-plan&amp;date=[date].</p>
            </li>
            <li>A server
              <strong>SHOULD</strong>be capable returning all of a patient&#8217;s active Assessment and Plan of Treatment information using GET /CarePlan?patient=[id]&amp;category=assess-plan&amp;status=active.</li>
            <li>
              <p>A server
                <strong>SHOULD</strong>be capable returning a patient&#8217;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].</p>
            </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 server is capable of returning a patients current care team members using GET[base]/CarePlan?patient=[id]&amp;category=careteam&amp;status=active</li> </ul>
          <p/>
          <span>Search Parameters:</span>
          <table border="1">
            <thead>
              <tr>
                <th style="width:2.71in ">
                  <span>Conformance</span> </th>
                <th>
                  <span>Parameter</span> </th>
                <th style="width:2.11in ">
                  <span>Type</span> </th>
                <th style="width:2.90in ">
                  <span>Modifiers</span> </th> </tr> </thead>
            <tbody>
              <tr>
                <td style="width:2.71in ">
                  <span>SHALL</span> </td>
                <td>
                  <span>patient</span> </td>
                <td style="width:2.11in ">
                  <span>reference</span> </td>
                <td style="width:2.90in ">&#160;</td> </tr>
              <tr>
                <td style="width:2.71in ">
                  <span>SHALL</span> </td>
                <td>
                  <span>category</span> </td>
                <td style="width:2.11in ">
                  <span>token</span> </td>
                <td style="width:2.90in ">&#160;</td> </tr>
              <tr>
                <td style="width:2.71in ">
                  <span>SHOULD</span> </td>
                <td>
                  <span>status</span> </td>
                <td style="width:2.11in ">
                  <span>token</span> </td>
                <td style="width:2.90in ">&#160;</td> </tr>
              <tr>
                <td style="width:2.71in ">
                  <span>SHOULD</span> </td>
                <td>
                  <span>date</span> </td>
                <td style="width:2.11in ">
                  <span>date</span> </td>
                <td style="width:2.90in ">
                  <p>The server SHALL support the
                    <a href="http://hl7.org/fhir/2017Jan/search.html#prefix">date search modifiers</a>&#8216;ge&#8217;,&#8216;le&#8217;,&#8216;gt','lt' for this profile</p>
                </td> </tr> </tbody> </table>
          <p/>
          <p>
            <span>Supported Search Combinations:</span>
            <span>patient</span>
            <span>+ </span>
            <span>category</span>
            <span>, </span>
            <span>patient</span>
            <span>+ </span>
            <span>category</span>
            <span>+ </span>
            <span>date</span>
            <span>, </span>
            <span>patient</span>
            <span>+ </span>
            <span>category</span>
            <span>+ </span>
            <span>status</span>
            <span>, </span>
            <span>patient</span>
            <span>+ </span>
            <span>category</span>
            <span>+ </span>
            <span>status</span>
            <span>+ </span>
            <span>date</span> </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/r2/StructureDefinition-argo-condition.html">
              <span>Argonaut Data Query Condition Profile</span>
              <br/> </a>
            <br/> </p>
          <p>
            <strong>Summary of Argonaut Data Query Search Criteria for StructureDefinition-argo-condition</strong>
          </p>
          <ul>
            <li>
              <p>A server is capable of returning a patient&#8217;s conditions list using GET/Condition?patient=[id].</p>
            </li>
            <li>A server
              <strong>SHOULD</strong>be capable returning all of a patient&#8217;s active problems and health concerns using &#8216;GET /Condition?patient=[id]&amp;clinicalstatus=active,recurrance,remission&#8217;</li>
            <li>
              <p>A server
                <strong>SHOULD</strong>be capable returning all of a patient&#8217;s problems or all of patient&#8217;s health concerns using &#8216;GET /Condition?patient=[id]&amp;category=[problem|health-concern]&#8217;</p>
            </li> </ul>
          <p/>
          <span>Search Parameters:</span>
          <table border="1">
            <thead>
              <tr>
                <th style="width:2.71in ">
                  <span>Conformance</span> </th>
                <th>
                  <span>Parameter</span> </th>
                <th style="width:2.11in ">
                  <span>Type</span> </th>
                <th style="width:2.90in ">
                  <span>Modifiers</span> </th> </tr> </thead>
            <tbody>
              <tr>
                <td style="width:2.71in ">
                  <span>SHALL</span> </td>
                <td>
                  <span>patient</span> </td>
                <td style="width:2.11in ">
                  <span>reference</span> </td>
                <td style="width:2.90in ">&#160;</td> </tr>
              <tr>
                <td style="width:2.71in ">
                  <span>SHOULD</span> </td>
                <td>
                  <span>category</span> </td>
                <td style="width:2.11in ">
                  <span>token</span> </td>
                <td style="width:2.90in ">&#160;</td> </tr>
              <tr>
                <td style="width:2.71in ">
                  <span>SHOULD</span> </td>
                <td>
                  <span>clinicalstatus</span> </td>
                <td style="width:2.11in ">
                  <span>token</span> </td>
                <td style="width:2.90in ">&#160;</td> </tr> </tbody> </table>
          <p/>
          <p>
            <span>Supported Search Combinations:</span>
            <span>patient</span>
            <span>+ </span>
            <span>clinicalstatus</span>
            <span>, </span>
            <span>patient</span>
            <span>+ </span>
            <span>category</span> </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/r2/StructureDefinition-argo-device.html">
              <span>Argonaut Data Query Device Profile</span>
              <br/> </a>
            <br/> </p>
          <p>
            <strong>Summary of Argonaut Data Query Search Criteria for StructureDefinition-argo-device</strong>
          </p>
          <ul>
            <li>A server is capable of returning all Unique device identifier(s)(UDI) for a patient&#8217;s implanted device(s) using GET /Device?patient=[id].</li> </ul>
          <p/>
          <span>Search Parameters:</span>
          <table border="1">
            <thead>
              <tr>
                <th style="width:2.71in ">
                  <span>Conformance</span> </th>
                <th>
                  <span>Parameter</span> </th>
                <th style="width:2.11in ">
                  <span>Type</span> </th>
                <th style="width:2.90in ">
                  <span>Modifiers</span> </th> </tr> </thead>
            <tbody>
              <tr>
                <td style="width:2.71in ">
                  <span>SHALL</span> </td>
                <td>
                  <span>patient</span> </td>
                <td style="width:2.11in ">
                  <span>reference</span> </td>
                <td style="width:2.90in ">&#160;</td> </tr> </tbody> </table>
          <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/r2/StructureDefinition-argo-documentreference.html">
              <span>Argonaut Data Query Document Reference Profile</span>
              <br/> </a>
            <br/> </p>
          <h4>Search Criteria for StructureDefinition-argo-documentreference</h4>
          <ul>
            <li>To fetch document references, the Server
              <strong>SHALL</strong>support
              <strong>either</strong>:
              <ul>
                <li>a direct query for DocumentReference resources as described here</li>
                <li>or the
                  <a href="http://fhir.org/guides/argonaut/r2/OperationDefinition-docref.html">$docref operation</a>&#160;operation</li> </ul> </li> </ul>
          <p style="padding-left: 60px">The Client
            <strong>SHALL</strong>support both methods.</p>
          <ul>
            <li>If supporting a direct query, a&#160;server
              <strong>SHALL</strong>&#160;be capable of returning at least the most recent CCD document references and
              <strong>MAY</strong>provide most recent references to other document types for a patient using:GET [base]/DocumentReference/$docref?patient=[id]</li>
            <li>If supporting a direct query, A server
              <strong>SHOULD</strong>&#160;be capable of returning references to CCD documents and
              <strong>MAY</strong>provide references to other document types for a patient searched by type and/or date using:GET [base]/DocumentReference/$docref?patient=[id]{&amp;type=[type]}{&amp;period=[date]}</li> </ul>
          <p/>
          <span>Search Parameters:</span>
          <table border="1">
            <thead>
              <tr>
                <th style="width:2.71in ">
                  <span>Conformance</span> </th>
                <th>
                  <span>Parameter</span> </th>
                <th style="width:2.11in ">
                  <span>Type</span> </th>
                <th style="width:2.90in ">
                  <span>Modifiers</span> </th> </tr> </thead>
            <tbody>
              <tr>
                <td style="width:2.71in ">
                  <span>SHALL</span> </td>
                <td>
                  <span>patient</span> </td>
                <td style="width:2.11in ">
                  <span>reference</span> </td>
                <td style="width:2.90in ">&#160;</td> </tr>
              <tr>
                <td style="width:2.71in ">
                  <span>SHOULD</span> </td>
                <td>
                  <span>period</span> </td>
                <td style="width:2.11in ">
                  <span>date</span> </td>
                <td style="width:2.90in ">
                  <p>The server SHALL support the
                    <a href="http://hl7.org/fhir/2017Jan/search.html#prefix">date search modifiers</a>&#8216;ge&#8217;,&#8216;le&#8217;,&#8216;gt','lt' for this profile</p>
                </td> </tr>
              <tr>
                <td style="width:2.71in ">
                  <span>SHOULD</span> </td>
                <td>
                  <span>type</span> </td>
                <td style="width:2.11in ">
                  <span>token</span> </td>
                <td style="width:2.90in ">&#160;</td> </tr> </tbody> </table>
          <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/r2/StructureDefinition-argo-goal.html">
              <span>Argonaut Data Query Goal Profile</span>
              <br/> </a>
            <br/> </p>
          <p>
            <strong>Summary of Argonaut Data Query Search Criteria for StructureDefinition-argo-device</strong>
          </p>
          <ul>
            <li>A server is capable of returning all of a patient&#8217;s goals using GET [base]/Goal?patient=[id].</li>
            <li>A server is capable of returning all of all of a patient&#8217;s goals over a specified time period using GET [base]/Goal?patient=[id]&amp;date=[date]{&amp;date=[date]}.</li> </ul>
          <p/>
          <span>Search Parameters:</span>
          <table border="1">
            <thead>
              <tr>
                <th style="width:2.71in ">
                  <span>Conformance</span> </th>
                <th>
                  <span>Parameter</span> </th>
                <th style="width:2.11in ">
                  <span>Type</span> </th>
                <th style="width:2.90in ">
                  <span>Modifiers</span> </th> </tr> </thead>
            <tbody>
              <tr>
                <td style="width:2.71in ">
                  <span>SHALL</span> </td>
                <td>
                  <span>patient</span> </td>
                <td style="width:2.11in ">
                  <span>reference</span> </td>
                <td style="width:2.90in ">&#160;</td> </tr>
              <tr>
                <td style="width:2.71in ">
                  <span>SHALL</span> </td>
                <td>
                  <span>date</span> </td>
                <td style="width:2.11in ">
                  <span>date</span> </td>
                <td style="width:2.90in ">
                  <p>The server SHALL support the
                    <a href="http://hl7.org/fhir/2017Jan/search.html#prefix">date search modifiers</a>&#8216;ge&#8217;,&#8216;le&#8217;,&#8216;gt','lt' for this profile</p>
                </td> </tr> </tbody> </table>
          <p/>
          <p>
            <span>Supported Search Combinations:</span>
            <span>patient</span>
            <span>+ </span>
            <span>date</span> </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/r2/StructureDefinition-argo-immunization.html">
              <span>Argonaut Data Query Immunization Profile</span>
              <br/> </a>
            <br/> </p>
          <p>
            <strong>Summary of Argonaut Data Query Search Criteria for StructureDefinition-argo-immunization</strong>
          </p>
          <ul>
            <li>A client has connected to a server and fetched all immunizations for a patient using GET /Immunization?patient=[id].</li> </ul>
          <p/>
          <span>Search Parameters:</span>
          <table border="1">
            <thead>
              <tr>
                <th style="width:2.71in ">
                  <span>Conformance</span> </th>
                <th>
                  <span>Parameter</span> </th>
                <th style="width:2.11in ">
                  <span>Type</span> </th>
                <th style="width:2.90in ">
                  <span>Modifiers</span> </th> </tr> </thead>
            <tbody>
              <tr>
                <td style="width:2.71in ">
                  <span>SHALL</span> </td>
                <td>
                  <span>patient</span> </td>
                <td style="width:2.11in ">
                  <span>reference</span> </td>
                <td style="width:2.90in ">&#160;</td> </tr> </tbody> </table>
          <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/r2/StructureDefinition-argo-diagnosticreport.html">
              <span>Argonaut Data Query DiagnosticReport Profile</span>
              <br/> </a>
            <br/> </p>
          <p>
            <strong>Summary of Argonaut Data Query Search Criteria for StructureDefinition-argo-diagnosticreport</strong>
          </p>
          <ul>
            <li>A server is capable of returning all of a patient&#8217;s laboratory diagnostic reports queried by category using GET [base]/DiagnosticReport?patient=[id]&amp;category=LAB.</li>
            <li>A server is capable of returning all of a patient&#8217;s laboratory diagnostic reports queried by category code and date range using GET [base]/DiagnosticReport?patient=[id]&amp;category=LAB&amp;date=[date]{&amp;date=[date]}.</li>
            <li>
              <p>A server is capable of returning all of a patient&#8217;s laboratory diagnostic reports queried by category and code using GET [base]/DiagnosticReport?patient=[id]&amp;category=LAB&amp;code=[LOINC].</p>
            </li>
            <li>
              <p>A server
                <strong>SHOULD</strong>be capable of returning all of a patient&#8217;s laboratory diagnostic reports queried by category and one or more codes and date range using GET [base]/DiagnosticReport?patient=[id]&amp;category=LAB&amp;code=[LOINC1{,LOINC2,LOINC3,&#8230;}]&amp;date=[date]{&amp;date=[date]}.</p>
            </li> </ul>
          <p/>
          <span>Search Parameters:</span>
          <table border="1">
            <thead>
              <tr>
                <th style="width:2.71in ">
                  <span>Conformance</span> </th>
                <th>
                  <span>Parameter</span> </th>
                <th style="width:2.11in ">
                  <span>Type</span> </th>
                <th style="width:2.90in ">
                  <span>Modifiers</span> </th> </tr> </thead>
            <tbody>
              <tr>
                <td style="width:2.71in ">
                  <span>SHALL</span> </td>
                <td>
                  <span>patient</span> </td>
                <td style="width:2.11in ">
                  <span>reference</span> </td>
                <td style="width:2.90in ">&#160;</td> </tr>
              <tr>
                <td style="width:2.71in ">
                  <span>SHALL</span> </td>
                <td>
                  <span>category</span> </td>
                <td style="width:2.11in ">
                  <span>token</span> </td>
                <td style="width:2.90in ">&#160;</td> </tr>
              <tr>
                <td style="width:2.71in ">
                  <span>SHALL</span> </td>
                <td>
                  <span>code</span> </td>
                <td style="width:2.11in ">
                  <span>token</span> </td>
                <td style="width:2.90in ">&#160;</td> </tr>
              <tr>
                <td style="width:2.71in ">
                  <span>SHALL</span> </td>
                <td>
                  <span>date</span> </td>
                <td style="width:2.11in ">
                  <span>date</span> </td>
                <td style="width:2.90in ">
                  <p>The server SHALL support the
                    <a href="http://hl7.org/fhir/2017Jan/search.html#prefix">date search modifiers</a>&#8216;ge&#8217;,&#8216;le&#8217;,&#8216;gt','lt' for this profile</p>
                </td> </tr> </tbody> </table>
          <p/>
          <p>
            <span>Supported Search Combinations:</span>
            <span>patient</span>
            <span>+ </span>
            <span>category</span>
            <span>, </span>
            <span>patient</span>
            <span>+ </span>
            <span>category</span>
            <span>+ </span>
            <span>date</span>
            <span>, </span>
            <span>patient</span>
            <span>+ </span>
            <span>category</span>
            <span>+ </span>
            <span>code</span>
            <span>, </span>
            <span>patient</span>
            <span>+ </span>
            <span>category</span>
            <span>+ </span>
            <span>code</span>
            <span>+ </span>
            <span>date</span> </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/r2/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/>
          <span>Search Parameters:</span>
          <table border="1">
            <thead>
              <tr>
                <th style="width:2.71in ">
                  <span>Conformance</span> </th>
                <th>
                  <span>Parameter</span> </th>
                <th style="width:2.11in ">
                  <span>Type</span> </th>
                <th style="width:2.90in ">
                  <span>Modifiers</span> </th> </tr> </thead>
            <tbody>
              <tr>
                <td/> </tr> </tbody> </table>
          <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/r2/StructureDefinition-argo-medicationstatement.html">
              <span>Argonaut Data Query MedicationStatement Profile</span>
              <br/> </a>
            <br/> </p>
          <p>
            <strong>Summary of Argonaut Data Query Search Criteria for StructureDefinition-argo-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 must support both methods.</p>
          <ul>
            <li>A server is capable of returning a patient&#8217;s medications using one of or both</li> </ul>
          <ol>
            <li>GET /MedicationStatement?patient=[id]</li>
            <li>GET /MedicationStatement?patient=[id]&amp;_include=MedicationStatement:medication</li> </ol>
          <p/>
          <span>Search Parameters:</span>
          <table border="1">
            <thead>
              <tr>
                <th style="width:2.71in ">
                  <span>Conformance</span> </th>
                <th>
                  <span>Parameter</span> </th>
                <th style="width:2.11in ">
                  <span>Type</span> </th>
                <th style="width:2.90in ">
                  <span>Modifiers</span> </th> </tr> </thead>
            <tbody>
              <tr>
                <td style="width:2.71in ">
                  <span>SHALL</span> </td>
                <td>
                  <span>patient</span> </td>
                <td style="width:2.11in ">
                  <span>reference</span> </td>
                <td style="width:2.90in ">&#160;</td> </tr> </tbody> </table>
          <p/>
          <p>
            <span>Supported Includes: </span>
            <span>MedicationStatement.medicationReference</span> </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/r2/StructureDefinition-argo-MedicationOrder.html">
              <span>Argonaut Data Query MedicationOrder Profile</span>
              <br/> </a>
            <br/> </p>
          <p>
            <strong>Summary of Argonaut Data Query Search Criteria for StructureDefinition-argo-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/2017Jan/references.html#contained">contained</a>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
            <a href="http://hl7.org/fhir/2017Jan/references.html#include">include</a>parameter for searching this element. The client application must support both methods.</p>
          <ul>
            <li>A server is capable of returning a patient&#8217;s medications using one of or both</li> </ul>
          <ol>
            <li>GET /MedicationOrder?patient=[id]</li>
            <li>GET /MedicationOrder?patient=[id]&amp;_include=MedicationOrder:medication</li> </ol>
          <p/>
          <span>Search Parameters:</span>
          <table border="1">
            <thead>
              <tr>
                <th style="width:2.71in ">
                  <span>Conformance</span> </th>
                <th>
                  <span>Parameter</span> </th>
                <th style="width:2.11in ">
                  <span>Type</span> </th>
                <th style="width:2.90in ">
                  <span>Modifiers</span> </th> </tr> </thead>
            <tbody>
              <tr>
                <td style="width:2.71in ">
                  <span>SHALL</span> </td>
                <td>
                  <span>patient</span> </td>
                <td style="width:2.11in ">
                  <span>reference</span> </td>
                <td style="width:2.90in ">&#160;</td> </tr> </tbody> </table>
          <p/>
          <p>
            <span>Supported Includes: </span>
            <span>MedicationOrder.medicationReference</span> </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/r2/StructureDefinition-argo-observationresults.html">
              <span>Argonaut Data Query Result Observation Profile</span>
              <br/> </a>
            <a href="http://fhir.org/guides/argonaut/r2/StructureDefinition-argo-vitalsigns.html">
              <span>Argonaut Data Query Vital Signs Profile</span>
              <br/> </a>
            <a href="http://fhir.org/guides/argonaut/r2/StructureDefinition-argo-smokingstatus.html">
              <span>Argonaut Data Query Smoking Status Observation Profile</span>
              <br/> </a>
            <br/> </p>.
          <p>
            <strong>Summary of Argonaut Data Query Search Criteria for StructureDefinition-argo-observationresults</strong>
          </p>
          <ul>
            <li>A server is capable of returning all of a patient's laboratory results queried by category using GET [base]/Observation?patient=[id]&amp;category=laboratory.</li>
            <li>A server is capable of returning all of a patient's laboratory results queried by category code and date range usingGET [base]/Observation?patient=[id]&amp;category=laboratory&amp;date=[date]{&amp;date=[date]}.</li>
            <li>A server is capable of returning all of a patient's laboratory results queried by category and code using GET [base]/Observation?patient=[id]&amp;category=laboratory&amp;code=[LOINC].</li>
            <li>A server SHOULD be capable of returning all of a patient's laboratory results queried by category and one or more codes and date range using GET [base]/Observation?patient=[id]&amp;category=laboratory&amp;code=[LOINC1{,LOINC2,LOINC3,&#8230;}]&amp;date=[date]{&amp;date=[date]}.</li> </ul>
          <p>
            <strong>Summary of Argonaut Data Query Search Criteria for StructureDefinition-argo-smokingstatus</strong>
          </p>
          <ul>
            <li>A server is capable of returning a a patient&#8217;s smoking status using GET [base]/Observation?patient=[id]&amp;code=72166-2</li> </ul>
          <p>
            <strong>Summary of Argonaut Data Query Search Criteria for StructureDefinition-argo-vitalsigns</strong>
          </p>
          <ul>
            <li>A server is capable of returning all of a patient&#8217;s vital signs that it supports using GET [base]/Observation?patient=[id]&amp;category=vital-signs.</li>
            <li>A server is capable of returning all of a patient&#8217;s vital signs queried by date range using GET [base]/Observation?patient=[id]&amp;category=vital-signs&amp;date=[date]{&amp;date=[date]}.</li>
            <li>
              <p>A server is capable of returning any of a patient&#8217;s vital signs queried by one or more of the codes listed below using GET [base]/Observation?patient=[id]&amp;code[vital sign LOINC{,LOINC2,LOINC3,&#8230;}].</p>
            </li>
            <li>
              <p>A server
                <strong>SHOULD</strong>be capable of returning any of a patient&#8217;s vital signs queried by one or more of the codes listed below and date range using GET [base]/Observation?patient=[id]&amp;code=[LOINC{,LOINC2&#8230;}]vital-signs&amp;date=[date]{&amp;date=[date]}.</p>
            </li> </ul>
          <p/>
          <span>Search Parameters:</span>
          <table border="1">
            <thead>
              <tr>
                <th style="width:2.71in ">
                  <span>Conformance</span> </th>
                <th>
                  <span>Parameter</span> </th>
                <th style="width:2.11in ">
                  <span>Type</span> </th>
                <th style="width:2.90in ">
                  <span>Modifiers</span> </th> </tr> </thead>
            <tbody>
              <tr>
                <td style="width:2.71in ">
                  <span>SHALL</span> </td>
                <td>
                  <span>patient</span> </td>
                <td style="width:2.11in ">
                  <span>reference</span> </td>
                <td style="width:2.90in ">&#160;</td> </tr>
              <tr>
                <td style="width:2.71in ">
                  <span>SHALL</span> </td>
                <td>
                  <span>category</span> </td>
                <td style="width:2.11in ">
                  <span>token</span> </td>
                <td style="width:2.90in ">&#160;</td> </tr>
              <tr>
                <td style="width:2.71in ">
                  <span>SHALL</span> </td>
                <td>
                  <span>code</span> </td>
                <td style="width:2.11in ">
                  <span>token</span> </td>
                <td style="width:2.90in ">&#160;</td> </tr>
              <tr>
                <td style="width:2.71in ">
                  <span>SHALL</span> </td>
                <td>
                  <span>date</span> </td>
                <td style="width:2.11in ">
                  <span>date</span> </td>
                <td style="width:2.90in ">
                  <p>The server SHALL support the
                    <a href="http://hl7.org/fhir/2017Jan/search.html#prefix">date search modifiers</a>&#8216;ge&#8217;,&#8216;le&#8217;,&#8216;gt','lt' for this profile</p>
                </td> </tr> </tbody> </table>
          <p/>
          <p>
            <span>Supported Search Combinations:</span>
            <span>patient</span>
            <span>+ </span>
            <span>category</span>
            <span>, </span>
            <span>patient</span>
            <span>+ </span>
            <span>category</span>
            <span>+ </span>
            <span>date</span>
            <span>, </span>
            <span>patient</span>
            <span>+ </span>
            <span>category</span>
            <span>+ </span>
            <span>code</span>
            <span>, </span>
            <span>patient</span>
            <span>+ </span>
            <span>category</span>
            <span>+ </span>
            <span>code</span>
            <span>+ </span>
            <span>date</span> </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/r2/StructureDefinition-argo-procedure.html">
              <span>Argonaut Data Query Procedure Profile</span>
              <br/> </a>
            <br/> </p>
          <p>
            <strong>Summary of Argonaut Data Query Search Criteria for StructureDefinition-argo-procedure</strong>
          </p>
          <ul>
            <li>A server is capable of returning a patient&#8217;s procedures using GET/Procedure?patient=[id].</li>
            <li>A server is capable of returning all of all of a patient&#8217;s procedures over a specified time period using GET /Procedure?patient=[id]&amp;date=[date]{&amp;date=[date]}.</li> </ul>
          <p/>
          <span>Search Parameters:</span>
          <table border="1">
            <thead>
              <tr>
                <th style="width:2.71in ">
                  <span>Conformance</span> </th>
                <th>
                  <span>Parameter</span> </th>
                <th style="width:2.11in ">
                  <span>Type</span> </th>
                <th style="width:2.90in ">
                  <span>Modifiers</span> </th> </tr> </thead>
            <tbody>
              <tr>
                <td style="width:2.71in ">
                  <span>SHALL</span> </td>
                <td>
                  <span>patient</span> </td>
                <td style="width:2.11in ">
                  <span>reference</span> </td>
                <td style="width:2.90in ">&#160;</td> </tr>
              <tr>
                <td style="width:2.71in ">
                  <span>SHALL</span> </td>
                <td>
                  <span>date</span> </td>
                <td style="width:2.11in ">
                  <span>date</span> </td>
                <td style="width:2.90in ">
                  <p>The server SHALL support the
                    <a href="http://hl7.org/fhir/2017Jan/search.html#prefix">date search modifiers</a>&#8216;ge&#8217;,&#8216;le&#8217;,&#8216;gt','lt' for this profile</p>
                </td> </tr> </tbody> </table>
          <p/>
          <p>
            <span>Supported Search Combinations:</span>
            <span>patient</span>
            <span>+ </span>
            <span>date</span> </p>
          <p/>
          <hr/>
        </li> </ol>
      <br/>
      <br/>
      <br/> </div>
  </text>
  <url value="http://fhir.org/guides/argonaut/Conformance/server"/>
  <name value="Argonaut Data Query Implementation Guide Server"/>
  <status value="draft"/>
  <publisher value="Argonaut Project"/>
  <contact>
    <telecom>
      <system value="other"/>
      <value value="http://argonautwiki.hl7.org"/>
    </telecom>
  </contact>
  <date value="2016-12-15"/>
  <description value="This profile defines the expected capabilities of a Argonaut Data Query server when conforming to the Argonaut Data Query IG The conformance resource includes the complete list of actual profiles, RESTful operations, and search parameters supported by Argonaut Data Query Servers. Servers have the option of choosing from this list to access necessary data based on their local use cases and other contextual requirements."/>
  <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/r2/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/r2/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/r2/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/r2/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/r2/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/r2/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/r2/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/r2/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/r2/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/r2/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/r2/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/r2/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/r2/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/r2/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/r2/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/r2/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/r2/StructureDefinition-argo-procedure.html"/>
    <display value="Argonaut Data Query Procedure Profile"/>
  </profile>
  <rest>
    <mode value="server"/>
    <documentation value="&lt;p&gt;&lt;strong&gt;The Argonaut Data Query Server SHALL:&lt;/strong&gt;&lt;/p&gt; &lt;ol&gt; &lt;li&gt;Support the Argonaut Data Query Patient resource profile.&lt;/li&gt; &lt;li&gt;Support at least one additional resource profile from the list of Argonaut Data Query Profiles&lt;/li&gt; &lt;li&gt;Implement REST behavior according to the FHIR specification&lt;/li&gt; &lt;li&gt;Support json resource formats for all Argonaut Data Query interactions.&lt;/li&gt; &lt;li&gt;Identify the Argonaut Data Query profile(s) supported as part of the &lt;a href=&quot;http://build.fhir.org/resource-definitions.html#Meta.profile&quot;&gt;FHIR Meta profile attribute&lt;/a&gt; for each instance.&lt;/li&gt; &lt;li&gt;Declare a Conformance identifying the list of profiles, operations, search parameter supported. &lt;/li&gt; &lt;/ol&gt; &lt;p&gt;&lt;strong&gt;The Argonaut Data Query Server SHOULD:&lt;/strong&gt; &lt;/p&gt; &lt;ol&gt; &lt;li&gt;Support xml resource formats for all Argonaut Data Query interactions. &lt;/li&gt; &lt;/ol&gt;"/>
    <security>
      <description value="&lt;p&gt;&lt;strong&gt;Argonaut Data Query Servers SHALL&lt;/strong&gt;&lt;/p&gt; &lt;ol&gt; &lt;li&gt;implement the &lt;a href=&quot;index.html#security&quot;&gt;security requirements&lt;/a&gt; documented in this guide&lt;/li&gt; &lt;li&gt;A server has ensured that every API request includes a valid Authorization token, supplied via: &lt;code&gt;Authorization: Bearer {server-specific-token-here}&lt;/code&gt;&lt;/li&gt; &lt;li&gt;A server has rejected any unauthorized requests by returning an &lt;code&gt;HTTP 401&lt;/code&gt; Unauthorized response code.&lt;/li&gt; &lt;/ol&gt;"/>
    </security>
    <resource>
      <extension url="http://fhir.org/guides/argonaut/StructureDefinition/argo-resource-documentation">
        <valueMarkdown value="&lt;p&gt;&lt;strong&gt;Summary of Argonaut Data Query Search Criteria for StructureDefinition-argo-patient&lt;/strong&gt;&lt;/p&gt; &lt;ul&gt; &lt;li&gt;A server is capable of returning a patient using GET [base]/Patient/[id].&lt;/li&gt; &lt;li&gt;A server returns valid FHIR Patient resources according to the Data Access Framework (DAF) Patient Profile..&lt;/li&gt; &lt;li&gt;A server has exposed a FHIR Patient search endpoint supporting at a minimum the following search parameters: &lt;ul&gt; &lt;li&gt;identifier&lt;/li&gt; &lt;/ul&gt;&lt;/li&gt; &lt;li&gt;A server has exposed a FHIR Patient search endpoint supporting at a minimum the following search parameters when at least 2 (example name and gender) are present: &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; "/>
      </extension>
      <extension url="http://hl7.org/fhir/StructureDefinition/conformance-search-parameter-combination">
        <extension url="required">
          <valueString value="name"/>
        </extension>
        <extension url="required">
          <valueString value="gender"/>
        </extension>
      </extension>
      <extension url="http://hl7.org/fhir/StructureDefinition/conformance-search-parameter-combination">
        <extension url="required">
          <valueString value="name"/>
        </extension>
        <extension url="required">
          <valueString value="birthdate"/>
        </extension>
      </extension>
      <extension url="http://hl7.org/fhir/StructureDefinition/conformance-search-parameter-combination">
        <extension url="required">
          <valueString value="family"/>
        </extension>
        <extension url="required">
          <valueString value="gender"/>
        </extension>
      </extension>
      <extension url="http://hl7.org/fhir/StructureDefinition/conformance-search-parameter-combination">
        <extension url="required">
          <valueString value="given"/>
        </extension>
        <extension url="required">
          <valueString value="gender"/>
        </extension>
      </extension>
      <type value="Patient"/>
      <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 Data Query patient 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 Data Query patients 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 Data Query patient 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 Data Query patient instance"/>
      </interaction>
      <searchParam>
        <extension url="http://hl7.org/fhir/StructureDefinition/conformance-expectation">
          <valueCode value="SHALL"/>
        </extension>
        <name value="name"/>
        <definition value="http://hl7.org/fhir/SearchParameter/Patient-name"/>
        <type value="string"/>
      </searchParam>
      <searchParam>
        <extension url="http://hl7.org/fhir/StructureDefinition/conformance-expectation">
          <valueCode value="SHALL"/>
        </extension>
        <name value="family"/>
        <definition value="http://hl7.org/fhir/SearchParameter/Patient-family"/>
        <type value="string"/>
      </searchParam>
      <searchParam>
        <extension url="http://hl7.org/fhir/StructureDefinition/conformance-expectation">
          <valueCode value="SHALL"/>
        </extension>
        <name value="given"/>
        <definition value="http://hl7.org/fhir/SearchParameter/Patient-given"/>
        <type value="string"/>
      </searchParam>
      <searchParam>
        <extension url="http://hl7.org/fhir/StructureDefinition/conformance-expectation">
          <valueCode value="SHALL"/>
        </extension>
        <name value="identifier"/>
        <definition value="http://hl7.org/fhir/SearchParameter/Patient-identifier"/>
        <type value="token"/>
      </searchParam>
      <searchParam>
        <extension url="http://hl7.org/fhir/StructureDefinition/conformance-expectation">
          <valueCode value="SHALL"/>
        </extension>
        <name value="gender"/>
        <definition value="http://hl7.org/fhir/SearchParameter/Patient-gender"/>
        <type value="token"/>
      </searchParam>
      <searchParam>
        <extension url="http://hl7.org/fhir/StructureDefinition/conformance-expectation">
          <valueCode value="SHALL"/>
        </extension>
        <name value="birthdate"/>
        <definition value="http://hl7.org/fhir/SearchParameter/Patient-birthdate"/>
        <type value="date"/>
      </searchParam>
    </resource>
    <resource>
      <extension url="http://fhir.org/guides/argonaut/StructureDefinition/argo-resource-documentation">
        <valueMarkdown value="&lt;p&gt;&lt;strong&gt;Summary of Argonaut Data Query Search Criteria for StructureDefinition-argo-allergyintolerance&lt;/strong&gt;&lt;/p&gt; &lt;ul&gt; &lt;li&gt;A server is capable of returning a patient&#8217;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="SHALL"/>
        </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="SHALL"/>
        </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="SHOULD"/>
        </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="SHOULD"/>
        </extension>
        <code value="vread"/>
        <documentation value="Allows retrieval of a historical version of a Argonaut Data Query AllergyIntolerance instance"/>
      </interaction>
      <searchParam>
        <extension url="http://hl7.org/fhir/StructureDefinition/conformance-expectation">
          <valueCode value="SHALL"/>
        </extension>
        <name value="patient"/>
        <definition value="http://hl7.org/fhir/SearchParameter/AllergyIntolerance-Patient"/>
        <type value="reference"/>
      </searchParam>
    </resource>
    <resource>
      <extension url="http://fhir.org/guides/argonaut/StructureDefinition/argo-resource-documentation">
        <valueMarkdown value="&lt;p&gt;&lt;strong&gt;Summary of Argonaut Data Query Search Criteria for StructureDefinition-argo-careplan&lt;/strong&gt;&lt;/p&gt; &lt;ul&gt; &lt;li&gt;A server is capable of returning all of a patient&#8217;s Assessment and Plan of Treatment information using GET /CarePlan?patient=[id]&amp;ampcategory=assess-plan.&lt;/li&gt; &lt;li&gt;&lt;p&gt;A server &lt;strong&gt;SHOULD&lt;/strong&gt; be capable of returning a patient&#8217;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;/p&gt;&lt;/li&gt; &lt;li&gt;A server &lt;strong&gt;SHOULD&lt;/strong&gt; be capable returning all of a patient&#8217;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;&lt;p&gt;A server &lt;strong&gt;SHOULD&lt;/strong&gt; be capable returning a patient&#8217;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;/p&gt;&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 server is capable of returning 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>
      <extension url="http://hl7.org/fhir/StructureDefinition/conformance-search-parameter-combination">
        <extension url="required">
          <valueString value="patient"/>
        </extension>
        <extension url="required">
          <valueString value="category"/>
        </extension>
      </extension>
      <extension url="http://hl7.org/fhir/StructureDefinition/conformance-search-parameter-combination">
        <extension url="required">
          <valueString value="patient"/>
        </extension>
        <extension url="required">
          <valueString value="category"/>
        </extension>
        <extension url="required">
          <valueString value="date"/>
        </extension>
      </extension>
      <extension url="http://hl7.org/fhir/StructureDefinition/conformance-search-parameter-combination">
        <extension url="required">
          <valueString value="patient"/>
        </extension>
        <extension url="required">
          <valueString value="category"/>
        </extension>
        <extension url="required">
          <valueString value="status"/>
        </extension>
      </extension>
      <extension url="http://hl7.org/fhir/StructureDefinition/conformance-search-parameter-combination">
        <extension url="required">
          <valueString value="patient"/>
        </extension>
        <extension url="required">
          <valueString value="category"/>
        </extension>
        <extension url="required">
          <valueString value="status"/>
        </extension>
        <extension url="required">
          <valueString value="date"/>
        </extension>
      </extension>
      <type value="CarePlan"/>
      <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 Data Query careplan 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 Data Query careplan 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 Data Query careplan 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 Data Query careplan instance"/>
      </interaction>
      <searchParam>
        <extension url="http://hl7.org/fhir/StructureDefinition/conformance-expectation">
          <valueCode value="SHALL"/>
        </extension>
        <name value="patient"/>
        <definition value="http://hl7.org/fhir/SearchParameter/CarePlan-Patient"/>
        <type value="reference"/>
      </searchParam>
      <searchParam>
        <extension url="http://hl7.org/fhir/StructureDefinition/conformance-expectation">
          <valueCode value="SHALL"/>
        </extension>
        <name value="category"/>
        <definition value="http://hl7.org/fhir/SearchParameter/CarePlan-Category"/>
        <type value="token"/>
      </searchParam>
      <searchParam>
        <extension url="http://hl7.org/fhir/StructureDefinition/conformance-expectation">
          <valueCode value="SHOULD"/>
        </extension>
        <name value="status"/>
        <definition value="http://hl7.org/fhir/SearchParameter/CarePlan-Status"/>
        <type value="token"/>
      </searchParam>
      <searchParam>
        <extension url="http://hl7.org/fhir/StructureDefinition/conformance-expectation">
          <valueCode value="SHOULD"/>
        </extension>
        <name value="date"/>
        <definition value="http://hl7.org/fhir/SearchParameter/CarePlan-Date"/>
        <type value="date"/>
        <documentation value="&lt;p&gt;The server SHALL support the &lt;a href=&quot;http://hl7.org/fhir/2017Jan/search.html#prefix&quot;&gt;date search modifiers&lt;/a&gt; &#8216;ge&#8217;,&#8216;le&#8217;,&#8216;gt&apos;,&apos;lt&apos; for this profile&lt;/p&gt;"/>
      </searchParam>
    </resource>
    <resource>
      <extension url="http://fhir.org/guides/argonaut/StructureDefinition/argo-resource-documentation">
        <valueMarkdown value="&lt;p&gt;&lt;strong&gt;Summary of Argonaut Data Query Search Criteria for StructureDefinition-argo-condition&lt;/strong&gt;&lt;/p&gt; &lt;ul&gt; &lt;li&gt;&lt;p&gt;A server is capable of returning a patient&#8217;s conditions list using GET/Condition?patient=[id].&lt;/p&gt;&lt;/li&gt; &lt;li&gt;A server &lt;strong&gt;SHOULD&lt;/strong&gt; be capable returning all of a patient&#8217;s active problems and health concerns using &#8216;GET /Condition?patient=[id]&amp;ampclinicalstatus=active,recurrance,remission&#8217;&lt;/li&gt; &lt;li&gt;&lt;p&gt;A server &lt;strong&gt;SHOULD&lt;/strong&gt; be capable returning all of a patient&#8217;s problems or all of patient&#8217;s health concerns using &#8216;GET /Condition?patient=[id]&amp;ampcategory=[problem|health-concern]&#8217;&lt;/p&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="clinicalstatus"/>
        </extension>
      </extension>
      <extension url="http://hl7.org/fhir/StructureDefinition/conformance-search-parameter-combination">
        <extension url="required">
          <valueString value="patient"/>
        </extension>
        <extension url="required">
          <valueString value="category"/>
        </extension>
      </extension>
      <type value="Condition"/>
      <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 Data Query condition 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 Data Query condition 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 Data Query condition 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 Data Query condition instance"/>
      </interaction>
      <searchParam>
        <extension url="http://hl7.org/fhir/StructureDefinition/conformance-expectation">
          <valueCode value="SHALL"/>
        </extension>
        <name value="patient"/>
        <definition value="http://hl7.org/fhir/SearchParameter/Condition-Patient"/>
        <type value="reference"/>
      </searchParam>
      <searchParam>
        <extension url="http://hl7.org/fhir/StructureDefinition/conformance-expectation">
          <valueCode value="SHOULD"/>
        </extension>
        <name value="category"/>
        <definition value="http://hl7.org/fhir/SearchParameter/Condition-Category"/>
        <type value="token"/>
      </searchParam>
      <searchParam>
        <extension url="http://hl7.org/fhir/StructureDefinition/conformance-expectation">
          <valueCode value="SHOULD"/>
        </extension>
        <name value="clinicalstatus"/>
        <definition value="http://hl7.org/fhir/SearchParameter/Condition-ClinicalStatus"/>
        <type value="token"/>
      </searchParam>
    </resource>
    <resource>
      <extension url="http://fhir.org/guides/argonaut/StructureDefinition/argo-resource-documentation">
        <valueMarkdown value="&lt;p&gt;&lt;strong&gt;Summary of Argonaut Data Query Search Criteria for StructureDefinition-argo-device&lt;/strong&gt;&lt;/p&gt; &lt;ul&gt; &lt;li&gt;A server is capable of returning all Unique device identifier(s)(UDI) for a patient&#8217;s implanted 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="SHALL"/>
        </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="SHALL"/>
        </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="SHOULD"/>
        </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="SHOULD"/>
        </extension>
        <code value="vread"/>
        <documentation value="Allows retrieval of a historical version of a Argonaut Data Query device instance"/>
      </interaction>
      <searchParam>
        <extension url="http://hl7.org/fhir/StructureDefinition/conformance-expectation">
          <valueCode value="SHALL"/>
        </extension>
        <name value="patient"/>
        <definition value="http://hl7.org/fhir/SearchParameter/Device-Patient"/>
        <type value="reference"/>
      </searchParam>
    </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;ul&gt; &lt;li&gt;To fetch document references, the Server &lt;strong&gt;SHALL&lt;/strong&gt; support &lt;strong&gt;either&lt;/strong&gt;: &lt;ul&gt; &lt;li&gt;a direct query for DocumentReference resources as described here&lt;/li&gt; &lt;li&gt;or the &lt;a href=&quot;OperationDefinition-docref.html&quot;&gt;$docref operation&lt;/a&gt;&amp;nbspoperation&lt;/li&gt; &lt;/ul&gt; &lt;/li&gt; &lt;/ul&gt; &lt;p style=&quot;padding-left: 60px&quot;&gt;The Client &lt;strong&gt;SHALL&lt;/strong&gt; support both methods.&lt;/p&gt; &lt;ul&gt; &lt;li&gt;If supporting a direct query, a&amp;nbspserver &lt;strong&gt;SHALL&lt;/strong&gt;&amp;nbspbe capable of returning at least the most recent CCD document references and &lt;strong&gt;MAY&lt;/strong&gt; provide most recent references to other document types for a patient using:GET [base]/DocumentReference/$docref?patient=[id]&lt;/li&gt; &lt;li&gt;If supporting a direct query, A server &lt;strong&gt;SHOULD&lt;/strong&gt;&amp;nbspbe capable of returning references to CCD documents and &lt;strong&gt;MAY&lt;/strong&gt; provide references to other document types for a patient searched by type and/or date using:GET [base]/DocumentReference/$docref?patient=[id]{&amp;amptype=[type]}{&amp;ampperiod=[date]}&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>
      <searchParam>
        <extension url="http://hl7.org/fhir/StructureDefinition/conformance-expectation">
          <valueCode value="SHALL"/>
        </extension>
        <name value="patient"/>
        <definition value="http://hl7.org/fhir/SearchParameter/DocumentReference-Patient"/>
        <type value="reference"/>
      </searchParam>
      <searchParam>
        <extension url="http://hl7.org/fhir/StructureDefinition/conformance-expectation">
          <valueCode value="SHOULD"/>
        </extension>
        <name value="period"/>
        <definition value="http://hl7.org/fhir/SearchParameter/DocumentReference-Period"/>
        <type value="date"/>
        <documentation value="&lt;p&gt;The server SHALL support the &lt;a href=&quot;http://hl7.org/fhir/2017Jan/search.html#prefix&quot;&gt;date search modifiers&lt;/a&gt; &#8216;ge&#8217;,&#8216;le&#8217;,&#8216;gt&apos;,&apos;lt&apos; for this profile&lt;/p&gt;"/>
      </searchParam>
      <searchParam>
        <extension url="http://hl7.org/fhir/StructureDefinition/conformance-expectation">
          <valueCode value="SHOULD"/>
        </extension>
        <name value="type"/>
        <definition value="http://hl7.org/fhir/SearchParameter/DocumentReference-Type"/>
        <type value="token"/>
      </searchParam>
    </resource>
    <resource>
      <extension url="http://fhir.org/guides/argonaut/StructureDefinition/argo-resource-documentation">
        <valueMarkdown value="&lt;p&gt;&lt;strong&gt;Summary of Argonaut Data Query Search Criteria for StructureDefinition-argo-device&lt;/strong&gt;&lt;/p&gt; &lt;ul&gt; &lt;li&gt;A server is capable of returning all of a patient&#8217;s goals using GET [base]/Goal?patient=[id].&lt;/li&gt; &lt;li&gt;A server is capable of returning all of all of a patient&#8217;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>
      <extension url="http://hl7.org/fhir/StructureDefinition/conformance-search-parameter-combination">
        <extension url="required">
          <valueString value="patient"/>
        </extension>
        <extension url="required">
          <valueString value="date"/>
        </extension>
      </extension>
      <type value="Goal"/>
      <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 Data Query Goal 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 Data Query Goal 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 Data Query Goal 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 Data Query Goal instance"/>
      </interaction>
      <searchParam>
        <extension url="http://hl7.org/fhir/StructureDefinition/conformance-expectation">
          <valueCode value="SHALL"/>
        </extension>
        <name value="patient"/>
        <definition value="http://hl7.org/fhir/SearchParameter/Goal-Patient"/>
        <type value="reference"/>
      </searchParam>
      <searchParam>
        <extension url="http://hl7.org/fhir/StructureDefinition/conformance-expectation">
          <valueCode value="SHALL"/>
        </extension>
        <name value="date"/>
        <definition value="http://hl7.org/fhir/SearchParameter/Goal-Date"/>
        <type value="date"/>
        <documentation value="&lt;p&gt;The server SHALL support the &lt;a href=&quot;http://hl7.org/fhir/2017Jan/search.html#prefix&quot;&gt;date search modifiers&lt;/a&gt; &#8216;ge&#8217;,&#8216;le&#8217;,&#8216;gt&apos;,&apos;lt&apos; for this profile&lt;/p&gt;"/>
      </searchParam>
    </resource>
    <resource>
      <extension url="http://fhir.org/guides/argonaut/StructureDefinition/argo-resource-documentation">
        <valueMarkdown value="&lt;p&gt;&lt;strong&gt;Summary of Argonaut Data Query Search Criteria for StructureDefinition-argo-immunization&lt;/strong&gt;&lt;/p&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="SHALL"/>
        </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="SHALL"/>
        </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="SHOULD"/>
        </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="SHOULD"/>
        </extension>
        <code value="vread"/>
        <documentation value="Allows retrieval of a historical version of a Argonaut Data Query immunization instance"/>
      </interaction>
      <searchParam>
        <extension url="http://hl7.org/fhir/StructureDefinition/conformance-expectation">
          <valueCode value="SHALL"/>
        </extension>
        <name value="patient"/>
        <definition value="http://hl7.org/fhir/SearchParameter/Immunization-Patient"/>
        <type value="reference"/>
      </searchParam>
    </resource>
    <resource>
      <extension url="http://fhir.org/guides/argonaut/StructureDefinition/argo-resource-documentation">
        <valueMarkdown value="&lt;p&gt;&lt;strong&gt;Summary of Argonaut Data Query Search Criteria for StructureDefinition-argo-diagnosticreport&lt;/strong&gt;&lt;/p&gt; &lt;ul&gt; &lt;li&gt;A server is capable of returning all of a patient&#8217;s laboratory diagnostic reports queried by category using GET [base]/DiagnosticReport?patient=[id]&amp;ampcategory=LAB.&lt;/li&gt; &lt;li&gt;A server is capable of returning all of a patient&#8217;s laboratory diagnostic reports queried 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;&lt;p&gt;A server is capable of returning all of a patient&#8217;s laboratory diagnostic reports queried by category and code using GET [base]/DiagnosticReport?patient=[id]&amp;ampcategory=LAB&amp;ampcode=[LOINC].&lt;/p&gt;&lt;/li&gt; &lt;li&gt;&lt;p&gt;A server &lt;strong&gt;SHOULD&lt;/strong&gt; be capable of returning all of a patient&#8217;s laboratory diagnostic reports queried by category and one or more codes and date range using GET [base]/DiagnosticReport?patient=[id]&amp;ampcategory=LAB&amp;ampcode=[LOINC1{,LOINC2,LOINC3,&#8230;}]&amp;ampdate=[date]{&amp;ampdate=[date]}.&lt;/p&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="category"/>
        </extension>
      </extension>
      <extension url="http://hl7.org/fhir/StructureDefinition/conformance-search-parameter-combination">
        <extension url="required">
          <valueString value="patient"/>
        </extension>
        <extension url="required">
          <valueString value="category"/>
        </extension>
        <extension url="required">
          <valueString value="date"/>
        </extension>
      </extension>
      <extension url="http://hl7.org/fhir/StructureDefinition/conformance-search-parameter-combination">
        <extension url="required">
          <valueString value="patient"/>
        </extension>
        <extension url="required">
          <valueString value="category"/>
        </extension>
        <extension url="required">
          <valueString value="code"/>
        </extension>
      </extension>
      <extension url="http://hl7.org/fhir/StructureDefinition/conformance-search-parameter-combination">
        <extension url="required">
          <valueString value="patient"/>
        </extension>
        <extension url="required">
          <valueString value="category"/>
        </extension>
        <extension url="required">
          <valueString value="code"/>
        </extension>
        <extension url="required">
          <valueString value="date"/>
        </extension>
      </extension>
      <type value="DiagnosticReport"/>
      <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 Data Query diagnosticreport 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 Data Query diagnosticreport 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 Data Query diagnosticreport 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 Data Query diagnosticreport instance"/>
      </interaction>
      <searchParam>
        <extension url="http://hl7.org/fhir/StructureDefinition/conformance-expectation">
          <valueCode value="SHALL"/>
        </extension>
        <name value="patient"/>
        <definition value="http://hl7.org/fhir/SearchParameter/DiagnosticReport-Patient"/>
        <type value="reference"/>
      </searchParam>
      <searchParam>
        <extension url="http://hl7.org/fhir/StructureDefinition/conformance-expectation">
          <valueCode value="SHALL"/>
        </extension>
        <name value="category"/>
        <definition value="http://hl7.org/fhir/SearchParameter/DiagnosticReport-Category"/>
        <type value="token"/>
      </searchParam>
      <searchParam>
        <extension url="http://hl7.org/fhir/StructureDefinition/conformance-expectation">
          <valueCode value="SHALL"/>
        </extension>
        <name value="code"/>
        <definition value="http://hl7.org/fhir/SearchParameter/DiagnosticReport-Code"/>
        <type value="token"/>
      </searchParam>
      <searchParam>
        <extension url="http://hl7.org/fhir/StructureDefinition/conformance-expectation">
          <valueCode value="SHALL"/>
        </extension>
        <name value="date"/>
        <definition value="http://hl7.org/fhir/SearchParameter/DiagnosticReport-Date"/>
        <type value="date"/>
        <documentation value="&lt;p&gt;The server SHALL support the &lt;a href=&quot;http://hl7.org/fhir/2017Jan/search.html#prefix&quot;&gt;date search modifiers&lt;/a&gt; &#8216;ge&#8217;,&#8216;le&#8217;,&#8216;gt&apos;,&apos;lt&apos; for this profile&lt;/p&gt;"/>
      </searchParam>
    </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="IF the Medication Resource is used in a MedicationStatement or a MedicationOrder. Allows discovery of existing Argonaut Data Query Medication 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="IF the Medication Resource is used in a MedicationStatement or a MedicationOrder. Allows retrieval of a specific Argonaut Data Query Medication 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 Data Query Medication 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 Data Query Medication 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 Argonaut Data Query Search Criteria for StructureDefinition-argo-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 must support both methods.&lt;/p&gt; &lt;ul&gt; &lt;li&gt;A server is capable of returning a patient&#8217;s medications using one of or both&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="SHALL"/>
        </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="SHALL"/>
        </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="SHOULD"/>
        </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="SHOULD"/>
        </extension>
        <code value="vread"/>
        <documentation value="Allows retrieval of a historical version of a Argonaut Data Query medicationstatement instance"/>
      </interaction>
      <searchInclude value="MedicationStatement.medicationReference">
        <extension url="http://hl7.org/fhir/StructureDefinition/conformance-expectation">
          <valueCode value="MAY"/>
        </extension>
      </searchInclude>
      <searchParam>
        <extension url="http://hl7.org/fhir/StructureDefinition/conformance-expectation">
          <valueCode value="SHALL"/>
        </extension>
        <name value="patient"/>
        <definition value="http://hl7.org/fhir/SearchParameter/MedicationStatement-Patient"/>
        <type value="reference"/>
      </searchParam>
    </resource>
    <resource>
      <extension url="http://fhir.org/guides/argonaut/StructureDefinition/argo-resource-documentation">
        <valueMarkdown value="&lt;p&gt;&lt;strong&gt;Summary of Argonaut Data Query Search Criteria for StructureDefinition-argo-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/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 if the an external reference to Medication is used, the server SHALL 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 must support both methods.&lt;/p&gt; &lt;ul&gt; &lt;li&gt;A server is capable of returning a patient&#8217;s medications using one of or both&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="SHALL"/>
        </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="SHALL"/>
        </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="SHOULD"/>
        </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="SHOULD"/>
        </extension>
        <code value="vread"/>
        <documentation value="Allows retrieval of a historical version of a Argonaut Data Query MedicationOrder instance"/>
      </interaction>
      <searchInclude value="MedicationOrder.medicationReference">
        <extension url="http://hl7.org/fhir/StructureDefinition/conformance-expectation">
          <valueCode value="MAY"/>
        </extension>
      </searchInclude>
      <searchParam>
        <extension url="http://hl7.org/fhir/StructureDefinition/conformance-expectation">
          <valueCode value="SHALL"/>
        </extension>
        <name value="patient"/>
        <definition value="http://hl7.org/fhir/SearchParameter/MedicationOrder-Patient"/>
        <type value="reference"/>
      </searchParam>
    </resource>
    <resource>
      <extension url="http://fhir.org/guides/argonaut/StructureDefinition/argo-resource-documentation">
        <valueMarkdown value=". &lt;p&gt;&lt;strong&gt;Summary of Argonaut Data Query Search Criteria for StructureDefinition-argo-observationresults&lt;/strong&gt;&lt;/p&gt; &lt;ul&gt; &lt;li&gt;A server is capable of returning all of a patient&amp;rsquos laboratory results queried by category using GET [base]/Observation?patient=[id]&amp;ampcategory=laboratory.&lt;/li&gt; &lt;li&gt;A server is capable of returning all of a patient&amp;rsquos laboratory results queried by category code and date range usingGET [base]/Observation?patient=[id]&amp;ampcategory=laboratory&amp;ampdate=[date]{&amp;ampdate=[date]}.&lt;/li&gt; &lt;li&gt;A server is capable of returning all of a patient&amp;rsquos laboratory results queried by category and code using GET [base]/Observation?patient=[id]&amp;ampcategory=laboratory&amp;ampcode=[LOINC].&lt;/li&gt; &lt;li&gt;A server SHOULD be capable of returning all of a patient&amp;rsquos laboratory results queried 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;hellip}]&amp;ampdate=[date]{&amp;ampdate=[date]}.&lt;/li&gt; &lt;/ul&gt; &lt;p&gt;&lt;strong&gt;Summary of Argonaut Data Query Search Criteria for StructureDefinition-argo-smokingstatus&lt;/strong&gt;&lt;/p&gt; &lt;ul&gt; &lt;li&gt;A server is capable of returning a a patient&#8217;s smoking status using GET [base]/Observation?patient=[id]&amp;ampcode=72166-2&lt;/li&gt; &lt;/ul&gt; &lt;p&gt;&lt;strong&gt;Summary of Argonaut Data Query Search Criteria for StructureDefinition-argo-vitalsigns&lt;/strong&gt;&lt;/p&gt; &lt;ul&gt; &lt;li&gt;A server is capable of returning all of a patient&#8217;s vital signs that it supports using GET [base]/Observation?patient=[id]&amp;ampcategory=vital-signs.&lt;/li&gt; &lt;li&gt;A server is capable of returning all of a patient&#8217;s vital signs queried by date range using GET [base]/Observation?patient=[id]&amp;ampcategory=vital-signs&amp;ampdate=[date]{&amp;ampdate=[date]}.&lt;/li&gt; &lt;li&gt;&lt;p&gt;A server is capable of returning any of a patient&#8217;s vital signs queried by one or more of the codes listed below using GET [base]/Observation?patient=[id]&amp;ampcode[vital sign LOINC{,LOINC2,LOINC3,&#8230;}].&lt;/p&gt;&lt;/li&gt; &lt;li&gt;&lt;p&gt;A server &lt;strong&gt;SHOULD&lt;/strong&gt; be capable of returning any of a patient&#8217;s vital signs queried by one or more of the codes listed below and date range using GET [base]/Observation?patient=[id]&amp;ampcode=[LOINC{,LOINC2&#8230;}]vital-signs&amp;ampdate=[date]{&amp;ampdate=[date]}.&lt;/p&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="category"/>
        </extension>
      </extension>
      <extension url="http://hl7.org/fhir/StructureDefinition/conformance-search-parameter-combination">
        <extension url="required">
          <valueString value="patient"/>
        </extension>
        <extension url="required">
          <valueString value="category"/>
        </extension>
        <extension url="required">
          <valueString value="date"/>
        </extension>
      </extension>
      <extension url="http://hl7.org/fhir/StructureDefinition/conformance-search-parameter-combination">
        <extension url="required">
          <valueString value="patient"/>
        </extension>
        <extension url="required">
          <valueString value="category"/>
        </extension>
        <extension url="required">
          <valueString value="code"/>
        </extension>
      </extension>
      <extension url="http://hl7.org/fhir/StructureDefinition/conformance-search-parameter-combination">
        <extension url="required">
          <valueString value="patient"/>
        </extension>
        <extension url="required">
          <valueString value="category"/>
        </extension>
        <extension url="required">
          <valueString value="code"/>
        </extension>
        <extension url="required">
          <valueString value="date"/>
        </extension>
      </extension>
      <type value="Observation"/>
      <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 Data Query results observation, smokingstatus, and vitals signs observation 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 Data Query results observation, smokingstatus, and vitals signs observation 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 Data Query results observation, smokingstatus, and vitals signs observation 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 Data Query results observation, smokingstatus, and vitals signs observation instance"/>
      </interaction>
      <searchParam>
        <extension url="http://hl7.org/fhir/StructureDefinition/conformance-expectation">
          <valueCode value="SHALL"/>
        </extension>
        <name value="patient"/>
        <definition value="http://hl7.org/fhir/SearchParameter/Observation-Patient"/>
        <type value="reference"/>
      </searchParam>
      <searchParam>
        <extension url="http://hl7.org/fhir/StructureDefinition/conformance-expectation">
          <valueCode value="SHALL"/>
        </extension>
        <name value="category"/>
        <definition value="http://hl7.org/fhir/SearchParameter/Organization-Category"/>
        <type value="token"/>
      </searchParam>
      <searchParam>
        <extension url="http://hl7.org/fhir/StructureDefinition/conformance-expectation">
          <valueCode value="SHALL"/>
        </extension>
        <name value="code"/>
        <definition value="http://hl7.org/fhir/SearchParameter/Organization-Code"/>
        <type value="token"/>
      </searchParam>
      <searchParam>
        <extension url="http://hl7.org/fhir/StructureDefinition/conformance-expectation">
          <valueCode value="SHALL"/>
        </extension>
        <name value="date"/>
        <definition value="http://hl7.org/fhir/SearchParameter/Organization-Date"/>
        <type value="date"/>
        <documentation value="&lt;p&gt;The server SHALL support the &lt;a href=&quot;http://hl7.org/fhir/2017Jan/search.html#prefix&quot;&gt;date search modifiers&lt;/a&gt; &#8216;ge&#8217;,&#8216;le&#8217;,&#8216;gt&apos;,&apos;lt&apos; for this profile&lt;/p&gt;"/>
      </searchParam>
    </resource>
    <resource>
      <extension url="http://fhir.org/guides/argonaut/StructureDefinition/argo-resource-documentation">
        <valueMarkdown value=" &lt;p&gt;&lt;strong&gt;Summary of Argonaut Data Query Search Criteria for StructureDefinition-argo-procedure&lt;/strong&gt;&lt;/p&gt; &lt;ul&gt; &lt;li&gt;A server is capable of returning a patient&#8217;s procedures using GET/Procedure?patient=[id].&lt;/li&gt; &lt;li&gt;A server is capable of returning all of all of a patient&#8217;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>
      <extension url="http://hl7.org/fhir/StructureDefinition/conformance-search-parameter-combination">
        <extension url="required">
          <valueString value="patient"/>
        </extension>
        <extension url="required">
          <valueString value="date"/>
        </extension>
      </extension>
      <type value="Procedure"/>
      <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 Data Query procedure 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 Data Query procedure 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 Data Query procedure 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 Data Query procedure instance"/>
      </interaction>
      <searchParam>
        <extension url="http://hl7.org/fhir/StructureDefinition/conformance-expectation">
          <valueCode value="SHALL"/>
        </extension>
        <name value="patient"/>
        <definition value="http://hl7.org/fhir/SearchParameter/Procedure-Patient"/>
        <type value="reference"/>
      </searchParam>
      <searchParam>
        <extension url="http://hl7.org/fhir/StructureDefinition/conformance-expectation">
          <valueCode value="SHALL"/>
        </extension>
        <name value="date"/>
        <definition value="http://hl7.org/fhir/SearchParameter/Procedure-Date"/>
        <type value="date"/>
        <documentation value="&lt;p&gt;The server SHALL support the &lt;a href=&quot;http://hl7.org/fhir/2017Jan/search.html#prefix&quot;&gt;date search modifiers&lt;/a&gt; &#8216;ge&#8217;,&#8216;le&#8217;,&#8216;gt&apos;,&apos;lt&apos; for this profile&lt;/p&gt;"/>
      </searchParam>
    </resource>
    <operation>
      <extension url="http://hl7.org/fhir/StructureDefinition/conformance-expectation">
        <valueCode value="MAY"/>
      </extension>
      <name value="docref"/>
      <definition>
        <reference value="http://fhir.org/guides/argonaut/OperationDefinition/docref"/>
        <display value="Argonaut Get DocumentReferences"/>
      </definition>
    </operation>
  </rest>
</Conformance>

Unknown message Conformance "client" Version "1"

Tags: (no tags)  +

This Resource , XML or JSON representation, or the full version history.. provenance for this resource
Updated: by

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>

Unknown message Conformance "phr" Version "1"

Tags: (no tags)  +

This Resource , XML or JSON representation, or the full version history.. provenance for this resource
Updated: by

Prototype Conformance Statement for September 2013 Connectathon

The server offers read and search support on the following resource types:

  • Patient
  • DocumentReference
  • Condition
  • DiagnosticReport

<?xml version="1.0" encoding="UTF-8"?>
<Conformance xmlns="http://hl7.org/fhir">
  <id value="phr"/>
  <meta>
    <versionId value="1"/>
    <lastUpdated value="2018-10-08T18:32:09.503Z"/>
  </meta>
  <text>
    <status value="generated"/>
    <div xmlns="http://www.w3.org/1999/xhtml">
      <p>Prototype Conformance Statement for September 2013 Connectathon</p>
      <p>The server offers read and search support on the following resource types:</p>
      <ul>
        <li>Patient</li>
        <li>DocumentReference</li>
        <li>Condition</li>
        <li>DiagnosticReport</li> </ul> </div>
  </text>
  <name value="PHR Template"/>
  <publisher value="FHIR Project"/>
  <contact>
    <telecom>
      <system value="other"/>
      <value value="http://hl7.org/fhir"/>
    </telecom>
  </contact>
  <date value="2013-06-18"/>
  <description value="Prototype Conformance Statement for September 2013 Connectathon"/>
  <kind value="capability"/>
  <software>
    <name value="ACME PHR Server"/>
  </software>
  <fhirVersion value="1.0.0"/>
  <acceptUnknown value="no"/>
  <format value="json"/>
  <format value="xml"/>
  <rest>
    <mode value="server"/>
    <documentation value="Protoype server conformance statement for September 2013 Connectathon"/>
    <security>
      <service>
        <text value="OAuth"/>
      </service>
      <description value="We recommend that PHR servers use standard OAuth using a standard 3rd party provider. We are not testing the ability to provide an OAuth authentication/authorization service itself, and nor is providing any security required for the connectathon at all"/>
    </security>
    <resource>
      <type value="Patient"/>
      <interaction>
        <code value="read"/>
      </interaction>
      <interaction>
        <code value="search-type"/>
        <documentation value="When a client searches patients with no search criteria, they get a list of all patients they have access too. Servers may elect to offer additional search parameters, but this is not required"/>
      </interaction>
    </resource>
    <resource>
      <type value="DocumentReference"/>
      <interaction>
        <code value="read"/>
      </interaction>
      <interaction>
        <code value="search-type"/>
      </interaction>
      <searchParam>
        <name value="_id"/>
        <type value="token"/>
        <documentation value="_id parameter always supported. For the connectathon, servers may elect which search parameters are supported"/>
      </searchParam>
    </resource>
    <resource>
      <type value="Condition"/>
      <interaction>
        <code value="read"/>
      </interaction>
      <interaction>
        <code value="search-type"/>
      </interaction>
      <searchParam>
        <name value="_id"/>
        <type value="token"/>
        <documentation value="Standard _id parameter"/>
      </searchParam>
    </resource>
    <resource>
      <type value="DiagnosticReport"/>
      <interaction>
        <code value="read"/>
      </interaction>
      <interaction>
        <code value="search-type"/>
      </interaction>
      <searchParam>
        <name value="_id"/>
        <type value="token"/>
        <documentation value="Standard _id parameter"/>
      </searchParam>
      <searchParam>
        <name value="service"/>
        <type value="token"/>
        <documentation value="which diagnostic discipline/department created the report"/>
      </searchParam>
    </resource>
  </rest>
</Conformance>

Unknown message Conformance "example" Version "1"

Tags: (no tags)  +

This Resource , XML or JSON representation, or the full version history.. provenance for this resource
Updated: by

The EHR Server supports the following transactions for the resource Person: read, vread, update, history, search(name,gender), create and updates.

The EHR System supports the following message: admin-notify::Person.

The EHR Application has a general document profile.


<?xml version="1.0" encoding="UTF-8"?>
<Conformance xmlns="http://hl7.org/fhir">
  <id value="example"/>
  <meta>
    <versionId value="1"/>
    <lastUpdated value="2018-10-08T18:32:09.472Z"/>
  </meta>
  <text>
    <status value="generated"/>
    <div xmlns="http://www.w3.org/1999/xhtml">
      <p>The EHR Server supports the following transactions for the resource Person: read, vread, update, history, search(name,gender), create and updates.</p>
      <p>The EHR System supports the following message: admin-notify::Person.</p>
      <p>The EHR Application has a
        <a href="http://fhir.hl7.org/base/Profilebc054d23-75e1-4dc6-aca5-838b6b1ac81d/_history/b5fdd9fc-b021-4ea1-911a-721a60663796">general document profile</a>. </p> </div>
  </text>
  <url value="68D043B5-9ECF-4559-A57A-396E0D452311"/>
  <version value="20130510"/>
  <name value="ACME EHR Conformance statement"/>
  <status value="draft"/>
  <experimental value="true"/>
  <publisher value="ACME Corporation"/>
  <contact>
    <name value="System Administrator"/>
    <telecom>
      <system value="email"/>
      <value value="wile@acme.org"/>
    </telecom>
  </contact>
  <date value="2012-01-04"/>
  <description value="This is the FHIR conformance statement for the main EHR at ACME for the private interface - it does not describe the public interface"/>
  <requirements value="Main EHR conformance statement, published for contracting and operational support"/>
  <copyright value="Copyright &#169; Acme Healthcare and GoodCorp EHR Systems"/>
  <kind value="instance"/>
  <software>
    <name value="EHR"/>
    <version value="0.00.020.2134"/>
    <releaseDate value="2012-01-04"/>
  </software>
  <implementation>
    <description value="main EHR at ACME"/>
    <url value="http://10.2.3.4/fhir"/>
  </implementation>
  <fhirVersion value="1.0.0"/>
  <acceptUnknown value="both"/>
  <format value="xml"/>
  <format value="json"/>
  <rest>
    <mode value="server"/>
    <documentation value="Main FHIR endpoint for acem health"/>
    <security>
      <cors value="true"/>
      <service>
        <coding>
          <system value="http://hl7.org/fhir/restful-security-service"/>
          <code value="SMART-on-FHIR"/>
        </coding>
      </service>
      <description value="See Smart on FHIR documentation"/>
      <certificate>
        <type value="application/jwt"/>
        <blob value="IHRoaXMgYmxvYiBpcyBub3QgdmFsaWQ="/>
      </certificate>
    </security>
    <resource>
      <type value="Patient"/>
      <profile>
        <reference value="http://fhir.hl7.org/base/Profile7896271d-57f6-4231-89dc-dcc91eab2416"/>
      </profile>
      <interaction>
        <code value="read"/>
      </interaction>
      <interaction>
        <code value="vread"/>
        <documentation value="Only supported for patient records since 12-Dec 2012"/>
      </interaction>
      <interaction>
        <code value="update"/>
      </interaction>
      <interaction>
        <code value="history-instance"/>
      </interaction>
      <interaction>
        <code value="create"/>
      </interaction>
      <interaction>
        <code value="history-type"/>
      </interaction>
      <versioning value="versioned-update"/>
      <readHistory value="true"/>
      <updateCreate value="false"/>
      <conditionalCreate value="true"/>
      <conditionalUpdate value="false"/>
      <conditionalDelete value="not-supported"/>
      <searchInclude value="Organization"/>
      <searchRevInclude value="Person"/>
      <searchParam>
        <name value="identifier"/>
        <definition value="http://hl7.org/fhir/SearchParameter/Patient-identifier"/>
        <type value="token"/>
        <documentation value="Only supports search by institution MRN"/>
        <modifier value="missing"/>
      </searchParam>
      <searchParam>
        <name value="careprovider"/>
        <definition value="http://hl7.org/fhir/SearchParameter/Patient-careprovider"/>
        <type value="reference"/>
        <target value="Organization"/>
        <modifier value="missing"/>
        <chain value="name"/>
        <chain value="identifier"/>
      </searchParam>
    </resource>
    <interaction>
      <code value="transaction"/>
    </interaction>
    <interaction>
      <code value="history-system"/>
    </interaction>
    <compartment value="http://hl7.org/fhir/compartment/Patient"/>
  </rest>
  <messaging>
    <endpoint>
      <protocol>
        <system value="http://hl7.org/fhir/message-transport"/>
        <code value="mllp"/>
      </protocol>
      <address value="mllp:10.1.1.10:9234"/>
    </endpoint>
    <reliableCache value="30"/>
    <documentation value="ADT A08 equivalent for external system notifications"/>
    <event>
      <code>
        <system value="http://hl7.org/fhir/message-type"/>
        <code value="admin-notify"/>
      </code>
      <category value="Consequence"/>
      <mode value="receiver"/>
      <focus value="Patient"/>
      <request>
        <reference value="StructureDefinition/daf-patient"/>
      </request>
      <response>
        <reference value="StructureDefinition/MessageHeader"/>
      </response>
      <documentation value="Notification of an update to a patient resource. changing the links is not supported"/>
    </event>
  </messaging>
  <document>
    <mode value="consumer"/>
    <documentation value="Basic rules for all documents in the EHR system"/>
    <profile>
      <reference value="http://fhir.hl7.org/base/Profilebc054d23-75e1-4dc6-aca5-838b6b1ac81d/_history/b5fdd9fc-b021-4ea1-911a-721a60663796"/>
    </profile>
  </document>
</Conformance>

Unknown message Conformance "conformance-terminology-server" Version "1"

Tags: (no tags)  +

This Resource , XML or JSON representation, or the full version history.. provenance for this resource
Updated: by

Terminology Service Conformance Statement

Basic conformance statement for a Terminology Server. A server can support more fucntionality than defined here, but this is the minimum amount

Mode SERVER
Description RESTful Terminology Server
Transaction
System History
System Search
Resource Type Profile Read V-Read Search Update Updates Create Delete History
ValueSet StructureDefinition/ValueSet y y
ConceptMap StructureDefinition/ConceptMap y y

<?xml version="1.0" encoding="UTF-8"?>
<Conformance xmlns="http://hl7.org/fhir">
  <id value="conformance-terminology-server"/>
  <meta>
    <versionId value="1"/>
    <lastUpdated value="2018-10-08T18:32:09.440Z"/>
  </meta>
  <text>
    <status value="generated"/>
    <div xmlns="http://www.w3.org/1999/xhtml">
      <h2>Terminology Service Conformance Statement</h2>
      <p>Basic conformance statement for a Terminology Server. A server can support more fucntionality than defined here, but this is the minimum amount</p>
      <table>
        <tr>
          <td>Mode</td>
          <td>SERVER</td> </tr>
        <tr>
          <td>Description</td>
          <td>RESTful Terminology Server</td> </tr>
        <tr>
          <td>Transaction</td>
          <td/> </tr>
        <tr>
          <td>System History</td>
          <td/> </tr>
        <tr>
          <td>System Search</td>
          <td/> </tr> </table>
      <table>
        <tr>
          <th>
            <b>Resource Type</b> </th>
          <th>
            <b>Profile</b> </th>
          <th>
            <b>Read</b> </th>
          <th>
            <b>V-Read</b> </th>
          <th>
            <b>Search</b> </th>
          <th>
            <b>Update</b> </th>
          <th>
            <b>Updates</b> </th>
          <th>
            <b>Create</b> </th>
          <th>
            <b>Delete</b> </th>
          <th>
            <b>History</b> </th> </tr>
        <tr>
          <td>ValueSet</td>
          <td>
            <a href="StructureDefinition/ValueSet">StructureDefinition/ValueSet</a> </td>
          <td>y</td>
          <td/>
          <td>y</td>
          <td/>
          <td/>
          <td/>
          <td/>
          <td/> </tr>
        <tr>
          <td>ConceptMap</td>
          <td>
            <a href="StructureDefinition/ConceptMap">StructureDefinition/ConceptMap<