Skip to content

Main content

Postnatal Mother Infant Pair Key

Record an explicit maternal/infant pair for a postnatal contact without verifying identities or relationships.

Loading tool…

Description

Record an explicit maternal/infant pair for a postnatal contact.

Midwifery records link contact identities, referrals, translated documents, equipment dates and user-preferred formats. A recorded receipt or listed format differs from actual service availability. Calendar margins and kit counts preserve supplied records without establishing readiness, appropriate response time or clinical need.

Record an explicit maternal/infant pair for a postnatal contact.

When to use this tool

Use Postnatal Mother Infant Pair Key when you already have maternalRecordId, infantRecordId, contactId and need to record an explicit maternal/infant pair for a postnatal contact.

How to use the tool and how it works

  1. Enter maternalRecordId, infantRecordId, contactId. Use the units and conventions below.
  2. Run the tool. Correct any format, range, or cross-field input error before interpreting the output.
  3. Read token. Use the output convention below.

Enter maternalRecordId, infantRecordId, contactId using the field constraints below. Encode these values, in exactly that order, as a JSON array and return the serialized array as text in token. String values are preserved without trimming or external terminology lookup.1

Input fieldMeaning and unitsAccepted input
maternalRecordIdMaternal Record IdRequired. Text; minimum UTF-16 length 1; maximum UTF-16 length 8192.
infantRecordIdInfant Record IdRequired. Text; minimum UTF-16 length 1; maximum UTF-16 length 8192.
contactIdContact IdRequired. Text; minimum UTF-16 length 1; maximum UTF-16 length 8192.
Output fieldInterpretationReturned shape
tokenTokenRequired. Text; maximum UTF-16 length 8192.
json
{
  "input": {
    "maternalRecordId": "M17",
    "infantRecordId": "I17",
    "contactId": "C3"
  },
  "output": {
    "token": "[\"M17\",\"I17\",\"C3\"]"
  }
}

Limitations and assumptions

  • The result records supplied values without verifying identities or relationships. Sources and asserted relationships are not independently authenticated.
  • Inputs must satisfy both the field types and the cross-field conditions above. Invalid input causes an error; a successful false flag or documented placeholder is a different result.

Alternative or Complementary methods

Review original contact, referral, equipment and education records when actual delivery or readiness matters. Preserve requested language and format preferences; the local count, date or membership check does not verify the broader care workflow.

References

  1. Calculation and input contract: midwifery/postnatal-mother-infant-pair-key — tool.io

Similar or alternative tools