Description
Record explicit due-date text and its dating source.
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 explicit due-date text and its dating source.
When to use this tool
Use Due Date Source Tag when you already have pregnancyRecordId, dueDateText, datingSource and need to record explicit due-date text and its dating source.
How to use the tool and how it works
- Enter pregnancyRecordId, dueDateText, datingSource. 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 pregnancyRecordId, dueDateText, datingSource 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 |
|---|---|---|
| pregnancyRecordId | Pregnancy Record Id | Required. Text; minimum UTF-16 length 1; maximum UTF-16 length 8192. |
| dueDateText | Due Date Text | Required. Text; minimum UTF-16 length 1; maximum UTF-16 length 8192. |
| datingSource | Dating 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": {
"pregnancyRecordId": "P17",
"dueDateText": "2027-01-15",
"datingSource": "Recorded estimate A"
},
"output": {
"token": "[\"P17\",\"2027-01-15\",\"Recorded estimate A\"]"
}
}Limitations and assumptions
- The result records supplied values without estimating or adjudicating a due date. 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.
- Maternity Record Maternal Infant Link
Record an explicitly asserted maternal/infant record link.