HealthShare

We are receiving XML documents and storing them. When we click to go into the clinician portal and again to view a patient, we can see the documents but none of the data is mapped to their respective buckets, i.e. allergies or medications.

I am thinking that I need to build an XSLT parser and change the format to SDA3, is this an appropriate approach? Or would using the Data Transformation (Ensemble -> Build -> Data Transformation) be a better idea? Lastly, if the XSLT idea is preferred, where would I call it within the stack?

During the Unconfernce and Sessions during the Global Summit several folks had questions and wanted to see how Ohio State setup our Managed Alerts.  Attached is an export I did along with Documentation I had given to our group here at OSU for Managed Alerts.

Learn how to start troubleshooting productions.

Presenter: Alex MacLeod
Task: Understand and use IHE in HealthShare
Approach: Provide a real-world example of a successful IHE implementation
 

In this session, we will discuss the basics of IHE in HealthShare, as well as share a real world example of a successful IHE implementation.

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.

Presenters: Pete Greskoff, Sebastian Musielak
Task: Ensure high availability of your HealthShare deployments
Approach: Discuss high-availability options and focus on HealthShare’s new support for database mirroring
 

With the new release of HealthShare, Mirroring is now support for high availability. This session will describe high availability options and focus on mirroring your HealthShare deployments.

Content related to this session, including slides, video and additional learning content can be found here.

Presenter: Randy Pallotta
Task: Automatically create cohorts of high-risk patients. Send them critical action alerts
Approach: Use the new HealthShare features: “Smart Programs” and “Advanced Clinical Notifications”
 

In this session, we will cover HealthShare "Smart Programs" and "Advanced Clinical Notifications" which allow you to automatically create cohorts of high risk patients in Health Insight and Information Exchange and to send critical actionable alerts. After this session, you should understand this new feature and how to configure a new program or alert.

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: Russell Leftwich
Task: Understand the concepts of the Fast Healthcare Interoperability Resources (FHIR) standard
Approach: Discuss what FHIR is, and what it’s for
 

This session will introduce the concepts of FHIR - Fast Healthcare Interoperability Resources.

Content related to this session, including slides, video and additional learning content can be found here.

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.