Endpoint Directory

The Veradigm and Altera FHIR Endpoint Directories contain information about each Veradigm and Altera client organization and their FHIR installation. At the time that the Veradigm and Altera FHIR API is installed in a client environment, the client's endpoints are registered in the Veradigm "downtown" environment. Only endpoints that are designated for production environments are listed in the applicable Endpoint Directory. Veradigm and Altera partner developers can then use the client endpoints when connecting to that Veradigm or Altera client.

A single organization can have multiple FHIR endpoints for both patient and provider endpoints. However, the organization must have at least one patient endpoint.

The FHIR Endpoint Directory has been divided into two pages:

• Veradigm FHIR Endpoint Directory: For Veradigm EHR environments.
• Altera FHIR Endpoint Directory: For TouchWorks EHR, Sunrise, and Paragon environments.

The list of endpoints on each page is divided into two tables: FHIR R4 endpoints and FHIR DSTU2 endpoints. Click FHIR at the top of the screen to navigate between the two tables. The R4 table can be filtered to include just patient endpoints (default), just provider endpoints, or both.

Endpoints are marked with the following badges:

• Patient: Endpoint for use with patient-facing applications. These endpoints generally end in /open.
• Provider: Endpoint for use with provider-facing applications. These endpoints generally end in /fhir.
• Versionless: Multiple FHIR versions (DSTU2 and R4) are functioning on the same endpoint.

Note: In the context of the Veradigm and Altera FHIR API, “Versionless” specifically refers to only the combination of DSTU2 and R4 versions of the HL7 FHIR specification. The Veradigm and Altera FHIR API does not, for example, support HL7 FHIR Release 3.

The default version of the Veradigm and Altera FHIR API is specified at the time FHIR is installed. When a properly formatted and supported Accept header (examples below) is not supplied with a request, the Veradigm and Altera FHIR API uses that default version.

To determine the default version of FHIR in a multi version environment, refer to the FHIR Capability Statement. Send the request {{FhirURL}}/metadata with no version specified in the request header. The default FHIR version is indicated in the fhirVersion value.

Headers directed to specific FHIR versions are formatted as follows:

Accept: application/fhir+json; fhirVersion=4.0

Accept: application/fhir+json; fhirVersion=2.0

For more information, see https://build.fhir.org/versioning.html#mt-version.

Download Bundles

You can download a filtered list of endpoints in two possible formats. By default, the bundle contains just patient endpoints, but use the Patient, Provider, and All options to edit the file contents.

• FHIR Bundle: Creates a FHIR bundle file in NDJSON format. Each organization is described in a FHIR Organization resource and includes the organization's name, identifiers, and endpoints. Contact information is not included in the Organization resource at this time because the ONC certification requirement applies to patient use only. The organization contact designated in the LMP may be the contact related to the technical support of the endpoint rather than a contact who a patient would contact about their clinical data.
• CSV: Creates a JSON file.