Mortuary Management Software in India: Test Identity and Release

Sources checked · Recheck due

Place an unopened synthetic release packet on the demonstration desk. Ask the vendor to prove every condition in it by walking backward through the record.

If identity, authority, custody, location, or property cannot be proved, the path stops. The software must preserve why.

Takeaways

  • Start at the release desk and prove every condition backward.
  • Keep identity status, unique reference, storage location, and custody distinct.
  • Make uncertainty visible and block silent merges or releases.
  • Test custody, property, and downtime without using real personal information.

This is a software-evaluation worksheet, not forensic, legal, clinical, police, or mortuary-operating advice. Qualified local owners define the applicable process and release authority.

Begin with the release packet

Delhi State Health Mission’s support-services SOP describes checking particulars, recipient identity, refrigerated location, register sign-out, and recipient details in its process. Medico-legal cases have different authority in that SOP.

Configure synthetic pathways selected by the hospital’s qualified owners. A release packet may need current identity status, release authority, recipient verification, custody status, property disposition, time, responsible staff, and unresolved holds. The product should block release when a required condition is absent, but authorised people remain responsible for the decision.

Leave one condition unresolved. Confirm that the product records the stop without converting uncertainty into a negative answer or an approval.

Work backward through four facts

A mortuary record needs at least four concepts that should never collapse into one field:

FactWhy it stays separate
identity statusknown, possible, unknown, or under authorised review
unique mortuary referencestable local record key, not proof of identity
physical locationcurrent cabinet, bay, examination area, or authorised movement
custody statusresponsible role or agency and the supporting event

A correction to one fact must not silently rewrite the others. Keep the earlier value, reason, actor, time, and evidence source.

The DGHS 2025 Hospital Manual includes mortuary-service guidance on dignity, secured information, premises privacy, staff sensitisation, and infrastructure. It is an official operational reference, not a complete specification for every facility.

Take the uncertain-identity branch

Create a synthetic record with incomplete identity information. Give it a unique local reference, record the source and receiving roles, list attached documents, capture property under the approved process, and assign a storage location. Then add a second record with a similar invented name.

Try to merge them. The system should require an authorised decision and retain both source histories. It must not confirm identity from spelling, mobile number, photograph, or demographic similarity alone.

ESIC’s 2025 hospital SOPs describe body handling, identification, storage logs, release documentation, intake records, and property handling in its scheme setting. A hospital must map current local rules and authorities rather than copying that workflow blindly.

Retrace every movement

Move an invented record from receipt to storage, from storage to an authorised work area, and back to a different cabinet. Ask for:

  • release from the prior custodian;
  • acceptance by the next custodian;
  • departure and arrival times;
  • source and destination locations;
  • reason and supporting authority;
  • unresolved discrepancy handling.

Swap two cabinet labels in the test environment. The product should expose the conflict and prevent an ordinary release until authorised owners resolve it.

Open the property lane separately

Create synthetic property items, including one sealed item, one high-value item, and one item found after receipt. Record description, package or seal state, source, custodian, storage point, movement, and recipient evidence under approved policy. Do not place sensitive property details on screens visible to visitors.

The software should link property to the mortuary record without treating that link as proof of identity. Try transferring the record without transferring the property and confirm that an exception remains open.

Put the packet through a paper shift

During a tabletop outage, receive one synthetic record, move another, log a temperature or equipment exception under local procedure, and prepare but do not complete a release. When the system returns, enter events in their original sequence. Detect duplicate references and a cabinet conflict. Preserve the paper source under policy.

Return to the unopened release packet after reconciliation. Score whether every condition now points to a retained source, whether conflicts remain visible, and whether the final decision belongs to the authorised role. Never test with real deceased-person or family information unless the authorised operational programme has approved it.

Patient Square does not publish a standalone mortuary module. Do not infer body tracking, cabinet monitoring, forensic workflow, police connectivity, property custody, or release controls from Hospital Copilot. A procurement should name every local workflow, role, document, device, interface, exception, report, and acceptance drill.

FAQ

Common questions

What does mortuary management software record?

Scope may include receipt time and source, identity status, unique reference, tags, storage location, custody changes, property, temperature or equipment logs, medico-legal status, documents, viewing or examination events, release authority, recipient, and reports. Verify local requirements and exact quoted scope.

Can software confirm the identity of a deceased person?

No. Authorised professionals and agencies follow the applicable identification process. Software can preserve identifiers, evidence sources, uncertainty, decisions, and corrections; it should never turn a possible match into a confirmed identity on its own.

How should software handle medico-legal and non-medico-legal cases?

The hospital's qualified legal, forensic, and administrative owners define separate workflows, authorities, documents, and release conditions under current rules. The product should enforce the configured separation and retain overrides rather than applying a generic national shortcut.

Does Patient Square sell mortuary management software?

Patient Square does not publish a standalone mortuary module. Do not assume that body tracking, cold-storage monitoring, medico-legal workflow, property custody, police interfaces, or release controls are included in Hospital Copilot.

Sources

  1. DGHS, MoHFW: Hospital Manual, 2025.
  2. ESIC: Standard Operating Procedures for Hospitals, 2025.
  3. Delhi State Health Mission: Support Services SOP.