Use LONIC codes where possible. - PCDE #5

XMLWordPrintableJSON

    • Type: Change Request
    • Resolution: Not Persuasive
    • Priority: Medium
    • US Da Vinci PCDE (FHIR)
    • STU3
    • Financial Mgmt
    • (profiles) [deprecated]
    • Hide

      It is our intention to request LOINC codes for the document and sections once the implementation guide has received vetting in the implementation space and we are more confident in exactly which codes are needed. We don't want to request LOINC codes too early in the process. The specification already indicates our intention to do this here: http://hl7.org/fhir/us/davinci-pcde/2019SEP/spec.html#terminology

      Show
      It is our intention to request LOINC codes for the document and sections once the implementation guide has received vetting in the implementation space and we are more confident in exactly which codes are needed. We don't want to request LOINC codes too early in the process. The specification already indicates our intention to do this here: http://hl7.org/fhir/us/davinci-pcde/2019SEP/spec.html#terminology
    • Kathleen Connor / Rachael Foerster: 20-0-1
    • Clarification

      Comment:

      Several comments:

      1. LOINC has long been the accepted terminology system for document and section codes in HL7. Requesting codes from LOINC for a specific purpose is not challenging. I would prefer the document and section codes use LOINC so that we have fewer vocabularies to reference for document ontology.

      PCDex seems to be missing a case of how this would be handled using existing technology, or a description of how the proposed solution would impact user workflows, or perhaps even a description of who those users are and what their current workflows are. Again, it shows some variance from other Da Vinci specifications.

      Summary:

      Use LONIC codes where possible.

            Assignee:
            Unassigned
            Reporter:
            Keith W. Boone
            Watchers:
            2 Start watching this issue

              Created:
              Updated:
              Resolved: