Toggle menu
Toggle preferences menu
Toggle personal menu
Not logged in
Your IP address will be publicly visible if you make any edits.

Flows/Create a patient: Difference between revisions

From OHC Network Wiki
More languages
Content deleted Content added
OHC identity seed
 
OHC identity seed
Tag: Reverted
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}}