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

Conformance statements don't belong on the home page

    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
    • Documentation Templates and Rules Implementation Guide Home Page
    • Hide

      Remove all references that include conformance language from homepage, and include them as part of the specifications. 

      Show
      Remove all references that include conformance language from homepage, and include them as part of the specifications. 
    • Bob Dieterle / Jeff Brown : 12-0-2
    • Clarification
    • Non-substantive

    Description

      The paragraphs at the end of the Overview section (starting with "Although not detailed in this IG") don't belong here.

      First, support for EHR-based vs. SMART-app based functionality should absolutely be called out as a completely defined set of capabilities with their own conformance expectations.  If EHRs are going to rely on this approach to meet regulations, we have to define exactly how it's expected to work (at least from an interface perspective). 

      Second, we're calling out technical details here with conformance language when we haven't explained any of the technical foundation yet.  All language around conformance requirements should appear within the 'specification' pages.

      Note: Some of these declarations may go away - see subsequent tracker items.

      Attachments

        Activity

          People

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

            Dates

              Created:
              Updated:
              Resolved: