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

When would Task.reasonReference be a ServiceRequest?

    XMLWordPrintableJSON

Details

    • Icon: Change Request Change Request
    • Resolution: Persuasive with Modification
    • Icon: Highest Highest
    • US Da Vinci CDex (FHIR)
    • current
    • Patient Care
    • Artifacts Summary
    • Hide

      See 

      1. FHIR-31050

      which explains the provider-provider use case

      Will clarify that ServiceRequest may be used by a requesting provider in a provider to provider transaction, it is unlikely to be used by a payor.

       

      Show
      See  FHIR-31050 which explains the provider-provider use case Will clarify that ServiceRequest may be used by a requesting provider in a provider to provider transaction, it is unlikely to be used by a payor.  
    • Eric Haas/Jay Lyle: 5-0-8
    • Clarification
    • Non-substantive

    Description

      I don't understand (and I think the spec doesn't explain) under what circumstances a payer's request for clinical information would be authorized by a ServiceRequest/order instead of a text of string or a Claim resource. You've explicitly taken provider-to-provider out of scope in this version.

      (Comment 24 - imported by: Jean Duteau)

      Attachments

        Activity

          People

            Unassigned Unassigned
            Isaac.Vetter Isaac Vetter
            Watchers:
            3 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved: