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

add language

    XMLWordPrintableJSON

Details

    • Icon: Change Request Change Request
    • Resolution: Persuasive with Modification
    • Icon: Highest Highest
    • US Da Vinci CRD (FHIR)
    • 1.1.0-ballot [deprecated]
    • Financial Mgmt
    • Supported Hooks
    • 4.3.2.3
    • Hide

      Will revise this: "CRD servers SHALL, at minimum, offer configuration options for each type of card they support (with a code corresponding to the CRD Card Types ValueSet and a type of ‘boolean’, where setting the flag to false will result in the server not returning any cards of the specified type. This allows CRD clients to control what types of cards they wish to receive at all, or to receive in particular workflow contexts or for certain users."

      to

      "CRD servers SHALL, at minimum, offer configuration options for each type of card they support (with a code corresponding to the CRD Card Types ValueSet and a type of ‘boolean’, where setting the flag to false will result in the server not returning any cards of the specified type. This allows CRD clients to control what types of cards they wish to receive at all, or to receive in particular workflow contexts or for certain users.  This configuration mechanism also allows EHRs to minimize information overload and avoid presentation of duplicative or low-utility CRD alerts."

       

      Will change "

      • A default value SHOULD also be provided to show users what to expect when an override is not specified."

      to be 'SHALL'.

      Show
      Will revise this: "CRD servers  SHALL , at minimum, offer configuration options for each type of card they support (with a code corresponding to the  CRD Card Types ValueSet and a type of ‘boolean’, where setting the flag to false will result in the server not returning any cards of the specified type. This allows CRD clients to control what types of cards they wish to receive at all, or to receive in particular workflow contexts or for certain users." to "CRD servers  SHALL , at minimum, offer configuration options for each type of card they support (with a code corresponding to the  CRD Card Types ValueSet and a type of ‘boolean’, where setting the flag to false will result in the server not returning any cards of the specified type. This allows CRD clients to control what types of cards they wish to receive at all, or to receive in particular workflow contexts or for certain users.  This configuration mechanism also allows EHRs to minimize information overload and avoid presentation of duplicative or low-utility CRD alerts."   Will change " A  default  value  SHOULD also be provided to show users what to expect when an override is not specified." to be 'SHALL'.
    • Bob Dieterle / Andy Stechischin : 8-0-1
    • Correction
    • Non-compatible
    • Yes

    Description

      In New Hook configuration – add language here to more overtly reiterate the importance of providers being able to set/determine preferences to avoid information overload

      Attachments

        Activity

          People

            Unassigned Unassigned
            celine_lefebvre Celine Lefebvre
            Celine Lefebvre
            Watchers:
            2 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved: