APIs overview


The following APIs are available for EMR Integration:

  • Roche FHIR API

  • Roche Services API

  • AWS Retrieve File API (S3 SDK)


The following endpoints are available from the Roche APIs:


Description Version Version History Technical specification
Patient Creation v1 - Initial version Patient Creation v1
Patient Creation v2 - Provides patient.id (FHIR ID) in response aligned with FHIR Standards
- Includes new optional field patient.managingOrganization		 Patient Creation v2
Patient Update v1 - Initial version Patient Update v1
Patient Update v2 - Supports updates based on patient.id provided in Patient Creation v2 Patient Update v2
Patient Read v1 - Initial version Patient Read
Practitioner Creation v1 - Initial version Practitioner Creation v1
Practitioner Creation v2 - Provides practitioner.id (FHIR ID) in response aligned with FHIR Standards Practitioner Creation v2
Practitioner Update v1 - Initial version Practitioner Update v1
Practitioner Update v2 - Supports updates based on practitioner.id provided in Practitioner Creation v2 Practitioner Update v2
Get S3 temporary token to download files v1 - Initial version Get S3 Temporary Token
Notification acknowledgement v1 - Initial version Notification ACK

The base URL of the endpoints depends on the environment:



Authentication:

Roche Diabetes Care APIs are secured with mutual TLS for identifying both parties and for securing communication between systems. Roche validates the identity of the client (middleware) and middleware verifies the identity of the server (Roche).

More information can be found in the Authentication section