Don't mandate specific HTML UI elements. - DTR #67

XMLWordPrintableJSON

    • Type: Change Request
    • Resolution: Not Persuasive
    • Priority: Medium
    • US Da Vinci DTR (FHIR)
    • STU3
    • Clinical Decision Support
    • (profiles) [deprecated]
    • Provider Attestation
    • Hide

      Current workding: This mechanism MAY be an HTML input element with the type set to button or it may be an a element.

      This sentence is only providing guidance and not requiring (SHOULD or SHALL) an HTML element.

      Leave as guidance

      Show
      Current workding: This mechanism MAY be an HTML input element with the type set to button or it may be an a element. This sentence is only providing guidance and not requiring (SHOULD or SHALL) an HTML element. Leave as guidance
    • Bob Dieterle / Floyd Eisenberg: 9-0-3

      Existing Wording: This mechanism MAY be an HTML input element with the type set to button or it may be an a element.

      Comment:

      This level of specificity is inappropriate. DTR apps should no be shackled to specific html; rather, they should be enabled to innovate their UI to provide the best possible experience for their users. Note that this requirement?/recommendation? completely disallows mobile and desktop apps. This sentence should be removed.

      Summary:

      Don't mandate specific HTML UI elements.

            Assignee:
            Unassigned
            Reporter:
            Michael Clifton
            Watchers:
            3 Start watching this issue

              Created:
              Updated:
              Resolved: