You find an old document repository containing thousands of files with names such as:
123456.hed
123457.hed
123458.hed
Windows does not recognize them. Microsoft Word cannot open them. A browser cannot display them.
So what are these files?
If they originate from a legacy enterprise or healthcare application, they may be HighEdit HED documents.
HighEdit was a document editing and reporting technology integrated into applications for creating and displaying formatted documents. Although HighEdit itself is no longer a current document platform, many organizations still have HED files created by those applications.
HEDBridge provides a way to read these legacy documents and convert them into modern formats.
What Is a HighEdit HED File?
An HED file is a document created by the former HighEdit document technology.
Applications integrated HighEdit as an embedded component rather than requiring users to work with a separate word processor.
From the user's perspective, the document simply appeared inside the business application.
Behind the scenes, the content could be stored as an HED document.
These files may contain formatted information such as:
- Text
- Paragraphs
- Tables
- Headers and footers
- Images
- Page layouts
- Reports
- Forms
- Correspondence
The .hed file was therefore part of the application's document storage architecture.
Why Can't I Open an HED File in Microsoft Word?
HED is not the same as DOCX, RTF, or PDF.
It is a proprietary legacy document format associated with HighEdit.
Modern office applications do not generally understand its internal structure.
Renaming a file from:
document.hed
to:
document.docx
will not convert it.
The document needs to be interpreted by software that understands the original HighEdit file format.
Where Do HighEdit HED Files Come From?
HighEdit was integrated into business applications in a variety of industries.
HED files can therefore appear in legacy:
- Healthcare applications
- EHR systems
- Document management applications
- Reporting applications
- Administrative software
- Industry-specific enterprise systems
Healthcare migrations are a particularly common scenario because older systems may contain years or decades of patient documentation stored as HED files.
Why Are the Filenames Sometimes Just Numbers?
Legacy applications frequently use internal identifiers rather than human-readable filenames.
A repository may therefore contain files such as:
4839217.hed
4839218.hed
4839219.hed
The actual information describing the document may reside in the application's database.
For example:
Document ID: 4839217
Patient ID: 102733
Type: Physician Letter
Date: 2014-09-18
File: 4839217.hed
This is important during migration because the HED file alone may not tell you where the document belongs.
How Can You Open a HighEdit HED File Today?
If the original HighEdit application is still available, it may still be possible to open documents through that environment.
However, maintaining an entire legacy application just to view historical documents is rarely a good long-term strategy.
A more sustainable option is to convert the HED file into a modern document format.
HEDBridge provides this conversion path.
Convert HED to PDF
If the document is historical and does not need to be edited, PDF is usually the most practical format.
To convert one HED file from the Windows console, use /s: for the source, /d: for the destination, and /f:pdf for the output format:
HEDBrigde.exe /s:D:\Archive\document.hed /d:D:\Output /f:pdf
After conversion, the file can be opened using:
- Modern browsers
- PDF viewers
- EHR systems
- Document management applications
- Archive systems
This removes the need for HighEdit when viewing the document.
Convert HED to PDF/A
For documents intended for long-term preservation, PDF/A can be used as an archival target.
This is particularly relevant for healthcare records, legal documents, financial records, and other documents subject to long retention periods.
Convert HED to DOCX
If the document needs to remain editable, DOCX may be a better destination.
This can be useful for:
- Templates
- Standard letters
- Forms
- Reusable documents
- Application modernization projects
Instead of preserving only a fixed representation, the document can continue to participate in an editable workflow.
HighEdit and TX Text Control
Some software vendors and organizations have moved from HighEdit to TX Text Control for modern document editing and processing.
In these scenarios, HEDBridge can help bridge the historical document repository while TX Text Control provides the technology for current and future document workflows.
Existing HED content can be converted while the application itself moves away from its dependency on HighEdit.
Can You Convert Thousands of HED Files?
Yes. Legacy document repositories often contain far more documents than could realistically be processed manually.
HEDBridge is designed for batch conversion scenarios.
For a folder or nested archive, use the recursive batch command:
HEDBrigde.exe /s:D:\Archive\HED /d:D:\Output /f:pdf --recursive --continue-on-error
Use HEDBrigde.exe --license to check the current license status before starting the conversion.
A directory containing:
001.hed
002.hed
003.hed
004.hed
can be converted into corresponding modern documents such as:
001.pdf
002.pdf
003.pdf
004.pdf
This is particularly useful during system migrations and archive projects.
Do Not Forget the Database
If you discover an HED repository from an old business application, investigate the corresponding database before shutting the application down.
The database may contain the information required to identify the documents.
Look for metadata such as:
- Document IDs
- Patient IDs
- Customer IDs
- File paths
- Categories
- Dates
- Authors
- Encounter IDs
Converting the file is only one part of a successful migration.
The converted document must also remain associated with the correct record.
Should You Keep the Original HED Files?
During a migration, retaining the original files is useful until the conversion has been completely validated.
This allows teams to compare documents, investigate failures, and repeat conversions if necessary.
The important goal is to make sure the original HED files are no longer the only accessible representation of important documents.
HEDBridge Makes Legacy HED Files Accessible Again
Discovering thousands of files in an unsupported format can initially look like a major migration obstacle.
But the information stored inside those documents does not need to remain tied to HighEdit forever.
HEDBridge converts legacy HighEdit HED documents into modern formats including PDF, DOCX, RTF, TXT, HTML, and TX Text Control compatible formats. PDF/A validation can be performed after PDF conversion when long-term archival requirements apply.
That allows organizations to open, archive, migrate, and continue using documents created by applications that may have been deployed decades ago.