Too Many Elements Marked Must Support

XMLWordPrintableJSON

    • Type: Change Request
    • Resolution: Persuasive
    • Priority: Medium
    • Clinical Guidelines (FHIR)
    • STU3
    • Clinical Decision Support
    • STU
    • Profile Definitions and Documentation
    • Hide

      Agreed, in addition to providing Must Support documentation (as suggested by other commenters), we will review the Must Support flags for the profiles. Also, define "draft" vs "published" profiles, and an "indexable" profile to support searching in a repository.

      Show
      Agreed, in addition to providing Must Support documentation (as suggested by other commenters), we will review the Must Support flags for the profiles. Also, define "draft" vs "published" profiles, and an "indexable" profile to support searching in a repository.
    • Bob Dieterle/Floyd Eisenberg: 9-0-2
    • Enhancement
    • Non-substantive

      The IG doesn't make it clear what "Must Support" means, but lacking that information, it seems to me that the IG uses the Must Support flag too liberally – ultimately increasing the burden of implementation. Each MS represents a non-negotiable requirement, and I have a difficult time believing that every one of these attributes must be supported for a functioning system (particularly some of the metadata fields; for example, must a system really understand the "codesystem-keyWord" extension to properly use a Code System in a Guideline definition? I doubt it – but tat is just one example of many.)

            Assignee:
            Unassigned
            Reporter:
            cmoesel
            Watchers:
            1 Start watching this issue

              Created:
              Updated:
              Resolved: