bhie bhie bhie (bidirectional health information exchange) is a series of communications protocols developed by the us department of veterans affairs (va). it is used to exchange healthcare information between va healthcare facilities nationwide and between va facilities and department of defense healthcare facilities. bhie is one of the most widely used healthcare data exchange systems in routine healthcare use, and is used to facilitate healthcare data exchange associated with a patient's medical record. types of data managed outpatient pharmacy data, allergy data, patient identification correlation, laboratory result data (including surgical pathology reports, cytology and microbiology data, chemistry and hematology data), lab orders data, radiology reports, problem lists, encounters, procedures, and clinical notes are examples of the types of healthcare data that are exchanged using bhie. integration with electronic health record systems bhie is currently integrated into the vista emr (electronic medical record) system used nationwide in va hospitals. va hospitals have regional specialized capabilities, and veterans often travel to receive specialized care. their vista medical records are able to be transmitted in their entirety using this protocol. history in response to 1998 presidential review directive 5, the department of defense (dod), the va, and the us indian health service (ihs) collaborated to create the first developmental instances of a secure data-sharing system for electronic patient record data. this was initially called the government computer-based patient record system, or gcpr. the development of gcpr used uml modeling tools to define the various expected use cases where medical care providers in any medical treatment facility (mtf) would need to have access to patient records or other data from within another participating agency. the uml modeling design was selected for its ability to clearly define the business logic that would be required for the gcpr framework and for its ability to provide detailed tracking of the iterative development of the framework software. the uml model for the framework is still used for the ongoing maintenance and support of the bhie system. early development of the gcpr system proved that it could meet the requirements of a robust interagency data sharing system, but details of implementation, policy, and security management issues caused delays in full implementation of the gcpr system as it was originally designed. as the project progressed, the ihs withdrew from gcpr participation, and agreements between the dod and the va led to the gcpr near-term solution (gcpr-nts) being managed principally by the va, with support from the dod. the va installed the preliminary systems for gcpr-nts in the va silver spring, md oifo, where extensive testing took place between the dod ei/ds and the va cprs developers. these teams worked together to finalize the needed infrastructure and security systems for one-way data transport of dod separatee data to the va. the gcpr-nts was structurally designed to house a static repository of this dod separatee data for use by va care providers. this one-way transfer of data from dod to the va repository continues to be one of the principal functions of the bhie system. upon completion of initial testing, the va deployed another gcpr-nts system into the austin automation center, in austin texas. this system became the "production" environment, which came to be known as the gcpr-mid-term solution (gcpr-mts). as the use of the system grew within the va, it was later renamed to become the federal healthcare information exchange, or fhie. the previously constructed system in the silver spring oifo was re-tasked to become an iterative testing environment for proofing planned changes prior to deployment in the fhie production system in austin. in 2004, interest in the system for use within the dod was renewed, and further development was done to add a true bi-directional connection component to the fhie system. initially called the data sharing initiative (dsi), adapters were added to the fhie system using the web services xml-based protocol standard. a similar web services adapter was developed for the dod to connect to their chcs-i legacy patient record systems. in this way, both systems hosted a peer web services client that is accessible to the other with proper authentication, allowing bi-directional, query-based data exchanges between the disparate systems. direct cross-domain write capability and fully computable data storage and transfers are not supported at this time. with the addition of the dsi components to the fhie system, the entire project was renamed the federal bi-directional healthcare information exchange, or bhie. all references to fhie (other than historical) are generally being phased out. bhie represents the previous framework system as was deployed for the va, and all additional capabilities added to support near-real-time data exchange between the framework and participating dod medical treatment facilities (mtfs). in short: fhie + dsi = bhie. the current bhie project participants are exclusively the dod and the va, though any number of additional domains will probably be added over time with proper development of adapters and policies. this project has the support of the va under-secretary for health, and the acting assistant secretary of defense/health affairs of dod. there is also congressional interest in a successful outcome to this work. since 2q-fy05, the dod is supporting the development of a separate dod bhie domain, including dedicated hardware and infrastructure to support this new system within the disa network. the details of the dod system are still in development, as are the details of the expected interoperability with the existing va bhie system. additional data types were added to the system during the 2005-2006 operational periods, including the provision of discharge summaries from selected dod mtfs, and the inclusion of pre-post deployment form data availability. in march 2006, the usage of bhie across the country was outlined before the house committee on veterans affairs. in 2007 the dod's ahlta interface was connected to bhie to allow ahlta clinicians to see va data and va clinicians to see dod data stored within the cdr. additionally in 2007 the theater medical data store (tmds) was connected to bhie to allow va and dod clinicians to access medical records from combat theaters. in the 2007–2009 years, a parallel “two-pass” system for exchanging imaging metadata was added to the scope of bhie. a special-purpose server, the bhie imaging adapter (bia) was added to the other bhie systems. this bia server takes the first pass of an image study query, obtains metadata about the images for a specific patient from the bhie system, then presents a list of available images to the end-user, who can then select the images of interest from the list. the bia then has variable functions as an intelligent proxy for retrieving and delivering the selected images. as of 2011, other additional functions related to images are being added to both the bia and bhie systems. from 2008 through 2011, the central focus of bhie was to upgrade the system hardware and migrate all of the production functions onto the new hardware. the upgrades began in the spring of 2009, when the initial sets of hardware were delivered and development began to create a set of identical-hardware environments on which the bhie systems' migration could occur. the migration to the new production bhie location in philadelphia, pennsylvania, was accomplished in january 2011, and enhancements to all of the systems continue as an ongoing process. the austin "legacy" bhie system remained in production operation until 2011, when the replacement bhie hardware installed in philadelphia, pennsylvania, assumed all of those functions. the austin systems went dark and were retired from service in april 2011.