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

Refactor relaunch documentation

    XMLWordPrintableJSON

Details

    • Icon: Change Request Change Request
    • Resolution: Persuasive with Modification
    • Icon: Medium Medium
    • US Da Vinci DTR (FHIR)
    • 1.0.0 [deprecated]
    • Clinical Decision Support
    • Persisting Application State [deprecated]
    • Hide

      We will consolidate all information about app launch (CRD launch, stand-alone launch and re-launch) into one part of the spec.

      Information about storage will now be simpler because storage of work in progress will only occur on the provider system.

      Show
      We will consolidate all information about app launch (CRD launch, stand-alone launch and re-launch) into one part of the spec. Information about storage will now be simpler because storage of work in progress will only occur on the provider system.
    • Bob Dieterle / Greg White: 10-0-2
    • Clarification
    • Non-substantive

    Description

      The documentation should make clear up-front that there are two different mechanisms for storing "work in progress", driven by whether the EHR has the ability to store QuestionnaireResponses with the relevant extensions or not.  Then have a separate sub-section that walks through each.  As things are currently written, that choice isn't clear and the option to persist as a QuestionnaireResponse doesn't jump out - even though that's the most preferred option.

      Also, there's redundant information here about app launch.  We should talk about app launch in only one place.  This section should only talk about storing work in progress.

      Attachments

        Activity

          People

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

            Dates

              Created:
              Updated:
              Resolved: