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

Do better job of explaining HRex decision points

    XMLWordPrintableJSON

Details

    • Icon: Change Request Change Request
    • Resolution: Persuasive
    • Icon: Medium Medium
    • US Da Vinci DTR (FHIR)
    • 1.0.0 [deprecated]
    • Clinical Decision Support
    • Retrieval of Payer Resources [deprecated]
    • Hide

      Replace the paragraph in question with documentation describing the two primary architectural decisions to highlight the rationale for:

      • using SMART as a primary mechanism for supporting DTR
      • using an operation as a mechanism to retrieve the relevant Questionnaire (and other data)
      Show
      Replace the paragraph in question with documentation describing the two primary architectural decisions to highlight the rationale for: using SMART as a primary mechanism for supporting DTR using an operation as a mechanism to retrieve the relevant Questionnaire (and other data)
    • Bob Dieterle / Jeff Brown : 12-0-2
    • Clarification
    • Non-substantive

    Description

      "This IG will support the HRex Decision point - REST searchable? when using RESTful endpoints to get payer resources (e.g., CQL rules and templates)."

      This seems like an attempt to comply with the HRex expectation that all Da Vinci IGs will describe how they've navigated the HRex decision tree.  However, that's not really what's needed.  See CRD here for an example.  There are two primary architectural decisions to highlight the rationale for:

      • using SMART as a primary mechanism for supporting DTR
      • using an operation as a mechanism to retrieve the relevant Questionnaire (and other data)

      Attachments

        Activity

          People

            Unassigned Unassigned
            lloyd Lloyd McKenzie
            Watchers:
            3 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved: