Practitioner
Practitioner Services allow Health Information Systems (HIS) to create and update practitioners in Roche ecosystem.
Data Flow
- The administrative / HIS creates / update a practitioner.
- The middleware receives the practitioner creation / update message.
- The middleware transforms the message delivered by HIS into the FHIR message and send it to Partners FHIR API.
- Roche creates / updates the practitioner in Diabetes Care Platform and sends a response to the EMR middleware.
Assigning authority
The possible identifier systems that we accept to identify the assigning authority that is generating the practitioners ID are:
| Assigning authority | Identifier system |
|---|---|
| Meteda | urn:oid:1.3.6.1.4.1.56221.2.2 |
| DNI | urn:oid:2.16.724.4.305 |
For more details please check Practitioner create / update chapter:
Practitioner Create
Practitioner creation API definition
In order to create a Practitioner it is required to send a Practitioner Resource.
| Method | Endpoint | URI Parameters | Request Headers | Request Body | Response Body | Security |
|---|---|---|---|---|---|---|
| POST | https://[host]/partners/fhir/stu3/api/[Resource] | Resource: Practitioner | org_id : Organization OID x-origin-request-id: Request unique id, generated by EMR middleware client_id : Public identifier for organizations generated by Roche DC client_secret : Client related secret known only to the EMR and Roche DC Content-Type: Default value application/json |
Practitioner Resource - Please check Request Definition | Please check Response Definition | Mutual TLS Authentication (mTLS) |
Complete FHIR API Specification here
Request Definition
- Please find Practitioner Resource Schema Overview here
- Please find Sample Practitioner here
- Please find Practitioner Example cURL Request here
- Please find FHIR STU3 Schema here
Response Definition
Success response: On successful creation of Practitioner through API will return HTTP 200 Status Code and Roche internal ID is returned for Practitioner ID in the body of response.
- Please find Example Response here
Error response: Please check error codes in validation section below.
Uniqueness
In RDCP the practitioner is uniquely identified by the email.
Note: if a practitioner is created with the same email an “duplicate” error will be thrown.
Data Validation
| Validation | Error code |
|---|---|
| A required element is missing. | required |
| A structural issue in the content such as wrong namespace, or unable to parse the content completely, or invalid json syntax | structure |
| An internal timeout has occurred. | timeout |
| An unexpected internal error has occurred. | exception |
| Content invalid against the specification or a profile. | invalid |
| Provided content is too long (typically, this is a denial of service protection type of error). | too-long |
| An attempt was made to create a duplicate record. | duplicate |
Please find Error handling details here
Response Time
The average and the worst case scenario response time for the practitioner creation API are:
| Response Time (ms) | |
|---|---|
| Average | 1391.93 |
| Worst case scenario | 9203 |
Practitioner Update
Practitioner update API definition
In order to update a Practitioner it is required to send a Practitioner Resource.
| Method | Endpoint | URI Parameters | Request Headers | Request Body | Response Body | Security |
|---|---|---|---|---|---|---|
| PUT | https://[host]/partners/fhir/stu3/api/[Resource]/[id] | Resource: Practitioner id: Practitioner ID |
org_id : Organization OID x-origin-request-id: Request unique id, generated by EMR middleware client_id : Public identifier for organizations generated by Roche DC client_secret : Client related secret known only to the EMR and Roche DC Content-Type: Default value application/json |
Practitioner Resource - Please check Request Definition | Please check Response Definition | Mutual TLS Authentication (mTLS) |
Complete FHIR API Specification here
Request Definition
- Please find Practitioner Resource Schema Overview here
- Please find Sample Practitioner here
- Please find Practitioner Example cURL Request here
- Please find FHIR STU3 Schema here
Response Definition
Success response: On successful update of Practitioner through API will return HTTP 200 Status Code with empty body.
Error response: Please check error codes in validation section below.
Data Validation
| Validation | Error code |
|---|---|
| A required element is missing. | required |
| A structural issue in the content such as wrong namespace, or unable to parse the content completely, or invalid json syntax | structure |
| An internal timeout has occurred. | timeout |
| An unexpected internal error has occurred. | exception |
| Content invalid against the specification or a profile. | invalid |
| Provided content is too long (typically, this is a denial of service protection type of error). | too-long |
| The reference provided was not found. | not-found |
Please find Error handling details here
Response Time
The average and the worst case scenario response time for the practitioner update API are:
| Response Time (ms) | |
|---|---|
| Average | 949.39 |
| Worst case scenario | 2550 |
Profiles
Below are the list of profiles used in practitioner transactions like creation, updation.
- practitioner-v2 (mandatory)