Posts Tagged ‘EHR’

Semantically Aligned Design Principles At Core of Australian Electronic Health Records Platform

site-header-10th-blog-304x200At the upcoming Semantic Technology & Business Conference in San Jose, Dr. Terry Roach, principal of  CAPSICUM Business Architects, and Dr. Dean Allemang, principal consultant at Working Ontologist, will host a session on A Semantic Model for an Electronic Health Record (EHR). It will focus on Australia’s electronic-Health-As-A-Service  (eHaas) national platform for personal electronic health records, provided by the CAPSICUM semantic framework for strategically aligned business architectures.

Roach and Allemang participated in an email interview with The Semantic Web Blog to preview the topic:

The Semantic Web Blog: Can you put the work you are doing on the semantic EHR model in context: How does what Australia is doing with its semantic framework compare with how other countries are approaching EHRs and healthcare information exchange?

Roach and Allemang: The eHaaS project that we have been working on has been an initiative of Telstra, a large, traditional telecommunications provider in Australia. Its Telstra Health division, which is focused on health-related software investments, for the past two years has embarked on a set of strategic investments in the electronic health space. Since early 2013 it has acquired and/or established strategic partnerships with a number of local and international healthcare software providers ranging from hospital information systems [to] mobile health applications [to] remote patient monitoring systems to personal health records [to] integration platforms and health analytics suites.

At the core of these investments is a strategy to develop a platform that captures and maintains diverse health-related interactions in a consolidated lifetime health record for individuals. The eHaaS platform facilitates interoperability and integration of several health service components over a common secure authentication service, data model, infrastructure, and platform. Starting from a base of stand-alone, vertical applications that manage fragmented information across the health spectrum, the eHaaS platform will establish an integrated, continuously improving, shared healthcare data platform that will aggregate information from a number of vertical applications, as well as an external gateway for standards-based eHealth messages, to present a unified picture of an individual’s health care profile and history.

Read more

Health Language Selected by Holy Name Medical Center to Improve Problem and Diagnosis Search

Wolterskluwer_new

July 7, 2014 – Wolters Kluwer Health, a leading global provider of information for healthcare professionals and students, announced today that Holy Name Medical Center (HNMC) has selected Health Language® to improve problem and diagnosis searches within its electronic health record (EHR). HNMC will use the Health Language Workflow-Enhancing Search solution to support encoding its problem lists in SNOMED-CT® for Stage 2 Meaningful Use and the transition to ICD-10. Read more

A Closer Look At SemTechBiz Startup Competition Winner: KnowMED And Its Clinical Discovery Platform

KnowMED walked away the big winner of the Semantic Start-Up Competition. The Semantic Web Blog caught up with CTO Matthew Vagnoni, MS, and CEO Jerry D. Scott to further discuss the company’s winning entry, the Clinical Discovery Platform, for helping the health care sector semantically integrate data and ask natural language questions of that data, to support clinical research and complex decision-making.

The problem that the health care industry at large faces of not being able to easily and efficiently integrate and share data across organizations’ borders is equally a challenge right within the institutions themselves. “Large modern health care organizations are somewhat insular,” says Vagnoni.

At Medical City Children’s Hospital in Dallas, as an example, there are three separate electronic health record systems just for its neonatal division. The diverse formats and vocabularies made it difficult to try to ask questions of this data for research or efficiency purposes. But within two months of deploying KnowMED’s Clinical Discovery Platform, Vagnoni says, most of the data was integrated into a single view, “so clinicians could interact with it almost like using Google. …We combined the data from all the different sources so that clinicians could go in and ask questions [that reflect] how they think, not how [the information] is in the data schema.”

Read more

RDF’s Role In A Universal Healthcare Exchange Language

LOGO: Semantic Technology & Business Conference; June 2-5, 2013, San Francisco, CaliforniaWhat are the possibilities for RDF (Resource Description Framework) as a Universal Healthcare Exchange Language? It’s an issue to be explored next week at a SemTechBiz workshop in San Francisco.

The healthcare sector is rife with medical vocabularies and localized terminologies. In fact, says David Booth, Senior Software Architect, KnowMED, one of the leaders of the upcoming event, “some people have characterized the problem as not being one of a lack of vocabularies but of too many vocabularies.” To some extent that can’t be helped, because specific languages have grown up with various medical specialties and healthcare subdomains. What can be helped, though, is to create semantic connections among these vocabularies, to avoid the disconnects that can harm patients, researchers, and others.

Read more

Certify Data Systems Launches HealthLogix HIE Platform

Certify Data Systems has announced the availability of HealthLogix, a Health Information Exchange (HIE) platform. The platform “is the first HIE solution to deliver on the promise of an aggregated patient view from all healthcare encounters across the community no matter what native EMR/EHR system is in use. Without this capability, healthcare organizations and providers participating in a Medical Home or an Accountable Care initiative will continue to struggle with incomplete clinical data to care for their patients.” Read more

3M Opens Access to Healthcare Data Dictionary

3M has opened up the 3M Healthcare Data Dictionary under an agreement with the Department of Defense and the Department of Veterans Affairs. According to the article, “The 3M Healthcare Data Dictionary will provide the core technology to enable semantic interoperability for the joint DoD/VA integrated Electronic Health Record (iEHR), making it possible to share medical knowledge and secure patient data between care providers at U.S. military treatment facilities located around the world and VA Medical Centers. Access to actionable clinical information whenever and wherever care is delivered will enable safer, better coordinated, and higher quality care for the country’s 32 million veterans, active service members, and their families.” Read more

Intelligent Healthcare part 4 – Process Management & Modeling

In our last post on Intelligent Healthcare, we talked a bit about Electronic Healthcare Record systems. EHR/EMR technology is an important piece of the larger set of clinical systems as it represents a patient centric organizational framework. However; EHRs are only part of a larger picture. One area that is particularly promising for the application of Semantic technology to healthcare is process management. When we discuss process management in this context, we’re not talking about traditional process management software solutions. Healthcare process management is in a sense a formalization of (medical) practice approaches that for the most part aren’t automated and in many cases likely never can be fully automated.

Read more

Intelligent Healthcare – Part 1

Integration is more than the coding of application or data interfaces. When dealing with complex integration within or across enterprises, there must be sufficient discipline to achieve reproducible results. Furthermore, that discipline must be tailored to the unique requirements of the domain/s in question. Few domains are as complex as Healthcare. Even more important perhaps is that integration cannot be viewed outside of the context of the outcomes within the domains they are meant to serve. Technical success may not translate to process or performance improvement if the relationships between domain goals and enabling technologies aren’t properly understood. Some of the basic concepts associated with our IH include the following:

Read more