Presentation is loading. Please wait.

Presentation is loading. Please wait.

2015 Edition Certification NPRM HPD Group Report Out May 7, 2015 Architecture, Services, and APIs Arien Malec, co-chair David McCallie, co-chair.

Similar presentations


Presentation on theme: "2015 Edition Certification NPRM HPD Group Report Out May 7, 2015 Architecture, Services, and APIs Arien Malec, co-chair David McCallie, co-chair."— Presentation transcript:

1 2015 Edition Certification NPRM HPD Group Report Out May 7, 2015 Architecture, Services, and APIs Arien Malec, co-chair David McCallie, co-chair

2 ASA Workgroup - Active Members 1 NameOrganization David McCallie, co-chairCerner Arien Malec, co-chairRelayHealth Clinical Solutions Janet CampbellEpic George ColeAllscripts Josh MandelChildren's Hospital Boston Jeff GuntherPremier, Inc. Gajen Sunthara, ex officioDepartment of Health and Human Services (HHS) Albert BonnemaDefense Health Agency Debbie Bucci, staff leadHHS, Office of the National Coordinator

3 Architecture, Services and Application Program Interfaces (APIs) Workplan 2 MeetingsTask April 9, 2015 12:00 – 1:30pm ET Overview of Certification NPRM and prepare to comment April 22, 2015 – HITSC meeting Interoperability Roadmap V.1 comments to the HITSC April 23, 2015 12:00 – 1:30pm ET API Group to Comment on Certification NPRM May 5, 2015 4:00 - 5:00pm ET Non-API Group to Comment on Certification NPRM  May 7, 2015 2:00 – 3:30pm ET HPD Group to Comment on Certification NPRM May 19, 2015 9:00 – 10:00am ET Finalize comments on Certification NPRM May 20, 2015 – HITSC Meeting Present Certification NPRM Comments to the HITSC

4 Architecture, Services & APIs Assignments 3 API Group - Workgroup Meeting, April 23Non API Group – Workgroup Meeting, May 5HPD Group - Workgroup Meeting, May 7 Homework due April 20 th Homework due May 4 th VDT - Application Access to Common Clinical Data Set Application Access to Common Clinical Data Set XDM Package Processing Data Portability “Create” and Patient Matching Data Quality Healthcare Provider Directory – Query Request Healthcare Provider Directory – Query Response

5 XDM Package Processing 4/27/20154 Intro to Proposed Rule: Therefore, if Edge System B does not support XDM package processing, interoperability could be impacted when HISP-B forwards XDM packages to Edge System B via the SMTP protocol. To mitigate this potential incompatibility, we propose to include a specific capability in this certification criterion that would require a Health IT Module presented for certification that is also being certified to the SMTP-based edge to demonstrate its ability to accept and process an XDM package it receives, which would include extracting relevant metadata and document(s). Comments: No comment received

6 Healthcare Provider Directory – Query Request 4/27/20155 Intro to Proposed Rule: (4) Healthcare provider directory – query request. In accordance with the standard specified in § 170.202(f)(1), technology must be able to make, at a minimum, the following queries to a directory and subsequently process the response returned: (i) Query for an individual provider; (ii) Query for an organizational provider; (iii) Query for both individual and organizational providers in a single query; and (iv) Query for relationships between individual and organizational providers. (v) Optional - federation. In accordance with the standard specified in § 170.202(f)(1), technology must be able to process federated responses. Comments: Requiring HPD is, at this point, inappropriate. ONC interprets HITSC as saying that since HPD+ is too immature, HPD is an appropriate standard. However, HITSC’s actual quote (at reference 194) is “No existing provider directory standard is ready to become a national standard – IHE HPD+ is a good start, but needs proof in the marketplace.” As HITSC says, HPD+ is a promising standard and one that should be pursued. Locking HPD into certification would waste development time and energy.” Although we have concerns re: the stability and adoption of HPD: At 2015 Connectathon: 14 passed for HPD Query (so as clients) and 15 passed for HPD Responses (so as directories) IHE Product Registry, HPD: http://product- registry.ihe.net/PR/pr/search.seam?integrationProfile=215&domain=2&date=ANY|1430247909594|14302479 09594 lists 17 integration statements from 12 unique companies, 3 of which were updated in 2015.http://product- registry.ihe.net/PR/pr/search.seam?integrationProfile=215&domain=2&date=ANY|1430247909594|14302479 09594 IHE ITI is likely to move HPR profile to Final Text this August. Agree with federation responses as Optional.

7 Healthcare Provider Directory – Query Response 4/27/20156 Intro to Proposed Rule: (5) Healthcare provider directory – query response. In accordance with the standard specified in § 170.202(f)(1), technology must be able to, at a minimum, respond to the following queries to a directory: (i) Query for an individual provider; (ii) Query for an organizational provider; (iii) Query for both individual and organizational providers in a single query; and (iv) Query for relationships between individual and organizational providers. (v) Optional - federation. In accordance with the standard specified in § 170.202(f)(1), technology must be able to federate queries to other directories. Comments: Agree with federation of queries to other directories as Optional.

8 Process for Responding Cert. NPRM Introduction Group Comments Develop Consensus Review Comments with HITSC 7 Cert. NPRM Overview Discuss process Review deadlines Members draft and submit comments to ONC staff by April 17th Prepare materials for assigned meeting reviews comments workgroup Workgroup refines draft recommendations Chairs brief HITSC April 9Offline workApril 23 May 7 May 20 HITSC Meeting


Download ppt "2015 Edition Certification NPRM HPD Group Report Out May 7, 2015 Architecture, Services, and APIs Arien Malec, co-chair David McCallie, co-chair."

Similar presentations


Ads by Google