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

Resource "client" Version "6" (CapabilityStatement)

Tags:

XML or JSON representation . provenance for this resource

  • FHIR Version: 3.0.1
  • Supported formats: xml, json
  • Published: 2017-12-22
  • Published by: Health Level Seven International US Realm Steering Committee

The Section describes the expected capabilities of the US Core Client which is responsible for creating and initiating the queries for information about an individual patient. The complete list of FHIR profiles, RESTful operations, and search parameters supported by US Core Servers are defined in the Conformance requirements for the US Core Server section. US Core Clients have the option of choosing from this list to access necessary data based on their local use cases and other contextual requirements.

Behavior

Description:

The US Core Client SHOULD:

  • Support fetching and querying of one or more US Core profile(s), using the supported RESTful interactions and search parameters declared in the US Core Server CapabilityStatement.

security:

The US Core Client SHALL:

Resource Details:

Contents:

  1. Patient
  2. AllergyIntolerance
  3. CarePlan
  4. CareTeam
  5. Condition
  6. Device
  7. DiagnosticReport
  8. DocumentReference
  9. Encounter
  10. Goal
  11. Immunization
  12. Location
  13. Medication
  14. MedicationStatement
  15. MedicationRequest
  16. Observation
  17. Organization
  18. Practitioner
  19. PractitionerRole
  20. Procedure

Patient

Supported Profiles: US Core Patient Profile

Search Criteria:

  • A client SHOULD be capable of connecting to a server and fetching a patient using:

    GET [base]/Patient/[id].

  • A client SHOULD be capable of connecting to a server and fetching a patient by identifier using

    GET [base]/Patient?identifier=[system]|[code]

  1. A client SHOULD be capable of connecting to a server and fetching a patient by supporting at a minimum the following search parameters when at least 2 are present. To limit overly broad search results, a client search with gender should include family and given name search parameters.:
    • name
    • gender
    • birthdate

      • for example:

        GET [base]/Patient?family=[name]&?given=[name]&gender=[gender]


AllergyIntolerance

Supported Profiles: US Core AllergyIntolerance Profile

Search Criteria:

  1. A client SHOULD be capable of connecting to a server and fetching all patient’s allergies using:

    GET [base]/AllergyIntolerance?patient=[id]


CarePlan

Supported Profiles: US Core CarePlan Profile

Search Criteria:

  1. A client SHOULD be capable of connecting to a server and fetching all of a patient’s Assessment and Plan of Treatment information using:

    GET [base]/CarePlan?patient=[id]&category=assess-plan

  2. A client SHOULD be capable of connecting to a server and fetching a patient’s Assessment and Plan of Treatment information over a specified time period using:

    GET [base]/CarePlan?patient=[id]&category=assess-plan&date=[date]

  3. 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 [base]/CarePlan?patient=[id]&category=assess-plan&status=active

  4. A client SHOULD be capable of connecting to a server and fetching a patient’s active Assessment and Plan of Treatment information over a specified time period using

    GET [base]/CarePlan?patient=[id]&category=assess-plan&status=active&date=[date]


CareTeam

Supported Profiles: US Core CareTeam Profile

Search Criteria:

  1. A client SHOULD be capable of connecting to a server and fetching a patient’s current care team members using:

    GET [base]/CareTeam?patient=[id]&status=active


Condition

Supported Profiles: US Core Condition Profile

Search Criteria:

  1. A client SHOULD be capable of fetching all problems and health concerns for a patient, including current as well as historical problems and health concerns using:

    GET [base]/Condition?patient=[id]

  2. A client SHOULD be capable of connecting to a server and fetching all of a patient’s active problems and health concerns using:

    GET [base]/Condition?patient=[id]&clinicalstatus=active,recurrance,remission

  3. A client SHOULD be capable of connecting to a server and fetching all of a patient’s problems or all of patient’s health concerns using:

    GET [base]/Condition?patient=[id]&category=[problem|health-concern]


Device

Supported Profiles: US Core Device Profile

Search Criteria:

  1. A client SHOULD be capable of connecting to a server and fetching all Unique device identifier(s)(UDI) for a patient’s implanted device(s):

    GET [base]/Device?patient=[id]


DiagnosticReport

Supported Profiles: US Core DiagnosticReport Profile

Search Criteria:

  1. A client SHOULD be capable of connecting to a server and fetching all of a patient’s laboratory diagnostic reports queried by category using:

    GET [base]/DiagnosticReport?patient=[id]&category=LAB

  2. A client SHOULD be capable of connecting to a server and fetching 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]}

  3. A client SHOULD be capable of connecting to a server and fetching all of a patient’s laboratory diagnostic reports queried by category and code using:

    GET [base]/DiagnosticReport?patient=[id]&category=LAB&code=[LOINC]

  4. A client SHOULD be capable of connecting to a server and fetching 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]}


DocumentReference

Supported Profiles: US Core DocumentReference Profile

Search Criteria:

  1. A client SHOULD be capable of connecting to a server and fetching all of a patient’s DocumentReferences using:

    GET [base]/DocumentReference?patient=[id]

  2. A client SHOULD be capable of connecting to a server to execute the $docref operation:

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

  3. A client SHOULD be capable of connecting to a server and fetching all of a patient’s DocumentReferences for a given time period and document type:

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


Encounter

Supported Profiles: US Core Encounter Profile

Search Criteria:

  1. A client SHOULD be capable of connecting to a server and fetching all of a patient’s encounters using:

    GET [base]/Encounter?patient=[id]

  2. A client SHOULD be capable of connecting to a server and fetching all of all of a patient’s encounters over a specified time period using:

    GET [base]/Encounter?patient=[id]&date=[date]{&date=[date]}


Goal

Supported Profiles: US Core Goal Profile

Search Criteria:

  1. A client SHOULD be capable of connecting to a server and fetching all of a patient’s goals using:

    GET [base]/Goal?patient=[id]

  2. A client SHOULD be capable of connecting to a server and fetching all of all of a patient’s goals over a specified time period using:

    GET [base]/Goal?patient=[id]&date=[date]{&date=[date]}


Immunization

Supported Profiles: US Core Immunization Profile

Search Criteria:

  1. A client SHOULD be capable of connecting to a server and fetching all immunizations for a patient using:

    GET [base]/Immunization?patient=[id]


Location

Supported Profiles: US Core Location Profile

Search Criteria:

  1. A client SHOULD be capable of connecting to a server and fetching a location by name using:

    GET [base]/Location?name=[string]

  2. A client SHOULD be capable of connecting to a server and fetching a location by address using:

    GET [base]/Location?address=[string]


Medication

Supported Profiles: US Core Medication Profile

The MedicationStatement and MedicationRequest resources can represent a medication, using an external reference to a Medication resource. If an external Medication Resource is used in a MedicationStatement or a MedicationRequest, then the READ and SEARCH Criteria SHOULD be supported.


MedicationStatement

Supported Profiles: US Core MedicationStatement Profile

Search Criteria:

The MedicationStatement resources can represent a medication using either a code or refer to the Medication resource. When referencing a Medication resource, the resource may be contained or an external resource. IF, an external reference to Medication is used, the server SHALL support the _include parameter for searching this element. The client application SHALL support all methods.

A client SHOULD be capable of connecting to a server and fetching all medications for a patient using both:

GET /MedicationStatement?patient=[id]

and

GET /MedicationStatement?patient=[id]&_include=MedicationStatement:medication


MedicationRequest

Supported Profiles: US Core MedicationRequest Profile

Search Criteria:

The MedicationRequest resources can represent a medication using either a code or refer to the Medication resource. When referencing a Medication resource, the resource may be contained or an external resource. If, an external reference to Medication is used, the server SHALL support the _include parameter for searching this element. The client application SHALL support all methods.

A client SHOULD be capable of connecting to a server and fetching all medications for a patient using both:

GET /MedicationRequest?patient=[id]

and

GET /MedicationRequest?patient=[id]&_include=MedicationRequest:medication


Observation

Supported Profiles:

  1. US Core Result Observation Profile

    Search Criteria:

    1. A client SHOULD be capable of connecting to a server and fetching all of a patient’s laboratory results queried by category using:

      GET [base]/Observation?patient=[id]&category=laboratory

    2. A client SHOULD be capable of connecting to a server and fetching all of a patient’s laboratory results queried by category code and date range using:

      GET [base]/Observation?patient=[id]&category=laboratory&date=[date]{&date=[date]}

    3. A client SHOULD be capable of connecting to a server and fetching all of a patient’s laboratory results queried by category and code using:

      GET [base]/Observation?patient=[id]&category=laboratory&code=[LOINC]

    4. A client SHOULD be capable of connecting to a server and fetching 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]}

  2. Vital Signs Profile

    Search Criteria

    1. A client SHOULD be capable of connecting to a server and fetching all of a patient’s vital signs that it supports using:

      GET [base]/Observation?patient=[id]&category=vital-signs

    2. A client SHOULD be capable of connecting to a server and fetching all of a patient’s vital signs queried by date range using:

      GET [base]/Observation?patient=[id]&category=vital-signs&date=[date]{&date=[date]}

    3. A client SHOULD be capable of connecting to a server and fetching 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,…}]

    4. A client SHOULD be capable of connecting to a server and fetching 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]}

  3. US Core Smoking Status Observation Profile

    Search Criteria:

    1. A client SHOULD be capable of connecting to a server and fetching a patient’s smoking status using:

      GET [base]/Observation?patient=[id]&code=72166-2


Organization

Supported Profiles: US Core Organization Profile

Search Criteria:

  1. A client SHOULD be capable of connecting to a server and fetching an organization by identifier using:

    `GET [base]/Organization?identifier=[system] [code]’
  2. A client SHOULD be capable of connecting to a server and fetching an organization by name using:

    GET [base]/Organization?name=[string]

  3. A client SHOULD be capable of connecting to a server and fetching an organization by address using:

    GET [base]/Organization?address=[string]


Practitioner

Supported Profiles: US Core Practitioner Profile

Search Criteria:

  1. A client SHOULD be capable of connecting to a server and fetching a practitioner by identifier using:

    GET [base]/Practitioner?identifier=[system]|[code]

  2. A client SHOULD be capable of connecting to a server and fetching a practitioner by name using:

    GET [base]/Practitioner?family=[string]&given=[string]


PractitionerRole

Supported Profiles: US Core PractitionerRole Profile

Search Criteria:

  1. A client SHOULD be capable of connecting to a server and fetching PractitionerRoles by identifier using:

    GET [base]/PractitionerRole?practitioner.identifier=[system]|[code]

  2. A client SHOULD be capable of connecting to a server and fetching a PractitionerRoles by name using:

    GET [base]/PractitionerRole?practitioner.family=[string]&given=[string]

  3. A client SHOULD be capable of connecting to a server and fetching a PractitionerRoles by specialty using:

    GET [base]/PractitionerRole?specialty=[system]|[code]]


Procedure

Supported Profiles: US Core Procedure Profile

Search Criteria:

  1. A client SHOULD be capable of connecting to a server and fetching a patient’s procedures using:

    GET/Procedure?patient=[id]

  2. A client SHOULD be capable of connecting to a server and fetching 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"?>
<CapabilityStatement xmlns="http://hl7.org/fhir">
  <id value="client"/>
  <meta>
    <versionId value="6"/>
    <lastUpdated value="2018-09-06T12:43:49.265Z"/>
  </meta>
  <text>
    <status value="additional"/>
    <div xmlns="http://www.w3.org/1999/xhtml">
      <ul>
        <li>FHIR Version: 3.0.1</li>
        <li>Supported formats: xml, json</li>
        <li>Published: 2017-12-22</li>
        <li>Published by: Health Level Seven International US Realm Steering Committee</li> </ul>
      <p>The Section describes the expected capabilities of the US Core Client which is responsible for creating and initiating the queries for information about an individual patient. The complete list of FHIR profiles, RESTful operations, and search parameters supported by US Core Servers are defined in the
        <a href="http://hl7.org/fhir/us/core/CapabilityStatement/server">Conformance requirements for the US Core Server section</a>. US Core Clients have the option of choosing from this list to access necessary data based on their local use cases and other contextual requirements.</p>
      <h4 id="behavior-1">Behavior</h4>
      <p>Description:</p>
      <p>The US Core Client
        <strong>SHOULD</strong>:</p>
      <ul>
        <li>Support fetching and querying of one or more US Core profile(s), using the supported RESTful interactions and search parameters declared in the US Core Server CapabilityStatement.</li> </ul>
      <p>security:</p>
      <p>The US Core Client
        <strong>SHALL</strong>:</p>
      <ul>
        <li>implement the
          <a href="security.html">security requirements</a>documented in the US Core IG.</li> </ul>
      <h4 id="resource--details-1">Resource Details:</h4>
      <p>
        <strong>Contents:</strong> </p>
      <ol>
        <li>
          <a href="#patient-1">Patient</a> </li>
        <li>
          <a href="#allergyintolerance-1">AllergyIntolerance</a> </li>
        <li>
          <a href="#careplan-1">CarePlan</a> </li>
        <li>
          <a href="#careteam-1">CareTeam</a> </li>
        <li>
          <a href="#condition-1">Condition</a> </li>
        <li>
          <a href="#device-1">Device</a> </li>
        <li>
          <a href="#diagnosticreport-1">DiagnosticReport</a> </li>
        <li>
          <a href="#documentreference-1">DocumentReference</a> </li>
        <li>
          <a href="#encounter-1">Encounter</a> </li>
        <li>
          <a href="#goal-1">Goal</a> </li>
        <li>
          <a href="#immunization-1">Immunization</a> </li>
        <li>
          <a href="#location-1">Location</a> </li>
        <li>
          <a href="#medication-1">Medication</a> </li>
        <li>
          <a href="#medicationstatement-1">MedicationStatement</a> </li>
        <li>
          <a href="#medicationrequest-1">MedicationRequest</a> </li>
        <li>
          <a href="#observation-1">Observation</a> </li>
        <li>
          <a href="#organization-1">Organization</a> </li>
        <li>
          <a href="#practitioner-1">Practitioner</a> </li>
        <li>
          <a href="#practitionerrole-1">PractitionerRole</a> </li>
        <li>
          <a href="#procedure-1">Procedure</a> </li> </ol>
      <hr/>
      <h4 id="patient-1" class="no_toc">Patient</h4>
      <p>Supported Profiles:
        <a href="http://hl7.org/fhir/us/core/StructureDefinition-us-core-patient.html">US Core Patient Profile</a> </p>
      <p>Search Criteria:</p>
      <ul>
        <li>
          <p>A client
            <strong>SHOULD</strong>be capable of connecting to a server and fetching a patient using:</p>
          <p>
            <code class="highlighter-rouge">GET [base]/Patient/[id]</code>.</p> </li>
        <li>
          <p>A client
            <strong>SHOULD</strong>be capable of connecting to a server and fetching a patient by identifier using</p>
          <p>
            <code class="highlighter-rouge">GET [base]/Patient?identifier=[system]|[code]</code> </p> </li> </ul>
      <ol>
        <li>A client
          <strong>SHOULD</strong>be capable of connecting to a server and fetching a patient by supporting at a minimum the following search parameters when at least 2 are present. To limit overly broad search results, a client search with gender should include family and given name search parameters.:
          <ul>
            <li>name</li>
            <li>gender</li>
            <li>
              <p>birthdate</p>
              <ul>
                <li>
                  <p>for example:</p>
                  <p>
                    <code class="highlighter-rouge">GET [base]/Patient?family=[name]&amp;?given=[name]&amp;gender=[gender]</code> </p> </li> </ul> </li> </ul> </li> </ol>
      <hr/>
      <h4 id="allergyintolerance-1" class="no_toc">AllergyIntolerance</h4>
      <p>Supported Profiles:
        <a href="http://hl7.org/fhir/us/core/StructureDefinition-us-core-allergyintolerance.html">US Core AllergyIntolerance Profile</a> </p>
      <p>Search Criteria:</p>
      <ol>
        <li>
          <p>A client
            <strong>SHOULD</strong>be capable of connecting to a server and fetching all patient&#8217;s allergies using:</p>
          <p>
            <code class="highlighter-rouge">GET [base]/AllergyIntolerance?patient=[id]</code> </p> </li> </ol>
      <hr/>
      <h4 id="careplan-1" class="no_toc">CarePlan</h4>
      <p>Supported Profiles:
        <a href="http://hl7.org/fhir/us/core/StructureDefinition-us-core-careplan.html">US Core CarePlan Profile</a> </p>
      <p>Search Criteria:</p>
      <ol>
        <li>
          <p>A client
            <strong>SHOULD</strong>be capable of connecting to a server and fetching all of a patient&#8217;s Assessment and Plan of Treatment information using:</p>
          <p>
            <code class="highlighter-rouge">GET [base]/CarePlan?patient=[id]&amp;category=assess-plan</code> </p> </li>
        <li>
          <p>A client
            <strong>SHOULD</strong>be capable of connecting to a server and fetching a patient&#8217;s Assessment and Plan of Treatment information over a specified time period using:</p>
          <p>
            <code class="highlighter-rouge">GET [base]/CarePlan?patient=[id]&amp;category=assess-plan&amp;date=[date]</code> </p> </li>
        <li>
          <p>A client
            <strong>SHOULD</strong>be capable of connecting to a server and fetching all of a patient&#8217;s active Assessment and Plan of Treatment information using</p>
          <p>
            <code class="highlighter-rouge">GET [base]/CarePlan?patient=[id]&amp;category=assess-plan&amp;status=active</code> </p> </li>
        <li>
          <p>A client
            <strong>SHOULD</strong>be capable of connecting to a server and fetching a patient&#8217;s active Assessment and Plan of Treatment information over a specified time period using</p>
          <p>
            <code class="highlighter-rouge">GET [base]/CarePlan?patient=[id]&amp;category=assess-plan&amp;status=active&amp;date=[date]</code> </p> </li> </ol>
      <hr/>
      <h4 id="careteam-1" class="no_toc">CareTeam</h4>
      <p>Supported Profiles:
        <a href="http://hl7.org/fhir/us/core/StructureDefinition-us-core-careteam.html">US Core CareTeam Profile</a> </p>
      <p>Search Criteria:</p>
      <ol>
        <li>
          <p>A client
            <strong>SHOULD</strong>be capable of connecting to a server and fetching a patient&#8217;s current care team members using:</p>
          <p>
            <code class="highlighter-rouge">GET [base]/CareTeam?patient=[id]&amp;status=active</code> </p> </li> </ol>
      <hr/>
      <h4 id="condition-1" class="no_toc">Condition</h4>
      <p>Supported Profiles:
        <a href="http://hl7.org/fhir/us/core/StructureDefinition-us-core-condition.html">US Core Condition Profile</a> </p>
      <p>Search Criteria:</p>
      <ol>
        <li>
          <p>A client
            <strong>SHOULD</strong>be capable of fetching all problems and health concerns for a patient, including current as well as historical problems and health concerns using:</p>
          <p>
            <code class="highlighter-rouge">GET [base]/Condition?patient=[id]</code> </p> </li>
        <li>
          <p>A client
            <strong>SHOULD</strong>be capable of connecting to a server and fetching all of a patient&#8217;s
            <em>active</em>problems and health concerns using:</p>
          <p>
            <code class="highlighter-rouge">GET [base]/Condition?patient=[id]&amp;clinicalstatus=active,recurrance,remission</code> </p> </li>
        <li>
          <p>A client
            <strong>SHOULD</strong>be capable of connecting to a server and fetching all of a patient&#8217;s problems
            <em>or</em>all of patient&#8217;s health concerns using:</p>
          <p>
            <code class="highlighter-rouge">GET [base]/Condition?patient=[id]&amp;category=[problem|health-concern]</code> </p> </li> </ol>
      <hr/>
      <h4 id="device-1" class="no_toc">Device</h4>
      <p>Supported Profiles:
        <a href="http://hl7.org/fhir/us/core/StructureDefinition-us-core-device.html">US Core Device Profile</a> </p>
      <p>Search Criteria:</p>
      <ol>
        <li>
          <p>A client
            <strong>SHOULD</strong>be capable of connecting to a server and fetching all Unique device identifier(s)(UDI) for a patient&#8217;s implanted device(s):</p>
          <p>
            <code class="highlighter-rouge">GET [base]/Device?patient=[id]</code> </p> </li> </ol>
      <hr/>
      <h4 id="diagnosticreport-1" class="no_toc">DiagnosticReport</h4>
      <p>Supported Profiles:
        <a href="http://hl7.org/fhir/us/core/StructureDefinition-us-core-diagnosticreport.html">US Core DiagnosticReport Profile</a> </p>
      <p>Search Criteria:</p>
      <ol>
        <li>
          <p>A client
            <strong>SHOULD</strong>be capable of connecting to a server and fetching all of a patient&#8217;s laboratory diagnostic reports queried by category using:</p>
          <p>
            <code class="highlighter-rouge">GET [base]/DiagnosticReport?patient=[id]&amp;category=LAB</code> </p> </li>
        <li>
          <p>A client
            <strong>SHOULD</strong>be capable of connecting to a server and fetching all of a patient&#8217;s laboratory diagnostic reports queried by category code and date range using:</p>
          <p>
            <code class="highlighter-rouge">GET [base]/DiagnosticReport?patient=[id]&amp;category=LAB&amp;date=[date]{&amp;date=[date]}</code> </p> </li>
        <li>
          <p>A client
            <strong>SHOULD</strong>be capable of connecting to a server and fetching all of a patient&#8217;s laboratory diagnostic reports queried by category and code using:</p>
          <p>
            <code class="highlighter-rouge">GET [base]/DiagnosticReport?patient=[id]&amp;category=LAB&amp;code=[LOINC]</code> </p> </li>
        <li>
          <p>A client
            <strong>SHOULD</strong>be capable of connecting to a server and fetching all of a patient&#8217;s laboratory diagnostic reports queried by category and one or more codes and date range using:</p>
          <p>
            <code class="highlighter-rouge">GET [base]/DiagnosticReport?patient=[id]&amp;category=LAB&amp;code=[LOINC1{,LOINC2,LOINC3,&#8230;}]&amp;date=[date]{&amp;date=[date]}</code> </p> </li> </ol>
      <hr/>
      <h4 id="documentreference-1" class="no_toc">DocumentReference</h4>
      <p>Supported Profiles:
        <a href="http://hl7.org/fhir/us/core/StructureDefinition-us-core-documentreference.html">US Core DocumentReference Profile</a> </p>
      <p>Search Criteria:</p>
      <ol>
        <li>
          <p>A client
            <strong>SHOULD</strong>be capable of connecting to a server and fetching all of a patient&#8217;s DocumentReferences using:</p>
          <p>
            <code class="highlighter-rouge">GET [base]/DocumentReference?patient=[id]</code> </p> </li>
        <li>
          <p>A client
            <strong>SHOULD</strong>be capable of connecting to a server to execute the
            <a href="OperationDefinition-docref.html">$docref</a>operation:</p>
          <p>
            <code class="highlighter-rouge">GET [base]/DocumentReference/$docref?patient=[id]</code> </p> </li>
        <li>
          <p>A client
            <strong>SHOULD</strong>be capable of connecting to a server and fetching all of a patient&#8217;s DocumentReferences for a given time period and document type:</p>
          <p>
            <code class="highlighter-rouge">GET [base]/DocumentReference?patient=[id]&amp;type=[type]&amp;period=[date]{&amp;date=[date]}</code> </p> </li> </ol>
      <hr/>
      <h4 id="encounter-1" class="no_toc">Encounter</h4>
      <p>Supported Profiles:
        <a href="http://hl7.org/fhir/us/core/StructureDefinition-us-core-encounter.html">US Core Encounter Profile</a> </p>
      <p>Search Criteria:</p>
      <ol>
        <li>
          <p>A client
            <strong>SHOULD</strong>be capable of connecting to a server and fetching all of a patient&#8217;s encounters using:</p>
          <p>
            <code class="highlighter-rouge">GET [base]/Encounter?patient=[id]</code> </p> </li>
        <li>
          <p>A client
            <strong>SHOULD</strong>be capable of connecting to a server and fetching all of all of a patient&#8217;s encounters over a specified time period using:</p>
          <p>
            <code class="highlighter-rouge">GET [base]/Encounter?patient=[id]&amp;date=[date]{&amp;date=[date]}</code> </p> </li> </ol>
      <hr/>
      <h4 id="goal-1" class="no_toc">Goal</h4>
      <p>Supported Profiles:
        <a href="http://hl7.org/fhir/us/core/StructureDefinition-us-core-goal.html">US Core Goal Profile</a> </p>
      <p>Search Criteria:</p>
      <ol>
        <li>
          <p>A client
            <strong>SHOULD</strong>be capable of connecting to a server and fetching all of a patient&#8217;s goals using:</p>
          <p>
            <code class="highlighter-rouge">GET [base]/Goal?patient=[id]</code> </p> </li>
        <li>
          <p>A client
            <strong>SHOULD</strong>be capable of connecting to a server and fetching all of all of a patient&#8217;s goals over a specified time period using:</p>
          <p>
            <code class="highlighter-rouge">GET [base]/Goal?patient=[id]&amp;date=[date]{&amp;date=[date]}</code> </p> </li> </ol>
      <hr/>
      <h4 id="immunization-1" class="no_toc">Immunization</h4>
      <p>Supported Profiles:
        <a href="http://hl7.org/fhir/us/core/StructureDefinition-us-core-immunization.html">US Core Immunization Profile</a> </p>
      <p>Search Criteria:</p>
      <ol>
        <li>
          <p>A client
            <strong>SHOULD</strong>be capable of connecting to a server and fetching all immunizations for a patient using:</p>
          <p>
            <code class="highlighter-rouge">GET [base]/Immunization?patient=[id]</code> </p> </li> </ol>
      <hr/>
      <h4 id="location-1" class="no_toc">Location</h4>
      <p>Supported Profiles:
        <a href="http://hl7.org/fhir/us/core/StructureDefinition-us-core-location.html">US Core Location Profile</a> </p>
      <p>Search Criteria:</p>
      <ol>
        <li>
          <p>A client
            <strong>SHOULD</strong>be capable of connecting to a server and fetching a location by name using:</p>
          <p>
            <code class="highlighter-rouge">GET [base]/Location?name=[string]</code> </p> </li>
        <li>
          <p>A client
            <strong>SHOULD</strong>be capable of connecting to a server and fetching a location by address using:</p>
          <p>
            <code class="highlighter-rouge">GET [base]/Location?address=[string]</code> </p> </li> </ol>
      <hr/>
      <h4 id="medication-1" class="no_toc">Medication</h4>
      <p>Supported Profiles:
        <a href="http://hl7.org/fhir/us/core/StructureDefinition-us-core-medication.html">US Core Medication Profile</a> </p>
      <p>The MedicationStatement and MedicationRequest resources can represent a medication, using an external reference to a Medication resource. If an external Medication Resource is used in a MedicationStatement or a MedicationRequest, then the READ and SEARCH Criteria SHOULD be supported.</p>
      <hr/>
      <h4 id="medicationstatement-1" class="no_toc">MedicationStatement</h4>
      <p>Supported Profiles:
        <a href="http://hl7.org/fhir/us/core/StructureDefinition-us-core-medicationstatement.html">US Core MedicationStatement Profile</a> </p>
      <p>Search Criteria:</p>
      <p>The MedicationStatement resources can represent a medication using either a code or refer to the Medication resource. When referencing a Medication resource, the resource may be
        <a href="http://hl7.org/fhir/STU3/references.html#contained">contained</a>or an external resource. IF, an external reference to Medication is used, the server
        <strong>SHALL</strong>support the
        <a href="http://hl7.org/fhir/STU3/references.html#include">
          <code class="highlighter-rouge">_include</code> </a>parameter for searching this element. The client application
        <strong>SHALL</strong>support all methods.</p>
      <p>A client
        <strong>SHOULD</strong>be capable of connecting to a server and fetching all medications for a patient using both:</p>
      <p>
        <code class="highlighter-rouge">GET /MedicationStatement?patient=[id]</code> </p>
      <p>and</p>
      <p>
        <code class="highlighter-rouge">GET /MedicationStatement?patient=[id]&amp;_include=MedicationStatement:medication</code> </p>
      <hr/>
      <h4 id="medicationrequest-1" class="no_toc">MedicationRequest</h4>
      <p>Supported Profiles:
        <a href="http://hl7.org/fhir/us/core/StructureDefinition-us-core-medicationrequest.html">US Core MedicationRequest Profile</a> </p>
      <p>Search Criteria:</p>
      <p>The MedicationRequest resources can represent a medication using either a code or refer to the Medication resource. When referencing a Medication resource, the resource may be
        <a href="http://hl7.org/fhir/STU3/references.html#contained">contained</a>or an external resource. If, an external reference to Medication is used, the server
        <strong>SHALL</strong>support the
        <a href="http://hl7.org/fhir/STU3/references.html#include">
          <code class="highlighter-rouge">_include</code> </a>parameter for searching this element. The client application
        <strong>SHALL</strong>support all methods.</p>
      <p>A client
        <strong>SHOULD</strong>be capable of connecting to a server and fetching all medications for a patient using both:</p>
      <p>
        <code class="highlighter-rouge">GET /MedicationRequest?patient=[id]</code> </p>
      <p>and</p>
      <p>
        <code class="highlighter-rouge">GET /MedicationRequest?patient=[id]&amp;_include=MedicationRequest:medication</code> </p>
      <hr/>
      <h4 id="observation-1" class="no_toc">Observation</h4>
      <p>Supported Profiles:</p>
      <ol>
        <li>
          <p>
            <a href="http://hl7.org/fhir/us/core/StructureDefinition-us-core-observationresults.html">US Core Result Observation Profile</a> </p>
          <p>Search Criteria:</p>
          <ol>
            <li>
              <p>A client
                <strong>SHOULD</strong>be capable of connecting to a server and fetching all of a patient&#8217;s laboratory results queried by category using:</p>
              <p>
                <code class="highlighter-rouge">GET [base]/Observation?patient=[id]&amp;category=laboratory</code> </p> </li>
            <li>
              <p>A client
                <strong>SHOULD</strong>be capable of connecting to a server and fetching all of a patient&#8217;s laboratory results queried by category code and date range using:</p>
              <p>
                <code class="highlighter-rouge">GET [base]/Observation?patient=[id]&amp;category=laboratory&amp;date=[date]{&amp;date=[date]}</code> </p> </li>
            <li>
              <p>A client
                <strong>SHOULD</strong>be capable of connecting to a server and fetching all of a patient&#8217;s laboratory results queried by category and code using:</p>
              <p>
                <code class="highlighter-rouge">GET [base]/Observation?patient=[id]&amp;category=laboratory&amp;code=[LOINC]</code> </p> </li>
            <li>
              <p>A client
                <strong>SHOULD</strong>be capable of connecting to a server and fetching all of a patient&#8217;s laboratory results queried by category and one or more codes and date range using:</p>
              <p>
                <code class="highlighter-rouge">GET [base]/Observation?patient=[id]&amp;category=laboratory&amp;code=[LOINC1{,LOINC2,LOINC3,...}]&amp;date=[date]{&amp;date=[date]}</code> </p> </li> </ol> </li>
        <li>
          <p>
            <a href="http://hl7.org/fhir/STU3/vitalsigns.html">Vital Signs Profile</a> </p>
          <p>Search Criteria</p>
          <ol>
            <li>
              <p>A client
                <strong>SHOULD</strong>be capable of connecting to a server and fetching all of a patient&#8217;s vital signs that it supports using:</p>
              <p>
                <code class="highlighter-rouge">GET [base]/Observation?patient=[id]&amp;category=vital-signs</code> </p> </li>
            <li>
              <p>A client
                <strong>SHOULD</strong>be capable of connecting to a server and fetching all of a patient&#8217;s vital signs queried by date range using:</p>
              <p>
                <code class="highlighter-rouge">GET [base]/Observation?patient=[id]&amp;category=vital-signs&amp;date=[date]{&amp;date=[date]}</code> </p> </li>
            <li>
              <p>A client
                <strong>SHOULD</strong>be capable of connecting to a server and fetching any of a patient&#8217;s vital signs queried by one or more of the codes listed below using:</p>
              <p>
                <code class="highlighter-rouge">GET [base]/Observation?patient=[id]&amp;code[vital sign LOINC{,LOINC2,LOINC3,&#8230;}]</code> </p> </li>
            <li>
              <p>A client
                <strong>SHOULD</strong>be capable of connecting to a server and fetching any of a patient&#8217;s vital signs queried by one or more of the codes listed below and date range using:</p>
              <p>
                <code class="highlighter-rouge">GET [base]/Observation?patient=[id]&amp;code=[LOINC{,LOINC2&#8230;}]vital-signs&amp;date=[date]{&amp;date=[date]}</code> </p> </li> </ol> </li>
        <li>
          <p>
            <a href="http://hl7.org/fhir/us/core/StructureDefinition-us-core-smokingstatus.html">US Core Smoking Status Observation Profile</a> </p>
          <p>Search Criteria:</p>
          <ol>
            <li>
              <p>A client
                <strong>SHOULD</strong>be capable of connecting to a server and fetching a patient&#8217;s smoking status using:</p>
              <p>
                <code class="highlighter-rouge">GET [base]/Observation?patient=[id]&amp;code=72166-2</code> </p> </li> </ol> </li> </ol>
      <hr/>
      <h4 id="organization-1" class="no_toc">Organization</h4>
      <p>Supported Profiles:
        <a href="http://hl7.org/fhir/us/core/StructureDefinition-us-core-organization.html">US Core Organization Profile</a> </p>
      <p>Search Criteria:</p>
      <ol>
        <li>
          <p>A client
            <strong>SHOULD</strong>be capable of connecting to a server and fetching an organization by identifier using:</p>
          <table>
            <tbody>
              <tr>
                <td>`GET [base]/Organization?identifier=[system]</td>
                <td>[code]&#8217;</td> </tr> </tbody> </table> </li>
        <li>
          <p>A client
            <strong>SHOULD</strong>be capable of connecting to a server and fetching an organization by name using:</p>
          <p>
            <code class="highlighter-rouge">GET [base]/Organization?name=[string]</code> </p> </li>
        <li>
          <p>A client
            <strong>SHOULD</strong>be capable of connecting to a server and fetching an organization by address using:</p>
          <p>
            <code class="highlighter-rouge">GET [base]/Organization?address=[string]</code> </p> </li> </ol>
      <hr/>
      <h4 id="practitioner-1" class="no_toc">Practitioner</h4>
      <p>Supported Profiles:
        <a href="http://hl7.org/fhir/us/core/StructureDefinition-us-core-practitioner.html">US Core Practitioner Profile</a> </p>
      <p>Search Criteria:</p>
      <ol>
        <li>
          <p>A client
            <strong>SHOULD</strong>be capable of connecting to a server and fetching a practitioner by identifier using:</p>
          <p>
            <code class="highlighter-rouge">GET [base]/Practitioner?identifier=[system]|[code]</code> </p> </li>
        <li>
          <p>A client
            <strong>SHOULD</strong>be capable of connecting to a server and fetching a practitioner by name using:</p>
          <p>
            <code class="highlighter-rouge">GET [base]/Practitioner?family=[string]&amp;given=[string]</code> </p> </li> </ol>
      <hr/>
      <h4 id="practitionerrole-1" class="no_toc">PractitionerRole</h4>
      <p>Supported Profiles:
        <a href="http://hl7.org/fhir/us/core/StructureDefinition-us-core-practitionerrole.html">US Core PractitionerRole Profile</a> </p>
      <p>Search Criteria:</p>
      <ol>
        <li>
          <p>A client
            <strong>SHOULD</strong>be capable of connecting to a server and fetching PractitionerRoles by identifier using:</p>
          <p>
            <code class="highlighter-rouge">GET [base]/PractitionerRole?practitioner.identifier=[system]|[code]</code> </p> </li>
        <li>
          <p>A client
            <strong>SHOULD</strong>be capable of connecting to a server and fetching a PractitionerRoles by name using:</p>
          <p>
            <code class="highlighter-rouge">GET [base]/PractitionerRole?practitioner.family=[string]&amp;given=[string]</code> </p> </li>
        <li>
          <p>A client
            <strong>SHOULD</strong>be capable of connecting to a server and fetching a PractitionerRoles by specialty using:</p>
          <p>
            <code class="highlighter-rouge">GET [base]/PractitionerRole?specialty=[system]|[code]]</code> </p> </li> </ol>
      <hr/>
      <h4 id="procedure-1" class="no_toc">Procedure</h4>
      <p>Supported Profiles:
        <a href="http://hl7.org/fhir/us/core/StructureDefinition-us-core-procedure.html">US Core Procedure Profile</a> </p>
      <p>Search Criteria:</p>
      <ol>
        <li>
          <p>A client
            <strong>SHOULD</strong>be capable of connecting to a server and fetching a patient&#8217;s procedures using:</p>
          <p>
            <code class="highlighter-rouge">GET/Procedure?patient=[id]</code> </p> </li>
        <li>
          <p>A client
            <strong>SHOULD</strong>be capable of connecting to a server and fetching all of a patient&#8217;s procedures over a specified time period using:</p>
          <p>
            <code class="highlighter-rouge">GET /Procedure?patient=[id]&amp;date=[date]{&amp;date=[date]}</code> </p> </li> </ol>
      <p/>
      <p/>
      <p/> </div>
  </text>
  <url value="http://hl7.org/fhir/us/core/CapabilityStatement/client"/>
  <version value="1.1.0"/>
  <name value="US Core Client"/>
  <status value="draft"/>
  <date value="2017-03-20T00:00:00+00:00"/>
  <publisher value="HL7 US Realm Steering Committee"/>
  <contact>
    <telecom>
      <system value="other"/>
      <value value="http://www.hl7.org/SpecialCommittees/usrealm/index.cfm"/>
    </telecom>
  </contact>
  <description value="This profile defines the expected capabilities of the US Core Client conforming to the US Core IG."/>
  <jurisdiction>
    <coding>
      <system value="urn:iso:std:iso:3166"/>
      <code value="US"/>
      <display value="United States of America"/>
    </coding>
  </jurisdiction>
  <kind value="requirements"/>
  <fhirVersion value="3.0.1"/>
  <format value="xml"/>
  <format value="json"/>
  <rest>
    <mode value="client"/>
    <resource>
      <type value="Patient"/>
      <interaction>
        <extension url="http://hl7.org/fhir/StructureDefinition/capabilitystatement-expectation">
          <valueCode value="SHOULD"/>
        </extension>
        <code value="search-type"/>
        <documentation value="Allows discovery of existing US Core patient resources using different search criteria"/>
      </interaction>
      <interaction>
        <extension url="http://hl7.org/fhir/StructureDefinition/capabilitystatement-expectation">
          <valueCode value="SHOULD"/>
        </extension>
        <code value="read"/>
        <documentation value="Allows retrieval of a specific US Core patients by id"/>
      </interaction>
      <interaction>
        <extension url="http://hl7.org/fhir/StructureDefinition/capabilitystatement-expectation">
          <valueCode value="SHOULD"/>
        </extension>
        <code value="history-instance"/>
        <documentation value="Allows review of changes to US Core patient instance over time"/>
      </interaction>
      <interaction>
        <extension url="http://hl7.org/fhir/StructureDefinition/capabilitystatement-expectation">
          <valueCode value="SHOULD"/>
        </extension>
        <code value="vread"/>
        <documentation value="Allows retrieval of a historical version of a US Core patient instance"/>
      </interaction>
    </resource>
    <resource>
      <type value="AllergyIntolerance"/>
      <interaction>
        <extension url="http://hl7.org/fhir/StructureDefinition/capabilitystatement-expectation">
          <valueCode value="SHOULD"/>
        </extension>
        <code value="search-type"/>
        <documentation value="Allows discovery of existing US Core AllergyIntolerance resources using different search criteria"/>
      </interaction>
      <interaction>
        <extension url="http://hl7.org/fhir/StructureDefinition/capabilitystatement-expectation">
          <valueCode value="SHOULD"/>
        </extension>
        <code value="read"/>
        <documentation value="Allows retrieval of a specific US Core AllergyIntolerance by id"/>
      </interaction>
      <interaction>
        <extension url="http://hl7.org/fhir/StructureDefinition/capabilitystatement-expectation">
          <valueCode value="SHOULD"/>
        </extension>
        <code value="history-instance"/>
        <documentation value="Allows review of changes to US Core AllergyIntolerance instance over time"/>
      </interaction>
      <interaction>
        <extension url="http://hl7.org/fhir/StructureDefinition/capabilitystatement-expectation">
          <valueCode value="SHOULD"/>
        </extension>
        <code value="vread"/>
        <documentation value="Allows retrieval of a historical version of a US Core AllergyIntolerance instance"/>
      </interaction>
    </resource>
    <resource>
      <type value="CarePlan"/>
      <interaction>
        <extension url="http://hl7.org/fhir/StructureDefinition/capabilitystatement-expectation">
          <valueCode value="SHOULD"/>
        </extension>
        <code value="search-type"/>
        <documentation value="Allows discovery of existing US Core careplan resources using different search criteria"/>
      </interaction>
      <interaction>
        <extension url="http://hl7.org/fhir/StructureDefinition/capabilitystatement-expectation">
          <valueCode value="SHOULD"/>
        </extension>
        <code value="read"/>
        <documentation value="Allows retrieval of a specific US Core careplan by id"/>
      </interaction>
      <interaction>
        <extension url="http://hl7.org/fhir/StructureDefinition/capabilitystatement-expectation">
          <valueCode value="SHOULD"/>
        </extension>
        <code value="history-instance"/>
        <documentation value="Allows review of changes to US Core careplan instance over time"/>
      </interaction>
      <interaction>
        <extension url="http://hl7.org/fhir/StructureDefinition/capabilitystatement-expectation">
          <valueCode value="SHOULD"/>
        </extension>
        <code value="vread"/>
        <documentation value="Allows retrieval of a historical version of a US Core careplan instance"/>
      </interaction>
    </resource>
    <resource>
      <type value="CareTeam"/>
      <interaction>
        <extension url="http://hl7.org/fhir/StructureDefinition/capabilitystatement-expectation">
          <valueCode value="SHOULD"/>
        </extension>
        <code value="search-type"/>
        <documentation value="Allows discovery of existing US Core careteam resources using different search criteria"/>
      </interaction>
      <interaction>
        <extension url="http://hl7.org/fhir/StructureDefinition/capabilitystatement-expectation">
          <valueCode value="SHOULD"/>
        </extension>
        <code value="read"/>
        <documentation value="Allows retrieval of a specific US Core careteam by id"/>
      </interaction>
      <interaction>
        <extension url="http://hl7.org/fhir/StructureDefinition/capabilitystatement-expectation">
          <valueCode value="SHOULD"/>
        </extension>
        <code value="history-instance"/>
        <documentation value="Allows review of changes to US Core careteam instance over time"/>
      </interaction>
      <interaction>
        <extension url="http://hl7.org/fhir/StructureDefinition/capabilitystatement-expectation">
          <valueCode value="SHOULD"/>
        </extension>
        <code value="vread"/>
        <documentation value="Allows retrieval of a historical version of a US Core careteam instance"/>
      </interaction>
    </resource>
    <resource>
      <type value="Condition"/>
      <interaction>
        <extension url="http://hl7.org/fhir/StructureDefinition/capabilitystatement-expectation">
          <valueCode value="SHOULD"/>
        </extension>
        <code value="search-type"/>
        <documentation value="Allows discovery of existing US Core condition resources using different search criteria"/>
      </interaction>
      <interaction>
        <extension url="http://hl7.org/fhir/StructureDefinition/capabilitystatement-expectation">
          <valueCode value="SHOULD"/>
        </extension>
        <code value="read"/>
        <documentation value="Allows retrieval of a specific US Core condition by id"/>
      </interaction>
      <interaction>
        <extension url="http://hl7.org/fhir/StructureDefinition/capabilitystatement-expectation">
          <valueCode value="SHOULD"/>
        </extension>
        <code value="history-instance"/>
        <documentation value="Allows review of changes to US Core condition instance over time"/>
      </interaction>
      <interaction>
        <extension url="http://hl7.org/fhir/StructureDefinition/capabilitystatement-expectation">
          <valueCode value="SHOULD"/>
        </extension>
        <code value="vread"/>
        <documentation value="Allows retrieval of a historical version of a US Core condition instance"/>
      </interaction>
    </resource>
    <resource>
      <type value="Device"/>
      <interaction>
        <extension url="http://hl7.org/fhir/StructureDefinition/capabilitystatement-expectation">
          <valueCode value="SHOULD"/>
        </extension>
        <code value="search-type"/>
        <documentation value="Allows discovery of existing US Core device resources using different search criteria"/>
      </interaction>
      <interaction>
        <extension url="http://hl7.org/fhir/StructureDefinition/capabilitystatement-expectation">
          <valueCode value="SHOULD"/>
        </extension>
        <code value="read"/>
        <documentation value="Allows retrieval of a specific US Core device by id"/>
      </interaction>
      <interaction>
        <extension url="http://hl7.org/fhir/StructureDefinition/capabilitystatement-expectation">
          <valueCode value="SHOULD"/>
        </extension>
        <code value="history-instance"/>
        <documentation value="Allows review of changes to US Core device instance over time"/>
      </interaction>
      <interaction>
        <extension url="http://hl7.org/fhir/StructureDefinition/capabilitystatement-expectation">
          <valueCode value="SHOULD"/>
        </extension>
        <code value="vread"/>
        <documentation value="Allows retrieval of a historical version of a US Core device instance"/>
      </interaction>
    </resource>
    <resource>
      <type value="DocumentReference"/>
      <interaction>
        <extension url="http://hl7.org/fhir/StructureDefinition/capabilitystatement-expectation">
          <valueCode value="SHOULD"/>
        </extension>
        <code value="search-type"/>
        <documentation value="Allows discovery of existing US Core DocumentReference resources using different search criteria"/>
      </interaction>
      <interaction>
        <extension url="http://hl7.org/fhir/StructureDefinition/capabilitystatement-expectation">
          <valueCode value="SHOULD"/>
        </extension>
        <code value="read"/>
        <documentation value="Allows retrieval of a specific US Core DocumentReference by id"/>
      </interaction>
      <interaction>
        <extension url="http://hl7.org/fhir/StructureDefinition/capabilitystatement-expectation">
          <valueCode value="SHOULD"/>
        </extension>
        <code value="history-instance"/>
        <documentation value="Allows review of changes to US Core DocumentReference instance over time"/>
      </interaction>
      <interaction>
        <extension url="http://hl7.org/fhir/StructureDefinition/capabilitystatement-expectation">
          <valueCode value="SHOULD"/>
        </extension>
        <code value="vread"/>
        <documentation value="Allows retrieval of a historical version of a US Core DocumentReference instance"/>
      </interaction>
    </resource>
    <resource>
      <type value="Encounter"/>
      <interaction>
        <extension url="http://hl7.org/fhir/StructureDefinition/capabilitystatement-expectation">
          <valueCode value="SHOULD"/>
        </extension>
        <code value="search-type"/>
        <documentation value="Allows discovery of existing US Core Encounter resources using different search criteria"/>
      </interaction>
      <interaction>
        <extension url="http://hl7.org/fhir/StructureDefinition/capabilitystatement-expectation">
          <valueCode value="SHOULD"/>
        </extension>
        <code value="read"/>
        <documentation value="Allows retrieval of a specific US Core Encounter by id"/>
      </interaction>
      <interaction>
        <extension url="http://hl7.org/fhir/StructureDefinition/capabilitystatement-expectation">
          <valueCode value="SHOULD"/>
        </extension>
        <code value="history-instance"/>
        <documentation value="Allows review of changes to US Core Encounter instance over time"/>
      </interaction>
      <interaction>
        <extension url="http://hl7.org/fhir/StructureDefinition/capabilitystatement-expectation">
          <valueCode value="SHOULD"/>
        </extension>
        <code value="vread"/>
        <documentation value="Allows retrieval of a historical version of a US Core Encounter instance"/>
      </interaction>
    </resource>
    <resource>
      <type value="Goal"/>
      <interaction>
        <extension url="http://hl7.org/fhir/StructureDefinition/capabilitystatement-expectation">
          <valueCode value="SHOULD"/>
        </extension>
        <code value="search-type"/>
        <documentation value="Allows discovery of existing US Core goal resources using different search criteria"/>
      </interaction>
      <interaction>
        <extension url="http://hl7.org/fhir/StructureDefinition/capabilitystatement-expectation">
          <valueCode value="SHOULD"/>
        </extension>
        <code value="read"/>
        <documentation value="Allows retrieval of a specific US Core goal by id"/>
      </interaction>
      <interaction>
        <extension url="http://hl7.org/fhir/StructureDefinition/capabilitystatement-expectation">
          <valueCode value="SHOULD"/>
        </extension>
        <code value="history-instance"/>
        <documentation value="Allows review of changes to US Core goal instance over time"/>
      </interaction>
      <interaction>
        <extension url="http://hl7.org/fhir/StructureDefinition/capabilitystatement-expectation">
          <valueCode value="SHOULD"/>
        </extension>
        <code value="vread"/>
        <documentation value="Allows retrieval of a historical version of a US Core goal instance"/>
      </interaction>
    </resource>
    <resource>
      <type value="Immunization"/>
      <interaction>
        <extension url="http://hl7.org/fhir/StructureDefinition/capabilitystatement-expectation">
          <valueCode value="SHOULD"/>
        </extension>
        <code value="search-type"/>
        <documentation value="Allows discovery of existing US Core immunization resources using different search criteria"/>
      </interaction>
      <interaction>
        <extension url="http://hl7.org/fhir/StructureDefinition/capabilitystatement-expectation">
          <valueCode value="SHOULD"/>
        </extension>
        <code value="read"/>
        <documentation value="Allows retrieval of a specific US Core immunization by id"/>
      </interaction>
      <interaction>
        <extension url="http://hl7.org/fhir/StructureDefinition/capabilitystatement-expectation">
          <valueCode value="SHOULD"/>
        </extension>
        <code value="history-instance"/>
        <documentation value="Allows review of changes to US Core immunization instance over time"/>
      </interaction>
      <interaction>
        <extension url="http://hl7.org/fhir/StructureDefinition/capabilitystatement-expectation">
          <valueCode value="SHOULD"/>
        </extension>
        <code value="vread"/>
        <documentation value="Allows retrieval of a historical version of a US Core immunization instance"/>
      </interaction>
    </resource>
    <resource>
      <type value="DiagnosticReport"/>
      <interaction>
        <extension url="http://hl7.org/fhir/StructureDefinition/capabilitystatement-expectation">
          <valueCode value="SHOULD"/>
        </extension>
        <code value="search-type"/>
        <documentation value="Allows discovery of existing US Core diagnosticreport resources using different search criteria"/>
      </interaction>
      <interaction>
        <extension url="http://hl7.org/fhir/StructureDefinition/capabilitystatement-expectation">
          <valueCode value="SHOULD"/>
        </extension>
        <code value="read"/>
        <documentation value="Allows retrieval of a specific US Core diagnosticreport by id"/>
      </interaction>
      <interaction>
        <extension url="http://hl7.org/fhir/StructureDefinition/capabilitystatement-expectation">
          <valueCode value="SHOULD"/>
        </extension>
        <code value="history-instance"/>
        <documentation value="Allows review of changes to US Core diagnosticreport instance over time"/>
      </interaction>
      <interaction>
        <extension url="http://hl7.org/fhir/StructureDefinition/capabilitystatement-expectation">
          <valueCode value="SHOULD"/>
        </extension>
        <code value="vread"/>
        <documentation value="Allows retrieval of a historical version of a US Core diagnosticreport instance"/>
      </interaction>
    </resource>
    <resource>
      <type value="Observation"/>
      <interaction>
        <extension url="http://hl7.org/fhir/StructureDefinition/capabilitystatement-expectation">
          <valueCode value="SHOULD"/>
        </extension>
        <code value="search-type"/>
        <documentation value="Allows discovery of existing US Core resultobs resources using different search criteria"/>
      </interaction>
      <interaction>
        <extension url="http://hl7.org/fhir/StructureDefinition/capabilitystatement-expectation">
          <valueCode value="SHOULD"/>
        </extension>
        <code value="read"/>
        <documentation value="Allows retrieval of a specific US Core resultobs by id"/>
      </interaction>
      <interaction>
        <extension url="http://hl7.org/fhir/StructureDefinition/capabilitystatement-expectation">
          <valueCode value="SHOULD"/>
        </extension>
        <code value="history-instance"/>
        <documentation value="Allows review of changes to US Core resultobs instance over time"/>
      </interaction>
      <interaction>
        <extension url="http://hl7.org/fhir/StructureDefinition/capabilitystatement-expectation">
          <valueCode value="SHOULD"/>
        </extension>
        <code value="vread"/>
        <documentation value="Allows retrieval of a historical version of a US Core resultobs instance"/>
      </interaction>
    </resource>
    <resource>
      <type value="Location"/>
      <interaction>
        <extension url="http://hl7.org/fhir/StructureDefinition/capabilitystatement-expectation">
          <valueCode value="SHOULD"/>
        </extension>
        <code value="search-type"/>
        <documentation value="Allows discovery of existing US Core location resources using different search criteria."/>
      </interaction>
      <interaction>
        <extension url="http://hl7.org/fhir/StructureDefinition/capabilitystatement-expectation">
          <valueCode value="SHOULD"/>
        </extension>
        <code value="read"/>
        <documentation value="Allows retrieval of a historical version of a US Core location instance"/>
      </interaction>
      <interaction>
        <extension url="http://hl7.org/fhir/StructureDefinition/capabilitystatement-expectation">
          <valueCode value="SHOULD"/>
        </extension>
        <code value="history-instance"/>
        <documentation value="Allows review of changes to US Core Medication instance over time"/>
      </interaction>
      <interaction>
        <extension url="http://hl7.org/fhir/StructureDefinition/capabilitystatement-expectation">
          <valueCode value="SHOULD"/>
        </extension>
        <code value="vread"/>
        <documentation value="Allows retrieval of a historical version of a US Core Medication instance"/>
      </interaction>
    </resource>
    <resource>
      <type value="Medication"/>
      <interaction>
        <extension url="http://hl7.org/fhir/StructureDefinition/capabilitystatement-expectation">
          <valueCode value="SHOULD"/>
        </extension>
        <code value="search-type"/>
        <documentation value="IF the Medication Resource is used in a MedicationStatement or a MedicationRequest. Allows discovery of existing US Core Medication resources using different search criteria."/>
      </interaction>
      <interaction>
        <extension url="http://hl7.org/fhir/StructureDefinition/capabilitystatement-expectation">
          <valueCode value="SHOULD"/>
        </extension>
        <code value="read"/>
        <documentation value="IF the Medication Resource is used in a MedicationStatement or a MedicationRequest. Allows retrieval of a specific US Core Medication by id"/>
      </interaction>
      <interaction>
        <extension url="http://hl7.org/fhir/StructureDefinition/capabilitystatement-expectation">
          <valueCode value="SHOULD"/>
        </extension>
        <code value="history-instance"/>
        <documentation value="Allows review of changes to US Core Medication instance over time"/>
      </interaction>
      <interaction>
        <extension url="http://hl7.org/fhir/StructureDefinition/capabilitystatement-expectation">
          <valueCode value="SHOULD"/>
        </extension>
        <code value="vread"/>
        <documentation value="Allows retrieval of a historical version of a US Core Medication instance"/>
      </interaction>
    </resource>
    <resource>
      <type value="MedicationStatement"/>
      <interaction>
        <extension url="http://hl7.org/fhir/StructureDefinition/capabilitystatement-expectation">
          <valueCode value="SHOULD"/>
        </extension>
        <code value="search-type"/>
        <documentation value="Allows discovery of existing US Core medicationstatement resources using different search criteria"/>
      </interaction>
      <interaction>
        <extension url="http://hl7.org/fhir/StructureDefinition/capabilitystatement-expectation">
          <valueCode value="SHOULD"/>
        </extension>
        <code value="read"/>
        <documentation value="Allows retrieval of a specific US Core medicationstatement by id"/>
      </interaction>
      <interaction>
        <extension url="http://hl7.org/fhir/StructureDefinition/capabilitystatement-expectation">
          <valueCode value="SHOULD"/>
        </extension>
        <code value="history-instance"/>
        <documentation value="Allows review of changes to US Core medicationstatement instance over time"/>
      </interaction>
      <interaction>
        <extension url="http://hl7.org/fhir/StructureDefinition/capabilitystatement-expectation">
          <valueCode value="SHOULD"/>
        </extension>
        <code value="vread"/>
        <documentation value="Allows retrieval of a historical version of a US Core medicationstatement instance"/>
      </interaction>
    </resource>
    <resource>
      <type value="MedicationRequest"/>
      <interaction>
        <extension url="http://hl7.org/fhir/StructureDefinition/capabilitystatement-expectation">
          <valueCode value="SHOULD"/>
        </extension>
        <code value="search-type"/>
        <documentation value="Allows discovery of existing US Core medicationorder resources using different search criteria"/>
      </interaction>
      <interaction>
        <extension url="http://hl7.org/fhir/StructureDefinition/capabilitystatement-expectation">
          <valueCode value="SHOULD"/>
        </extension>
        <code value="read"/>
        <documentation value="Allows retrieval of a specific US Core medicationorder by id"/>
      </interaction>
      <interaction>
        <extension url="http://hl7.org/fhir/StructureDefinition/capabilitystatement-expectation">
          <valueCode value="SHOULD"/>
        </extension>
        <code value="history-instance"/>
        <documentation value="Allows review of changes to US Core medicationorder instance over time"/>
      </interaction>
      <interaction>
        <extension url="http://hl7.org/fhir/StructureDefinition/capabilitystatement-expectation">
          <valueCode value="SHOULD"/>
        </extension>
        <code value="vread"/>
        <documentation value="Allows retrieval of a historical version of a US Core medicationorder instance"/>
      </interaction>
    </resource>
    <resource>
      <type value="Organization"/>
      <interaction>
        <extension url="http://hl7.org/fhir/StructureDefinition/capabilitystatement-expectation">
          <valueCode value="SHOULD"/>
        </extension>
        <code value="search-type"/>
        <documentation value="Allows discovery of existing US Core organization resources using different search criteria"/>
      </interaction>
      <interaction>
        <extension url="http://hl7.org/fhir/StructureDefinition/capabilitystatement-expectation">
          <valueCode value="SHOULD"/>
        </extension>
        <code value="read"/>
        <documentation value="Allows retrieval of a specific US Core organization by id"/>
      </interaction>
      <interaction>
        <extension url="http://hl7.org/fhir/StructureDefinition/capabilitystatement-expectation">
          <valueCode value="SHOULD"/>
        </extension>
        <code value="history-instance"/>
        <documentation value="Allows review of changes to US Core organization instance over time"/>
      </interaction>
      <interaction>
        <extension url="http://hl7.org/fhir/StructureDefinition/capabilitystatement-expectation">
          <valueCode value="SHOULD"/>
        </extension>
        <code value="vread"/>
        <documentation value="Allows retrieval of a historical version of a US Core organization instance"/>
      </interaction>
    </resource>
    <resource>
      <type value="Practitioner"/>
      <interaction>
        <extension url="http://hl7.org/fhir/StructureDefinition/capabilitystatement-expectation">
          <valueCode value="SHOULD"/>
        </extension>
        <code value="search-type"/>
        <documentation value="Allows discovery of existing US Core practitioner resources using different search criteria"/>
      </interaction>
      <interaction>
        <extension url="http://hl7.org/fhir/StructureDefinition/capabilitystatement-expectation">
          <valueCode value="SHOULD"/>
        </extension>
        <code value="read"/>
        <documentation value="Allows retrieval of a specific US Core practitioner by id"/>
      </interaction>
      <interaction>
        <extension url="http://hl7.org/fhir/StructureDefinition/capabilitystatement-expectation">
          <valueCode value="SHOULD"/>
        </extension>
        <code value="history-instance"/>
        <documentation value="Allows review of changes to US Core practitioner instance over time"/>
      </interaction>
      <interaction>
        <extension url="http://hl7.org/fhir/StructureDefinition/capabilitystatement-expectation">
          <valueCode value="SHOULD"/>
        </extension>
        <code value="vread"/>
        <documentation value="Afllows retrieval of a historical version of a US Core practitioner instance"/>
      </interaction>
    </resource>
    <resource>
      <type value="PractitionerRole"/>
      <interaction>
        <extension url="http://hl7.org/fhir/StructureDefinition/capabilitystatement-expectation">
          <valueCode value="SHOULD"/>
        </extension>
        <code value="search-type"/>
        <documentation value="Allows discovery of existing US Core PractitionerRole resources using different search criteria"/>
      </interaction>
      <interaction>
        <extension url="http://hl7.org/fhir/StructureDefinition/capabilitystatement-expectation">
          <valueCode value="SHOULD"/>
        </extension>
        <code value="read"/>
        <documentation value="Allows retrieval of a specific US Core PractitionerRole by id"/>
      </interaction>
      <interaction>
        <extension url="http://hl7.org/fhir/StructureDefinition/capabilitystatement-expectation">
          <valueCode value="SHOULD"/>
        </extension>
        <code value="history-instance"/>
        <documentation value="Allows review of changes to US Core PractitionerRole instance over time"/>
      </interaction>
      <interaction>
        <extension url="http://hl7.org/fhir/StructureDefinition/capabilitystatement-expectation">
          <valueCode value="SHOULD"/>
        </extension>
        <code value="vread"/>
        <documentation value="Afllows retrieval of a historical version of a US Core PractitionerRole instance"/>
      </interaction>
    </resource>
    <resource>
      <type value="Procedure"/>
      <interaction>
        <extension url="http://hl7.org/fhir/StructureDefinition/capabilitystatement-expectation">
          <valueCode value="SHOULD"/>
        </extension>
        <code value="search-type"/>
        <documentation value="Allows discovery of existing US Core procedure resources using different search criteria"/>
      </interaction>
      <interaction>
        <extension url="http://hl7.org/fhir/StructureDefinition/capabilitystatement-expectation">
          <valueCode value="SHOULD"/>
        </extension>
        <code value="read"/>
        <documentation value="Allows retrieval of a specific US Core procedure by id"/>
      </interaction>
      <interaction>
        <extension url="http://hl7.org/fhir/StructureDefinition/capabilitystatement-expectation">
          <valueCode value="SHOULD"/>
        </extension>
        <code value="history-instance"/>
        <documentation value="Allows review of changes to US Core procedure instance over time"/>
      </interaction>
      <interaction>
        <extension url="http://hl7.org/fhir/StructureDefinition/capabilitystatement-expectation">
          <valueCode value="SHOULD"/>
        </extension>
        <code value="vread"/>
        <documentation value="Allows retrieval of a historical version of a US Core procedure instance"/>
      </interaction>
    </resource>
  </rest>
</CapabilityStatement>