Presentation is loading. Please wait.

Presentation is loading. Please wait.

Physician Office System Program VCUR Conformance Testing Joint POSP CHITTA Vendor Session May 8, 2003.

Similar presentations


Presentation on theme: "Physician Office System Program VCUR Conformance Testing Joint POSP CHITTA Vendor Session May 8, 2003."— Presentation transcript:

1 Physician Office System Program VCUR Conformance Testing Joint POSP CHITTA Vendor Session May 8, 2003

2 Table of Contents  objective  overview  timeframe  policies under consideration  Alberta / Ontario collaboration update  VCUR requirements clarification  approach - input required

3 Conformance Testing Objective to enable vendors to successfully meet all the VCUR requirements by providing appropriate support and constructive feedback during the conformance testing process

4 Conformance Testing Overview VCUR 2004 Requirements EHR Interfaces: e.g. PIN, PPHI etc. Other VCUR Requirements: e.g. EMR, Security etc. Other Interfaces: e.g. AHW Billing, Regional Lab Test Results Delivery etc. ‘Independent’ Testing Organization Vendors Letter of Conformance Testing

5 Timeframe  VCUR publicationApril 8, 2003  PIN 1.2.5 and PPHI 2.0 specifications frozenApril 30, 2003  ‘Sand Box’ environment available  release 1 April 30, 2003  release 2 June 30, 2003  ‘independent’ testing organization in placeJune 30, 2003  issue invitation to conformance testing includingAug. 31, 2003  approach and process  test scripts  conformance testing commencesSept. 2003  publication of first Vendor Conformance ListApril 2004

6 Policies Under Consideration  physicians who purchased software and their vendors are not on the Vendor Conformance List  testing stages  EHR interfaces (PIN and PPHI)  other interfaces (AHW Billing and regional lab test results delivery)  access, privacy, security, technical and mobile communications devices  billing, scheduling, EMR, workflow, usability, ergonomics and clinical decision support  change process for VCUR requirements

7 Alberta / Ontario Collaboration Update  short term  develop cross reference for terminology  develop cross reference for ‘identical’ requirements; identify minor differences  information sharing on process and approach  medium term  harmonizing terminology, requirements, process and approach  long term  reciprocal agreement on testing

8 VCUR Requirement Clarification  submit your request in writing to Kari Taylor Atkins POSP IT Services at kari.tayloratkins@gov.ab.ca  written response will be provided, on a best effort basis, within 5 working days  written response will also be posted on the POSP AMA, CHITTA and Alberta Wellnet websites

9 Approach - Input Required 1 testing location A testing location  PIN, PPHI  other VCUR requirements  ASP  local installation  options:  remote  vendor site  clinic site  Testing Organization site  others

10 Approach - Input Required 1 testing location B testing at the clinic site  in addition to testing the software, do we need testing at every clinic? (similar to what Capital Health does for lab)  options:  yes  no  others

11 Approach - Input Required 2 re-test upon failure  options:  re-test all items  re-test failed items only  re-test failed and related items; who decides on related items?  others

12 Approach - Input Required 3 who pays  first test  second test  third test etc………..  options:  Testing Organization  vendor  sharing based on a formula; formula?  others

13 Approach - Input Required 4 re-test on software changes (software upgrade) and ASP facility A re-test on software changes (software upgrade)  options:  re-test software on any changes  re-test all VCUR requirements  re-test on changes and related items only; who decides on related items?  re-test on ‘major’ changes only; define ‘major’  re-test all VCUR requirements  re-test on changes and related items only; who decides on related items?  others

14 Approach - Input Required 4 re-test on software changes (software upgrade) and ASP facility B re-test on ASP facility  options:  re-test on any changes  re-test on ‘major’ changes; define ‘major’  re-test every 2 years  others

15 Approach - Input Required 5 testing windows  testing windows  from September 2003 to March 2004: continuously ‘on demand’ basis  thereafter,  options:  ‘on demand’ all year round  specific windows, e.g. 2 windows per year; 2 months per window  others

16 Approach - Input Required 6 publication of Vendor Conformance List and appeal process A publication of Vendor Conformance List  first list will be published in April 2004  thereafter,  options:  publish as vendor conforms  monthly  quarterly  others

17 Approach - Input Required 6 publication of Vendor Conformance List and appeal process B appeal process  options:  yes; who is on appeal panel? Decision final?  no  others

18 Questions? Contact: Joe Leung Team Lead, POSP IT Services (780) 415-1531 joe.leung@gov.ab.ca joe.leung@gov.ab.ca

19 Discussion Groups Facilitator Group 1Vic Toews Group 2John David Group 3Brendan Byrne Group 4Don Martin Group 5Donovan Volk Group 6Cam Kochorek


Download ppt "Physician Office System Program VCUR Conformance Testing Joint POSP CHITTA Vendor Session May 8, 2003."

Similar presentations


Ads by Google