PCC Profile Deprecation

From IHE Wiki
Jump to: navigation, search

Overview

From time to time IHE Profiles (and National Extensions) may need to be deprecated for one reason or another. PCC will follow general direction and guidance provided by IHE on the Evaluation of Published Profiles in addition to what is stated on the PCC Profile Deprecation Process page, which includes the details of the deprecation process as defined by the PCC committee.

Deprecation is a mechanism used to notify the community of intended removal/deletion/dropping of a Profile, National Extension, or other artifact. In order to deprecate a profile, an assessment must be performed to determine the community impact of the deprecation. If this assessment is not performed then there could be negative impact, causing disruption in interoperability implementations as vendors, policy-makers, and other stakeholders may decide to cease support for a profile based on deprecation status.

Profiles/National Extensions in Intent to Deprecate/Deprecated Status

Add links below to pages for Profiles or National Extensions that are going through the Deprecation Process

  • Transport Record Summary Profiles Deprecation - includes Emergency Department Transport Summary (ETS) and Interfacility Transport Summary (ITS) Profiles
    • Did the profile address a real problem? Yes,and the HL7 EMS run report expanded upon it so it is no longer current.
    • Are the business case still valid? Yes
    • Is the technical solution valid? No, it is obsolete and we are issuing the PCS profile to replace it.
    • Does a newer solution exist? Yes, in HL7 and we are profiling with the new PCS profile.
    • Do we need to keep it around for a legacy reason? Not that we know of.
    • Connectathon testing: Only as a content consumer by 2 systems.
    • Integration statements: Only one, and it is a content consumer only.
    • Is the profile being replaced by a new profile? Yes, by PCS. Make sure to add a note to the profile wiki page to link to the new profile and state that all links to ETS/ITS should be updated to reference PCS.
    • Are there any dependencies to or from other profiles or standards? No.
    • How do we survey implementers? Andrea will ask Zoll, Dr Myers, Oliver Egger, Laura Heerman-Langford, Larry Garber, and others to see if they will be affected.
    • If we do not hear back, we will issues a notice of intent to deprecate.


  • Guideline Appropriate Ordering (GAO)
    • Keith brought GAO and several CDS vendors committed to implementation to IHE before FHIR was really available.
    • They then took it over to HL7 as an implementation guide on the direction of ONC.
    • HL7 balloted a FHIR IG of GAO, but nobody is using it there either.
    • Then a different group went to HL7 with OAT, which addressed a lot of problems with GAO.
    • CMS brought together a group called AARA to great a new set of reporting options that have reached out to HL7.
    • All of this is disconnected from IHE GAO.
    • Did the profile address a real problem? It was a regulatory driven use case, which is still evolving.
    • Is the business case valid? No. The business case has changed from guidance for ordering decision support, it is now documenting actions for billing purposes.
    • Is the technical solution valid? No, it is out of date and did not evolve.
    • Does a new solution exist? Not yet, but it is in process with the CMS initiative.
    • Thom moved to file a notice of intent to deprecate. Tone seconded. Gila to update DCC and deployment committees.
    • If we do not hear any objections to deprecation before July, we will proceed with deprecation of eNS.
  • Patient Plan of Care (PPOC)
    • Did the profile address a real problem? Yes
    • Are the business case and technical solution valid? Yes, but... a newer solution exists.
    • Does PtPOC replace it? Somewhat. PtPOC covers the same concepts and adds detail.
    • Do we need to keep it around for a legacy reason? Not that we know of.
    • Tested once, at 1 Connectathon, with only 1 vendor as the content creator (e-MDS)
    • 3 integration statements, all content consumer - no creator
    • We are currently unaware of any users, however if we find some we can discuss whether the TI should move to Final Text.
    • No dependencies to or from other IHE profiles
    • How do we survey implementers? Gila to ask regional deployment committees and DCC to propagate the intent to deprecate.
    • If we do not hear any objections to deprecation before July, we will proceed with deprecation of PPOC.
  • Electronic Nursing Summary (eNS)

eNursing summary is a collection of data that nurses typically document.

    • Did the profile address a real problem? Yes
    • Are the business case and technical solution valid? Yes.
    • Does a newer solution exist? Yes in cCDA but not in IHE, and it is not 100% the same. CCDA created constructs that can be used to exchange the same type of information, such as the CCDA assessment scale observation template. CCDA is not international though, however we are not aware of international use cases for nurse-specific documents or sections. This is often communicated internally to the visit and captured at the end of the visit and isn't treated as an interoperability priority for IHE.
    • If it is not replaced but we still feel that there is a real business need, do we want to market it more for adoption?
    • Do we need to keep it around for a legacy reason? Not that we know of.
    • Connectathon testing: Only as a content consumer by 2 systems.
    • Integration statements: Only one, and it is a content consumer only.
    • Is the profile being replaced by a new profile? No.
    • Are there any dependencies to or from other profiles or standards? No.
    • How do we survey implementers? Gila to ask regional deployment committees and DCC to propagate the intent to deprecate. Amit and Tone to discuss the idea of a separate "intent to depracate" status with the DCC. Denise to ask AORN. Nemanja will ask in France if eNS is likely to ever be used.
    • If we do not hear any objections to deprecation before July, we will proceed with deprecation of eNS.