Add an "Implant Procedure" profile to describe the context of an implantable device in the required implantable device list. - USCore #41

XMLWordPrintableJSON

    • Type: Change Request
    • Resolution: Persuasive with Modification
    • Priority: Medium
    • US Core (FHIR)
    • STU3
    • Structured Documents
    • Procedure [deprecated]
    • Profiles and Extensions
    • SD
    • Hide

      The creation of a specific implant procedure profile is not necessary.

      Add Implementation note on the use case for Implantable devices. and the 'focalDevice' element can reference a US-Core-Device. which is an implantable device. See GF#20025

      Show
      The creation of a specific implant procedure profile is not necessary. Add Implementation note on the use case for Implantable devices. and the 'focalDevice' element can reference a US-Core-Device. which is an implantable device. See GF#20025
    • Eric Haas/Ioana Singureanu: 22-0-0
    • Enhancement
    • Non-substantive

      Comment:

      The CCDS (https://www.healthit.gov/sites/default/files/topiclanding/2018-04/2015Ed_CCG_CCDS.pdf) require the use of a "procedure" - as the context for an implant. Since the CCDA 2.1 already supports the surrounding procedure, it's useful to provide the same contextual information through a FHIR "search".

      "Exchanging unique device identifier(s) using the "Product Instance" which is

      embedded in the "Procedure Activity Procedure" in the C-CDA Release 2.1 is

      intended to make this information more easily retrievable. [see also 80 FR 62695]

      Note that the 2015 Edition final rule refers to the "Procedure Activity Procedure

      Section" and we clarify that this is not a Section.":

      Summary:

      Add an "Implant Procedure" profile to describe the context of an implantable device in the required implantable device list.

            Assignee:
            Unassigned
            Reporter:
            Ioana Singureanu
            Ioana Singureanu
            Watchers:
            3 Start watching this issue

              Created:
              Updated:
              Resolved: