Learn HIE Concepts

Administration Tools

Below is a selection of tools used to administer your HIE.

GHIN Admin Tool

The HIE Operator Health’s state-wide network will eventually encompass hundreds of provider entities with each having Edge servers. In addition, the HIE Operator will grow to encompass additional services (Rx history, quality reporting, medical home, etc.). Managing a complex network requires a strong foundation of node management. This is where the “Global Health Information Network Directory Manager” fits in. This system allows the HIE Operator to build a hierarchical standard LDAP based directory. Since this is standards-based, any Edge server can connect to it securely. Global secure message end points (i.e. physician addresses) are also managed here by the HIE Operator or can be delegated to Microsoft.

Here are some of the functions managed by this service:

  1. Unlimited number of Edge Servers and their configurations (e.g. IP addresses)
  2. Organize the state-wide exchange into smaller, manageable administrative exchanges (e.g. you can have a "network of networks" model)
  3. Central point to control, configure and manage end-point connections to external services (e.g. RxHub, other NHIN Gateways, HealthVault services etc.)
  4. Manage IHE configuration details so errors are minimized
  5. Manage administrative contacts for each Edge Server so appropriate people can be contacted in the event support at local provider end is required.

The user friendly tool is built on .NET Winforms technology using the latest innovations in user interface such as “Office 2007” controls.

Edge Server Provisioning

The HIE Operator Health’s network will typically start small and grow rapidly as new nodes and services are rolled out. Each Edge Server required needs to be provisioned rapidly and with near zero errors. This is accomplished by using our powerful node provisioning tools. An entire network can be provisioned from scratch in about 4 hours. A node can be provisioned in less than 30 minutes. With rapid provisioning capability, the HIE Operator can reduce its IT costs and support needs.

HIE Client (Smart client)

The HealthUnity HIE Client (Smart Client) is typically deployed for advanced users who configure the system or require local device integration (e.g. front desk staff that need to scan consent documents into the Edge Server). This tool is also used for configuring certain system functions. This client is in its 5th generation and customer proven.

HIE Client (Web client)

For the vast majority of users, we will provision them to use the Web based HIE client.

Administrative Portal

This administrative portal provides an intuitive interface for certain use cases (e.g. patient’s request to connect to their clinical record and then access their data via HealthVault). This request will be seen in the administrative portal. We also support alternate workflows for patient connectivity.

Network Management Tool

We provide an industrial strength monitoring and management tool called the HealthUnity Manager. Salient features of this tool include:

  1. Dashboard view of “red, yellow, green” status for critical services running throughout the network. If a service is down, the central administrator can immediately take action.
  2. Ability to monitor internal workings of the HIE system (e.g. if a workflow failed because some validation didn’t go through, then, that particular workflow can be traced all the way through the chain of processing steps and that workflow can be restarted using the HU Management tool).

Several system level configurations can also be accessed through this tool.

Adapter Services

We provide the full suite of management tools provided by Microsoft BizTalk Server (BTS) which is an embedded component of our solution. BTS is used by tens of thousands of organizations as their preferred interface/integration engine. BTS has such tools as schema editor, mapper, administrative console, etc. BTS comes built in with support for HL7, HIPAA EDI and various XML formats.

Outbound and inbound interfacing with EHRs is accomplished through our automated interface provisioning tool. This tool provides a single grid on which all interfaces can be listed and managed. When our HIE product is installed, we pre-create HL7 interfaces in the adapter server. All the installation engineer has to do is to direct the feeds to the ports created during installation.

Administrative Functions Supported

Our HIE solution has an extensive array of integrated tools to achieve the administrative needs of our HIE customers. Given our more than 5 years of experience in the HIE industry, we have built a highly integrated and robust set of tools that help with the following functions:

  1. Installation
    1. HIE core network services
    2. Edge servers
    3. HIE use case services
      1. E.g. Clinical summary service
      2. Secure messaging
      3. And over 15 other use cases
  2. Administration
    1. Provisioning and deprovisioning
      1. Nodes
      2. Services
      3. Users
      4. Adapters
  3. Operations
    1. HIE Network
    2. HIE Infrastructure
      1. SQL Server database management system
      2. BizTalk Server interface engine
      3. HealthUnity HIE Services

Since the array of tools is extensive, we will present a sampling of facilities to illustrate our experience:

Illustrative Requirement (note these are a sample; not the full set) How our HIE solution meets the requirement?
Add a new Edge Server
  1. Use our provisioning wizard tool to set up a new virtual edge server
  2. Add new administrative users to the edge server
  3. Log in to the edge server using the HealthUnity .NET client
Look up audit log entries
  1. Run audit log reports
  2. Or run the export job to export audit log file to flat file for further analysis
Adding a new outpatient lab service provider
  1. Ship to lab service provider a VPN device that will enable secure communication between lab and the HIE Operator HIE network
  2. Configure a virtual lab edge server on the the HIE Operator HIE network
  3. Once network is connected, Lab starts sending ORU (HL7) messages to the MLLP port to the virtual lab edge server
  4. Log into the admin portal to map lab result to appropriate end point within the HIE. This is the only administrative function needed.
  5. Lab results automatically flow to the appropriate application.