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

Simplify and make references consistent. Not sure what artifact is required.

    XMLWordPrintableJSON

Details

    • Icon: Change Request Change Request
    • Resolution: Duplicate
    • Icon: Highest Highest
    • Interoperable Digital Identity and Patient Matching (FHIR)
    • 1.0.0-ballot
    • Patient Administration
    • Patient1
    • 3.1
    • Hide

      Will update NIST 800-63-3A to an in-line hyperlink above in the page (1st use).

      Note that both UDAP and SMART reference are to non-permanent sites; will update these target links to permanent sites.

       

      Show
      Will update NIST 800-63-3A to an in-line hyperlink above in the page (1st use). Note that both UDAP and SMART reference are to non-permanent sites; will update these target links to permanent sites.  
    • Clarification

    Description

      Why is this IG written with links to references at the bottom of the page, rather than directly linking from the referncing text? E.g. section 3.1 reads "This section provides guidance that goes beyond NIST 800-63A for its practical application in healthcare settings. ..." and lower on the page is "References: ... NIST 800-63-3A..." with the reference as a link. Why not provide the link in the initial mention of the document? Managing references is also error prone and confusing: Some of the reference are after section 3.2 and labelled references, while others are after section 3.3 and only preceded by a footnote number (which can be confused with other numbering on the page), without clear reason why the two styles are used.

      Section 3 is used only as an example of these confusing approaches. The whole IG should be reviewed, and a consistent approach taken.

      (Comment 6 - imported by: Ron G. Parker)

      Attachments

        Activity

          People

            Unassigned Unassigned
            esilver Elliot Silver
            Watchers:
            3 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved: