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

Differentiate performer (individual) from performer (role)

    XMLWordPrintableJSON

Details

    • Icon: Change Request Change Request
    • Resolution: Not Persuasive
    • Icon: Highest Highest
    • US Core (FHIR)
    • 4.1.0 [deprecated]
    • Cross-Group Projects
    • STU
    • US Core Screening Response Observation Profile [deprecated]
    • 10.122.1.1
    • Hide

      Background:

      The current profile reflects the community consensus minimum expectations for the Observation resource to record, search, and fetch retrieve observations that represent the questions and responses to form/survey and assessment tools such as the Protocol for Responding to and Assessing Patients’ Assets, Risks, and Experiences (PRAPARE) Survey. It is expected and encouraged that domain specific or implementation specific profile will build on the profile adding other elements and extensions for their use cases.

      Reasoning:

      Adding a Must Support for observation.performer may impose an undo burden on implementers whose systems do not support roles. These profile do not preclude or prevent implementations based on them from adding other profile elements to meet their use cases.

      Proposed Changes:

      There is no action needed by US Core on this issue.

      Show
      Background: The current profile reflects the community consensus minimum expectations for the Observation resource to record, search, and fetch retrieve observations that represent the questions and responses to form/survey and assessment tools such as the Protocol for Responding to and Assessing Patients’ Assets, Risks, and Experiences (PRAPARE) Survey. It is expected and encouraged that domain specific or implementation specific profile will build on the profile adding other elements and extensions for their use cases. Reasoning: Adding a Must Support for observation.performer may impose an undo burden on implementers whose systems do not support roles. These profile do not preclude or prevent implementations based on them from adding other profile elements to meet their use cases. Proposed Changes: There is no action needed by US Core on this issue.
    • Brett Marquard/Eric Haas: 16-0-1

    Description

      The Observation includes a Must Support for observation.performer. However, there is not a corresponding requirement to indicate a performer.role, i.e., what role the performer plays in the care of the patient (self, RelatedPerson caregiver, etc. etc.). As specified, a performer may be an individual without a specified role or a role without identifying an individual - both should be required (or at least available to specify for later inclusion as Must Support as systems support the distinction).

      Attachments

        Activity

          People

            Unassigned Unassigned
            feisenberg Floyd Eisenberg
            Floyd Eisenberg
            Watchers:
            1 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved: