Posts Tagged ‘John Fraser’

The Patient Centered Medical Home

Friday, August 13th, 2010

- By John Fraser, MEDNET

A Medical Home can have a significant impact on patients, especially patients with a chronic (or multiple) conditions, as well as the patient’s family. Healthcare organizations need suitable technology solutions to enable the secure sharing of patient information across organizational boundaries, to automate workflows, to comply with regulations, and to manage patients with chronic conditions outside the acute care setting.  Enter the Medical Home, or Patient-Centered Medical Home.

But what is a Medical Home exactly? As defined by The National Committee on Quality Assurance (NCQA), “The Patient Centered Medical Home is a health care setting that facilitates partnerships between individual patients, and their personal physicians, and when appropriate, the patient’s family. Care is facilitated by registries, information technology, health information exchange and other means to assure that patients get the indicated care when and where they need and want it in a culturally and linguistically appropriate manner.”

Living with multiple or chronic conditions can be difficult for patients.  Patients and providers need quick and easy access to health information to better understand and manage chronic conditions. Provider organizations are committed to helping patients live a happier and healthier life by helping them manage these chronic conditions outside the acute care setting. With chronic care delivery being fragmented by patients visiting multiple care providers at different locations, it is a challenge to deliver the right care to patients.  Lack of current, relevant patient information across the different care facilities also adds to the challenge.

A Medical Home can help providers manage patients with specific conditions, manage chronic diseases, coordinate multiple caregivers, and help collect quality information.  A Medical Home can track patients across care settings and over time to improve patient outcomes and quality.

A Medical Home can be deployed as a separate service for individual projects, or integrated with other, existing services and Health Information Exchanges.   In fact, Medical Homes can be fully integrated and supported by the Nationwide Health Information Network, or NHIN.  Therefore, Medical Homes should be considered in a provider’s HIT roadmap, as well as the roadmap of services and integrated/supported offerings by a Health Information Exchange.

Next month, we will dive deeper into Medical Homes, use-cases, and goals of the interoperable Medical Home.

The Role of PHRs in Health Information Exchange

Tuesday, July 20th, 2010

- By John Fraser, CEO of MEDNET

In an ideal world, empowered patients should be able to manage their healthcare on-line, through a Personal Health Record. A Personal Health Record (PHR) is the newer term for systems that allow patients to manage their own health information on-line. The goal of PHRs is to allow patients to directly communicate with a multitude of providers and disparate clinical systems, creating a more efficient marketplace and driving value in healthcare.

Connecting PHRs via Health Information Exchanges (HIEs):

Some PHRs are connected to clinical (or EMR) systems run by a provider (called tethered), while other (un-tethered) PHRs are independent of any particular provider/clinical system.  For example, Google Health and Microsoft’s HealthVault are un-tethered systems and provide ways to connect to many different, existing provider clinical systems, while EMR vendors sell an electronic medical record system that includes a PHR option, which is directly tied, or tethered into only that specific EMR system.

Many people believe that Health Information Exchanges, or HIE, should be able to help bridge the connectivity/tethered PHR gap, and see HIEs as having the ability to simplify the connectivity between PHRs and EMRs and clinical systems.

Within an HIE, a patient is usually registered within the HIE’s Master Patient Index.  Connecting the patient’s PHR to their clinical information (within an HIE) involves connecting and linking the Master Patient Index record to the specific account the patient has setup within their PHR.  Utilizing the Nationwide Health Information Network (NHIN) to connect the HIE nationally, the patient could then use a PHR to connect locally and nationally.  Connecting nationally with their PHR is important for patients applying for Federal programs and benefits, such as Medicare or Social Security Benefits.

By connecting HIEs and PHRs using these new standards like NHIN, we can simplify access to services by the patient, allow better more uniform access on-line, and speed up access to government services and benefits.

HIEs, Identity Management, and Access Controls

Monday, June 14th, 2010

- By John Fraser, CEO of MEDNET

Last month, we discussed the benefit of Federated Identity Management or FIM (read more here). If you recall, Federated Identity Management is the sharing of an identity, carefully managed between different systems. Now lets look at some successful Federated Identity Management implementations:

Microsoft developed a single, sharable login called “Microsoft Passport” which was released in 1999. While in use by a fairly large amount of people, it has not been commercially successful. In fact, the product has been renamed 4 times, from Passport, to .Net Passport, then Microsoft Passport Network, but is now called simply “Windows Live ID”. The idea was to create a single login that could be shared between systems and vendors, but for many reasons, Windows Live ID is mostly used by web sites that are owned or controlled by Microsoft.

Another related effort to create a multi-vendor (vs. Microsoft’s single vendor) standard was the Liberty Alliance, formed in September 2001. Liberty developed the SAML2.0 specification which allows the setup and sharing of secure identities. While commercially successful, it has not been adopted by larger public web sites given its complexity. When security is critical, however, SAML2.0 and the Liberty standards have been considered “industrial quality”.

Liberty has now merged with a new organization called the Kantara Initiative. Kantara is a collaboration of the old Liberty Alliance and the newer OpenID and InfoCard efforts. Kantara has a health care identity assurance Work Group, which is working on a patient portal service to allow patients to access their providers over the new Nationwide Health Information Network, or NHIN.

The most successful, multi-vendor federated identity management system is OpenID, originally developed in 2005. With over a billon OpenID enabled accounts, the system is now owned by the OpenID Foundation, formed in June 2007. The goal of OpenID is to create a simple, easy way to log into many web sites using a single set of credentials. It has been adopted by thousands of web sites, including Sears, Kmart, FoxNews, AOL, Google, PayPal, MySpace, FaceBook, Microsoft, etc. Even the federal government is working to allow OpenID access to certain government services. OpenID’s biggest challenge is ensuring that identity providers are secure, and not the weakest link.

I believe that it’s just a matter of time until federated identity management, or FIM, plays a key role in health care, allowing providers, patients and others a fast, secure and easy way to access scores of services with a single ID. FIM is here to stay, and can be of great benefit to healthcare and the healthcare ecosystem.

Role-Based Access Controls (RBAC) in HIEs

Tuesday, April 13th, 2010

Health Information Exchanges (HIEs) provide access to thousands (or millions) of patient records, shared between participating clinics, hospitals and other providers.  How does an HIE ensure the privacy of patient information within the HIE?  How does the HIE ensure that only appropriate users are accessing patient information?

Today, providers (and some HIEs) use Username and Passwords for access control (to protect patient data and databases). Many security experts believe this level of security is far too low and puts at risk many or all of the records within an HIE with the loss of one username/password.

So, what options does an HIE have for increasing security?

Organizations are looking to upgrade security by using what is called “two factor authentication”, similar to your ATM card and PIN.  Two factor authentication is based upon two parts — something you have (your ATM card) and something you know (your ATM PIN number).

One of the benefits of two factor authentication is the ability to integrate security and encryption technologies as one of the authentication factors (ie the ’something you have’).  Public Key Infrastructure, or PKI, is an example of security and encryption technologies utilized for one of the factors in two factor authentication. In this model, a PKI digital certificate is issued specifically for a user as ’something they have’, with an associated PIN used for something they know, the second factor.  The issuance of the PKI digital certificate (an X.509 certificate), and the integration of a PIN provides higher security for organizations and for an HIE.

Once you have two factor authentication, you know and can audit who is logging in to the system.  You can then provide access to only specific information for a given role – known as role-based access control.  This means that, based upon your role in an organization or HIE, you can be allowed specific access to only applications, services, and systems that are specific to your role. For example, an administrative assistant could access the scheduling software, but not the clinical data or clinical systems.  Conversely, the physician has access to the clinical data and systems, but does not have access to the accounting software and payroll.  User and role based access is a key benefit of two factor authentication with PKI.

Next month we will dive further into access control, Federated Identity Management, and the impact on HIEs.

The Impact of Public Health on HIEs

Tuesday, March 16th, 2010

Will public health benefit from working with health information exchanges (HIEs) and the nationwide health information network (NHIN)?  Much has been written about HIEs and NHIN, but public health is often lost in the shuffle of Health Information Exchange.

Health Information Exchanges are being designed and built to share clinical information between providers.  Public health agencies are both providers (usually in County Health Departments), and researchers, especially at the state departments of health.  Having worked for 10 years at the Minnesota Department of Health, I came to appreciate how important these state health agencies are to keeping the population healthy.  For example, did you know every state health department has an investigative team that carry beepers, ever vigilant to investigate fast moving disease outbreaks?  When an outbreak happens this team will work up to 24 hours a day to determine why groups of people suddenly become ill (getting to the bottom of food-borne or infectious disease outbreaks). These teams are the unsung heroes of our public health agencies, working constantly to keep us all healthy.

So, how will HIEs help public health, and vice versa?  Information is public health’s lifeblood. The unusual reports of disease and outbreaks are critical to finding and solving health problems affecting the population.  Disease and outbreaks are typically reported second-hand, from calls in emergency rooms, to “disease report cards” that every state gets via the mail from providers.

Imagine a world where every provider automatically reports disease outbreaks or unusual problems directly to state health departments, through their health information exchange.  This electronic reporting process would dramatically speed up the investigative response times for outbreak, whether the outbreak is a food poisoning incident at a restaurant, or a bio-terrorism event in the water supply.  Additionally, once we have this type of data flowing in to public health, we can develop sophisticated software to “watch” for disease outbreak patterns (across multiple emergency departments, for example).

HIEs can speed up reporting to local, state, and national public health agencies.  Reporting of infectious diseases, outbreaks, and even bio-terrorism are critical to public health agencies.  With the ability of NHIN to connect HIEs, healthcare reporting should no longer siloed by provider or region.  HIEs can aggregate and report to public health agencies both locally and nationally.

HIEs can also consume data from public health — a good example is immunization registries.  Image the impact on an Urgent Care provider if they could query the state immunization registry on a 6 year old patient who walks in for care after business hours.  Instead of guessing what immunizations the child has had, the provider could query and obtain the necessary immunization information quickly and easily (and electronically, through the HIE).

Public Health and HIEs working together are important to all of us.  With technologies like NHIN and its ability to link HIEs together, public health data can flow more freely to foster better public health.

MEDNET Demonstrates NHIN MITA Specification to Dr. David Blumenthal at HiMSS

Friday, March 5th, 2010

MEDNET Chief Architect Seonho Kim and MEDNET CEO John Fraser personally demonstrated the new NHIN Medicaid MITA Specification to Dr. David Blumenthal, National Coordinator of Health Information Technology (ONC) at the HiMSS Annual Conference in Atlanta.
Seonho Kim has been leading the MITA workgroup on the NHIN Specification Factory to design the new Medicaid NHIN MITA eligibility transaction.

Visit MEDNET at HiMSS – MITA Medicaid NHIN Demo and Session 246 – NHIN

Thursday, February 25th, 2010

If you are attending the upcoming HiMSS Conference in Atlanta make sure you stop by and see:

MEDNET Chief Architect Seonho Kim will be demonstrating the MITA Medicaid NHIN Specification in the ONC booth at the Interoperability Showcase. This demo shows the future of instant Medicaid eligibility for HIEs, over the NHIN.

MEDNET CEO John Fraser speaking in Breakout Session 246 on Thursday on NHIN and Federated Identity Management.

As always, plenty of MEDNET staff will be at the show and around, make sure to contact us if you would like to connect and discuss HIE, NHIN, and the future of healthcare!

HIE, Federal Connectivity and NHIN

Tuesday, February 16th, 2010

- By John Fraser

The Social Security Administration (SSA) just funded 15 NHIN projects to dramatically speed up delivery of SSA benefits to injured workers.  This is an exciting new project for the Nationwide Health Information Network and the 15 contracted entities.  MEDNET is proud to be one of the project participants.

How will this SSA project work and what is the impact?  Providers will use a local health information exchange to connect through the NHIN to the SSA.  SSA spends over $500 million a year to enroll injured workers into SSA disability programs, a paper-intensive process that can delay an injured workers benefits for months.  Using the NHIN standards for electronic data exchange, SSA expects to reduce the injured workers wait for benefits from months to weeks, and potentially days.  This means a disabled person unable to work can receive financial support quickly.  In Minnesota there are over 100,000 injured workers relying on SSA disability benefits to help feed their families.

Compatibility with other health information exchanges is another benefit of adopting NHIN.  SSA is one of the first agencieCompatibility with other health information exchanges is another benefit of adopting NHIN. SSA is one of the first agencies to fund a number of NHIN connections, and other federal agencies including CDC, the VA and DoD are also implementing NHIN projects. This means NHIN connectivity can now be seen as a key connectivity standard for federal business, now and in the future. From SSA disability, to public health reporting, to eligibility determinations for Medicaid, many federal agencies have decided to transition their business processes to NHIN.

As health information exchanges (HIE) are built, and HIEs utilize the NHIN standards, they will reduce the risk of becoming obsolete or isolated, and increase the opportunities for federal connectivity and interoperability. NHIN helps to “future-proof” health information exchanges that adopt the underlying technologies of the NHIN.

Be sure to hear John Fraser speak at Session 246 on Thursday, March 4th on Identity Management in a Federated NHIN at the HIMSS Annual Conference in Atlanta, Georgia.

MEDNET TO DEMONSTRATE NHIN & HIE TECHNOLOGIES AT HIMSS CONFERENCE

Thursday, February 11th, 2010

MEDNETWorld.com (MEDNET) will be featured at the March 1-4, 2010 Healthcare Information and Management Systems Society (HIMSS) annual conference in Atlanta, Ga. with a special demonstration at the “Interoperability Booth” by MEDNET Chief Architect Seonho Kim. On March 4, MEDNET CEO John Fraser will give a presentation on Identity Management in a Federated Nationwide Health Information Network (NHIN).

The demonstration will show how administrative data is exchanged across the NHIN between a state Medicaid organization, an HIE and a healthcare provider. Enabling Medicaid Eligibility Verification through the NHIN will allow providers, health care organizations and health information technology vendors to more quickly and cost-efficiently support administrative transactions between the health care provider and payer communities.

Kim was appointed to lead the NHIN Medicaid Eligibility Project team to develop new NHIN specifications for the Centers for Medicare and Medicaid Services (CMS) as part of the Medicaid Information Technology Architecture (MITA) initiative. Kim has extensive experience designing distributed systems for academia and industry and sits on several national healthcare committees and NHIN workgroup and committees. Fraser was also appointed a member of the project team and will contribute his industry knowledge and expertise.

The Impact of Medicaid and Administrative Transactions on NHIN

Monday, January 18th, 2010

By John Fraser, MEDNET

The federal government is continuing to develop NHIN, the Nationwide Health Information Network. NHIN has been focused on sharing clinical information between hospitals, clinics and federal agencies. Recently, however, the design of two new standards for NHIN, related to Medicaid insurance eligibility and Medicare quality reporting, has been of focus.

Medicaid is a government program for low income Americans, partially funded by the federal government, and administered and run by each state / territory (there are 54 current Medicaid systems today). Each of these 54 Medicaid programs run eligibility systems to help providers check Medicaid insurance eligibility, ensuring providers properly bill and provide appropriate services for patients. Providers check Medicaid eligibility frequently, since many Medicaid enrollees enter and leave the Medicaid program monthly. Given this turnover, and the number of different Medicaid systems, it has been challenging for providers to directly check Medicaid eligibility within their states and in bordering states.

In 2005, the Center for Medicaid and State Operations (CMSO) within the Department of Health and Human Services (DHHS) developed the MITA program to directly address this issue. The MITA program is a collaboration of all the state Medicaid systems and CMSO to “establish national guidelines for technologies and processes that can enable improved program administration for Medicaid enterprises.”

One MITA-sponsored project is to develop and prototype a national NHIN service that would allow providers to quickly check a patient’s Medicaid status using a single system. This single system service would allow Medicaid providers a secure way to check any one of the 54 Medicaid systems with the click of a mouse (using the Internet). All a provider would need is an Internet connection, proper security credentials and connectivity to a health information exchange that has NHIN connectivity. Once installed, providers could see such benefits as improved patient care, improved cash flow, and an overall improved process from the Medicaid single system service.

Seonho Kim, Chief Architect at MEDNET, is leading the NHIN planning group to develop and test this new Medicaid single system service. MEDNET and Seonho will be demonstrating the Medicaid MITA NHIN service with the Department of Health and Human Services in the upcoming HIMSS conference in Atlanta in March. Please feel free to stop by at the Interoperability Demonstration area to see how this new Medicaid system works, and impact this system would have on healthcare.