Flows/Create a patient - Revision history

Admin: Automated edit (via update-page on MediaWiki MCP Server)

2026-07-06T04:00:53Z

Automated edit (via update-page on MediaWiki MCP Server)

← Older revision		Revision as of 09:30, 6 July 2026
Line 97:		Line 97:

	Deployment-specific handling (unknown identity, emergency intake without ID, duplicate merges) is documented in playbooks, not here.		Deployment-specific handling (unknown identity, emergency intake without ID, duplicate merges) is documented in playbooks, not here.

			{{Navbox clinical}}

	{{Related}}		{{Related}}
			Wiki: ohcnwiki.tellmey.fyi

Admin: OHC identity seed

2026-07-04T22:46:15Z

OHC identity seed

← Older revision		Revision as of 04:16, 5 July 2026
Line 3:		Line 3:
	\|domain=clinical		\|domain=clinical
	\|title=Create a patient		\|title=Create a patient
			\|summary=Registering a new patient in Care — the minimum path from search to a saved record ready for an encounter.
	\|order=1		\|order=1
	\|introduced=3.0		\|introduced=3.0
Line 11:		Line 12:
	This flow walks through registering a '''new patient''' in Care — the minimum path from search to a saved record ready for an encounter.		This flow walks through registering a '''new patient''' in Care — the minimum path from search to a saved record ready for an encounter.

	{{Info\|title=Prerequisite\|1=Read [[Concepts/Patient]] to understand what a patient record contains and how identifiers work.}}		{{Info\|title=Prerequisite\|1=Read [[Concepts/Patient\|Patient]] to understand what a patient record contains and how identifiers work.}}

	== Before you start ==		== Before you start ==
Line 34:		Line 35:

	{\| class="wikitable"		{\| class="wikitable"
		⚫	! Field !! Notes
	\|-		\|-
		⚫	\| Name \|\| Legal name; supports multiple given names where configured
⚫	! Field
	! Notes
	\|-		\|-
		⚫	\| Date of birth \|\| Used for duplicate detection
	\| Name
⚫	\| Legal name; supports multiple given names where configured
	\|-		\|-
		⚫	\| Sex \|\| Administrative sex for clinical context
	\| Date of birth
⚫	\| Used for duplicate detection
	\|-		\|-
		⚫	\| Phone \|\| Often required for OTP or follow-up contact
	\| Sex
⚫	\| Administrative sex for clinical context
	\|-		\|-
		⚫	\| Identifier \|\| Facility MRN or national ID when applicable
	\| Phone
⚫	\| Often required for OTP or follow-up contact
	\|-
	\| Identifier
⚫	\| Facility MRN or national ID when applicable
	\|}		\|}

Line 73:		Line 67:

	{\| class="wikitable"		{\| class="wikitable"
		⚫	! Next step !! When
	\|-		\|-
		⚫	\| Start an encounter \|\| Patient is at the desk for a visit ''(flow coming soon)''
⚫	! Next step
	! When
	\|-		\|-
		⚫	\| Print registration slip \|\| Facility policy requires a paper token
	\| Start an encounter
⚫	\| Patient is at the desk for a visit ''(flow coming soon)''
	\|-		\|-
		⚫	\| Link national health ID \|\| ABDM or other rails are enabled on your deployment
	\| Print registration slip
⚫	\| Facility policy requires a paper token
	\|-
	\| Link national health ID
⚫	\| ABDM or other rails are enabled on your deployment
	\|}		\|}

	== API equivalent ==		== API equivalent ==

	<syntaxhighlight lang="http">~~POST /api/v1/patient/~~		<syntaxhighlight lang="http">
			POST /api/v1/patient/
	Content-Type: application/json		Content-Type: application/json
		⚫	</syntaxhighlight>

			<syntaxhighlight lang="json">
	{		{
	"name": "Jane Doe",		"name": "Jane Doe",
Line 97:		Line 89:
	"gender": "female",		"gender": "female",
	"phone_number": "+91XXXXXXXXXX"		"phone_number": "+91XXXXXXXXXX"
			}
⚫	}</syntaxhighlight>
			</syntaxhighlight>

	Exact payload shape depends on your Care version and facility questionnaire. Use the OpenAPI schema for your instance.		Exact payload shape depends on your Care version and facility questionnaire. Use the OpenAPI schema for your instance.

Line 103:		Line 97:

	Deployment-specific handling (unknown identity, emergency intake without ID, duplicate merges) is documented in playbooks, not here.		Deployment-specific handling (unknown identity, emergency intake without ID, duplicate merges) is documented in playbooks, not here.

	→ See [[Outpatient registration\|Outpatient registration]] for HMIS registration desk scenarios.

	{{Related}}		{{Related}}

Admin: OHC identity seed

2026-07-04T22:43:46Z

OHC identity seed

← Older revision		Revision as of 04:13, 5 July 2026
Line 3:		Line 3:
	\|domain=clinical		\|domain=clinical
	\|title=Create a patient		\|title=Create a patient
	\|summary=Registering a new patient in Care — the minimum path from search to a saved record ready for an encounter.
	\|order=1		\|order=1
	\|introduced=3.0		\|introduced=3.0
Line 12:		Line 11:
	This flow walks through registering a '''new patient''' in Care — the minimum path from search to a saved record ready for an encounter.		This flow walks through registering a '''new patient''' in Care — the minimum path from search to a saved record ready for an encounter.

	{{Info\|title=Prerequisite\|1=Read [[Concepts/~~Patient\|~~Patient]] to understand what a patient record contains and how identifiers work.}}		{{Info\|title=Prerequisite\|1=Read [[Concepts/Patient]] to understand what a patient record contains and how identifiers work.}}

	== Before you start ==		== Before you start ==
Line 35:		Line 34:

	{\| class="wikitable"		{\| class="wikitable"
⚫	! Field ~~!! Notes~~
	\|-		\|-
		⚫	! Field
⚫	~~\| Name \|~~\| Legal name; supports multiple given names where configured
			! Notes
	\|-		\|-
			\| Name
⚫	~~\| Date of birth \|~~\| Used for duplicate detection
		⚫	\| Legal name; supports multiple given names where configured
	\|-		\|-
			\| Date of birth
⚫	~~\| Sex \|~~\| Administrative sex for clinical context
		⚫	\| Used for duplicate detection
	\|-		\|-
			\| Sex
⚫	~~\| Phone \|~~\| Often required for OTP or follow-up contact
		⚫	\| Administrative sex for clinical context
	\|-		\|-
			\| Phone
⚫	~~\| Identifier \|~~\| Facility MRN or national ID when applicable
		⚫	\| Often required for OTP or follow-up contact
			\|-
			\| Identifier
		⚫	\| Facility MRN or national ID when applicable
	\|}		\|}

Line 67:		Line 73:

	{\| class="wikitable"		{\| class="wikitable"
⚫	! Next step ~~!! When~~
	\|-		\|-
		⚫	! Next step
⚫	~~\| Start an encounter \|~~\| Patient is at the desk for a visit ''(flow coming soon)''
			! When
	\|-		\|-
			\| Start an encounter
⚫	~~\| Print registration slip \|~~\| Facility policy requires a paper token
		⚫	\| Patient is at the desk for a visit ''(flow coming soon)''
	\|-		\|-
			\| Print registration slip
⚫	~~\| Link national health ID \|~~\| ABDM or other rails are enabled on your deployment
		⚫	\| Facility policy requires a paper token
			\|-
			\| Link national health ID
		⚫	\| ABDM or other rails are enabled on your deployment
	\|}		\|}

	== API equivalent ==		== API equivalent ==

	<syntaxhighlight lang="http">		<syntaxhighlight lang="http">POST /api/v1/patient/
	POST /api/v1/patient/
	Content-Type: application/json		Content-Type: application/json
⚫	</syntaxhighlight>

	<syntaxhighlight lang="json">
	{		{
	"name": "Jane Doe",		"name": "Jane Doe",
Line 89:		Line 97:
	"gender": "female",		"gender": "female",
	"phone_number": "+91XXXXXXXXXX"		"phone_number": "+91XXXXXXXXXX"
		⚫	}</syntaxhighlight>
	}
	</syntaxhighlight>

	Exact payload shape depends on your Care version and facility questionnaire. Use the OpenAPI schema for your instance.		Exact payload shape depends on your Care version and facility questionnaire. Use the OpenAPI schema for your instance.

Line 97:		Line 103:

	Deployment-specific handling (unknown identity, emergency intake without ID, duplicate merges) is documented in playbooks, not here.		Deployment-specific handling (unknown identity, emergency intake without ID, duplicate merges) is documented in playbooks, not here.

			→ See [[Outpatient registration\|Outpatient registration]] for HMIS registration desk scenarios.

	{{Related}}		{{Related}}

Admin: OHC identity seed

2026-07-04T22:31:18Z

OHC identity seed

New page

{{Doc header
|type=flow
|domain=clinical
|title=Create a patient
|summary=Registering a new patient in Care — the minimum path from search to a saved record ready for an encounter.
|order=1
|introduced=3.0
|concept=Concepts/Patient
|reference=References/Patient
}}

This flow walks through registering a '''new patient''' in Care — the minimum path from search to a saved record ready for an encounter.

{{Info|title=Prerequisite|1=Read [[Concepts/Patient|Patient]] to understand what a patient record contains and how identifiers work.}}

== Before you start ==

* You need a role with '''patient create''' permission (typically registration or front-desk staff).
* Know which '''identifiers''' your facility requires (MRN, national ID, phone-only intake, etc.).
* If your deployment enforces duplicate checks, have at least two identifiers ready (e.g. name + date of birth + phone).

== Steps ==

=== 1. Open patient search ===

From the facility dashboard, go to '''Patients''' → '''Search''' (or use the global patient search shortcut).

Search first — Care expects you to confirm the person is not already registered before creating a duplicate.

=== 2. Start registration ===

If no match is found, select '''Register new patient'''.

The registration form opens. Required fields depend on your facility's questionnaire configuration; the baseline set is:

{| class="wikitable"
! Field !! Notes
|-
| Name || Legal name; supports multiple given names where configured
|-
| Date of birth || Used for duplicate detection
|-
| Sex || Administrative sex for clinical context
|-
| Phone || Often required for OTP or follow-up contact
|-
| Identifier || Facility MRN or national ID when applicable
|}

=== 3. Complete demographics ===

Fill optional fields as required by your program — address, emergency contact, blood group, photo, etc.

If duplicate detection is enabled, Care may warn when a similar record exists. Resolve the warning before saving (merge, override with justification, or cancel).

=== 4. Save the record ===

Select '''Save''' (or '''Register''').

On success:

* A patient ID and facility MRN are assigned (if auto-generated).
* The patient profile opens.
* You can start an '''encounter''' or return to the queue.

== After creation ==

{| class="wikitable"
! Next step !! When
|-
| Start an encounter || Patient is at the desk for a visit ''(flow coming soon)''
|-
| Print registration slip || Facility policy requires a paper token
|-
| Link national health ID || ABDM or other rails are enabled on your deployment
|}

== API equivalent ==

<syntaxhighlight lang="http">
POST /api/v1/patient/
Content-Type: application/json
</syntaxhighlight>

<syntaxhighlight lang="json">
{
"name": "Jane Doe",
"age": 34,
"gender": "female",
"phone_number": "+91XXXXXXXXXX"
}
</syntaxhighlight>

Exact payload shape depends on your Care version and facility questionnaire. Use the OpenAPI schema for your instance.

== Edge cases ==

Deployment-specific handling (unknown identity, emergency intake without ID, duplicate merges) is documented in playbooks, not here.

{{Related}}