Healthcare organizations replacing or consolidating an EHR system often discover that migrating the database is only part of the project. Years of patient documentation may still exist in proprietary document formats that were created by older applications.
One example is the HighEdit HED format. HighEdit was used as a document editing and reporting technology in healthcare applications, including environments based on NextGen. Although HighEdit is no longer available as an actively developed product, many organizations still have large archives of .hed documents that contain clinically or operationally important information.
When moving to a new EHR, archive, or document management platform, these documents must remain accessible.
For many migration projects, converting HED files to PDF or PDF/A is the most practical solution.
Why NextGen Migrations Can Include HED Files
A mature EHR installation can contain documents created over many years and across multiple generations of software.
While structured information such as patient demographics, appointments, diagnoses, or billing information may reside directly in a database, formatted documents can be stored separately. Depending on the application and implementation, these documents may include HighEdit HED files.
Typical examples can include:
- Clinical reports
- Patient letters
- Physician documentation
- Correspondence
- Billing documents
- Historical forms
- Archived reports
- Other formatted patient documents
When an organization moves away from a legacy system, simply exporting database records may therefore not provide complete access to the historical patient record.
The underlying HED documents must be considered separately.
What Is a HighEdit HED File?
A HighEdit HED file is a document created using the former HighEdit document technology.
Unlike PDF or DOCX, HED is not a commonly supported document format in modern applications. Standard desktop applications and modern browsers generally cannot display these files directly.
This creates a problem during system migrations.
The files may still contain valid and important information, but access depends on software capable of understanding the original HighEdit document structure.
That is where HEDBridge comes in.
HEDBridge is designed to read legacy HighEdit HED documents and convert them into formats that can be used by modern applications and document archives.
Why Convert HED Files to PDF?
For historical patient documents, PDF is often the preferred target format because the original document usually needs to be preserved rather than edited.
Converting HED files to PDF provides several advantages.
Long-Term Accessibility
PDF is supported by virtually every desktop operating system, browser, document management system, and enterprise archive.
Once a legacy HED document has been converted to PDF, access no longer depends on the original HighEdit software.
Preserving the Original Appearance
Healthcare documents frequently contain carefully formatted content such as tables, headers, patient information, paragraphs, and page layouts.
A document conversion should preserve that presentation as closely as possible so users can continue to view the document as it originally appeared.
PDF is particularly well suited for this purpose because the resulting document has a fixed layout.
Easier Integration with a New EHR
Most modern EHR and document management platforms can store or display PDF files.
Instead of requiring the new system to understand HighEdit HED files, the migration process can convert the documents beforehand and import standard PDF documents into the destination system.
Reduced Dependency on Legacy Software
Legacy software creates operational risk.
Even if an old HighEdit-based application still runs today, maintaining the operating system, application environment, databases, dependencies, and licenses required to access historical documents can become increasingly difficult.
Converting the documents separates access to the archive from the legacy application.
PDF or PDF/A?
For long-term healthcare archives, it may be useful to convert HED documents to PDF/A rather than standard PDF.
PDF/A is a standardized form of PDF designed specifically for long-term preservation.
The appropriate format depends on the migration requirements.
Use regular PDF when documents primarily need to be displayed, downloaded, or transferred between systems.
Use PDF/A when documents are intended for long-term archival and the archive or compliance requirements specify an archival PDF standard.
HEDBridge can be used as part of a migration workflow that transforms legacy documents into standardized formats suitable for modern document repositories.
A Typical NextGen HED Migration
A migration project often involves substantially more than converting a single file.
An organization may have tens of thousands, hundreds of thousands, or even millions of historical documents distributed across directories or referenced by database records.
A typical workflow looks like this:
- Identify HED documents in the existing NextGen or legacy document repository.
- Determine how each file relates to patients, encounters, reports, or other records.
- Convert the HED documents to PDF or PDF/A.
- Preserve the original filenames or identifiers required to maintain the relationship with the source database.
- Validate the converted documents.
- Import the resulting files into the new EHR, document management system, or archive.
The document conversion itself is therefore only one part of the migration process.
Maintaining the relationship between the document and its associated metadata is equally important.
Batch Converting HED Documents
Manually opening and converting individual files is not realistic for an EHR migration.
HEDBridge is designed for batch processing and automated migration workflows.
Instead of processing documents individually, entire archives can be converted systematically.
For example, a migration could process a directory containing legacy HED files and create corresponding PDF documents:
Legacy archive
123456.hed
123457.hed
123458.hed
123459.hed
Converted archive
123456.pdf
123457.pdf
123458.pdf
123459.pdf
Keeping identifiers consistent makes it easier for migration software to associate converted documents with the corresponding patient or database record.
For a repeatable NextGen archive conversion, run the HEDBridge console locally on the Windows migration machine:
HEDBrigde.exe /s:D:\NextGen\HED /d:D:\Migration\PDF /f:pdf --recursive --continue-on-error
Use HEDBrigde.exe --license first to verify the installed trial or paid license. Keep the source and destination folders separate while the results are being validated.
Do Not Lose the Metadata
One of the most important aspects of an EHR migration is determining where the document belongs.
The HED file itself may contain the formatted document, while important metadata can reside somewhere else in the application database.
This metadata might include:
- Patient identifiers
- Encounter identifiers
- Document types
- Creation dates
- Physician information
- Record identifiers
- Original storage locations
A successful migration therefore typically combines document conversion with database migration.
HEDBridge converts the document content, while migration scripts or integration software can preserve the relationship between the resulting PDF file and the corresponding record in the new system.
What About Documents That Still Need to Be Edited?
Not every HED document is necessarily an archive document.
Some organizations may have HED files that are still used as templates or editable documents.
In these cases, PDF may not be the ideal target format.
HEDBridge can also convert HighEdit documents into editable formats such as DOCX or formats that can be processed using TX Text Control.
This can be useful when an organization is modernizing an existing HighEdit-based application rather than simply archiving its historical documents.
A common strategy is therefore:
- Historical documents: Convert to PDF or PDF/A.
- Documents that require continued editing: Convert to DOCX.
- Applications replacing HighEdit with TX Text Control: Convert documents into a format that can continue to be processed programmatically.
This allows different parts of the legacy document repository to be migrated according to their actual purpose.
HighEdit to TX Text Control
TX Text Control has frequently been used as a successor technology in applications that previously relied on HighEdit.
For software vendors maintaining or modernizing an existing healthcare application, this provides another migration path.
Instead of preserving an entire legacy HighEdit environment, developers can migrate the application to a modern document processing technology while converting the existing document repository.
TX Text Control provides document editing, generation, reporting, and conversion capabilities for modern .NET, web, desktop, Linux, and cloud applications.
HEDBridge complements this migration by providing access to the historical HighEdit documents.
Converting Before the Legacy System Is Decommissioned
Document conversion should ideally be planned before the old EHR or legacy application is switched off.
During the migration project, teams still have access to the original databases, file repositories, application configuration, and people who understand the system.
This makes it significantly easier to answer questions such as:
- Where are HED documents stored?
- How are filenames connected to patient records?
- Are all HED files historical documents?
- Are some files templates?
- Which documents need to remain editable?
- Which documents should be archived?
- Are there multiple repositories?
- Are there duplicate or obsolete files?
Once the legacy application has been decommissioned, reconstructing these relationships can become considerably more difficult.
Planning a Large HED Conversion
Before converting a complete archive, start with a representative sample.
Select documents from different years, document types, departments, and application versions.
Then verify:
- Document content
- Pagination
- Tables
- Headers and footers
- Fonts
- Images
- Special characters
- File naming
- Metadata mapping
This provides an opportunity to identify unusual document variants before processing the complete archive.
For larger projects, conversion should also produce logging that makes it possible to identify failed or problematic documents without interrupting the complete migration.
HEDBridge for NextGen and HighEdit Migrations
HEDBridge is designed for organizations and migration specialists who need to preserve documents created with discontinued HighEdit technology.
It can be used to convert legacy HED archives into modern formats including:
- DOCX
- RTF
- TXT
- HTML
- TX Text Control compatible formats
If the destination archive requires PDF/A, treat PDF/A validation as a separate step after the documented PDF conversion.
HEDBridge can process documents locally and can be integrated into controlled migration workflows where healthcare data must remain within the organization's infrastructure.
For NextGen migrations, this makes it possible to preserve historical HighEdit documents without maintaining the original document technology indefinitely.
Preserve the Documents Before They Become a Problem
Legacy document formats are easy to overlook during an EHR migration.
The database may migrate successfully while years of formatted patient documentation remain inaccessible in an old file repository.
Finding those documents after the original system has already been decommissioned can turn a straightforward migration into a much more complicated project.
If your NextGen or healthcare archive contains HighEdit HED files, identifying and converting them should be part of the migration plan from the beginning.
For historical records, PDF or PDF/A provides a practical path to long-term access.
For documents that still need to be edited or processed, DOCX and TX Text Control provide additional migration options.
HEDBridge provides the bridge between those legacy HighEdit documents and the modern systems that need to use them.