• FHIR Version: 3.0.0
• Supported formats: xml, json
• Published: 2017-03-08
• Published by: Health Level Seven International US Realm Steering Committee

The Section describes the expected capabilities of the US Core Server actor which is responsible for providing responses to the queries submitted by the US Core Requestors. The complete list of FHIR profiles, RESTful operations, and search parameters supported by US Core Servers are defined. Systems implementing this capability statement should meet the ONC 2015 Common Clinical Data Set (CCDS) access requirement for Patient Selection 170.315(g)(7) and Application Access - Data Category Request 170.315(g)(8). 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 Server SHALL:

• Support the US Core Patient resource profile.
• Support at least one additional resource profile from the list of US Core Profiles.
• Implement the RESTful behavior according to the FHIR specification.
• Return the following response classes:
  • (Status 200): successful operation
  • (Status 400): invalid parameter
  • (Status 401/4xx): unauthorized request
  • (Status 403): insufficient scope
  • (Status 404): unknown resource
  • (Status 410): deleted resource.
• Support json resource formats for all US Core interactions.
• Declare a CapabilityStatement identifying the list of profiles, operations, search parameter supported.

The US Core Server SHOULD:

• Support xml resource formats for all US Core interactions.
• Identify the US Core profiles supported as part of the FHIR meta.profile attribute for each instance.

Security:

US Core Servers SHALL:

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

Profile Interaction Summary:

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

Summary of US Core search criteria

Specific server search capabilities are described in detail in each of the resource sections below.

Resource Details:

1. Patient

Supported Profiles: US Core Patient Profile

Search Criteria:

• A server SHALL be capable of returning a patient using:

  GET [base]/Patient/[id].

• A server SHALL be capable of returning a patient by identifier using GET [base]/Patient?identifier=[system]|[code]

• A server SHALL be capbable of returning a patient by supporting at a minimum the following search parameters when at least 2 are present:

  • name
  • gender

  • birthdate

    • for example:

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

Search Parameters:

2. AllergyIntolerance

Supported Profiles: US Core AllergyIntolerance Profile

Search Criteria:

• A server SHALL be capable of returning all patient's allergies using:

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

Search Parameters:

3. CarePlan

Supported Profiles: US Core CarePlan Profile

Search Criteria:

• A server SHALL be capable of returning all of a patient's Assessment and Plan of Treatment information using:

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

• A server SHALL be capable of returning 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]

• A server SHOULD be capable returning all of a patient's active Assessment and Plan of Treatment information using

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

Search Parameters:

4. CareTeam

Supported Profiles: US Core CareTeam Profile

Search Criteria:

• A server SHALL be capable of returning a patient's current care team members using:

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

Search Parameters:

5. Condition

Supported Profiles: US Core Condition Profile

Search Criteria:

• A server SHALL be capable of returning a patient's conditions list using:

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

• A server SHOULD be capable returning all of a patient's active problems and health concerns using:

  Get [base]/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 [base]/Condition?patient=[id]&category=[problem|health-concern]

Search Parameters:

6. Device

Supported Profiles: US Core Device Profile

Search Criteria:

• A server SHALL be capable of returning all Unique device identifier(s)(UDI) for a patient's implanted device(s):

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

Search Parameters:

7. DiagnosticReport

Supported Profiles: US Core DiagnosticReport Profile

Search Criteria:

• A server SHALL be capable of returning all of a patient's laboratory diagnostic reports queried by category using:

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

• A server SHALL be 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 SHALL be 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:

8. Goal

Supported Profiles: US Core Goal Profile

Search Criteria:

• A server SHALL be capable of returning all of a patient's goals using:

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

• A server SHALL be 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:

9. Immunization

Supported Profiles: US Core Immunization Profile

Search Criteria:

• A server SHALL be capable of returning all patient's allergies using:

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

Search Parameters:

10. Location

Supported Profiles: US Core Location Profile

Search Criteria:

• A server SHALL be capable of returning a location by name using:

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

• A server SHALL be capable of returning a location by address using:

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

Search Parameters:

11. 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 SHALL be supported.

12. 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. The server application MAY choose any one way or more than one method, but if an external reference to Medication is used, the server SHALL support the _include parameter for searching this element. The client application must support all methods.

A server SHALL be capable of returning all medications for a patient using one of or both:

GET /MedicationStatement?patient=[id]

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

Search Parameters:

13. 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. The server application MAY choose any one way or more than one method, but if an external reference to Medication is used, the server SHALL support the _include parameter for searching this element. The client application must support all methods.

A server SHALL be capable of returning all medications for a patient using one of or both:

GET /MedicationRequest?patient=[id]

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

Search Parameters:

14. Observation

Supported Profiles: 1. US Core Result Observation Profile

Search Criteria:

• A server SHALL be capable of returning all of a patient's laboratory results queried by category using:

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

• A server SHALL be capable of returning 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]}

• A server SHALL be 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]}

1. Vital Signs Profile

Search Criteria

• A server SHALL be capable of returning all of a patient's vital signs that it supports using:

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

• A server SHALL be 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 SHALL be 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]}

1. US Core Smoking Status Observation Profile

Search Criteria:

• A server SHALL be capable of returning a patient's smoking status using:

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

Search Parameters:

15. Organization

Supported Profiles: US Core Organization Profile

Search Criteria:

• A server SHALL be capable of returning an organization by identifier using:

  `GET [base]/Organization?identifier=[system]

  [code]'

• A server SHALL be capable of returning an organization by name using:

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

• A server SHALL be capable of returning an organization by address using:

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

Search Parameters:

16. Practitioner

Supported Profiles: US Core Practitioner Profile

Search Criteria:

• A server SHALL be capable of returning a practitioner by identifier using:

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

• A server SHALL be capable of returning a practitioner by name using:

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

Search Parameters:

17. Procedure

Supported Profiles: US Core Procedure Profile

Search Criteria:

• A server SHALL be capable of returning a patient's procedures using: GET/Procedure?patient=[id]

• A server SHALL be capable of returning all of a patient's procedures over a specified time period using:

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

Search Parameters: