Make CapabilityStatement.software 0..*

XMLWordPrintableJSON

    • Type: Change Request
    • Resolution: Not Persuasive
    • Priority: Medium
    • FHIR Core (FHIR)
    • R5
    • FHIR Infrastructure
    • CapabilityStatement (Conformance)
    • Hide

      CapabilityStatement.software is normative.  Changing the cardinality would be a breaking change for the JSON representation, so this is something we're very reluctant to do at this point.

      We're happy to contemplate defining a standard (complex?) extension for this use-case.  We will need guidance on what you'd like the extension called and how it should work - i.e. is it to be treated as "additional repetitions" or should the existing CapabilityStatement.software represent the 'overall package' and the extension represent detailed components.  Please submit a new change request once you've decided how you'd prefer this to be handled.

      Show
      CapabilityStatement.software is normative.  Changing the cardinality would be a breaking change for the JSON representation, so this is something we're very reluctant to do at this point. We're happy to contemplate defining a standard (complex?) extension for this use-case.  We will need guidance on what you'd like the extension called and how it should work - i.e. is it to be treated as "additional repetitions" or should the existing CapabilityStatement.software represent the 'overall package' and the extension represent detailed components.  Please submit a new change request once you've decided how you'd prefer this to be handled.
    • Rick Geimer/Gino Canessa: 14-0-1

      Currently, CapabilityStatement allows 0..1 software products to be listed as being covered by the CapabilityStatement.  In some cases there may be multiple software products being covered by a single CapabilityStatement.  This of course does depend somewhat on your definition of "software product". 

       

      The specific issue we ran into is that ONC/Lantern is looking to correlate our ConformanceStatement with products listed in the CHPL (https://chpl.healthit.gov/).  We have multiple products listed in the CHPL, but we only have one CapabilityStatement.

      Independent of the ONC/CHPL issue, we do have multiple products (e.g. our scheduling product, billing product, EHR product, etc.) that are all covered by the same CapabilityStatement.  Being able to indicate all the products supported by our CapabilityStatement would be nice.

       

      Suggestion:  update CapabilityStatement.software cardinality from 0..1 to 0..*

            Assignee:
            Unassigned
            Reporter:
            Cooper Thompson
            Watchers:
            1 Start watching this issue

              Created:
              Updated:
              Resolved: