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

Clarify that developers and implementers will retain data visualization between DSTU2 to R4 upgrades.

    XMLWordPrintableJSON

    Details

    • Type: Change Request
    • Status: Applied (View Workflow)
    • Priority: Highest
    • Resolution: Persuasive with Modification
    • Specification:
      US Core (FHIR)
    • Raised in Version:
      3.1.1
    • Work Group:
      Cross-Group Projects
    • Related Page(s):
      DSTU2 to R4 Conversion
    • Related Section(s):
      7.4
    • Resolution Description:
      Hide

      Add bullet that Clients should be considerate of updates to the data visualization when updating between versions.

      Show
      Add bullet that Clients should be considerate of updates to the data visualization when updating between versions.
    • Resolution Vote:
      Brett Marquard / Eric Haas: 9-0-1
    • Change Category:
      Clarification
    • Change Impact:
      Non-substantive

      Description

      Are there any assurances that developers and implementers will retain data visualization between DSTU2 to R4 upgrades? Will implementation, customization, or configuration decisions made at a provider's medical office be retained after an upgrade? Recognizing this guide is not specifically addressing UX or UI, what can be done to maintain "usability fidelity" in a conversion? Further, If there are conversion issues, will the practice receive messages indicating that some data are missing in R4?

      Existing Wording:

      Expectation that DSTU2 Data is Preserved in R4

      (Comment 24 - imported by: Jean Duteau)

        Attachments

          Issue Links

            Activity

              People

              Assignee:
              Unassigned Unassigned
              Reporter:
              molly.malavey@ama-assn.org Molly Malavey
              Request in-person:
              Molly Malavey
              Watchers:
              3 Start watching this issue

                Dates

                Created:
                Updated:
                Resolved:
                Vote Date: