More guidance on code vs. text - CG #22

  • 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...
  • Applied
  • 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: Will make the point that what we provide are examples that are standardized, but that there are some other examples which do lack standardization today.

      Show
      Persuasive with Mod: Will make the point that what we provide are examples that are standardized, but that there are some other examples which do lack standardization today.
    • Bob D / Bob M: 11-0-0
    • Clarification
    • Non-substantive

      Existing Wording: In some cases, genotypes are sufficiently standardized to be conveyed as codes in genotype.valueCodeableConcept.code.

      Comment:

      In which cases? Possibly is it in cases where some authority (system) has agreed to manage it as a code?

      There seems to be too many hints here on when to use a codeableConcept.text vs a code; yet following examples seem to be clear distinction. So the lead text might simply need to be more assertive.

      Summary:

      More guidance on code vs. text

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

              Assignee:
              Unassigned
              Reporter:
              John Moehrke
              Watchers:
              2 Start watching this issue

                Created:
                Updated:
                Resolved:

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