Description
Record an explicitly asserted maternal/infant record link.
Maternity records distinguish estimated dates, recorded gestational age, postpartum calendar time and linked maternal/infant identifiers. Completed weeks plus remaining days is a representation of supplied days, not a dating estimate. Image planes, channels and birth-order labels depend on verified clinical records and source conventions.
Record an explicitly asserted maternal/infant record link.
When to use this tool
Use Maternity Record Maternal Infant Link when you already have maternalRecordId, infantRecordId, assigningSource and need to record an explicitly asserted maternal/infant record link.
How to use the tool and how it works
- Enter maternalRecordId, infantRecordId, assigningSource. 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 maternalRecordId, infantRecordId, assigningSource 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 |
|---|---|---|
| maternalRecordId | Maternal Record Id | Required. Text; minimum UTF-16 length 1; maximum UTF-16 length 8192. |
| infantRecordId | Infant Record Id | Required. Text; minimum UTF-16 length 1; maximum UTF-16 length 8192. |
| assigningSource | Assigning Source | 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": {
"maternalRecordId": "M17",
"infantRecordId": "I17",
"assigningSource": "System A"
},
"output": {
"token": "[\"M17\",\"I17\",\"System A\"]"
}
} Limitations and assumptions
- The result records supplied values without identity resolution or relationship verification. 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
Consult the original dating, visit, imaging and birth records for a substantive question. Preserve each estimate's source and measurement convention; local date differences and labels do not choose a pregnancy date or assess maternal/fetal health.
References
Similar or alternative tools
- Fetal Monitor Twin Channel Label
Record an explicitly assigned fetus/channel association.
- Due Date Source Tag
Record explicit due-date text and its dating source.