• Item:operations-top-levelMoreItem:operations-workItem:greenhopper_issue...Item:operations-archiveItem:operations-attach...Item:operations-votesw...Item:operations-subtasksItem:devstatus-cta-listItem:operations-operat...Item:operations-deleteItem:operations-manual...
  • Published
  • AdminItem:operations-fieldsItem:operations-admin-...
  • Item:operations-restore
Item:jira.issue.tools ExportXMLWordPrintableJSON

    • Type: Change Request
    • Resolution: Persuasive with Modification
    • Priority: Medium
    • Genomics Reporting (FHIR)
    • STU3
    • Clinical Genomics
    • (profiles) [deprecated]
    • Hide

      Persuasive with mod - add "Abstract" grouping for relevant profiles (viewable on artifacts.html)

      Show
      Persuasive with mod - add "Abstract" grouping for relevant profiles (viewable on artifacts.html)
    • Arthur / Patrick: 14-0-0
    • Clarification
    • Non-substantive

      When reviewing the contents of the IG, it is not clear when review which profiles are abstract and which are implementable. I would propose we adopt a consistant naming convention to clearly indicate to a reviewer the type of profile. This would need to be reflected on the profile page itself, the profiles name on the TOC, and any reference to it on other pages in the IG.

      On the TOC, we could include a note explaining our naming convention.

      Ideas:

      1) Append a common suffix to profile names (like " - Base" or "- Abstract" or perhaps " (A)")

      2) To match the diagrams, italizie the name on the TOC page - though this is unlikely to work n the profile page)

            Panel: location:atl.jira.view.issue.left.context

              Assignee:
              Unassigned
              Reporter:
              Kevin Power
              Watchers:
              1 Start watching this issue

                Created:
                Updated:
                Resolved:

                  Panel: location:atl.jira.view.issue.right.context