InterSystems HealthShare is a healthcare informatics platform for hospitals, integrated delivery networks (IDNs) and regional and national health information exchanges (HIE). HealthShare includes health information exchange, data aggregation, workflow, text analysis, and analytics technology.
Overview
Integrated Delivery networks (IDNs) face complex challenges in getting the right data into the right hands, at the right time, with the goal of more informed decision-making and improved clinical and financial performance.
In many cases today, even with the use of traditional business intelligence tools and an enterprise data warehouse, important data often remains hard to access and difficult to aggregate and present to healthcare providers in a useful, unified format.
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.
The CIO Perspective
Executive Summary
Addressing the challenge of reducing hospital readmissions using manual processes is not a viable long-term solution. With other IT mandates demanding time and attention, your readmissions initiatives may suffer. However, with the right health information technology (HIT) platform, you can sustain efforts to reduce readmission rates and make processes more efficient and effective. Enabling interoperability and access to real-time data is key.
Strategic Interoperability
Executive Overview
This white paper discusses the critical requirements for the U.S. Departments of Defense (DoD) and Veterans Affairs (VA) to share Service members’ medical records – including real-time access to a complete composite health record – and it proposes an immediate solution via implementation of a health informatics platform. This approach will provide significant and clearly visible results in a matter of months, while positioning the Departments for strategic improvements in the years ahead.
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
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.
Strategic interoperability —The key to connected care
Introduction
The aging population and increasing incidence of chronic diseases are putting unmanageable pressures on healthcare services, not just in Europe, but worldwide. The current models of healthcare are unsustainable in the face of increased demand for services and rising costs. This was evident even before the financial crisis led to severe cuts in healthcare budgets in many countries.
I've worked with our Healthshare instance for almost 2 years now and I still can't answer so many basic questions like "How many searches were performed today".
Two of the reasons (and there are many) are simply the size and complexity of the ATNA table.
To avoid this issue, I'm considering a custom Ensemble/Cache class that would log each ATNA event type to a separate and simpler reporting table.
I wanted to see if anyone had any experience or advice on this front.
Okay, maybe not like I'm 5, but can anyone explain it like I'm a Javascript/SQL developer?
From one of our contracted developers:
I'm getting the error above while trying to use the NIST validation tool on a CCD created by Healthshare.
Here is the full <patient> element:
<patient>
<name use="L">
<family>TESTPATIENT</family>
<given>ZZKIDJULY</given>
</name>
<administrativeGenderCode code="F" codeSystem="2.16.840.1.113883.5.Our requirement is to fetch the SDA to get the some clinical data from aggregated SDA. Will this soap service work for our requirement. "HS.Gateway.Access.WebServicesClient"?
Please review the code and let me know. Also while I am running testing the code in sand box getting this error "<ZSOAP>zInvokeClient+203^%SOAP.WebClient.1"
Set tSearchRequest = ##class(HS.Message.SearchAndFetchRequest).%New()
Set tGatewaySearch = ##class(HS.Gateway.Access.WebServicesClient).%New()
#DIM tResponse AS HS.Message.SearchAndFetchResponse
Set tSearchRequest.MPIID = tMPIID
#DIM tSDA As HS.SDA3.
I have been experimenting with the concept of transforming HL7 input into a CDA document and am running into a little problem. Let me describe my setup
First I have a HealthShare production with three simple components.
1. I have a Enslib.HL7.FileService which looks in a specified directory for files containing HL7 messages to process. That service picks up the message and passes it to a custom business operation which is setup to transform it to CDA.
2. I have a custom business operation that I wrote that accepts the a Enslib.HL7.
For message bank implementation, in Ensemble->Enterprise Portal->Message Bank Viewer the Search based on basic or extended criteria is not working, for instance if i have to find a message with some known session Id, & i add this in my extended criteria, the search shows no results , whereas that message exists in the portal.
Please suggest why is it not working.
Thanks
Hello,
We have exposed a REST service for external vendors to call and post the data. The content type is
application/x-www-form-urlencoded. Service reads the data from Form variable (strData).
This service works as long as data in the Form variable is less than 32KB anything more than that
size CSP gateway is sending the truncated request to superserver.
Is there any configuration that I am missing? or is there any size restriction on
Form variable or there is an issue.