Versions Compared

Old Version 26

changes.mady.by.user Kyle Hutson (Unlicensed)

Saved on

compared with

New Version 27

changes.mady.by.user Kyle Hutson (Unlicensed)

Saved on

Key

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

 

Contributors
showCounttrue
showAnonymoustrue
showLastTimetrue

Please use this checklist to form a comprehensive review of the readiness of your institution for SPARCRequest adoption.

Tip
title

Project Management

  1. Project Initiation

    1. A project charter exists.

    2. A set of project management plans exist.

    3. A project schedule has been created with benchmarks and milestones.

    4. Participation in SPARCRequest Open Source Governance committees.


Tip
title

Finance and Budget Capacity

  1. Cost Analysis

    1. SPARCRequest costs and benefits have been evaluated in a cost/benefit analysis.

    2. Return‐on‐investment analysis have been estimated and accounted for.

    3. Funds and sources for ongoing adoption of required standards and upgrades will be part of the general budget.


title
Tip

Operational Capacity

  1. Training

    1. A formal training plan is part of the planning process. 

    2. Additional training for users (and IT staff) involved in SPARCRequest adoption has been identified to ensure administrative users possess appropriate skill sets.

    3. Training support plan is in place.

  2. Workflow Process

    1. Current and proposed SPARCRequest‐related administrative and clinical processes are documented in a process map and included in product evaluation process; planning process is in place for workflow redesign.

    2. Policies, procedures and protocols necessary for SPARCRequest implementation have been analyzed developed, and ready to be introduced to the team. 

    3. SPARCRequest implementation, workflow design and skill‐set gaps will be collaboratively developed for users


Tip
title

Technology Capacity

  1. Information Management

    1. SPARCRequest has been optimized to support research transaction management.

    2. SPARCRequest‐generated reports have been defined and documented.

    3. Requirements are included in the product evaluation process.  

  2. IT Management and Support

    1. IT management has strong experience with system integration, data conversion and managing expert resources to fill internal skill or knowledge gaps. 

    2. IT staff have been educated about SPARCRequest objectives in order to actively engage in the decision‐making process and determine necessary IT infrastructure requirements.  

    3. See Implementation Resources Required

  3. IT Infrastructure

    1. A needs assessment of hardware, desktop terminals and other devices necessary to support SPARCRequest usage has been performed and requirements included in the planning process.

    2. A plan for a technical infrastructure using a high‐ availability platform, upgraded to be standardized, scalable, and easily maintained is in place and will be standards‐ compliant with HIPAA, HL7 and other clinical and administrative transaction standards. 


title
Tip

Organizational Alignment

  1. Strategy

    1. IT strategic planning has been an integral part of the practice’s strategic planning process, resulting in a clearly‐defined  plan that guides SPARCRequest procurement.  

    2. Quality and efficiency issues are documented as key objectives in the Strategic Plan with measurable objectives and corresponding timeline.  

Other related resource for SPARCRequest adoption:

  1. Example Technical Implementation Resources Required for SPARCRequest

  2. SPARC Technology Stack

*Reference: 

1. Healthcare Information and Management Systems Society (HIMSS) Readiness Assessments Webpage: https://www.himss.org/readiness-assessment

2. FAFP EHR Readiness Assessment Tool: https://s3.amazonaws.com/rdcms-himss/files/production/public/HIMSSorg/Content/files/Code%2049%20FAFP%20Readiness%20Assessment.pdf

...