Methods of Implementation

XMLWordPrintableJSON

    • Type: Change Request
    • Resolution: Persuasive
    • Priority: Medium
    • Clinical Guidelines (FHIR)
    • STU3
    • Clinical Decision Support
    • Profile Definitions and Documentation
    • Hide

      Agreed, update wording as suggested, and add documentation describing service-based versus ingestion/intake approach

      Show
      Agreed, update wording as suggested, and add documentation describing service-based versus ingestion/intake approach
    • Chris Moesel/Rob Samples: 18-0-2
    • Enhancement
    • Non-substantive

      suggest this 3rd tier should say "Consume CQL (implementation)
      Directly intake, interpret, and execute CQL artifacts

      (should be silent on where CQL is being interpreted/executed – could be 'native' in either EHR, or could be via services in a cloud-based architecture interfacing with the EHR)

      Need to consider other implications to support BOTH native EHR and service-oriented architecture. For instance, may need to consider support for an optional layer at data interface (monitoring of patient state) and at the recommendations/suggestions/requests interface (monitoring of EHR workflow state).

            Assignee:
            Unassigned
            Reporter:
            matthew_burton
            Watchers:
            1 Start watching this issue

              Created:
              Updated:
              Resolved: