How to Integrate Any External Application with Clinicea EMR: Clinical Sections, Master Data & JSON Mapping

Overview

This guide explains how an external application can send structured clinical data into Clinicea EMR.

A common example is an AI-powered voice-to-text application. During a consultation, the doctor speaks naturally while a third-party application converts the conversation into structured clinical information. The application then sends this information to Clinicea, where it is automatically mapped to the appropriate sections of the patient's case sheet.

This article helps you understand:

Which clinical sections are available in the Clinicea case sheet.
How to identify the correct clinical section while sending data.
How to retrieve the required master data IDs before posting your payload.
Which APIs to use for different types of clinical master data.

Frequently Asked Questions (FAQs)

1. How is clinical data organized in Clinicea?

Clinicea organizes every patient case sheet into multiple clinical sections, such as Chief Complaint, Medical History, Vitals, Assessment, Procedures, Notes, Investigations, and more.

When an external application sends data to Clinicea, it should indicate which clinical section the data belongs to so that Clinicea can map it correctly within the patient's case sheet.

2. How do I specify the clinical section in my JSON payload?

Include the appropriate Clinical Group Enum Type in your payload.

Each enum represents a specific section of the Clinicea case sheet.

Clinical Group Enum Type	Clinical Section
621	Chief Complaint
622	POH (History)
623	Procedures
624	Family History
625	Assessment
626	Assessment Plan
627	Patient Details
641	Vitals
642	Examination
643	Review of Systems (ROS)
644	Investigations
645	Social History
646	Obstetric & Gynaecological History
647	Medical History
648	Advice
649	Notes
650	Health Reminders
651	Other History
652	Lab Results

Example

If your application is sending a patient's vital signs, use Clinical Group Enum Type = 641.

Similarly:

625 → Assessment
647 → Medical History
648 → Advice
644 → Investigations
Using the correct enum ensures that Clinicea stores the data in the appropriate section of the patient's case sheet.

3. Do I need to send only the clinical section, or do I also need master data IDs?

Some clinical information can simply be posted to the appropriate clinical section.
However, for predefined clinical records such as:

Medical History
Assessment
Investigations
Vaccinations
Other Clinicea master records

you should use the corresponding master data ID instead of sending only free-text values. This ensures accurate mapping and consistency across patient records.

4. How do I retrieve Investigation master data?

Use the following API to retrieve all Investigation master records available in your Clinicea organization.

GET https://api.clinicea.com/api/v3/emrMasterData/getInvestigations?lastSyncDTime=1900-12-31T06%3A30%3A00&organisationID=organisationID&pageNo=1&pageSize=100

5. How do I retrieve Immunization or Vaccine master data?

Use the following API to retrieve all Immunization Schedule and Vaccine master records.

GET https://api.clinicea.com/api/v3/emrMasterData/getImmunisationSchedules?lastSyncDTime=1900-12-31T06%3A30%3A00&organisationID=organisationID&pageNo=1&pageSize=100

6. How do I retrieve other clinical master data?

For all other clinical master data—including Medical History, Assessment, Advice, Notes, Family History, Social History, and similar sections—use the Get Clinical Groups API.

Pass the required Clinical Group Enum Type in the clinicalGroupType parameter.

GET https://api.clinicea.com/api/v3/emrMasterData/getClinicalGroups?lastSyncDTime=2015-03-21T14%3A30%3A10&clinicalGroupType=626&organisationID=organisationID&pageNo=1&pageSize=100

Replace 626 with the appropriate Clinical Group Enum Type depending on the clinical section whose master data you want to retrieve.
For example:

625 → Assessment
647 → Medical History
648 → Advice
649 → Notes

7. How do I retrieve medicine (Rx) master data?

To retrieve medicine inventory used while posting prescription (Rx) information, use the following API.

GET https://api.clinicea.com/api/v3/inventory/getChanges?lastSyncDTime=1900-12-31T06%3A30%3A00&organisationID=organisationID&pageNo=pageNo&pageSize=pageSize&inventoryType=1

8. How are these master data APIs used during integration?

A typical integration flow looks like this:

Retrieve the required master data from Clinicea.
Store the corresponding master IDs in your application.
While posting the clinical JSON payload, include:
- The appropriate Clinical Group Enum Type, and
- The corresponding master data ID (where applicable).
Clinicea uses this information to map the incoming data accurately into the patient's case sheet.

9. Do all API requests require authentication?

Yes.

Every API request must include:

A valid Authorization Token in the request headers.
Your Organisation ID in the API request.

For complete details on authentication, token generation, and API usage, refer to the Clinicea API guide.
API Guide

https://help.clinicea.com/en/article/how-to-use-the-api-1egs4c7/

https://api.clinicea.com/swagger/ui/index

10. Where can I get technical assistance?

If you require assistance with your integration or have questions regarding Clinicea APIs, our technical team will be happy to help.

Email: support@clinicea.com

Updated on: 22/07/2026

Was this article helpful?

Thank you!