01
Registration (HIS)
Creates the patient and visit identifiers.
SOLUTION 04 / Hospital IT and clinical operations
Hospital Application Integration
Connect registration, orders and results so authorized clinicians can follow the right patient’s visit.
Discuss a pilot at your site ↗
A clinician orders a radiology exam
- 01 Register
- 02 Order the exam
- 03 Acquire and store
- 04 Return the report
From exam order to result in the visit record
The hospital information system creates identifiers for the patient and the visit. The electronic medical record sends the order to the radiology information system. The exam is performed and the images are stored in the picture archiving and communication system. The approved report and image link appear in the clinical record according to the user’s permissions.
The archive holds the images. The approved report returns to the visit record with a link for authorized users.
Hospital integration components
Reference workflow for registration, laboratory orders and radiology studies
02
Clinical record (EMR)
Sends orders and displays results and reports.
03
Interface engine
Routes messages and maps identifiers across systems.
04
Laboratory system (LIS)
Tracks specimens and returns verified results.
05
Radiology system (RIS)
Schedules exams and issues approved reports.
06
Imaging modality
Acquires images for the ordered exam.
07
Image archive (PACS)
Stores studies for retrieval.
08
Image viewer
Opens the authorized study from the patient record.
09
Exception queue
Holds rejected messages for review.
What the project includes
- First interface
- Select one sending system, one receiving system and one clinical workflow.
- Optional extensions
- Additional lab or radiology interfaces, an image viewer and patient identity reconciliation.
- Site inputs
- Application versions, sample messages, patient identification policy and vendor interface fees.
Pilot one order and its result
- Identity matching — Use synthetic patients with similar names to verify that the result reaches the correct visit.
- Exception handling — Send a duplicate or unmatched order and confirm that it enters the review queue.
- Clinical sign-off — Agree on role-based access, downtime procedures and the sign-off owner for each application.
Include the IT lead, the clinical lead and both application vendors in the interface review.
Discuss a pilot at your site ↗Questions from the operations team
Where are images stored and where does the report appear?
The imaging archive stores the study. The approved report returns to the visit record with a link for authorized clinicians.
What happens when patient identifiers do not match?
Unmatched messages enter an exception queue for the hospital team. Test this workflow using synthetic patient data and agreed matching rules.
What site information is needed to define the scope?
Application versions, sample messages, patient identification policy and vendor interface fees.