FHIR Chat · Venue Details · australia-child-health

Stream: australia-child-health

Topic: Venue Details


view this post on Zulip Shovan Roy (Feb 07 2019 at 23:35):

Hi All,

I'm in the process of drafting profiles for few Health Interactions. As decided before, each health interaction is represented as a document (FHIR Composition). Majority of the sections are modeled with Observation resource.
Majority of the health interactions requires mapping the venue where the activity has happened.

Examples:
1. While recording Blood Spot Screening and Hearing Screening, we have to capture where the screening has happened.
2. While recording Health Check Assessments, we have to capture where the examinations/assessments has happened.
3. While drafting Newborn Delivery (birth) Health interaction, we have to capture the location of birth. ( atm, we have modeled this as Patient.birthPlace extn). But we want to follow a consistent approach

To profile the Venue, I can think of the following options:
Option 1: Use Composition.encounter.location, please note the encounter resource here is used for administrative purpose only
Option 2: Use an extension in the Observation profile to capture location where the Observation/Procedure was made
Option 3: Use Observation.performer(Organization)

My preference is to use Option 1. However Option 2 and 3 probably gives greater flexibility to capture individual locations.

Any suggestion?

view this post on Zulip Brett Esler (Feb 12 2019 at 04:38):

Think there is an issue in mixing recording a question on performance of an action (as an Observation) and the context of the procedure itself - elements of Observation are about the context of the recording the answer to the question - i.e. encounter where the question was asked and the performer as asker of the question - not the performer of the procedure

view this post on Zulip Brett Esler (Feb 12 2019 at 04:47):

if you really want to record the Procedure details then could use Procedure resource; Procedure.notDone to indicate it was or was not done; Procedure.subject is child; Procedure.context is encounter (with Organization.serviceProvider for organization providing encounter) ; performedDateTime for timing of procedure; Procedure.location for the physical location

view this post on Zulip Shovan Roy (Feb 13 2019 at 23:48):

Thanks @Brett Esler , what is your view on using Composition.encounter.location. I want to use this as a common approach which is applicable to all documents in NCDHC. meas this should be usable even we are not using any Observation/Procedure in the composition.


Last updated: Apr 12 2022 at 19:14 UTC