Presentation is loading. Please wait.

Presentation is loading. Please wait.

Physician Office System Program VCUR dependencies

Similar presentations


Presentation on theme: "Physician Office System Program VCUR dependencies"— Presentation transcript:

1 Physician Office System Program VCUR dependencies
POSP/CHITTA VENDOR SESSION May 8, 2003 A Joint Initiative Alberta Health & Wellness – Alberta Medical Association

2 Background VCUR approved by POSP Subcommittee March 28th, 2003 published April, 2003 majority of requirements to come into force April 1, 2004 conformance testing scheduled for late Fall, 2003 several dependencies identified majority of dependencies relate to EMR/EHR integration most “owned” by Alberta Wellnet some by regions, POSP

3 Background (cont.) Extract from VCUR Task Force final report:
“For the VCUR process to be realized, health system stakeholders must act now to ensure that the dependencies identified in Appendix Two are addressed. A mechanism to track performance relative to the dependencies timeline needs to be established, and any variances from that timeline brought to the attention of the Information Management/Information Technology Governance Council”

4 Background (cont.) monthly status reports prepared on progress relative to dependencies timeline status reports shared with CHITTA and CHITTA’s internal EMR/EHR working group need ongoing dialogue to determine impact of slippage (relative to timelines) on coming-into-force of VCUR

5 Break-out questions What are the “key” dependencies (i.e., those that have a “linear” relationship with VCUR coming-into-force date)? How will vendors provide status/feedback on their progress relative to implementing VCUR? What steps can we take together to ensure the process does not become adversarial?


Download ppt "Physician Office System Program VCUR dependencies"

Similar presentations


Ads by Google