Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

  • Pre-Discovery: Complete
    • Call for Participation
  • Discovery (Phase I): In Progress
    • Finalize Project Charter
    • Construct Use Cases & Functional Requirements
    • Analyze Standards Gaps
    • Engage Appropriate SDOs
  • Implementation (Phase II): Summer / Fall 2012
    • Create Harmonized Specifications
    • Conduct Technology Evaluations
    • Generate Reference Implementations
    • Design Pilot Plan
  • Pilot (Phase III): Winter / Spring 2013
    • Create Pilot Technology
    • Validate / Revise Specifications and Implementations
  • Evaluation (Phase IV): Spring 2013
    • Assess Outcomes
    • Present Final Recommendations
HeD_Timeline_ProjChart_Final.gifImage Modified

...


Expected Deliverables

Updated version of the deliverables and timeline can be found on the Health eDecisions Homepage

...

  • Risk 1: Including implementation of clinical/treatment guidelines may increase scope.
    • Mitigation/Response: Identify and manage scope by aligning to Meaningful Use Stage 3 target timelines.
  • Risk 2: Insufficient “end-user” input (e.g. physicians, clinicians, technology vendors).
    • Mitigation/Response: Evaluate role and type of initiative participants; invite additional participants early in the initiative process to balance representation.
  • Risk 3: Data reconciliation process may be negatively impacted due to a lack of value sets and terminology standards.
    • Mitigation/Response: Keep abreast and adopt developments and alignment strategies from the HIT Standards Committee and from the HIT Policy Committee. Such information may be part of an implementation guide.
  • Risk 4: Services integration may be negatively impacted due to a lack of standards.
    • Mitigation/Response: Identify gaps and partner with appropriate organizations to close them.
  • Risk 5: EHR vendors may resist opening their architectures to services integration.
    • Mitigation/Response: Identify and communicate the benefits early in the process; ensure EHR vendors are represented in the initiative participants (see Risk 2). As this initiative matures with deliverables, incorporation into MU3 would likely be an incentive for vendors to come aboard.
  • Risk 6: Standards and solutions may not scale to small vendors and small practices.
    • Mitigation/Response: Ensure that proposed standards and solutions are modular/scalable.
  • Risk 7: Proposed project timeline does not reflect actual deadlines in relevant SDO Balloting.
    • Mitigation/Response: Identify support to help mitigate this issue including inviting SDO members to participate in our work group and working with SDOs on out-of-cycle balloting. Change expectations in the HeD timeline. Begin working with the SDOs ASAP.
  • Risk 8: Proposed project timeline is significantly faster than what has traditionally been possible through participant effort alone.
    • Mitigation/Response: Monitor and communicate timeline, deliverables and progress frequently to all stakeholders; identify and request increased or reallocated resources (as needed).

...

Initiative Contacts

Initiative CoordinatorKen Kawamotokensaku.kawamoto@utah.edu
ONC LeadershipJacob Reiderjacob.reider@hhs.gov
ONC LeadershipAlicia Mortonalicia.morton@hhs.gov
SMEAziz Boxwalaaziz.boxwala@meliorix.com
SMEBryn Rhodesbryn@veracitysolutions.com
Project ManagerJamie Parkerjamie.parker@esacinc.com
Use Cases LeadAnna Langhansanna.langhans@accenturefederal.com
UC2 Harmonization LeadAtanu Senatanu.sen@accenture.com
Standards LeadAnna Langhansanna.langhans@accenturefederal.com
Standards LeadDivya Raghavacharidivya.raghavachari@accenturefederal.com