HIT Policy Committee<br />Information Exchange Workgroup<br />MickyTripathi, MA eHealth Collaborative, Chair<br />David Lansky, Pacific Business Group on Health, Co-Chair<br />December 6, 2010<br />
Today’s objectives<br />Review HIT Policy Committee meeting<br />Timeline for remaining provider directory recommendations <br />Policy options for promoting entity-level provider directories (ELPD) <br />Individual-level provider directories (ILPD)<br />Today’s discussion will focus on policy options for promoting creation of ELPDs with recommended characteristics<br />2<br />
Provider Directories - Where are we in process?<br />Recommendations on Directory <br />Requirements and Options<br />Policy <br />Recommendations<br />Users and Uses<br />Functions<br />Content<br />Operating rqmts<br />Business models<br />Policy issues<br />Policy actions<br />Who wants an entity directory?<br />What do they want to use it for?<br />What functions do users need for their desired uses?<br />What data will be required in order to enable desired functions?<br />What operating business requirements will be needed in order for this to be used?<br />What are possible business models for meeting needs?<br />Which business models should the government promote?<br />What are the policy issues related to each of the suggested business models?<br />What policy actions should be taken to address the policy issues?<br />-- Entity-Level Provider Directory (ELPD) Recommendations approved by HITPC on 11/19<br />-- Recommendations on Policy levers for ELPD to HITPC for 12/13<br />-- ILPD Recommendations to HITPC for 2/2 meeting<br />-- Recommendations to HITPC 12/13<br />3<br />
HIT Policy Committee<br />The ELPD recommendations were accepted by the Committee<br />
HITPC-approved recommendations (1)<br />Recommendation: The following entities should be listed in the ELPD<br />Health care provider organizations (i.e., hospitals, clinics, nursing homes, pharmacies, labs, etc)<br />Other health care organizations (i.e., health plans, public health agencies)<br />Health Information Organizations (i.e., regional HIE operators, health information service providers)<br />Other organizations involved in the exchange of health information (business associates, clearinghouses)<br />Recommendation: ELPDs should support the following functionality<br />Support directed exchanges (send/receive as well as query/retrieve)<br />Provide basic “discoverability” of entity<br />Provide basic “discoverability” information exchange capabilities (i.e. CCD, HL7 2.XX)<br />Provide basic “discoverability” of entity’s security credentials<br />5<br />
HITPC-approved recommendations (2)<br />Recommendation: ELPDcontent should be limited to the following categories of information<br />Entity ‘demographics’ and identification information<br />Name, address(es)<br />Other familiar names<br />Human level contact<br />Information Exchange Services<br />Relevant domains (as defined by each entity); relevant website locations<br />Protocols and standards supported for Information Exchange (SMTP, REST, CCD/CDA, CCR, HL7 2.x.x, etc) - Two Options:<br />Include a ‘pointer’ in the directory to the entity’s information (recommended)<br />Include the entity-level information in the directory<br />General Inbox location, if applicable (for message pick-up/drop-off)<br />Security<br />Basic information about security credentials (i.e., type, location for authentication)<br />6<br />HITPC-approved recommendations (2)<br />
HITPC-approved recommendations (3)<br />Recommendation: Business model and operating approach<br />Internet-like model (nationally coordinated, federated approach)<br />Certified registrars: registrars are ‘registered’ and certified to receive/process/accept entities in the ELPDs<br />National guidelines: Registrars follow national guidelines for who to accept, validation of application, addressing<br />Registrar reciprocity and Publication to National Registry System:<br /><ul><li>Entities registered by one registrar are ‘recognized’ across system (no need to register again at different registrars)
Each registrar publishes directory information into a national provider directory registry system that, like DNS, will support identification of entities across registrar domains</li></ul>ELPDs: maintained by registrars; cross-referenced through system (similar to DNS)<br />Possible roles of federal government:<br />National standardization and harmonization<br />Some agencies could be registrars themselves (i.e., Medicare, VA)<br />Build on existing national/federal tools (i.e., PECOS, NPPES, NLR, others)<br />7<br />HITPC-approved recommendations (3)<br />
Timeline<br />Currently working to schedule WG and Taskforce calls for January<br />8<br />
Discussion of Provider Directory Policy Recommendations<br />9<br />
Policy Questions<br />Which business models should the government promote?<br />What are the potential government roles and levers?<br />What is the appropriate level of depth in policy recommendations (and avoid stepping into role of Standards Committee)<br />What is critical and necessary to meet our goals (minimal necessary principal)<br />10<br />
Key questions<br />What approaches would best promote rapid adoption of an ELPD-network?<br />Standards: In which areas would standards and guidelines facilitate creation of market-sustainable ELPDs?<br />Infrastructure: Is a federal (or federally-mandated) infrastructure required to lay the foundation of a nationwide ELPD service?<br />Federally created ELPDs?<br />State-created ELPDs using state-level HIE funds?<br />Federal accreditation of ELPD registrars?<br />Participation and sustainability: How much carrot and stick is likely to be needed to launch a nationwide ELPD service that has high participation and can pay for itself (ie, no government funds needed)<br />Is the creation of robust standards enough to catalyze a market-driven solution?<br />Can government levers assist with creation and/or sustainability?<br />MU requirement?<br />Medicare registration requirement?<br />NHIN Exchange or Direct participation requirement?<br />Federal government contracting requirement?<br />12<br />
Recommendation for discussion <br />Proposed Recommendation: Standards for ELPD<br /><ul><li>HITSC develop certification and operating standards in key areas of ELPD recommendations:
Content: How should key content be represented in ELPDs?
Architecture: What technical guidelines should be promulgated to facilitate the federated architecture approach to ELPDs?
What standards should be used for ELPD registrars to communicate with each other?
What standards should apply to EHR vendors to consume ELPD services?
What standards should apply to source systems to enable automated population and updating of ELPDs?</li></ul>13<br />
14<br />Next Steps<br />Based on the conversation today draft recommendations will be circulated among the WG to finalize for presentation at the December 13 HITPC meeting<br />Provider Directory Taskforce will turn to individual-level provider directory<br />