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

Support Encounter.serviceType history

    XMLWordPrintableJSON

Details

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

      The ServiceType property in Encounter has already been updated in R5 to be consistent with the Appointment property of the same name and cardinality.

      The history portion of your request is covered through the new EncounterHistory resource which is able to track this information.

       

      Show
      The ServiceType property in Encounter has already been updated in R5 to be consistent with the Appointment property of the same name and cardinality. The history portion of your request is covered through the new EncounterHistory resource which is able to track this information.  
    • Reinhard Egelkraut/Joe Kelly: 6-0-0
    • Clarification
    • Non-substantive

    Description

      The patient service changes throughout an Encounter, currently only one ServiceType is supported and, although . documentation is a little unclear, I believe it refers to admission service. It is just as important to capture the changes in service in a similar way to changes in class. Several clinical quality metrics will rely on the discharge service to follow-up on patient care continuation. Can you evaluate adding a serviceType history element?

      Attachments

        Activity

          People

            Unassigned Unassigned
            gabbyesp Gabriela Espinosa (Inactive)
            Watchers:
            2 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved: