FHIR API

Roche Diabetes Care exposes an API using HL7 FHIR (Fast Healthcare Interoperability Resources) STU3 in order to allow EMRs, PHRs and other systems to communicate with Roche ecosystem.

FHIR is a standard for exchanging healthcare data electronically and takes a modern, web-based approach to API design. For more information about how to use FHIR, please visit the HL7 FHIR STU3 Documentation.

API INFORMATION

Title: FHIR API

Protocols: HTTPS

URI Live: https://api-services-eu.rochedcplatform.com/partners/fhir/stu3/api/

URI Demo: https://api-services-demo.rochedcplatform-sandbox.com/partners/fhir/stu3/api/

Swagger file: here

AUTHENTICATION

FHIR API is secured with mutual TLS for identifying both parties and for securing communication between systems.

More information can be found here: API Authentication

FHIR PROFILES

Below are the list of profiles used in Patient transactions like creation and update.

• message-header (mandatory)
• patient-v2 (mandatory)
• condition (optional)

Below are the list of profiles used in practitioner transactions like creation and update.

• practitioner-v2 (mandatory)

ENDPOINTS

• Patient Creation v1 (POST /partners/fhir/stu3/api/Bundle) Note: Planned to be deprecated
• Patient Creation v2 (POST /partners/fhir/stu3/api/v2/Bundle)
• Patient Update v1 (PUT /partners/fhir/stu3/api/Bundle) Note: Planned to be deprecated
• Patient Update v2 (PUT /partners/fhir/stu3/api/v2/Bundle)
• Patient Read (GET /partners/fhir/stu3/api/Patient)
• Practitioner Creation v1 (POST /partners/fhir/stu3/api/Practitioner) Note: Planned to be deprecated
• Practitioner Creation v2 (POST /partners/fhir/stu3/api/Practitioner)
• Practitioner Update v1 (PUT /partners/fhir/stu3/api/Practitioner) Note: Planned to be deprecated
• Practitioner Update v2 (PUT /partners/fhir/stu3/api/v2/Practitioner)