HealthData Storage - NetDirector Healthcare

Healthdata Storage.

NetDirector’s HealthData Storage (HDS) service allows the already powerful hub-style integration available via NetDirector to achieve new, unprecedented functionality within an integration. At its core, HDS allows data to be stored temporarily during transfer, accumulating and becoming available for calls/references from other endpoints as authorized by the customer.

This data is not only highly secure, but easily accessible, transformable, and can be referenced mid-process via integration by any platforms involved in the process (patient records, billing, labs, radiology, and any others in the customer’s data ecosystem).

HDS also allows integration ecosystem members to take advantage of unique HDS properties to solve long-standing issues in their own platforms and the other systems used by their integration trading partners, without lengthy and expensive custom development or full-on system replacement on the part of the provider.

Take a look at a few of our real-world HealthDat Storage use cases below!

What makes NetDirector Different?

Find out here!

Healthdata Storage Use Cases.

Overcoming the Limitations of Client Integration for Sending Data

Data Efficiency and Filtering Using Health Data Storage

Overcoming the Limitations of Trading Partner Systems

Workflow Efficiency with Advanced Filtering

Entirely New Functionality Via Health Data Storage

Click the images to go to the Use Cases

Problem:

One NetDirector client has a defined API that sends patient and charge messages to NetDirector for delivery to their trading partners. The APIs were designed so that Patient Information (including insurance) is coupled with the ADT message, which works in tandem with the charge information in the DFT. While working to implement a new data trading partner’s system, it was identified that they were unable to receive the Patient information messages (ADT) and wanted to receive only the DFT messages, but needed to gather the patient demographic information from the DFT message itself. This created a significant workflow hurdle: the charge message (DFT) from the client did not have any of the Insurance information in the message sent via the existing API. The level of effort to expand the scope of the Charge messages would have meant excessive development and redesign, and without this functionality our client would not be able to meet their trading partner’s needs.

Overcoming the Limitations of Client Integration for Sending Data.

NEXT: SEE THE SOLUTION

The

TABLE OF CONTENTS

Solution:

Using HDS, NetDirector receives the patient information (ADT) messages and extracts the critical insurance information. This insurance information is then stored in the HDS system, linked via patient ID, and updated with each ADT that is received for that patient to ensure the most recent Insurance Information is available. When a charge message is passed through NetDirector, a query is made to HDS to pull any insurance information for that patient, and NetDirector adds it to the charge message. This results in the needs of the trading partner being met, and neither the client nor their trading partner were forced to make changes to their API (or their desired workflow).

Overcoming the Limitations of Client Integration for Sending Data.

SEE THE NEXT USE CASE

The

GO BACK: SEE THE PROBLEM

TABLE OF CONTENTS

Problem:

A NetDirector client had a data trading partner who wanted to limit the charge messages that were received through NetDirector to a subset of the active users in the client’s platform. Since the activity in the client’s platform needed to continue for all users, the client didn’t have a way to easily block the sending of messages to NetDirector. The need was identified most easily as a message filter based on the provider value in the messages.

Data Efficiency and Filtering Using HDS.

NEXT: SEE THE SOLUTION

The

GO BACK: SEE THE PREVIOUS USE CASE

TABLE OF CONTENTS

Solution:

NetDirector built a storage system for “blocked providers” that stores the provider ID of providers that should be filtered. Once the processing was configured, the NetDirector engine references the list of excluded provider IDs before passing messages along to the trading partner, ensuring they receive only the data they require. An interface was also provided to allow the client to query and update the list of providers excluded whenever necessary, allowing “self-service” of this filtering process.

Data Efficiency and Filtering Using HDS.

SEE THE NEXT USE CASE

The

GO BACK: SEE THE PROBLEM

TABLE OF CONTENTS

Problem:

As part of the workflow that a NetDirector client has, they need prior reports associated with the current radiology study that they will be reading. Most trading partner systems can send prior reports as part of either their internal workflow or via stored images using DICOM messaging. One of the client’s data trading partners, however, did not have the ability to send prior reports through either of these methods. They were only able to export an archive file of all prior reports, so the client needed a way to query and send as needed from the archive. The client’s was not equipped to store and retrieve the data, however they could consume the data if sent with new Radiology orders.

Overcoming the Limitations Of Trading Partner Systems.

NEXT: SEE THE SOLUTION

The

GO BACK: SEE THE PREVIOUS USE CASE

TABLE OF CONTENTS

Solution:

NetDirector configured a storage solution that stores prior reports as entries which can be retrieved by the patient MRN. When a new order is sent from the trading partner, the NetDirector system queries the storage and sends the associated prior reports to the existing client endpoint. The solution currently stores prior reports from as far back as three years. Newly sent reports are automatically added to the archive for future retrieval.

Overcoming the Limitations Of Trading Partner Systems.

SEE THE NEXT USE CASE

The

GO BACK: SEE THE PREVIOUS USE CASE

TABLE OF CONTENTS

Problem:

Due to a specific data trading partner workflow, one client found there were a large number of duplicate prior reports being sent from a storage archive. This resulted in the client receiving too many messages, taxing the client’s system, creating bottlenecks, and preventing the client system from functioning efficiently. A temporary solution was put in place that allowed the client to trigger a query of prior reports only for studies that were active. Unfortunately, this still allowed for duplicate calls, and as a result duplicate reports being sent, overwhelming the client’s system. The client concluded that they needed a way to limit the query to only occurring once every three days – functionality that was not possible in the existing system.

Workflow efficiency with advanced filtering.

NEXT: SEE THE SOLUTION

The

GO BACK: SEE THE PREVIOUS USE CASE

TABLE OF CONTENTS

Solution:

NetDirector implemented a storage solution that tracks the date of the last pull for a particular MRN. As a request is received for an MRN to pull prior reports, the storage is queried to get the last date, and if the date is within the last 3 days the request is filtered. If the date is beyond that date or that MRN hasn’t been queried, the query is sent, and the storage solution is updated. This decreased the duplication significantly, and allowed the client’s system to function as expected while still maintaining their trading partner’s desired workflow.

Workflow efficiency with advanced filtering.

SEE THE NEXT USE CASE

The

GO BACK: SEE THE PROBLEM

TABLE OF CONTENTS

pROBLEM:

A NetDirector client’s system has the ability to manage group appointments (appointments with multiple members) however they do not have an integration process to receive inbound group appointment requests. One of their data trading partners requested to allow messages through NetDirector to create and manage group appointments within the client’s system.

Entirely New Functionality via HealthData Storage.

NEXT: SEE THE SOLUTION

The

GO BACK: SEE THE PREVIOUS USE CASE

TABLE OF CONTENTS

solution:

The group appointment management required a specific and elegant solution - because the information may be received either as a single message (all members in one message) or multiple messages (each member has a message but share an appointment ID), a method for storing member IDs and sending complete group members was needed. Group appointment functionality would require the storing of this information to reference as messages were processed. NetDirector worked closely alongside the client to utilize existing endpoints to manually create the group and appointment from compiled data stored and organized in a Health Data Storage instance via integration with NetDirector. Without the ability to store the information in NetDirector’s HDS, the inbound group appointment management would have required redevelopment and considerable delays for the client – all avoided with the aid of NetDirector as an intermediary.

Entirely New Functionality via HealthData Storage.

SEE THE NEXT USE CASE

The

GO BACK: SEE THE PROBLEM

TABLE OF CONTENTS

Expand the function of your existing system via integration, not development
Rapidly deployable, scalable solution for temporary parking and retrieval via your NetDirector integration
No custom development – configuration-based tools mean reduced costs and time-to-launch
Solve “impossible” problems – more than integration, the NetDirector hub becomes a tool to manipulate, store, sort, and push/pull healthcare data
Highest security standards – HDS, like the rest of the NetDirector infrastructure, is HIPAA and SOC 2 Type II compliant throughout the entire data lifecycle

Let's review your current interoperability plans.

Schedule an Integration Review

Learn about how NetDirector saves money and reduces labor for healthcare technology vendors by integrating and automating without hundreds of hours of development and API management.

Common Integration Requests

Testimonials

Our Additional Services

Details

Email us

Contact Us

Leave a Review on G2

Common Integration Requests

Testimonials

Our Additional Services

Details

Email us

Contact Us

Leave a Review on G2

Healthdata Storage.

Healthdata Storage Takes You Beyond Just Integration.

What makes NetDirector Different?

HealthData Storage Features

Let's review your current interoperability plans.

Real Interoperability, Real Results