FHIR API: Practitioner Creation v1


Note

This API version will be deprecated. We encourage you to migrate to the latest version of the API. You can find the documentation for the new API version at Practitioner Creation v2 (POST /partners/fhir/stu3/api/Practitioner).


Pre-requisites


Resource:

POST /partners/fhir/stu3/api/Practitioner

Authentication:

Endpoint is secured with mutual TLS. More information can be found here: API Authentication


API Request

Request Headers

Name Description Type Required Example
org_id Organization OID String Yes 2.16.724.4.2
x-origin-request-id String Request Unique ID generated by EMR middleware (UUID) Yes 5109d51b-421e-4746-b673-16e3fe2b3442
client_id Public identifier for organizations generated by Roche DC String Yes 1234567890
client_secret Client related secret known only to the EMR and Roche DC String Yes 1234567890
Content-Type json or fhir+json String Yes application/json or application/fhir+json

Profile overview

The list of profiles used in practitioner Creation:

Note

While creating a practitioner, the practitioner identifier value and the email must be unique.


Request Example

  • Patient Request example with Type-1 diabetes condition:
curl --location --request POST 'https://api-services-eu.rochedcplatform.com/partners/fhir/stu3/api/v2/Practitioner' \
--header 'Content-Type: application/json' \
--header 'client_id: 1234567890' \
--header 'client_secret: 1234567890' \
--header 'org_id: 2.16.724.4.2' \
--data-raw '{
    "resourceType": "Practitioner",
    "meta": {
        "profile":  [
            "http://roche.com/fhir/rdc/StructureDefinition/practitioner-v2"
        ]
    },
    "identifier":  [
        {
            "system": "urn:oid:2.16.724.4.305",
            "value": "11111111H"
        }
    ],
    "name":  [
        {
            "family": "Smith",
            "given":  [
                "James"
            ]
        }
    ],
    "telecom":  [
        {
            "system": "email",
            "value": "jamessmith111@email.com"
        }
    ]
}'

API Response

API code response

HTTP Response Code Description Response Body FHIR error code FHIR error code description
200 Practitioner created Practitioner NA NA
400 Request failed because of incorrect parameters, returns no data OperationOutcome required Request failed because of incorrect parameters, returns no data
400 Request failed because of incorrect parameters, returns no data OperationOutcome structure A structural issue in the content such as wrong namespace, or unable to parse the content completely, or invalid json syntax.
400 Request failed because of incorrect parameters, returns no data OperationOutcome invalid Content invalid against the specification or a profile.
401 Request failed with unauthorized access, returns no data Empty NA NA
405 Method Not Allowed Empty NA NA
409 Conflict / User already exists OperationOutcome duplicate User already exist!
415 Unsupported Media Type. OperationOutcome not-supported Content-Type is not one of (application/json, application/fhir+json)
500 Request failed with internal exception OperationOutcome exception Internal server error.
501 Not implemented Empty NA NA

API Payload response

Successful response object:

{
    "identifier": [
        {
            "system": "urn:oid:2.16.724.4.305",
            "value": "11111111H"
        }
    ],
    "meta": {
        "profile":  [
            "http://roche.com/fhir/rdc/StructureDefinition/practitioner-v2"
        ]
    },
    "name": [
        {
            "given": [
                "James"
            ],
            "family": "Smith"
        }
    ],
    "telecom": [
        {
            "system": "email",
            "value": "jamessmith111@email.com"
        }
    ],
    "id": "11111111H",
    "resourceType": "Practitioner"
}

Error response object:

As an example, If we try to create a record that already existis in Roche Diabetes Care (RDC), a 409 HTTP error status code is returned together the following response:

{
    "resourceType": "OperationOutcome",
    "issue": [
        {
            "severity": "error",
            "code": "duplicate",
            "diagnostics": "User already exist!"
        }
    ]
}

Response Time (ms):


  • Average: 1500

  • Worst case scenario: 10000