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

Add ImplementationGuide.kind

    XMLWordPrintableJSON

Details

    • Icon: Change Request Change Request
    • Resolution: Persuasive with Modification
    • Icon: Very High Very High
    • FHIR Core (FHIR)
    • STU3
    • FHIR Infrastructure
    • ImplementationGuide
    • Hide

      Define a new code for "usage-context-type":

      "agreement-scope" - "Describes the level and scope of agreement represented within the artifact.  Appropriate values can be found in the xxx value set" (value set defined and named below)

      Define a new code system (and whole-system value set) called "usage-context-agreement-scope" with the following codes:

      "realm-base" - Defines use-case independent foundational expectations for exchange within a particular country or jurisdiction.  Should be accompanied by a jurisdiction.  Commonly used as a 'base' for more restrictive artifacts.

      "knowledge" - Defines use-case-specific information or guidance that is relevant to a specific business or health domain but is not mandated for particular use.

      "domain" - Defines use-case-specific requirements for a specific business or health domain.  May vary in jurisdictional scope from international to small region and in business scope from broad to narrow

      "community" - Sets contractual or business expectations for systems participating in a particular exchange community

      "system-design" - Documents the specific capabilities of a single system as "available" for purchase or use.  May have some variability reflecting options that can be configured

      "system-implementation" - Documents the specific points of a single production system or endpoint.  This may be time-specific - i.e. reflecting the system "as it is now" or as it was at some point in the past

       

       Add this code system to the big example value set of all UsageContext value codes.

      Show
      Define a new code for "usage-context-type": "agreement-scope" - "Describes the level and scope of agreement represented within the artifact.  Appropriate values can be found in the xxx value set" (value set defined and named below) Define a new code system (and whole-system value set) called "usage-context-agreement-scope" with the following codes: "realm-base" - Defines use-case independent foundational expectations for exchange within a particular country or jurisdiction.  Should be accompanied by a jurisdiction.  Commonly used as a 'base' for more restrictive artifacts. "knowledge" - Defines use-case-specific information or guidance that is relevant to a specific business or health domain but is not mandated for particular use. "domain" - Defines use-case-specific requirements for a specific business or health domain.  May vary in jurisdictional scope from international to small region and in business scope from broad to narrow "community" - Sets contractual or business expectations for systems participating in a particular exchange community "system-design" - Documents the specific capabilities of a single system as "available" for purchase or use.  May have some variability reflecting options that can be configured "system-implementation" - Documents the specific points of a single production system or endpoint.  This may be time-specific - i.e. reflecting the system "as it is now" or as it was at some point in the past    Add this code system to the big example value set of all UsageContext value codes.
    • Grahame Grieve/Bryn Rhodes: 17-0-1
    • Enhancement
    • Compatible, substantive
    • R5

    Description

      It's clear that we have 4 kinds of guides emerging:

      1 National / realm base guides
      2 Domain guides - specify content models
      3 Exchange agreements - actual exchange contents
      4 System Documentation

      There's some lack of clarity in people's minds about this, and mixing between #1, #2, and #3 in ways that discourage proper re-use. Adding ImplementationGuide.kind to indicate the nature of the guide will help clarify people's minds.

      Attachments

        Activity

          People

            lloyd Lloyd McKenzie
            GrahameGrieve Grahame Grieve
            Watchers:
            3 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved: