Description
Record explicit referral-recipient receipt identifiers.
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 explicit referral-recipient receipt identifiers.
When to use this tool
Use Midwifery Referral Receipt Tag when you already have referralId, recipientId, receiptRecordId and need to record explicit referral-recipient receipt identifiers.
How to use the tool and how it works
- Enter referralId, recipientId, receiptRecordId. Use the units and conventions below.
- Run the tool. Correct any format, range, or cross-field input error before interpreting the output.
- Read token. Use the output convention below.
Enter referralId, recipientId, receiptRecordId 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 field | Meaning and units | Accepted input |
|---|---|---|
| referralId | Referral Id | Required. Text; minimum UTF-16 length 1; maximum UTF-16 length 8192. |
| recipientId | Recipient Id | Required. Text; minimum UTF-16 length 1; maximum UTF-16 length 8192. |
| receiptRecordId | Receipt Record Id | Required. Text; minimum UTF-16 length 1; maximum UTF-16 length 8192. |
| Output field | Interpretation | Returned shape |
|---|---|---|
| token | Token | Required. Text; maximum UTF-16 length 8192. |
{
"input": {
"referralId": "REF17",
"recipientId": "TEAM3",
"receiptRecordId": "ACK2"
},
"output": {
"token": "[\"REF17\",\"TEAM3\",\"ACK2\"]"
}
}Limitations and assumptions
- The result records supplied values without assessing referral acceptance or care transfer. 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
Similar or alternative tools
- Midwifery Continuity Contact Label
Record explicit provider and continuity-group identifiers for a contact.
- Postnatal Mother Infant Pair Key
Record an explicit maternal/infant pair for a postnatal contact.