Uploaded image for project: 'FHIR Specification Feedback'
  1. FHIR Specification Feedback
  2. FHIR-41244

Clarify description of both Patient.multipleBirthInteger and Extension: Patient Multiple Birth Total (R5+)to include fetal losses

    XMLWordPrintableJSON

Details

    • Icon: Change Request Change Request
    • Resolution: Persuasive
    • Icon: Medium Medium
    • FHIR Core (FHIR)
    • R4
    • Patient Administration
    • Patient
    • Hide

      We will update the description of Patient.multipleBirth and the patient-multipleBirthTotal extension to indicate that fetal losses are included in the counts.  

      Patient.multipleBirth[x]

      Definition: Indicates whether the patient is part of a multiple (boolean) or indicates the actual birth order (integer).  This count is relative to the total of live births and fetal losses.

      Comments:  Where the valueInteger is provided, the number is the birth number in the sequence. E.g. The middle birth in triplets would be valueInteger=2 and the third born would have valueInteger=3. If a boolean value was provided for this triplets example, then all 3 patient records would have valueBoolean=true (the ordering is not indicated).  If the first fetus was a loss, the second and third births would still be represented as valueInteger=2 and valueInteger=3, where you may have a Patient with valueInteger=1 with a fetal-delivery-status extension indicating fetal demise.

      patient-multipleBirthTotal 

      Definition: Where a patient is a part of a multiple birth, this is the total number of births that occurred in this pregnancy.  This includes all live births and all fetal losses.

       

       

       

      Show
      We will update the description of Patient.multipleBirth and the patient-multipleBirthTotal extension to indicate that fetal losses are included in the counts.   Patient.multipleBirth [x] Definition : Indicates whether the patient is part of a multiple (boolean) or indicates the actual birth order (integer).  This count is relative to the total of live births and fetal losses. Comments :  Where the valueInteger is provided, the number is the birth number in the sequence. E.g. The middle birth in triplets would be valueInteger=2 and the third born would have valueInteger=3. If a boolean value was provided for this triplets example, then all 3 patient records would have valueBoolean=true (the ordering is not indicated).  If the first fetus was a loss, the second and third births would still be represented as valueInteger=2 and valueInteger=3, where you may have a Patient with valueInteger=1 with a fetal-delivery-status extension indicating fetal demise. patient-multipleBirthTotal   Definition: Where a patient is a part of a multiple birth, this is the total number of births that occurred in this pregnancy.  This includes all live births and all fetal losses.      
    • Brian Postlethwaite / Sonja Ziegler : 21-0-0
    • Enhancement
    • Non-substantive

    Description

      The description of both Patient.multipleBirthInteger and Extension: Patient Multiple Birth Total are ambiguous as they do not specify whether or not they include fetal losses as well as live births.

      We recommend updating as follows:

      • Patient.multipleBirthInteger (https://loinc.org/73771-8/) "The order born in the delivery, live born or fetal death (1st, 2nd, 3rd, 4th, 5th, 6th, 7th, etc.). All live births and fetal losses are included."
      • Extension: Patient Multiple Birth Total (R5+) (https://loinc.org/57722-1/) "The number of fetuses delivered live or dead at any time in the pregnancy regardless of gestational age or if the fetuses were delivered at different dates in the pregnancy."

      Attachments

        Activity

          People

            Unassigned Unassigned
            minigrrl Sarah Gaunt
            Watchers:
            5 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved: