You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: versioned_docs/version-3.1/concepts/clinical/patient.mdx
+46-26Lines changed: 46 additions & 26 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -4,48 +4,68 @@ sidebar_position: 1
4
4
5
5
# Patient
6
6
7
-
A **patient** in Care is a person who receives care through your facility or program. It is the longitudinal anchor for clinical documentation — every encounter, observation, order, and care plan links back to a patient record.
7
+
## Definition
8
8
9
-
## What it represents
9
+
A **[patient](https://build.fhir.org/patient.html)** in Care is a person who receives care
10
+
through your facility or program. The patient record holds the demographic and contact
11
+
details of that person. Care ties every encounter, condition, note, appointment, and
12
+
clinical record to a patient record.
10
13
11
-
In Care's FHIR-aligned model, a patient maps to the **Patient** resource. It holds:
14
+
## Key Attributes
12
15
13
-
-**Identity** — name, date of birth, sex, photo, and government or facility identifiers
14
-
-**Contact** — phone, address, and emergency contacts
15
-
-**Administrative context** — registration status, facility association, and tags used by your deployment
16
-
-**Clinical linkage** — references to encounters, conditions, allergies, and other resources in the record
17
-
18
-
A patient is not the same as a single visit. One patient can have many encounters over time; the patient record is the container that makes that history coherent.
16
+
| Components | What it captures |
17
+
| --- | --- |
18
+
| Name | The full name of the person. Care stores the name as a single free-text entry. |
19
+
| Gender | The gender of the person: Male, Female, Non-binary, or Transgender. |
20
+
| Phone Number | The primary contact number of the person. |
21
+
| Emergency Phone Number | The number to call in an emergency. |
22
+
| Date of Birth | The date the person was born. |
23
+
| Age | The age of the person in years. Care converts the age to a year of birth. |
24
+
| Address | The current address of the person, as free text. |
25
+
| Permanent Address | The permanent address of the person. You can mark it the same as the current address. |
26
+
| PIN Code | The postal code of the address. |
27
+
| Blood Group | The blood group of the person. Staff collect this value at registration. |
28
+
| Geo Organization | The government administrative area that the person belongs to. |
29
+
| Patient Identifiers | The identifiers that your deployment configures, for example a national ID or a facility ID. |
30
+
| Patient Tags | The labels that administrators attach to the patient record. |
31
+
| Deceased Status | Whether the person is deceased, with the date and time of death. |
19
32
20
-
## Identifiers
21
33
22
-
Patients are located using one or more identifiers, depending on how your deployment is configured:
34
+
Note: You enter either a date of birth or an age, not both.
23
35
24
-
| Identifier type | Typical use |
25
-
| --- | --- |
26
-
| Facility MRN | Primary key inside a hospital or clinic |
27
-
| National health ID | ABDM, ABHA, or other national rails |
28
-
| Program ID | Public health or campaign-specific registries |
36
+
### Patient Identifiers
29
37
30
-
Identifiers must be unique within the scope your administrator defines. Duplicate detection during registration uses these fields.
38
+
Your deployment configures the identifier types that Care shows. A facility can define
39
+
its own identifier types, or the instance can define identifier types for all facilities.
40
+
Each identifier type is required or optional. An identifier type can also check the
41
+
format of the value that you enter.
31
42
32
-
## Lifecycle
43
+
## Status
33
44
34
-
```
35
-
Register → Active → (optional) Inactive / Deceased
36
-
```
37
-
38
-
-**Register** — a patient record is created with minimum demographics
39
45
-**Active** — the record is used for encounters and orders
40
-
-**Inactive** — retained for history but hidden from routine search (configurable)
41
46
-**Deceased** — administrative closure; clinical history remains auditable
42
47
43
48
## Permissions
44
49
45
-
Who can view or edit patient demographics is controlled by role-based access. Clinical staff typically can read full records; registration staff can create and update demographics; some fields may be restricted by facility or ward.
50
+
| Permission | What it allows |
51
+
| --- | --- |
52
+
| Can Create Patient | Register a new patient. |
53
+
| Can Update a Patient's data | Edit the details of an existing patient. |
54
+
| Can list patients | See patients in search results and lists. |
55
+
| Can view clinical data about patients | View the clinical information of a patient. |
56
+
| Can view questionnaire responses on patient | View the questionnaire responses of a patient. |
57
+
| Can submit questionnaire about patients | Submit a questionnaire about a patient. |
0 commit comments