XMLWordPrintableJSON

    • Type: Change Request
    • Resolution: Not Persuasive
    • Priority: Medium
    • FHIR Core (FHIR)
    • DSTU1 [deprecated]
    • Orders & Observations
    • DataElement (see StructureDefinition) [deprecated]
    • 6.20.2
    • Hide

      Ballot comment is not clear. In FHIR, LOINC content would be represented using DataElement. No obvious change to make.

      Show
      Ballot comment is not clear. In FHIR, LOINC content would be represented using DataElement. No obvious change to make.
    • Riki/Lorraine: 6-0-5
    • Clarification

      Existing Wording: DataElements when defining the data elements with the

      Profile. (For implementability reasons, the data constraints should still be explicitly exposed within the Profile (profile.html) rather

      than being included "by reference" to the DataElement

      Comment:

      There is a hidden assumption that they would never use standard data elements (or variables) such as LOINC or equivalents. Medicare forms are locked down. If we had the right set of locked down variables (or standard data elements) some bet that people would use them. Apgar and Glagow have met the test.

      We haven't tried yet.

      If we don't think anyone will use the pick from one big universal set of variables, why are we doing all of this work?? We are implicitly saying we won't succeed.

            Assignee:
            Unassigned
            Reporter:
            clemmcdonald
            clemmcdonald
            Watchers:
            2 Start watching this issue

              Created:
              Updated:
              Resolved: