P02 - Request for Information.docx

Clinical Informatics and Data Management Office Regulatory Affairs Request for Information Department of Veterans Affairs (VA) Office of Health Informatics (OHI) Clinical Informatics and Data Management Office (CIDMO) Department of Regulatory Affairs

Request for Information THIS IS A REQUEST FOR INFORMATION (RFI) ONLY (as defined in FAR 15.201(e)), this is not a solicitation, a solicitation is not available at this time. Requests for a solicitation will not receive a response. Respondents are advised that the Government is under no obligation to acknowledge receipt of the information received, provide feedback to respondents with respect to any information submitted, or respond to any questions or comments that may be submitted in response to this RFI. This notice does not constitute a commitment by the United States Government and does not obligate the Government to award a contract or otherwise pay for the information provided in response. Responders are solely responsible for all expenses associated with responding to this RFI.

The purpose of this RFI is to conduct market research to obtain information on potential market capability to provide neutral industry support as a convenor to drive digital health initiatives for the clinical informatics industry. Additionally, the Government aims to determine if any existing contract vehicles for executing tasks would be a viable pathway. The details of this requirement can be found in the Attachment A: Draft Performance Work Statement (PWS). Responses to this request for information may influence the chosen acquisition strategy (including Veteran-owned, Service-disabled Veteran-owned, and other small business participation, and vehicles and methods to acquire the services).

1. VA is requesting input from all vendors, with all socioeconomic statuses, however, Service-Disabled Veteran-Owned Small Business (SDVOSB) and Veteran-Owned Small Business (VOSB) are encouraged to respond. VA is requesting vendor capability to deliver all required support, along with experience/past work specified in the PWS. The Government requests that vendors respond using the INSTRUCTIONS provided in this Request for Information. Responses should “demonstrate” capability, not just “confirm” the company’s belief that the capability exists or could exist.

2. The VA does not intend to award a contract as a result of this RFI, but rather gather capabilities and market information pertinent for acquisition planning. The responses to this RFI will be captured as market research and may contribute to the development of an acquisition strategy. All submissions become Government property and will not be returned. The Government reserves the right to use information provided by respondents for any purpose deemed necessary and legally appropriate.

The information provided in the RFI is subject to change and is not binding on the Government.

INSTRUCTIONS FOR RESPONDING TO THIS RFI

CONFIDENTIALITY: No proprietary, classified, confidential, or sensitive information should be included in your response. The Government reserves the right to use any non-proprietary technical information in any resultant solicitation(s).

Response Format/Page Limitations:

The overall total page limit for responses to this RFI is ten (10) pages. Responses should be submitted in Microsoft Word format with 12 pt. or greater font size. Interested parties should limit marketing material in order to allow sufficient space for adequately, directly, and substantively responding with the information of most interest to the Government. Responses may also optionally include the provision of resumes of qualified personnel that demonstrate expertise in the domains, and resumes will not count towards the page limit.

In all correspondence relevant to this RFI please identify it as a response to the “Interoperability Roadmap” (on response and in Subject Line of email).

Any organization responding to this notice should ensure that its response is complete and sufficiently detailed. Respondents are requested to limit responses to the information, and in the format provided below.

A. GENERAL INFORMATION

a. Organization Name.

b. Company ownership (public, private, joint venture).

c. What is your business size designation in accordance with Small Business Administration (SBA) standards for the recommended NAICS code (541611, Administrative Management and General Management Consulting Services).

B. CAPABILITY AND EXPERIENCE INFORMATION

Interested firms are requested to provide Capability Statements addressing the following data/information, by the closing date.

a. Company name

b. Company address

c. Company Point-of-Contact (POC)

d. Company phone, fax, and email address

e. Company Tax ID Number (TIN)

f. Company CAGE Code and SAM Unique Entity ID

g. Type/Size of Business relative to NAICS Code 541611. If you suggest a more accurate NAICS, as it relates to the services noted herein, please provide it as well.

h. Federal Supply Schedule (FSS) Number (if applicable), meaning your FSS pertains to Clinical Informatics and Health Data Management.

i. Statement of Capability that demonstrates your business’s capability and past performance in providing the type of service(s) requirement; to include data and information stated herein.

In addition to providing your company’s capability statement as it pertains to the requirements of this RFI, interested and capable firms are also required to provide answers to the following questions.

1. How do you deal with pressures of politically sensitive health care issues that have national implications?

2. How do you determine the appropriate level of rigor and quality and adjust your work accordingly?

3. How do you ensure impartiality when managing and facilitating stakeholder forums?

4. How do you ensure a high level of professionalism in your interactions with the team and with external personnel during project work?

5. How do you ensure your work product meets a high standard in terms of quality and professionalism?

6. How do you advocate for minority voices on a project team when there are competing priorities?

7. How do you advocate for Clinical Informatics work on a project team when there are competing priorities?

8. How would you manage distinctly different stakeholder interests (e.g., Clinical Informaticists, Hospital Systems, Electronic Health Record (EHR) Vendors, Academic, and Government) in a collaborative environment with competing priorities?

9. What Key Personnel do you suggest that would likely be able to meet the Government’s requirements, which includes expertise in Health Level 7 (HL7), Healthcare Information and Management Systems Society (HIMSS), FHIR, Trusted Exchange Framework and Common Agreement (TEFCA), Recognized Coordinating Entity (RCE), Qualified Health Information Networks (QHINs), and American Medical Informatics Association (AMIA)?

10. What potential contract vehicles would you suggest might be able to meet the Government’s requirements?

11. How would you leverage existing relationships with leaders cross the industry to advance this work?

12. How would you engage and maintain existing relationships to advance national digital health priorities and remain neutral?

The purpose of this RFI is for Market Research and to gather input for use in further defining the requirement only, and to identify interested and potentially capable vendors.

Submission: Responses to this RFI shall be submitted to SAC-E via email to Caitlin.Ruc@va.gov and Shaundrica.Close@va.gov no later than 4:30 PM Eastern Standard Time (EST) on June 26, 2024.

Questions: No Questions are being accepted at this time. Depending upon the responses received, VA may request additional information, may conduct future question and answer sessions, or may conduct meetings or an industry day.

52.215-3 Request for Information or Solicitation for Planning Purposes (Oct 1997)

(a) The Government does not intend to award a contract on the basis of this solicitation or to otherwise pay for the information solicited except as an allowable cost under other contracts as provided in subsection 31.205-18, Bid and proposal costs, of the Federal Acquisition Regulation.

(b) Although “proposal” and “offeror” are used in this Request for Information, your response will be treated as information only. It shall not be used as a proposal.

(c) This Request is issued for the purpose of: Information.

(End of provision)

Please see Attachment A, Draft Interoperability Pledge Program Support PWS below.

image1.emf

P09 - Performance Work Statement.docx

PERFORMANCE WORK STATEMENT

Interoperability Pledge Program Support

1. INTRODUCTION

1.1. At “HealthDataPalooza”, the Undersecretary of Health from the US Department of Veterans Affairs (VA), Dr. Shereef Elnahal, announced the creation of a Veteran Interoperability Pledge initiative to facilitate the seamless care experience and immediate access to Veteran patients’ medical history as part of making timely and accurate treatment decisions. With aspirations to help advance treatment and reduce negative outcomes for patients in suicidal crisis, recognizing new and enhanced benefits available to Veterans based upon legislation related to toxic exposures, this pledge will help enhance access to key data between VA and community providers.

1.2. This initiative is driven in part by recent legislative actions in the form of the Sergeant First Class Heath Robinson Honoring our Promise to Address Comprehensive Toxics (PACT) and the Veterans Comprehensive Prevention, Access to Care, and Treatment (COMPACT) act addressing Veterans in suicidal crisis. This initiative was developed to promulgate awareness of these benefits and to advance utilization of those benefits to the advantage of the Veteran population we serve.

1.3. A group of thirteen (13) health systems were initial signatories to the Pledge, agreeing to work collaboratively with the VA to identify and address issues adversely affecting Veteran care, with initial focus on improving the identification of patients that are Veterans, in clarifying and improving eligibility determination for programs under which they may qualify, and to advance health data sharing across institutions in support of their care. Details about the pledge and the program can be found at the VA website at https://www.va.gov/health/veteran-interoperability-pledge.asp.

1.4. https://www.va.gov/health/veteran-interoperability-pledge.aspRecognizing interests in advancing this initiative to be available not only to (United States) Veterans across the country, but that many components of this program have collateral benefit to the public at large and other vulnerable communities. The VA requires support services with a neutral community convenor to assemble, manage, orchestrate, enable the broad community of interested parties and stakeholders to examine all dimensions of these issues, to prioritize and advance viable solution approaches to address these needs.

2. SCOPE OR PURPOSE

2.1. This effort will establish a neutral home for this community of interest, managed by professional facilitators under and organization providing open membership. It will allow the broader ecosystem involved in supporting both Veteran care and providing for similar communities to come together, determining shared priorities and solution approaches to take on the biggest challenges they face. It will allow for a unified voice to emerge and provide a powerful force in advancing viable solutions that consider existing laws, regulations, constraints, determining and advocating for changes needed on behalf of the ecosystem. It will allow VA to bring its voice into harmony with the community, advancing both administrative and clinical solutions that are not wholly dependent upon VA capacity and capability.

2.2. Perhaps most importantly, it provides a longevity and sustainability component to these efforts inherent in broadening the consideration beyond an initial set of use cases to broadly consider the holistic set of Veteran needs and how they align to other disadvantaged groups, providing long-term benefit to participating organizations and the beneficiaries they serve.

3. TASKS

3.1. TASK STATEMENT

3.1.1. Contractor’s Progress, Status and Management Report

3.1.1.1. The Project Manager (PM) shall provide a monthly progress report to the Contracting Officer’s Representative (COR) via electronic mail. This report shall include: (1) a summary of all project milestones and their anticipated completion dates, (2) data on cumulative funding and expenditure rates and status, (3) invoicing data, (4) an assessment of current month and future month activities, and (5) a discussion of any issues related to contract performance or administration. The Contractor shall provide a draft Program Management Plan (PMP) three (3) business days prior for review and discussion at the kick-off meeting. The COR shall inform the CO of any contractual issues raised during the kickoff meeting for CO resolution.

Task Three Deliverables: The Contractor shall deliver:

1.0 Project Management Plan and Monthly Updates

3.1.2. Kickoff Meeting

3.1.2.1. The Contractor shall conduct a technical kick-off meeting with the Government including the PM, COR, and contracting office. A technical kickoff meeting is required within ten (10) calendar days after contract award. The technical kick-off meeting shall occur along with the post award conference. The kick-off meeting shall set expectations.

Task Three Deliverables: The Contractor shall deliver:

2.0 Kick-off meeting

3.1.3. Staffing Roster

3.1.3.1. The contractor shall provide a roster of all participants with relevant demographic information to include location, phone number, and time zone on the fifth business day of the month.

Task Three Deliverables: The Contractor shall deliver:

3.0 Staffing Roster

3.1.4. Establish a Community of Practice

3.1.4.1. The objective is to transition the initial signatories into an open community of practice, to charter a new, open group, and to conduct outreach to attract and grow this community to involve other stakeholders contributing to or impacted by this objective. The starting-point of this community would be focused on current VA priorities (suicide prevention, toxic exposures, etc., the intention is to grow the scope to address full-spectrum community and cross-community care concerns (scheduling, registration, eligibility, payment, record sharing, problem list sharing, etc.). Moreover, while a key goal is to advance Veteran care and outcomes, the intention is to provide for improvements to care for much broader cohorts, including, but not limited to Veterans. Specific sub-objectives for this area include:

· Inviting and transitioning existing signatories to the new community.

· Identifying non-participating organizations and outreaching to spur their participation.

· Establishing a community charter, governance, policies, and procedures.

· Determining initial goals and objectives.

3.1.5. Integrating VA into the ecosystem

3.1.5.1. The contractor shall support establishment of a Community of Practice by leveraging existing industry partners, relationships, and bodies within the informatics communities who engage standards-based exchange. Industry community refers to partners relationship within the following areas and examples:

· Providers

· Payers

· Vendors

· Oracle Health

· Epic Systems

· Partners

· Healthcare Information and Management Systems Society (HIMSS)

· American Medical Informatics Association (AMIA)

· Health Level 7 (HL7)

· Trusted Exchange Framework and Common Agreement (TEFCA) entities, including Recognized Coordinating Entity (RCE) and Qualified Health Information Networks (QHINs), and established health information exchanges, such as eHealth Exchange

· Federal Partners such as:

· Office of National Coordinator

· Centers of Medicare and Medicaid Services

· Federal Drug Administration

· National Institute of Health

· Health and Human Services

· Indian Health Service

Task Three Deliverables: The Contractor shall deliver:

4.0 Community of Practice charter with identified representative participants from signatories.

4.1 Work Plan with key objectives to support industry stakeholder engagement and participation.

4.2 Prospective list of future signatories with points of contact and timelines of engagement.

4.3 Progress report on list of future signatories list, additional members, and status of new partners.

3.1.6. Monthly Reports on Community of Practice Management

3.1.6.1. Key to this tasking is providing ongoing support and management functions for the community of practice, assisting in establishing a regular cadence of meetings, planning agendas, determining shared priorities, tracking actions, and advancing the group toward a consensus position on items of import. The intention behind the facilitation and management of the community is to provide functions as services to support and sustain the community, freeing up participants to focus on high-value content contributions without getting bogged down in administrative operations.

3.1.6.2. Maintaining neutrality across the community, assuring open participation and egalitarian opportunity to contribute and benefit from the work is critical to this component. Dissenting voices should be heard, and concerns noted, with a goal toward finding common, consensus ground.

3.1.6.3. The contractor shall support the management of Community of Practice through strategic engagement and management by providing the enabling capabilities and management oversight to optimize the efficacy and utility of the community, allowing it to achieve its goals, such as:

· Status reports that include:

· Stakeholder management supported by meeting facilitation, agendas, and minutes.

· One (1) in-person conference to include all known industry partners.

· Hosting meetings, managing the community, building the community, convening in-person and virtual sessions, engaging stakeholders, and recruiting likely interested participants toward initiative success.

· Project management support (calendar management, meeting management, etc.).

· Facilitation and consensus-building.

· Meeting Support (planning, hosting [physical and virtual], notetaking, minutes, action items, etc.).

· Collaboration Support (providing tools to enable virtual collaboration [both synchronous and asynchronous], document sharing, decision-making, etc.)

· Determination of community priorities, establishment of consensus, establishment, management, and curation of community backlog.

Task Three Deliverables: The Contractor shall deliver:

5.0 Monthly progress reports of participants, areas of focus and development, and timelines of market development.

5.1 Stakeholder Reports

5.2 Stakeholder communication plans

5.3 Stakeholder conference

5.4 Strategic Communications plan

5.5 Presentations/briefings

5.6 Talking points and position papers

5.7 Public Facing SharePoint repository to house all stakeholder documents.

5.8 Health Care Policy and Industry Standards Analysis Reports.

3.1.7. Community of Practice Maturation Strategic Plan

3.1.7.1. To have comprehensive strategic support for the initiative, Clinical Informatics Office is primarily concerned with the identification, mitigation, inclusion of skills, capabilities, or expertise determined to be important for programmatic goals and lacking in the assembled community. The objectives include the ability to identify, recruit, and engage individuals and organizations to close any determined gaps, and to take pro-active steps to optimize the impact and outcome of community efforts. This includes, but are not limited to:

· Strategic plan that includes industry trends, opportunities for collaboration, industry threats, weaknesses, and impacts to public health.

· Interoperability trend analysis to include educational gaps, attrition, and manpower availability.

· National landscape of existing community, at the state, local, federal levels, and private sector approaches to health care interoperability and opportunities to leverage interstate or public/private partnerships.

· Determination of impactful trends affecting the community (AI, TEFCA, etc.)

· Identification and remediation of skillset gaps.

· Identification of collaborative, complementary, or competing activities and action steps to align/coordinate/harmonize this Community of Practice’s activities.

· Identify key challenges (such as technology or policy constraints) and mitigation strategies or actions to mitigate the key challenges.

· Establishing a virtual resource library of reference content to educate community on ongoing relevant work.

· The Contractor shall provide and leverage existing industry knowledge, relationships, and partnerships to enhance Community of Practice engagement and participation.

Task Three Deliverables: The Contractor shall deliver:

6.0 Community of Practice Maturation strategic plan

6.1 Semi-Annual Updated Community of Practice Maturation strategic plan

6.2 Report on health care interoperability trend analysis

6.3 Semi-Annual updated monthly report on health care interoperability trend analysis

6.4 Report of national landscape of existing community

6.5 Semi-Annual updated Report of national landscape

4. SCHEDULE

4.1 Base Period Deliverables

TASKS

TASK DELIVERABLES

QUANTITY

DELIVERY DATE

1.0

Project Management Plan

Within the first three (3) business days of contract award

2.0

Kickoff meeting

Within the first ten (10) calendar days of contract award

3.0

Staffing Roster

5th business day of the month

4.0

Community of Practice charter with identified representative participants from signatories.

Within twenty (20) business days of contract award

4.1

Work Plan with key objectives to support industry stakeholder engagement and participation.

Within ten (10) business days of contract award

4.2

Prospective list of future signatories list with points of contacts and timelines of engagement

Within thirty (30) business days of contract award

4.3

Progress report on list of future signatories list, additional members, and status of new partners

Bi-monthly every first Monday starting on the 61st day from contract award

5.0

Monthly progress reports of participants areas of focus and development, and timelines of market development.

5th business day of the month

5.1

Weekly Stakeholder Reports

Recurring every five (5) business days (once per week)

5.2

Stakeholder Communication Plan

Within twenty (20) business days of receipt of request

5.3

Stakeholder conference (in person) for up to 150 attendees

Within 120 calendar days of request

5.4

Strategic Communication Plan

Within twenty (20) business days of receipt of request

5.5

Presentation/Briefings

As requested, approximately bi-monthly, within ten (10) calendar days of request

5.6

Talking Points and Position Papers

As requested, approximately bi-monthly, within ten (10) calendar days of request

5.7

Public Facing SharePoint repository to house all stakeholder documents

Within four (4) months of receipt of request

5.8

Health Care Policy and Industry Standards Analysis Reports

As requested, approximately bi-monthly, within ten (10) calendar days of request

6.0

Community of Practice Maturation strategic plan

Within twenty (20) business days of receipt of request

6.1

Semi-Annual Updated Community of Practice Maturation strategic plan

As requested, six (6) months from contract award

6.2

Report on health care interoperability trend analysis

Within twenty (20) business days of receipt of request

6.3

Semi-Annual updated report on health care interoperability trend analysis

As requested, six (6) months from contract award

6.4

Report of national landscape of existing community

Within twenty (20) business days of receipt of request

6.5

Semi-Annual updated Report of national landscape

As requested, six (6) months from contract award

4.2. Option Period One (1) Deliverables

TASKS

TASK DELIVERABLES

QUANTITY

DELIVERY

DATE

1.0

Project Management Plan

Within the first eight (8) calendar days after the effective date of Option Period One (1)

3.0

Staffing Roster

5th Business Day of the month

4.2

Progress report on list of future signatories list, additional members, and status of new partners

Within twenty (20) business days of receipt of request

5.0

Monthly progress reports of participants areas of focus and development, and timelines of market development.

5th Business Day of the month

5.1

Weekly Stakeholder Reports

Recurring every five (5) business days (once per week)

5.8

Health Care Policy and Industry Standards Analysis Report

As requested, approximately semi-annually, deliver in the first six (6) and twelve (12) months of Option Period One (1)

6.1

Semi Annual Updated Community of Practice Maturation strategic plan

As requested, approximately semi-annually, deliver in the first six (6) and twelve (12) months of Option Period One (1)

6.3

Semi Annual updated report on health care interoperability

As requested, approximately semi-annually, deliver in the first six (6) and twelve (12) months of Option Period One (1)

6.4

Semi Annual updated Report of national landscape of existing community

As requested, approximately semi-annually, deliver in the first six (6) and twelve (12) months of Option Period One (1)

4.3. Option Period Deliverables (Option Periods Two (2) – Four (4))

4.3.1. Same as Option Period One (1)

5. Period of Performance

5.1. The period of performance for this contract is a base period of twelve months with four (4), twelve (12) month option periods. The Government’s decision not to exercise an option shall not be considered a termination.

6. Type of Contract

6.1. The contract shall be Firm-Fixed Price. Travel will be a Not to Exceed (NTE) amount per Period of Performance (POP).

7. Place of Performance

7.1. Efforts under this contract shall be performed at Contractor facilities or teleworking. The Contractor shall work to be scheduled in all time zones from Eastern to Pacific.

8. Travel

8.1. The Government anticipates travel under this effort. Travel must be pre-approved in writing by the Contracting Officer’s Representative (COR) and in accordance with Federal Travel Regulations. Each Contractor invoice must include copies of all receipts that support the travel costs claimed in the invoice. Local travel within a 50-mile radius from Government facilities within the Washington DC area and the contractor’s facility is considered the cost of doing business and will not be reimbursed. This includes travel, subsistence, and associated labor charges for travel time. Travel performed for personal convenience and daily travel to and from work at the Contractor’s facility will not be reimbursed. Travel, subsistence, and associated labor charges for travel time for travel beyond a 50-mile radius of the Contractor’s facility are authorized for reimbursement on a case-by-case basis and must be pre-approved by the COR and must be planned and executed according to Federal Travel Regulations. General and Admi

8.2. The FTR can be referenced at:

http://www.gsa.gov/portal/ext/public/site/FTR/file/FTRTOC.html/category/21865/hostUri/portal

9. Government-Furnished Information, Equipment, and Facilities

9.1. The VA Digital Health Office (DHO) office shall provide full administrator access to the tools listed below. If the mandated toolset changes throughout the POP, then the Government shall provide access to the new toolset.

9.2. VPN access to the VA network (RESCUE)

9.3. Citrix Access Gateway (CAG)

9.4. Microsoft Office 365

10. Security Requirements

10.1. If a solicitation is issued, this section will be completed at that time.

11. Changes to the Performance Work Statement

11.1. Any changes to this Performance Work Statement (PWS) shall be authorized and approved only through a signed modification to the contract from the CO. A copy of each modification shall be kept in a project folder along with all other products of the project.

12. Key Personnel

12.1. Contractor staff shall be fully qualified and have the level of experience necessary to accomplish the requirements of this PWS. In addition, Contractor personnel shall be acceptable to the Government in terms of personal and professional conduct, and in technical knowledge. Furthermore, Contractor personnel shall be proficient using office automation equipment and software, and have sufficient written and verbal communication skills to support VA. The work accomplished in this Task Order shall not use offshore labor unless specifically agreed to by the contracting office. Should any Contractor personnel be determined to be unacceptable in terms of technical competency or unacceptable personal conduct while on-site or while working on contract activities, the Contractor shall immediately remove and replace the unacceptable on-site personnel at no additional cost to the Government. Contractor personnel are to serve in a support role; final decisions regarding VA business will always be made by Government personnel.

12.2. Certain skilled experience professional and/or technical personnel are essential for accomplishing the work to be performed. These individuals are defined as “Key Personnel” whose experience biographies shall be submitted and marked by the Contractor as “Key Personnel”. Substitutions shall only be accepted if in compliance with the “Substitution of Key Personnel” provision identified below.

12.3. The Project Managers, Business Process Reengineering Specialists, Business Analysts, Scientific Data Analysts, Test Engineers, Subject Matter Experts, Communications Specialists, and Quality Assurance Analysts are defined as Key Personnel and, except in cases where individuals commit criminal conduct or violations of company policy, shall not be removed, diverted, or replaced from work without notifying the CO and COR.

12.4. Any personnel that the Contractor offers as substitutes shall have the ability and qualifications equal to or better than the key personnel who are being replaced. The Contractor shall submit a complete resume for the proposed substitute and any other information requested by the CO needed to approve or disapprove the proposed substitution. The CO will evaluate such requests and promptly notify the contractor of approval or disapproval thereof in writing.

ROLE

SKILL SET DEFINITION

MINIMUM EDUCATION LEVEL

MINIMUM EXPERIENCE

Health Governance and Policy Analyst

Skilled expert in health policy analysis and implications to industry. Expert knowledge of Federal, State and Local law and its impacts to the industry. Expert knowledge of and ability to leverage contacts within HIMSS, HL7 and other industry partners with established relationships with industry partners to include HIMSS, AMIA, Epic, Oracle Health, Office of the National Coordinator of Health IT, and other Federal Health Care partners at the state and local level. Expert knowledge in digital health initiatives and coordination activities in both public and private markets.

Master’s Degree or Juris Doctorate level completion

Four (4) years specialized experience in Health Information Technology

Health Care Analytics, Standards, and Interoperability Specialist

Expert knowledge, skill, and ability to leverage established Interoperability relationships and industry partners to be a neutral voice for quality standards-based exchange; working knowledge of HL7, OASIS, eHealth Exchange, and TEFCA; established relationships with industry partners to include HIMSS, AMIA, FHIR, Epic, Oracle Health, ONC and other Federal Health Care partners at the state and local level. Expert knowledge in digital health initiatives and coordination activities in both public and private markets.

Bachelor of Science in Nursing, Public Health, or Medical Doctor, Four (4) years specialized experience in Health Information Technology, Healthcare Informatics and Analytics

Communications Specialist

Expert knowledge and skill in providing high quality communication products to industry and government executives to include briefings, policy white papers, and press releases.

Bachelor of Arts or equivalent in Communications, English, Public Policy, Political Science, Journalism

Five years specialized experience in public affairs and/or communications

SharePoint Developer

Expert knowledge, skill, and ability to create SharePoint portal.

Bachelor’s degree or equivalent

Five years specialized experience in Microsoft Office SharePoint development, SQL, and coding

Program manager

Intermediate knowledge of the U.S. health care system and experience in digital health, including health information technology, data interoperability, digital product development, standards development. Lead project teams and manage multiple projects. Expert ability to manage project outcomes to ensure requirements are met, including timelines, budgets, and deliverables.

Bachelor’s degree or equivalent

Ten (10) years specialized experience in Health Information Technology, Healthcare Informatics and Analytics environment

Project manager

Knowledge, skill, and ability to create and oversee organized project plans and apply principals of project management. Expert skill and ability to lead project teams and manage multiple projects. Knowledge of health information technology, data interoperability and standards development. Ability and skill to facilitate meetings of varied stakeholders, manage large group dynamics, maintain neutrality, and achieve results.

Bachelor’s degree or equivalent

Five (5) years specialized experience in Health Information Technology, Healthcare Informatics and Analytics environment

Program Analyst

Excellent listening skills, detailed oriented, must have enough subject knowledge to create accurate written versions of meeting notes.

Bachelor’s degree or equivalent

Two (2) years knowledge and experience in Health Information Technology, Healthcare Informatics and Analytics environment

13. Quality Assurance Surveillance Plan (QASP)

The Contractor’s performance will be evaluated based on the following metrics:

REQUIREMENT

PERFORMANCE STANDARD

SURVIELLANCE METHOD

OUTCOME

Project Delivery Schedule

Deliverables should be delivered by the date either specified in the PWS, at the kick-off Meeting, as specified in the project management plan for this contract, or as specified by the COR.

Notifies customer in advance of problems with meeting the deliverable due date.

TBD

Deliverables are on time 100% of the time.

Customer notified no later than seven (7) business days before the due date.

Project Staffing

Personnel demonstrate proficiency in skills necessary to perform tasks.

Knowledge of Access, Excel spreadsheets, macros, effective written and oral communication, presentation and facilitation skills at an executive level.

Knowledge of SharePoint

Online, Office 365, Power Apps, Power Automate and Power BI at an expert level.

TBD

Demonstrated proficiency in the skills required to execute the defined deliverables independently and at high quality.

Complaints

No more than three (3) complaints per quarter on, but not limited to, resource availability, professionalism, engagement during collaboration, response time, effective communication, project deliverable quality.

TBD

100% of the time.