How to associate an observation to a process or activity

XMLWordPrintableJSON

    • Type: Question
    • Resolution: Considered - Question answered
    • Priority: Very High
    • FHIR Core (FHIR)
    • R4
    • Orders & Observations
    • Observation
    • Hide

      From OO discussion on 12/10/2020 (copied from comments):

      We don't need / should not add any element to Observation for this.

      ActivityDefinition and PlanDefinition are not processes or activities, they are protocol definitions.

      Protocols are defined once (e.g. 1. collect one sample; 2. set temperature at 15C; 3. measure viscosity; 4. dissolve in 200 ml water; 5. check color... "

      A specific inspection is not a PlanDefinition, it created as a xxxRequest (serviceRequest?)

       3 ways of linking, no change required:

      1. Observation is basedOn a ServiceRequest, which is the action plan for a given batch). ServiceRequest instantiates PlanDefinition or ActivityDefinition.

      2. the standard extension workflow-instantiatesCanonical can be used if the instance of the request does not need to be created

      3. Using a Task instead of serviceRequest in 1. above

      Show
      From OO discussion on 12/10/2020 (copied from comments): We don't need / should not add any element to Observation for this. ActivityDefinition and PlanDefinition are not processes or activities, they are protocol definitions. Protocols are defined once (e.g. 1. collect one sample; 2. set temperature at 15C; 3. measure viscosity; 4. dissolve in 200 ml water; 5. check color... " A specific inspection is not a PlanDefinition, it created as a xxxRequest (serviceRequest?)  3 ways of linking, no change required: 1. Observation is basedOn a ServiceRequest, which is the action plan for a given batch). ServiceRequest instantiates PlanDefinition or ActivityDefinition. 2. the standard extension  workflow-instantiatesCanonical  can be used if the instance of the request does not need to be created 3. Using a Task instead of serviceRequest in 1. above

      The observation resource can be based on different plans however neither ActivityDefinition nor PlanDefinition are in the constrained list.

       

      The use case relates to an inspection, lets use the example of validating the temperature in a cold storage facility.  Originally in Jira FHIR-29402 was created to resolve this however in discussion it was agreed it was incorrect, but in reviewing the constrained lists I am not understanding how we would accomplish the goal of recording an observation relating to an inspection

       

      If Observation.basedOn needs to be extended to include ActivityDefinition or PlanDefinition then please action FHIR-29697 - Extend Observation.basedOn otherwise, please explain how we make observations relating to inspections and I will retract the JIRA.

       

      The reason I made it a very high priority is it's needed for R4B

            Assignee:
            Unassigned
            Reporter:
            Peter Bomberg
            Peter Bomberg, Rik Smithies, Smita Hastak
            Watchers:
            2 Start watching this issue

              Created:
              Updated:
              Resolved: