Workflow heading suggestion

XMLWordPrintableJSON

    • Type: Change Request
    • Resolution: Not Persuasive
    • Priority: Highest
    • CDS Hooks patient-view [deprecated] (FHIR)
    • 1.0 [deprecated]
    • Clinical Decision Support
    • index
    • Hide

      The intent of the header on the hook definition page of "Workflow" is to specifically encourage hook definers to fully and beautifully describe the workflow. This intent is also codified within the HL7-published specification hook definition format:

      >Workflow

      >Describe when this hook occurs in a workflow. Hook creators SHOULD include as much detail and clarity as possible to minimize any ambiguity or confusion amongst implementors.

      https://cds-hooks.hl7.org/1.0/#workflow

       

      Show
      The intent of the header on the hook definition page of "Workflow" is to specifically encourage hook definers to fully and beautifully describe the workflow. This intent is also codified within the HL7-published specification hook definition format: >Workflow >Describe when this hook occurs in a workflow. Hook creators SHOULD include as much detail and clarity as possible to minimize any ambiguity or confusion amongst implementors. https://cds-hooks.hl7.org/1.0/#workflow  
    • Isaac Vetter/Howard Strasberg: 19-0-1

      The term workflow is misleading - is "Event" or "Trigger Event" not a more suitable name?

            Assignee:
            Unassigned
            Reporter:
            Bas van den Heuvel
            Watchers:
            2 Start watching this issue

              Created:
              Updated:
              Resolved: