Uploaded image for project: 'MedMij Standaarden'
  1. MedMij Standaarden
  2. MM-1795

Describe what the CapabilityStatement should be used for

Details

    • Wijzigingsverzoek
    • Status: Gesloten
    • 3
    • Resolution: Resolved
    • 2020.01 - April 2021
    • None
    • Nee
    • Alle
    • Technisch, FHIR
    • Minimal. This will clarify the questions we get around the use of our CapabilityStatements
    • Other
    • Hide
      In section 5.10 in the overarching principles for MedMij, a section for the interpretation of the CapabilityStatement will be added. This will state that "the CapabilityStatements are informative in nature and do not represent the max or minimal set your server should support. Our TO's will be leading in what to implement."
      Besides these changes to the wiki, the .purpose element in our CapabilityStatements will be used for a similair description.
      Show
      In section 5.10 in the overarching principles for MedMij, a section for the interpretation of the CapabilityStatement will be added. This will state that "the CapabilityStatements are informative in nature and do not represent the max or minimal set your server should support. Our TO's will be leading in what to implement." Besides these changes to the wiki, the .purpose element in our CapabilityStatements will be used for a similair description.
    • Hide

      In the STU3 FHIR IG a section is added on CapabilityStatements, this explains their informative nature. The same text is added to the CapabilityStatement instances.

      Show
      In the STU3 FHIR IG a section is added on CapabilityStatements, this explains their informative nature. The same text is added to the CapabilityStatement instances.

    Description

      For the various information standards, CapabiltyStatements are available to describe the requirements for both servers and clients. However, it is not quite clear what these CapabilityStatements should be used for. Are they used as documentation? Do they take precedence over the written specifications. This should be made clear in the overarching principles.

      Attachments

        Issue Links

          Activity

            People

              Opdenberg@nictiz.nl Stephan Opdenberg (Inactive)
              edelman@nictiz.nl Pieter Edelman
              Watchers:
              4 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved:

                Jigit Development

                  Branches:
                  Pull requests: