XMLWordPrintableJSON

Details

    • Change Request
    • Status: Published (View Workflow)
    • Medium
    • Resolution: Persuasive with Modification
    • US Core (FHIR)
    • 3.2.0
    • Cross-Group Projects
    • Home
    • 1.5
    • Hide

      We will update the

      1) introduction

      2) Capability Statement.

      3) Conformance page and

      4) each profile Quick Start

      To make clear that 'conformance to US Core' means different things - you can conform in a few different ways:

      1) conforming to only a US Core profiles ( in other words, the content structure only and no FHIR RESTful interactions ) is also possible by declaring support for a US Core profile for deriving a profile based upon a US Core profile.

      2) conforming to US Core Profiles CapabilityStatement in US CORE INCLUDES BOTH the US Core profiles ( in other words, the content structure )  AND the RESTful interactions.

      A system claiming conformance ins 1 or 2 is using the US Core content profiles.

      Also provide guidance how to use a CapabilityStatement to declare:

      1)   conformance to the guide

      2) declare support for a profile

       

      Show
      We will update the 1) introduction 2) Capability Statement. 3) Conformance page and 4) each profile Quick Start To make clear that 'conformance to US Core' means different things - you can conform in a few different ways: 1) conforming to only a US Core profiles ( in other words, the content structure only and no FHIR RESTful interactions ) is also possible by declaring support for a US Core profile for deriving a profile based upon a US Core profile. 2) conforming to US Core Profiles CapabilityStatement in US CORE INCLUDES BOTH the US Core profiles ( in other words, the content structure )  AND the RESTful interactions. A system claiming conformance ins 1 or 2 is using the US Core content profiles. Also provide guidance how to use a CapabilityStatement to declare: 1)   conformance to the guide 2) declare support for a profile  
    • Brett Marquard/Eric Haas: 17-0-3
    • Clarification
    • Non-substantive

    Description

      The current statements indicate that one must support RESTful transactions to be conformant to US Core.  As the scope of use cases expand it is reasonable to expect where one uses a different exchange paradigm.  It would be appropriate that the hard requirement to support RESTful is actually done outside of US Core, while within US Core any considerations of RESTful in the context of US Core is described.  Currently, anybody trying to claim conformance to US Core from a data content perspective would not be able to do so.  As the discussion for a true US base profile with further constrained profiles for specific use cases, the exchange paradigm should be separated from the data syntax and semantics.

      Attachments

        Issue Links

          Activity

            People

              Unassigned Unassigned
              hbuitendijk Hans Buitendijk
              Watchers:
              2 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: