Endpoint Directory

The Veradigm and Altera FHIR Endpoint Directories contain information about each Veradigm and Altera client organization and their FHIR installation and configuration. 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, and as a result, are listed in the 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.

The FHIR Endpoint Directory has been divided into two pages:

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.

The list of endpoints is divided into two tables: DSTU2 endpoints and R4 endpoints. Click FHIR at the top of the screen to navigate between the two tables.

The Veradigm and Altera FHIR API can support multiple FHIR versions (DSTU2 and R4) working on the same endpoint. When both the DSTU and R4 versions of FHIR are functioning on a single endpoint, the Endpoint Directory displays the Versionless badge.

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 Bundle

You can download a list of endpoints as a FHIR Bundle resource. Select the appropriate version of FHIR, and then click Download [version] Endpoints as a FHIR Bundle. The utility displays the response in JSON format, and you can download it manually. You do not need to authenticate to see the response.