The diagnosticRequest should distinguish between requested performer and performer - 2016-09 core #283

XMLWordPrintableJSON

    • Type: Change Request
    • Resolution: Not Persuasive with Modification
    • Priority: Medium
    • FHIR Core (FHIR)
    • DSTU2
    • FHIR Infrastructure
    • DiagnosticRequest (see ServiceRequest) [deprecated]
      Request Pattern
    • Hide

      Will add a usage note that the request does not capture information about the actual execution (i.e. actual code, actual performer, actual execution time, etc.) and that this is captured on a separate resource pointing to this one.

      Lloyd to check that complex performer extension exists

      Show
      Will add a usage note that the request does not capture information about the actual execution (i.e. actual code, actual performer, actual execution time, etc.) and that this is captured on a separate resource pointing to this one. Lloyd to check that complex performer extension exists
    • Jose Costa Teixeira/Eric Haas: 9-0-0
    • Enhancement
    • Non-substantive
    • DSTU2

      Comment:

      Since the whole resource represents a request and performer may not be finalized yet, I think we should distinguish between the performer element found on other resources that know the performer and this resources performer by calling it requestedPerformer.

      To add to that idea, does it make sense to have the ability to specify multiple requestedPerformers?

      Summary:

      The diagnosticRequest should distinguish between requested performer and performer

            Assignee:
            Unassigned
            Reporter:
            Danielle Friend
            Watchers:
            3 Start watching this issue

              Created:
              Updated:
              Resolved: