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

Request for a "born" (or "unborn") extension for Patient resource for a distinct fetal record

    XMLWordPrintableJSON

Details

    • Icon: Change Request Change Request
    • Resolution: Persuasive with Modification
    • Icon: Medium Medium
    • FHIR Core (FHIR)
    • R5
    • Patient Administration
    • Patient
    • Hide

      The joint PA/PC group agreed that:

      • Patient is the best resource to use (rather than BodyStructure)
      • An extension to indicate fetal status is appropriate, but should not be a modifier extension.
      • An invariant will not be added in the extension, but IGs may add a constraint as part of a profile.
      • A born extension will be added to the base specification:

      extension.bornStatus  0..1 code (born/unborn/fetal-demise/unknown) (required)

      Show
      The joint PA/PC group agreed that: Patient is the best resource to use (rather than BodyStructure) An extension to indicate fetal status is appropriate, but should not be a modifier extension. An invariant will not be added in the extension, but IGs may add a constraint as part of a profile. A born extension will be added to the base specification: extension.bornStatus   0..1 code (born/unborn/fetal-demise/unknown) (required)
    • Michael Tan / Brian Postlethwaite : 15-0-1
    • Enhancement
    • Compatible, substantive
    • R5

    Description

      We are looking to recognize/reference a "born" extension (Boolean) for the Patient resource that could indicate that there is an active record for a not yet born patient. Creation of a distinct record prior to delivery allows for orders (medications, blood products, imaging studies) intended for the newborn just after birth to be placed prior to delivery (while the subject is still a fetus) and allow for relevant conditions and observations for the fetus to be captured so that they are immediately available for a record of a newborn. It is essential that this record be distinct from the maternal record as the medications, blood products, etc... are intended for the newborn and not for the mother.
      Use cases are outlined in the Pregnancy, Fetal, and Child Health Record- Domain Analysis Model. See FHIR Resource modeling around page 35.

      lminne has modeled a number of options that have been proposed in simplifier.net: https://simplifier.net/internationalbirthandchildmodel

      The combination of using the Patient.active indicator along with a "born" extension - http://hl7.org/fhir/StructureDefinition/patient-born - could allow for the following scenarios:
      if active=true, born=false --> active fetal record
      if active=false, born=false --> indicates fetal demise (or simply that the record is no longer in use and will not transition to a liveborn patient record)
      if active: true, born: true --> active (newborn) record [Note: presence of a birthdate could indicate that born=true

      Note that some have proposed that "born" could instead be an "unborn" indicator as a Boolean.

      Please see the Zulip discussion on this topic as well. Thank you.

      Attachments

        Activity

          People

            brian.postlethwaite Brian Postlethwaite
            michael_padula Michael Padula
            Lilian Minne, Michael Padula
            Watchers:
            1 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved: