2015May core #260 - Use specific LOINC codes

XMLWordPrintableJSON

    • Type: Change Request
    • Resolution: Persuasive with Modification
    • Priority: Medium
    • US Core (FHIR)
    • DSTU1
    • US Realm Task Force
    • Profiles and Extensions
    • 4.20.12
    • Hide

      Latest update of US-Core will use the FHIR core profile Vital Signs. This has been reviewed wiht Regenstrief

      Show
      Latest update of US-Core will use the FHIR core profile Vital Signs. This has been reviewed wiht Regenstrief
    • Hans Buitendijk/Danielle Friend: 8-0-1
    • Clarification
    • Non-compatible
    • DSTU1

      Existing Wording: U.S. Data Access Framework (DAF) Vital Signs Profile

      Comment:

      This does not seem to add anything to what is in the overall spec and it does not speak to the specifics of meanful use vital signs that specifies the following:

      work.

      We propose to require that a Health IT

      Module be able to attribute a specific

      LOINC® code to each type of vital sign

      using the following identifiers:

      • ''Systolic blood pressure'' with

      LOINC® code 8480-6;

      • ''Diastolic blood pressure'' with

      LOINC® code 8462-4;

      • ''Body height'' with LOINC® code

      8302-2;

      • ''Body weight measured'' with

      LOINC® code 3141-9;

      • ''Heart rate'' with LOINC® code

      8867-4;

      • ''Respiratory rate'' with LOINC®

      code 9279-1;

      • ''Body temperature'' with LOINC®

      code 8310-5;

      • ''Oxygen saturation in arterial blood

      by pulse oximetry'' with LOINC® code

      59408-5;

      • ''Body mass index (BMI) [Ratio]''

      with LOINC® code 39156-5; and

      We understand that the industry is

      commonly identifying these vital signs

      using LOINC® codes today.

      59576-9) for youth 2-20 years of age;

      and

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

              Created:
              Updated:
              Resolved: