Home
Administration
Set up and manageBluechip.
File Formats for Import and Export
File formats for importing and exporting data.
Patients.In
Standard format for importing information.

Administration
Set up and manageBluechip.
- Bluechip System Requirements
  This information applies to Bluechip 4.2.
- Bluechip Installation
  About installing Bluechip.
- Performing a Silent Installation of Bluechip
  A silent installation involves installing Bluechip onto multiple workstations simultaneously, and is typically initiated after-hours, unattended.
- Automatic Updates
  MedicalDirector periodically releases updates to content.
- Upgrading Bluechip
  Preparing to update your Bluechip installation.
- Backup and Restore
- Routine Tasks in Bluechip
  Routine tasks ensure your business's financial data is accurate.
- Settings
  Configure practice, fee, list, template, printer, security and user settings.
- BC Secure
  Use BC Secure to set advanced permissions for each user and practitioner.
- Practitioner Records
- Managing User and Tenant Records
- Managing Other Records
- Searches
- Enabling and Reconnecting your EFTPOS Device for Bluechip
  Configure EFTPOS devices for use with Bluechip.
- Moving Your Bluechip Data to a New Server
- HCN SQL Repair Scripts Using SQL Server Management Studio
  Run these scripts if recommended by MedicalDirector Customer Care.
- Utilities
- File Formats for Import and Export
  File formats for importing and exporting data.
  - ADDRESS.IN
    Format for importing specialists' information.
  - Patients.In
    Standard format for importing information.
    - Patients.In file
      Format of the Patients.In file.
  - Patients.Out
    Legacy format for exporting information.
  - Transfer.Out
    Standard export file used by Clinical.

Patients.In

Standard format for importing information.

The PATIENTS.IN file is used as an interface between MedicalDirector Clinical and a billing package to transfer patient demographic data into Clinical. The format (referred to as 'Generic ASCII v2') is most commonly used by third-party packages to implement a link to Clinical and is the official standard for passing data to Clinical using the link file method.

The sending application writes information to a file named PATIENTS.IN (which conforms to the 'Generic ASCII v2' specification) every time a new patient is added or a patient's details are edited. With the link activated, Clinical checks the PATIENTS.IN approximately every 60 seconds, and if it is not empty, reads in the contents and clears the file. It then processes this data and adds the information it finds to its database.

The PATIENTS.IN file does not need to reside in the same directory as Clinical. A setting in the Link Option enables a path to be set to the PATIENTS.IN file from anywhere on the computer.

Note:

Network paths and mapped network drives are not supported.

Clinical locks the file during reading, so if an attempt to write to the file is made while Clinical has it open, it will fail and might need to be retried. Generally, Clinical should only have the file open for less than one second so a loop to retry for several seconds should ensure that the file can be opened.