Integrating External Systems

While configuring your Ignite instance it is possible that you might want to integrate with external systems in order to manage patients and additional functions such as billing, inventory and so on.

All of the guides below involve using an Backend client to write or read data from Medblocks Ignite - you can understand how to create a client from here.

Integrating with Patient Management Systems

Creating Patients

If you use external patient management systems to register patients and creation of encounters then you can use the Ignite FHIR APIs. Below is a simple REST API call that creates a patient inside Ignite.

POST /fhir/Patient
Authorization: Bearer <token> // This is the code generated from performing Authentication
Content-Type: application/fhir+json

{
  "resourceType": "Patient",
  "id": "example",
  "identifier": [
    {
      "use": "official",
      "system": "urn:oid:",
      "value": "12345"
    }
  ],
  "name": [
    {
      "use": "official",
      "family": "Doe",
      "given": ["John"]
    }
  ],
  "gender": "male",
  "birthDate": "1974-12-25"
}

This returns a 201 Created response with the patient resource which contains the ID of the patient created, you can use this for all further operations on the Patient.

{
    "resourceType": "Patient",
    "id": "80653af9-fc54-402c-9aa5-20bc487d4b69"
    // Other details
}

Creating Encounters

Patient management systems also create encounters for patients, you can use the Ignite FHIR APIs to create encounters as well. Below is a simple REST API call that creates an encounter inside Ignite.

POST /fhir/Encounter
Authorization: Bearer <token>
Content-Type: application/fhir+json

{
  "resourceType": "Encounter",
  "id": "example",
  "status": "in-progress",
  "subject": {
    "reference": "Patient/80653af9-fc54-402c-9aa5-20bc487d4b69"
  }
}

Once the Encounter is created you can then use the patient within Ignite to perform clinical operations. More details can be used from the FHIR Encounter documentation.