FHIR R4 Directory Rollout
New HAPI directories have been available since 4/12/2023
- For existing FHIR API users, ask to have your API key migrated to the HAPI directories. You can continue to access the legacy directories, as needed.
- For organizations that have not accessed the directory FHR API in the past, ask for a new FHIR API key to access the HAPI directories.
- Email techsupport@ehealthexchange.org for technical issues or concerns
- For urgent attention, copy administrator@ehealthexchange.org
New HAPI Directory – FHIR Implementation Guides (IGs)
- RESTful API: https://hl7.org/fhir/http.html
- FHIR Read: https://hl7.org/fhir/http.html#read
- Generalized search capabilities (see “parameters for all resources” and “search result parameters” under the Summary Table): https://www.hl7.org/fhir/search.html
- Search parameters for an FHIR Organization resource: https://hl7.org/fhir/organization.html#search
New HAPI Directory APIs – 3 API Choices But Only 2 APIs by Summer 2024
FHIR Client API
- Provides access to both Argonaut STU3 FHIR (same as the current directory offering) and FHIR R4 APIs
- Typically provides read-only access – no update or create operations
UDDI API (SOAP API) to be retired by 8/16/2024
- The new FHIR HAPI based directory will support a traditional UDDI/SOAP interface. Newer data elements introduced with STU3/R4 will not be available under the UDDI/SOAP interface.
- No access to sub-participant entries.
- Access will require SSL/TLS certificate-based security only and requires trust of DirectTrust CAs such as EMR Direct and MaxMD, as in the past.
- The UDDI API will be retired on 8/16/2024, so make plans to migrate to the FHIR R4 API.
New HAPI Directories and Hub Endpoints
FHIR Client API and Hub endpoints
- For all FHIR R4 entries with Hub endpoints: https://<<VAL-or-PROD-hostname>>/fhir/Organization/$hub-aware
- For a single FHIR R4 entry with Hub endpoints: https://<<VAL-or-PROD-hostname>>/fhir/Organization/2.16.840.1.113883/$hub-aware
UDDI API (SOAP API) and Hub endpoints [UDDI API to be retired 8/16/2024]
- Direct endpoints with the UDDI API:
- Hub endpoints with the UDDI API:
- https://<<VAL-or-PROD-hostname>>/uddi-hubaware
Directory Endpoint Options
Note: Email techsupport@ehealthexchange.org for the proper “VAL-HOSTNAME”
FHIR R4 API
- Direct endpoints: https://VAL-HOSTNAME/fhir/Organization?_apiKey=<INSERT_API_KEY>&_format=json
- Hub endpoints: https://VAL-HOSTNAME/fhir/Organization/$hub-aware?_apiKey=<INSERT_API_KEY>&_format=json
Argonaut STU3 API
- Direct endpoints: https://VAL-HOSTNAME/fhir-pre-stu3/Organization?_apiKey=<INSERT_API_KEY>&_format=xml
- Hub endpoints: https://VAL-HOSTNAME/fhir-pre-stu3/Organization/$hub-aware?_apiKey=<INSERT_API_KEY>&_format=xml
UDDI API [not available after 8/16/2024]
- Direct endpoints: https://VAL-HOSTNAME/uddi
- Hub endpoints: https://VAL-HOSTNAME/uddi-hubaware
PRODUCTION DIRECTORY
Note: Email techsupport@ehealthexchange.org for the proper “PROD-HOSTNAME”
FHIR R4 API
- Direct endpoints: https://PROD-HOSTNAME/fhir/Organization?_apiKey=<INSERT_API_KEY>&_format=json
- Hub endpoints: https://PROD-HOSTNAME/fhir/Organization/$hub-aware?_apiKey=<INSERT_API_KEY>&_format=json
Argonaut STU3 API
- Direct endpoints: https://PROD-HOSTNAME/fhir-pre-stu3/Organization?_apiKey=<INSERT_API_KEY>&_format=xml
- Hub endpoints: https://PROD-HOSTNAME/fhir-pre-stu3/Organization/$hub-aware?_apiKey=<INSERT_API_KEY>&_format=xml
UDDI API [not available after 8/16/2024]
- Direct endpoints: https://PROD-HOSTNAME/uddi
- Hub endpoints: https://PROD-HOSTNAME/uddi-hubaware
Change in Functionality – Inactivated Entries Are Now Logically Deleted
With the legacy directories, when a directory entry is inactivated and should no longer be consumed, we set the “active” element to false.
With the new HAPI directories, the following is done instead:
- The “active” element set to false now indicates that a directory entry is pending eHealth Exchange approval. An “active=false” entry should not be consumed by directory clients as it has not been approved.
- When a directory entry is removed from the HAPI directories, it will be logically deleted using HTTP DELETE and can no longer be found using a directory search for Organization entries.
- Logically deleted entries can be discovered by querying with a $status-changes operation, with an optional date range and “deleted=true” parameter.
- If the “deleted=true” option is used, then results will only be returned if the last state of a directory entry is deleted within the timeframe specified by the query. For example:
- If a directory entry is not deleted on 3/1, is deleted on 3/15 and is re-activated on 3/20:
- The directory entry will be included in the results if the end date for the query is 3/16.
- If the end date for the query is 3/21, then it will not be included in the results, because the entry was re-activated and is no longer deleted within that timeframe.
- If a directory entry is not deleted on 3/1, is deleted on 3/15 and is re-activated on 3/20:
- A simple FHIR R4 search query example using $status-changes is: https://VAL-HOSTNAME/fhir/Organization/$status-changes
- A FHIR R4 search query that uses $status-changes with a timeframe and the “deleted=true” option: https://VAL-HOSTNAME/fhir/Organization/$status-changes?deleted=true&start=2023-03-01T20:00:00&end=2023-03-16T23:59:59
- •The response to the $status-changes query is a FHIR List. An example of the response content is below:
- As per the example, the code of “deprecate” indicates the entry has been deleted.
- The XPath for the HCID of the deleted entry is: /List/entry/item/identifier/value/@value
Directory Query Recommendations
Directory entries with “active=false” are unapproved and not ready to query.
Unlike the legacy directories, if you don’t specify a value for “active“, then the default is not “active=true”. Entries will be returned with active set to true and false if the active parameter is not specified.
- Note: %7C is an URL encoded pipe character (“|”)
Rollout of New HAPI Directories and Retirement of Legacy Directories
- The legacy directories were retired on July 27, 2023, and are no longer accessible by participants.
- The eHealth Exchange has been forwarding requests from the retired legacy directories to the new HAPI directories since August 10, 2023. Directory request forwarding was documented in detail during the August 2023 all participant call and the slides are accessible under eHealth Exchange Communications.
- The eHealth Exchange is aware of several participants that need to use the endpoints for the HAPI directories and not rely on directory forwarding. If you are not certain whether your organization is using the endpoints of the HAPI-based directories for FHIR R4 content and/or are concerned you may be relying on forwarding from the retired legacy directories to the new HAPI-based directories, please send an inquiry to administrator@ehealthexchange.org.