DiagnosticReport.performer Definition

XMLWordPrintableJSON

    • Type: Change Request
    • Resolution: Persuasive
    • Priority: Medium
    • FHIR Core (FHIR)
    • DSTU2
    • Orders & Observations
    • STU
    • DiagnosticReport
    • Hide

      See event pattern discussion in WorkFlow [#11428] - apply to DR-

      performer 0..*
      role 0..1 CodeableConcept (steal vocabulary from Procedure)
      actor 1..1 Reference(Practitioner|RelatedPerson|Patient|Device|Organization)
      onBehalfOf 0..1 Organization

      Show
      See event pattern discussion in WorkFlow [#11428] - apply to DR- performer 0..* role 0..1 CodeableConcept (steal vocabulary from Procedure) actor 1..1 Reference(Practitioner|RelatedPerson|Patient|Device|Organization) onBehalfOf 0..1 Organization
    • Eric Haas/Jose Costa-Teixera: 7-0-5
    • Enhancement
    • Non-compatible
    • DSTU2

      Currently the DiagnosticReport.performer is ambiguous on its scope. The name implies a variety of participants (responsible, author, verifier, etc.) while the definition appears to narrow it to the responsible person and/or organization for the report. The suggestion is to either change the name from "performer" to "responsible party", or to open the description to fit the name and introduce the abiltiy to effectively type the participation of the performer on this diagnostic report. The first approach will require us to add new attributes to the resource as other performers become relevant (likely for verifier, author, ), while the second approach only requires in a change to the vocabulary supporting the participation.

            Assignee:
            Unassigned
            Reporter:
            Hans Buitendijk
            Hans Buitendijk
            Watchers:
            2 Start watching this issue

              Created:
              Updated:
              Resolved: