PHC Hub User Guide (v. March 2018)

Workaround for GE Centricity

Older versions of the GE Centricity EHR system (known as Logician) don't support the VXU message required by the CDC to connect to registries. However, they do support the ORU message which is normally used to report lab test results. This format is unusual, but can be used to transfer data.

Logician has a module called LinkLogic, which includes LabLink. While LabLink's main use is to receive test result data from labs, it can be used to export data. Vaccination data is stored in Logician using OBSTERM codes, which can be grouped together into Flowsheets. An export interface is associated with a Flowsheet and all associated OBSTERM codes can then be exported.

Since Logician stores immunizations differently, it makes the interface quite a bit different from other HL7 interfaces. For example, while most immunization applications use one code to represent a DTaP series, Logician uses nearly 50. Each code represents a different aspect of a particular dose in a series. The following is a small subset of OBS TERM codes for DTaP:

IWeb-Logician Code Map Spreadsheet

To integrate with IWeb, codes must be translated into CPT codes. Then, an XML document fragment must be added to the import profile (Import Profile > HL7 Observation Settings (ORU Only) section > Observation definition field). The IWeb-Logician Code Map spreadsheet helps create and edit the XML. This spreadsheet contains all the Logician codes and can automatically generate the XML. The spreadsheet was created for your convenience; it is not required for creating the XML. There may be other ways of managing the codes that work better for you.

1. Open the IWeb-Logician Code Map spreadsheet in Microsoft Excel.
2. Use the CODES tab to add information in the following columns. When working with a new interface, make sure that all the codes they plan to send to you are represented in the worksheet:
   

   Column	Description
   OBS TERM	The OBS TERM as assigned by Logician.
   TYPE	The type of data this code holds. Valid choices include: Date - Vaccination date. This field is required to add a vaccination in IWeb. MVX - Manufacturer code. BYID - Vaccinator ID. BYNAME - Vaccinator name. LOT - Manufacturer lot number. MVX - Manufacturer MVX code. ROUTE - Route of administration. SITE - Site of administration (on the body). HIST - Vaccination not administered here. VACCVFC - Vaccination VFC status. ATID - Facility where the vaccination was given. EXP - Expiration date, not used. VACCTYPE - Vaccination was publicly or privately supplied. ACTION - Vaccination was added, updated, or deleted.
   CPT	The code imported into IWeb. If no code is specified, then it's not added to the XML.
   DOSE	The dose number this code belongs to. Although not imported into IWeb, it's important to know which dose number a code refers to so it can be distinguished when multiple doses are sent together. This is required.
   OBS ID	Another internal representation of the OBS CODE. Both codes are sent in HL7 messages, but IWeb only reads the OBS ID. Logician users only see the OBS CODE.
   DESCRIPTION	A short description of the code.
   ADDITIONAL DESCRIPTION	A longer description of the same code.

3. When you are ready to extract the information, switch to the XML worksheet and copy the contents in Column A.
4. Paste the information in the import profile (Import Profiles > Select Import Profile > Edit > HL7 Observation Settings (ORU Only) section, then Observation definition field).

Exporting Logician Data

The Logician administrator configures the interface and specifies a flowsheet that lists all the codes to be exported. This flowsheet contains the immunization codes they use and corresponds to the XML you created.

Logician data is exported using the LabLink interface in LinkLogic. Data can be sent via TCP/IP (MLLP) or saved to a file. The HL7 Bridge can be configured to accept the data by TCP/IP or file.