Inconsistency about normative status of StructureDefinition operations

XMLWordPrintableJSON

    • Type: Change Request
    • Resolution: Persuasive with Modification
    • Priority: Medium
    • FHIR Core (FHIR)
    • STU3
    • FHIR Infrastructure
    • StructureDefinition
    • Hide

      Will mark $questionnaire and $generate as trial use

      Show
      Will mark $questionnaire and $generate as trial use
    • Grahame Grieve/Richard Ettema: 6-0-1
    • Enhancement
    • Non-substantive
    • STU3

      1. The ballot intro doesn't list the StructureDefinition operations, but according to Grahame and the page, they're supposed to be in scope for normative. How do we ensure that the artifact pages and ballot intro say the same thing?

      2. The operations should list their ballot status separately for each operation. This is clearer, ensures more consistency and makes clear that the statuses are independent.

      3. The $generate operation isn't eligible to go normative because it's brand new this release and FMM 5 criteria say it needs to have been in at least two prior STU publications. FMG would need to waive this requirement and it's doubtful they'd waive it until it had been in at least one STU publication.

            Assignee:
            Unassigned
            Reporter:
            Lloyd McKenzie
            Watchers:
            2 Start watching this issue

              Created:
              Updated:
              Resolved: