A Patient represents a person receiving healthcare services. It serves as the central record of a person's demographic and basic health information, linking all their healthcare interactions and data.

Key Purpose

• Maintain demographic information about patients
• Track patient's health status and medical history
• Link patient encounters, consultations, and care plans
• Support patient identification and contact across facilities
• Enable disease surveillance and monitoring
• Track vaccination and test status

{
"name" : "string",
"phone_number" : "string",
"emergency_phone_number" : "string",
"address" : "string",
"permanent_address" : "string",
"postal_code" : "string",
"gender" : "",
"date_of_birth" : "",
"year_of_birth" : 2000,
"deceased_datetime" : "datetime | None",
"marital_status" : "str", // ENUM Valueset from <https://hl7.org/fhir/valueset-marital-status.html>
// "contacts" : {}, // Structure from FHIR
"nationality" : "string" // Need to map to a code based on UN
}

Patient Identifier management.

Patients can have different identifiers in different facilities, patients might also have more than one identifier based on the area they are from.

ie Facilities registered in India might have Aadhar card, PAN card, Drivers license and Voters ID.

Some specific facilities might also have their own identification systems like their MRD number and other file numbers.

To account for this, we need to collect systems that can uniquely identify a patient at both the instance level and the facility level.

The instance level systems definition can be as simple as a JSON and the facility level config can be as simple as JSON configuration.