Skip to main content

Newborn Registration in Clinics: Separate Records, Twins and Name Changes

Register each newborn as an individual patient, even before a permanent name is chosen. Use a clear temporary naming convention, a distinct clinic identifier, attributable birth information and an explicit relationship to the mother or responsible adult. For twins, preserve each baby's separate identity and documented birth order. Add a later name to the existing record without losing earlier visits or confusing family relationships with consent authority.

By Bractis · Updated · 9 min read

For Indian clinics registering newborns and young infants, especially babies referred with 'Baby of' documents or attending alongside siblings.

The baby needs an individual record from the first encounter

A mother's record contains her own care history. It should not become a convenient container for the baby's examination, prescription or results. The baby needs an individual clinic identifier and encounter so later care can be followed without separating two people's information retrospectively.

A temporary label such as 'Baby of [recorded maternal name]' may help identify a newborn before naming, but it is not sufficient by itself. The label can recur, change or refer to more than one baby. Define the clinic's convention and make the individual identifier prominent for staff who handle the record.

The clinic record is also different from civil birth registration or a government identity record. Creating a patient file does not issue a birth certificate, verify legal parentage or establish every administrative fact. Requirements for those separate processes must be handled through the responsible authorities.

WHO's identification guidance supports explicit processes where standard identifiers are unavailable. Apply that principle without making urgent assessment wait for a permanent name or turning a temporary label into a substitute for individual identification.

Source: WHO: Patient Identification, Patient Safety Solutions

Capture birth information with its source and limits

Record the available birth date, time where relevant, place and source of the information. Distinguish a discharge document from a family recollection. If documents conflict, preserve the discrepancy for clinical review rather than selecting the value that makes the form easiest to complete.

Do not estimate gestational age or corrected age at reception. Those clinical interpretations belong to the responsible clinician using appropriate evidence. Similarly, an automated age display depends on the underlying birth information and its precision; an exact-looking counter is not proof that the input was verified.

Keep birth information connected to the infant's record. A maternal identifier can document a relationship, but it should not replace the infant's own identifier on a prescription, sample or report. Verify whose information is being displayed when navigating between linked family records.

Use the family's preferred and supported language for explanation where possible. Read back the recorded temporary name and identifying context without requiring a family to adopt a particular spelling or naming style solely for software convenience.

For twins, keep birth order and identity separate from arrival order

Twins can share a birth date, family contact, address and temporary 'Baby of' label. Those shared fields cannot distinguish them. Use each baby's individual record and the documented information that identifies that baby, with a clear unresolved state if the available papers do not establish the mapping.

Birth order is not the order in which the babies arrive at the clinic, appear in a queue or are entered into software. If a source labels them first and second born, preserve that source and verify how the local temporary naming convention maps to it. Do not guess the mapping from clothing, cot position or a screen's sort order.

FHIR R4 provides a multiple-birth field that can indicate membership of a multiple birth or, when represented as an integer, birth order. That distinction is useful: 'part of twins' does not identify which twin. It is a data-model example, not a guarantee of any vendor's behaviour.

Run the distinction through the complete visit. Check the infant's encounter, report attachment, clinical document and later return visit. A correct registration table does not help if a document-generation step silently reuses the sibling's details.

On a narrow screen, scroll the table horizontally to read all columns.

Fictional twins: shared family facts do not replace individual identity
FieldInfant NB-0041Infant NB-0042
Temporary labelBaby of Meera, first-born per sourceBaby of Meera, second-born per source
Individual clinic IDNB-0041NB-0042
Birth record contextSource records 06:42Source records 06:45
Family contactSame agreed family contactSame agreed family contact
Later chosen nameAdded to NB-0041 after verificationAdded to NB-0042 after verification
Unresolved mappingHold and review if evidence conflictsDo not infer from arrival order

Source: HL7 FHIR R4: Patient data definitions

Separate relationships, contact arrangements and decision authority

The adult bringing a newborn may be a parent, relative or another caregiver. Record the stated relationship and the relevant contact arrangement, but do not treat every accompanying adult as automatically authorised for every decision or disclosure.

Keep several questions separate: who supplied the information, who can be contacted, who is paying, who receives documents and who has the relevant authority for the decision at hand. These roles may overlap but are not interchangeable. Uncertainty about authority needs an appropriate clinical or administrative review.

A family link should not expose the mother's full history to everyone who can access the baby's record. Share or display information according to role, purpose and the clinic's applicable confidentiality arrangements. A convenient household view is not a general permission to reveal every member's records.

If the contact person changes, preserve the baby's identity and update the contact relationship through the normal process. Do not create a new infant record merely because another adult now brings the child or a different phone is used.

Rename the existing patient without breaking continuity

When the family supplies a chosen name, first confirm which baby the name belongs to. This is especially important for twins, similarly named siblings and documents carried together. Verify the relationship between the new name and the existing infant identifier before changing the displayed name.

Retain the earlier temporary name as historical or alias information where the system supports it. Staff should still be able to find the earlier 'Baby of' visit without creating a fresh patient. Record who made the change, when and what information supported it.

Do not make old issued documents appear to have been created under information that was not known then. The current patient name can change while historical document content remains attributable to its original issue, with an appropriate explanatory link or correction if required.

Review associated results and planned follow-up. A new name should not move a result to the sibling's chart or detach a pending task. Explain to the family which clinic identifier continues to locate the child's care.

Test the family workflow with synthetic twins

Ask the software team to create two fictional newborn records linked to the same family contact. Give them separate birth context and visits. Then add a later name to one baby and confirm that search finds the correct earlier record under both the current and retained temporary information.

Attach a clearly labelled fictional report to each child and inspect the output. A test should reveal whether staff can tell the intended infant before saving, whether the relationship view is clear and whether a correction preserves a traceable history.

Introduce an unresolved source discrepancy deliberately. The expected result is a visible review route, not a silently chosen birth order. Also test a family member arriving with the other twin's paper; possession of a document alone must not decide the mapping.

Keep the pilot focused on administrative identity and continuity. It does not validate neonatal assessment, prescribing, immunisation schedules or safeguarding decisions. Those require the responsible clinical service and appropriate professional review.

Fictional naming visit: preserve two histories through one family contact

Two babies initially attend with temporary labels and identifiers NB-0041 and NB-0042. Their discharge information distinguishes first-born at 06:42 and second-born at 06:45. At a later visit, the family provides a name for NB-0042 and brings both folders. Reception verifies the link to the second-born child's existing record rather than renaming whichever chart appeared first in the search. The clinic retains the earlier temporary label as history, confirms that NB-0042's earlier result and pending review remain attached, and leaves NB-0041 unchanged. If the source documents had not resolved which baby was which, staff would have escalated the mapping instead of inventing an order. These names, times and identifiers are fictional.

Newborn identity and renaming checklist

Use these prompts in your clinic’s own notes. Record the result, responsible person and next action for each item.

Individual identity
Does each baby have a separate record and identifier, including before a permanent name is chosen?
Birth evidence
What supports date, time and multiple-birth mapping, and how are conflicts preserved?
Adult roles
Who supplied information, who may be contacted and which authority questions need review?
Name continuity
Will later naming preserve earlier visits, document history, results and follow-up under the same infant identity?

Questions doctors ask

Can the baby's consultation be entered under the mother's record?

Keep the baby as an individual patient with a separate encounter. Link the relevant family relationship where appropriate, but do not mix the baby's clinical history with the mother's record.

What if the baby has not been named yet?

Use the clinic's approved temporary naming process with a distinct infant identifier and attributable birth context. A later chosen name should be linked to that existing record after verification.

Can a shared phone and birth date distinguish twins?

No. Those details may be identical. Preserve each child's individual identifier and documented multiple-birth mapping, and do not infer birth order from queue order, clothing or the first search result.

Does a family contact automatically have authority to consent?

No. Contactability, relationship, payment and decision authority are separate questions. Record the relevant roles and route uncertainty to the responsible clinician or authorised team under the applicable requirements.

Should we create a new record when the permanent name is added?

Usually the task is to update the correctly identified existing infant record while preserving the earlier label and history. Verify the specific baby first and inspect linked results and pending tasks after the change.

Sources and scope

Updated on . This article combines the cited references with Bractis’s original workflow analysis and illustrative examples. Product capabilities depend on the configured scope. No independent clinical or legal review is claimed.

  • WHO: Patient Identification, Patient Safety Solutions

    May 2007 international aide-memoire; relevant recommendations and limits read 25 October 2026. Supports multiple identifiers and a process for same-name or unidentified patients. The fictional clinic procedures are original, not an Indian statutory identity rule.

  • HL7 FHIR R4: Patient data definitions

    Version 4.0.1, relevant name, contact, birth-date and multiple-birth definitions accessed 25 October 2026. A data model, not proof of a clinic product's implementation, guardian authority or an Indian mandatory registration checklist.

Try the workflow
with Bractis.

Bring a synthetic twin scenario to a Bractis demonstration. Follow separate records, shared contact details, a later name change and a pending result, recording which relationship and history functions are actually supported.

Request a clinic demo