Patient information
registration and the core patient file
Hospitals & Healthcare
We digitize your medical records, link every document to the right patient and visit, and open each file only to the departments cleared to see it. When your project includes integration, documents link to your HIS.
Confidentiality applied
Every view on recordBuilt around patient privacy
ELArchive is a medical records archiving platform for hospitals. Every document is indexed to a patient file and a visit, sorted into six record categories, checked against its paper original, and restricted by user, group and department. When integration is in scope, IT-Blocks designs the link to your Hospital Information System (HIS) together with your HIS vendor.
The challenge
Clinicians work with the history in front of them, and a file that can’t be found in time doesn’t help anyone. Meanwhile, every paper file in circulation is a privacy risk nobody can fully track.
Discharged, file sent to storage
Back for a follow-up
registration and the core patient file
documents from clinic visits
documents from hospital stays
test results and radiology reports
letters linked to the case
documents outside the five categories above
How a patient file is organized
medical record number and identifying details.
visit ID, date and department.
type, date, review status and where the paper original is kept.
Your HIS stays the source of truth for who the patient is and which visit a document belongs to. When integration is part of the project, we design the link layer with your HIS vendor:
Integration is scoped for each hospital and tested jointly with your HIS vendor. Developing your HIS itself sits outside the project.
supplies the patient and visit identity.
matches identifiers and links each document to its patient and visit.
makes the document reference available as the agreed design sets out.
Staff sign in with their existing Active Directory accounts.
Every view, edit and borrow carries a name and a time, so your records team can answer privacy questions.
Every paper original is coded by location, so it can be found when needed.
files are received, sorted, coded and prepared for scanning.
pages are captured and matched against the original.
each document is assigned to its patient and visit, and its data is reviewed.
We check the scanned pages and the data linked to them.
Every rejection records its reason, and the document goes back to scanning or indexing depending on the fault.
Illustrative report · sample data•••| Period | Documents | Folders |
|---|---|---|
| Day 1 | 164 | 24 |
| Day 2 | 208 | 31 |
| Day 3 | 176 | 26 |
Illustrative report · sample data•••| File reference | Department | Status |
|---|---|---|
| DEMO-001 | Outpatient | Complete |
| DEMO-002 | Inpatient | Incomplete |
| DEMO-003 | Laboratory | Complete |
Illustrative report · sample data•••| User | Documents | Folders |
|---|---|---|
| User 01 | 342 | 51 |
| User 02 | 218 | 32 |
| User 03 | 396 | 59 |
Illustrative report · sample data•••| Department | Files | Complete |
|---|---|---|
| Outpatient | 86 | 72 |
| Inpatient | 74 | 58 |
| Laboratory | 48 | 36 |
Classification, fields, permissions and integration.
Installation and setup of the environment and users.
A sample of files and agreed tests.
Results accepted, administrators and users trained.
Handover, go-live and the agreed support.
| What we test | How we verify it | What you sign off |
|---|---|---|
| Document linking | Patient, visit and document type matched across a test sample | Matching rules and exception cases |
| Archive quality | Page count and clarity checked against the original, indexing reviewed | Quality checklist |
| Search and retrieval | Sample documents retrieved by the agreed fields | Search scenarios and expected results |
| Permissions | Operations run against the role matrix | Permissions matrix |
| Integration (when included) | Integration scenarios and error handling run | Joint test record with your HIS vendor |
Cost & timeline
Volumes, duration, cost and support are set once the detailed scope is agreed. They depend on how many patient files you hold, how many document types you index, and whether HIS integration is included. The scoping call covers all of it, and you get a written plan, a timeline and a quote afterwards.
Yes. We receive, scan, index and check patient files before they enter the archive, in the volumes agreed in your project scope.
By patient file and visit, across six categories: patient information, outpatient clinics, inpatient, lab and radiology, correspondence, and other.
It can, when integration is part of the project. We design the link layer with your HIS vendor and test it jointly before acceptance. Each integration is built for your HIS rather than plugged in off the shelf.
No. HIS development sits outside the project scope.
Only users whose group, department, permissions and confidentiality level allow it.
Yes. Every view, edit and borrow carries a name and a time.
Yes. Every original is coded by store, room, shelf and box.
Through two reviews: the image (clarity, page count, completeness) and the data (patient, category, index fields). Rejected documents go back with a recorded reason.
Document intake per period, file status, user performance and operational reports by department, user and file status.
As a minimum guide, an application server and a database server, each with 32 GB of memory, 4 cores and a 500 GB system disk, on Windows Server 2019 or later, with SQL Server 2019 or later for the database. Document storage and backups are sized separately.
Yes. Administrators and users are trained before handover.
Yes. Indexing and full-text search work in Arabic and English.
Both are set once the detailed scope is agreed. You get a timeline and a quote after the scoping call.
Let’s start with your records
Share a rough count, and we'll build the scoping call around it.
This request has not been sent. You can copy it and use ELArchive’s live contact page.
Use these guides to plan digitization, improve retrieval and review record quality.