XMLWordPrintableJSON

Details

    • Icon: Change Request Change Request
    • Resolution: Persuasive
    • Icon: Highest Highest
    • Canonical Resource Management Infrastructure (FHIR)
    • 1.0.0-ballot2
    • Clinical Decision Support
    • Withdrawn
    • CRMI Release Operation
    • Artifact Repository Service
      Content Lifecycle [deprecated]
    • Hide

      Agreed, add discussion of content lifecycle restrictions about disallowed transitions:
      active -> draft // not allowed
      retired -> active, draft // not allowed

      Show
      Agreed, add discussion of content lifecycle restrictions about disallowed transitions: active -> draft // not allowed retired -> active, draft // not allowed
    • Howard Strasberg / Greg White: 21-0-0
    • Clarification
    • Non-substantive

    Description

      In Content Lifecycle, there are some state change requirements listed:

      1. An active artifact SHALL NOT transition back to draft, a new version of the artifact is required
      2. retired artifact SHALL NOT transition back to active, a new version of the artifact is required

      However, these restrictions are not specified in the Artifact Repository Operations, nor are they listed in the related operation definitions (e.g., CRMI Release).

      If the lifecycle imposes status requirements, those should be described in the relevant interactions/operations/etc..

      Attachments

        Activity

          People

            Unassigned Unassigned
            ginocanessa Gino Canessa
            Watchers:
            1 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved: