Using the FHIR Interface

The FHIR Interface is a RESTful interface (Representational State Transfer), which provides a stateless, consistent way of accessing resources. This section introduces the basic concepts necessary to use the FHIR Interface.

Terms of Use

By using the HIEBus FHIR Interface, you agree to the following Terms of Use.


All FHIR requests are made over HTTP/HTTPS to a FHIR endpoint. A given site may implement any number of endpoints. For example:


Learn more about Endpoints.


FHIR resources (e.g., patient, procedure, claim) are implemented as REST resources. The resource becomes part of the request URL. For example:

Learn more about Resources.


Query parameters in the URL allow you to specify parameters for the FHIR request. For example:

Learn more about Building Requests.

Posting Data

Data can be POSTed to the FHIR server.

Learn more about Posting Data.


The FHIR Interface protects health data by requiring authentication on all operations. In order to access FHIR resources, you will need to obtain a valid access token and include it in the HTTP request header.

Learn more about Authentication.


The HTTP response will contain XML or JSON data for the request. Here is a small excerpt of a response showing a patient’s name:

        <use value="official">
            <extension url="">
                        <system value="" />
                        <code value="LegalName" />
                        <display value="Legal Name" />
                        <userSelected value="true" />
                    <text value="Legal Name" />
        <family value="Demoski" />
        <given value="Helen" />

Learn more about handling Responses and Errors.

Mapping and Codes

FHIR data must be translated between FHIR fields and their HIEBus equivalents. Coded values are commonly used to represent healthcare concepts.

Learn more about Field Mapping and Codes.