ONC Unveils Direct Guidance to Help Providers in Stage 2
Recently, Office of the National Coordinator for Health IT (ONC) released programmatic guidance for State HIE grantees who act as Health Information Service Providers (HISPs) for providers to engage in Direct, point-to-point, exchange. According to ONC, they have found that HISPs are deploying Direct in a way that “enables exchange within a given HISP’s boundaries while not offering mechanisms or supporting policies that enable exchange with other HISPs.” This guidance is meant to address this problem. The document defines and recommends guidelines for:
- Security and Trust Agents (STAs), another designation for HISPs, that facilitate Direct exchange services;
- Registration Authorities (RAs) that establish the identity of providers and;
- Certificate Authorities (CAs) that issue certificates.
“ONC believes that adoption of these consensus policies…will enable providers to easily and securely exchange patient health information using Direct irrespective of organizational and vendor boundaries to meet Stage 2 Meaningful Use exchange requirements and overall care coordination needs” [emphasis added]. And this is why it matters: Direct will most likely be the most viable way for many providers to meet exchange requirements under Stage 2, but the task is not as simple as its early cheerleaders would have you believe (especially in moving information across vendor boundaries). ONC has tapped DirectTrust to “establish and promote the adoption of security and trust ‘rules of the road,’ including the guidelines issued by ONC for Direct exchange, operationalized via accreditation,” ONC’s Kory Mertz wrote in a Buzz Blog. According to DirectTrust CEO, Dr. David Kibbe, they’re getting engaged with the vendor community and the HISPs, but many providers have not yet clued into the importance of Direct governance.
This is an important conversation for CHIME members to engage as they prepare for Stage 2. And expect more practical Direct implementation advise from ONC and CMS – instead of just extolling Direct’s virtues – moving forward.
House Committee Unveils Draft Legislation to Repeal SGR
The House Energy and Commerce Committee unveiled draft legislation to repeal the current Sustainable Growth Rate (SGR) system recently. The draft legislation is the latest step to reform the system and reward providers for delivering high-quality, efficient health care. On February 7, the Energy and Commerce and Ways and Means Committees outlined a framework to reform the current Medicare system that is fiscally responsible and free of politics. Committee leaders sought feedback and in early April outlined additional details of a proposal to repeal and replace the current SGR. Missing from this draft legislation was how the Committee was thinking about paying for the permanent fix; an update to how much a fix would cost or what the quality / alternative payment structure would look like.
Several groups, Republicans and Democrats, in both the House and Senate are focused on ways to repeal the SGR and phase in a reimbursement model that leads providers away from fee-for-service. This draft legislation joins a bill, HR 574offered by House Representatives Allyson Schwartz (D-PA) and Rep. Joe Heck (R-NV) that would repeal the SGR, while also incentivizing innovative payment and delivery models. So far, these are the only pieces of legislation – draft or otherwise – up for debate. But there will be more to follow.
The Energy & Commerce Subcommittee on Health has scheduled a hearing on the draft legislation for June 5 and is requesting feedback by June 31.
ONC Asks for Public Input on FDASIA Workgroup Deliberations
On Thursday of this week, ONC released a request for comment (RFC) asking for input “on the elements we should consider as we develop a report that contains a proposed strategy and recommendations on an appropriate, risk-based regulatory framework for health IT, including mobile medical applications, that promotes innovation, protects patient safety, and avoids regulatory duplication.” The three-question RFC asks: