Version Management Policy maturity levels need further specification for terminology service operations

XMLWordPrintableJSON

    • Type: Change Request
    • Resolution: Persuasive
    • Priority: Very High
    • FHIR Core (FHIR)
    • STU3
    • FHIR Mgmt Group
    • Normative
    • Change Management & Versioning (versions/compatibility)
    • Hide

      Will ensure the FMM levels in the core spec are updated to align with the wiki as currently stated

      Show
      Will ensure the FMM levels in the core spec are updated to align with the wiki as currently stated
    • Grahame Grieve/John Moehrke: 6-0-0
    • Clarification
    • Non-substantive
    • STU3

      The description of maturity levels is focused on resource exchange. These maturity levels are also applied to determine "maturity" of terminology service operations (and other operations?) but they do not describe testing that makes sense for an operation. Instead of "tested and exchanged" I would assume for an operation it should be tested with acceptable error messages and content exchange. There needs to be more documentation of what the "5 independent production systems in more than one country" have done to document that the operations have been tested.

            Assignee:
            Unassigned
            Reporter:
            Rob McClure
            Rob McClure
            Watchers:
            1 Start watching this issue

              Created:
              Updated:
              Resolved: