MANSOQ Knowledge
← Knowledge library

NPHIES

Handle patient, episode and message identity correctly

Keep clinical identities and transport identities stable for the operation they represent.

Current source · source reviewed · 6 min read

Before you begin

1. Validate the patient identifier type

Use the identifier namespace supported for the configured NPHIES transaction. A locally captured identifier is not automatically carriable on the wire.

2. Create a separate newborn record

A newborn must remain a distinct patient with its own provider MRN. Resolve the mother-policy relationship without reusing the mother’s patient identity.

3. Preserve the episode relationship

When services are added to an episode, retain the locally unique episode identifier and separate claim/invoice relationships.

4. Let the persisted exchange own transport identity

Use the stored bundle, message-header and claim identifiers during a permitted transport replay. Do not recreate them outside the supported exchange service.

Border-only identification

The guide describes routing an unsupported border-only submission context to administrative resolution rather than dropping the patient or inventing an accepted identifier.

Different identifiers answer different questions

Patient/MRN identifies the clinical subject; episode identifies the care episode; invoice/claim identifies financial records; bundle/header/correlation identifies exchange. Record the relevant type explicitly in support notes.

Troubleshooting

A duplicate-identifier response follows a transport retry

Inspect whether it is the known idempotent-replay contradiction and retain the attempt. Escalate with original bundle/correlation identifiers rather than creating a new patient or charge.

Source evidence

References are pinned to the private MANSOQ source repository. Repository access is required to open these links.