#HealthShare

Presenter: Boris Mamkin
Task: Understand and use CDA in HealthShare
Approach: Provide a real-world example of how the Clinical Document Architecture standard is being used in a clinical integration

In this session, we will discuss the basics of using CDA in HealthShare, as well as a real world example of how CDA is being used in a clinical integration.

Content related to this session, including slides, video and additional learning content can be found here. Please note that this content is available only to HealthShare customers and attendees of the Global Summit. On the learning web site you will be prompted for your Global Summit credentials to access this content.

Presenter: Matt Spielman
Task: Use the FHIR standard with HealthShare-based solutions
Approach: Provide an overview of how HealthShare will support the evolving FHIR

The next major release of HealthShare will be the first version to support the emerging HL7 FHIR standard. This presentation will discuss InterSystems’ involvement with the FHIR standard, detail the new FHIR functionality, and review our long term plans for FHIR in the HealthShare platform.

Content related to this session, including slides, video and additional learning content can be found here. Please note that this content is available only to HealthShare customers and attendees of the Global Summit. On the learning web site you will be prompted for your Global Summit credentials to access this content.

Presenter: Tom Spencer
Task: Add extra data to HealthShare’s data model and make it available to all HealthShare components
Approach: Use new extensions within HealthShare to add custom data

When deploying a HealthShare solution, you may need to add extra data to our SDA data model. In this session, we will present the new extension mechanism for adding data to HealthShare and to ensuring that data is available in Health Insight and Patient Index.

Content related to this session, including slides, video and additional learning content can be found here. Please note that this content is available only to HealthShare customers and attendees of the Global Summit. On the learning web site you will be prompted for your Global Summit credentials to access this content.

Presenter: Alex MacLeod
Task: Use Personal Community to build fully responsive and mobile-compatible portals
Approach: Demonstrate the new release of Personal Community. Provide a behind-the-scenes look at the new application development framework used to build it.

The new release of Personal Community v11 is now fully responsive and mobile compatible. It uses a new framework for development. In this session, we will give a functional overview of Personal Community, demo the new release and give a look behind the scenes into the application development framework used.

Content related to this session, including slides, video and additional learning content can be found here. Please note that this content is available only to HealthShare customers and attendees of the Global Summit. On the learning web site you will be prompted for your Global Summit credentials to access this content.

This will be a stretch to be useful, but it was sorta fun. If you just so happen to have a use case to make your HealthShare productions talk to a Slack channel, this is the Business Operation for you.

In Slack, it is a dead simple process to enable an incoming web hook:

• Name It
• Give it an Icon or Emoji
• Declare a Channel to Interact With

One you supplies those, it spits out a URL that you can go to town posting to your channel using that endpoint.

We have a situation where we want to detect and ignore documents/records at the earliest possible point based on certain criteria. We have an existing "CDA Preprocessor" in the workflow which is an XSL transform. This is what our contractors are planning to utilize to "filter" these documents. This doesn't really make sense to me. I see XSLT as a way to manipulate the contents of a document and filter certain peices of data. In my brain, I would use an Ensemble business rule to detect the criteria and route the document as necessary.

Are you going to be building an integration with Ensemble or HealthShare? Take the following course to learn about the core architecture in building an integration, the parts and pieces involved and the most common ways that data flows through that architecture.

Executive Summary

An accountable care organization (ACO) is a group of providers that are collectively responsible for the total cost and quality of care provided to a specific population of patients. Together, the group assumes risk and shares rewards. As with high-performing organizations in other industries, the hallmarks of ACOs are quality measurement and continuous improvement.

Changes in reimbursement approaches in healthcare are unleashing unprecedented business forces in the industry. As a result, providers are consolidating into larger integrated delivery networks, hoping to achieve economies of scale and operating efficiency.

Comprehensive patient view, communication and data sharing, and population health management are key components

Federal agencies have been incenting healthcare providers to leverage their electronic health records (EHRs) to get patients involved in the management of their care. Most organizations, however, haven’t moved beyond patient engagement as an item to be checked off in order to receive meaningful use incentive funding.

Information Sharing Enables Health Plans to Leverage Data and Analytical Assets to Deliver Sustained Value

Executive Summary

The shared-risk payment models that are central to health reform all require tight coordination among payers, providers, and patients if they are to succeed. As payers and providers enter into more and more such agreements, they need to enhance success by communicating and collaborating more effectively with their partners and actively engaging, supporting, and empowering their members.

Introduction

In healthcare, information accessibility can impact the outcome of a medical decision, or the success of a bundled payment initiative. To ensure that the right information is available at the right place and time, healthcare organizations typically have used HL7® interface engines to share data among clinical applications. But the demands on healthcare information technology are changing so rapidly that these simple engines are no longer sufficient.

Improved Access to Clinical Data Across Hospitals and Systems Helps Pharmaceutical Companies Reduce Delays and the Costs Associated With Bringing New Treatments to Market

Executive Summary

Introduction

As healthcare providers face increasing pressures to lower costs and reduce readmissions, they're rapidly shifting towards accountable?care organizations (ACOs) and other coordinated, quality-based reimbursement systems. However, most providers have historically?organized their data and workflows in ways that best fi t the fee-for-service payment model. Now that so many providers are sharing?risks and rewards, they must also share and coordinate information by adopting more streamlined health information technology?solutions.