Scope of work
1. Revamp/ enhance the UI of Orthanc DICOM server
2. Adding more permission levels if the listing is allowed.
3. Enable multilingual
4. Upgrade the performance of listing studies in main page
5. Advise on the hardware requirement to enhance the performance as DICOM node
6. Integration with OHIF DICOM viewer
7. Scalability or clustering upon multiple nodes and incremental storage required
8. Security enhancement for internet access
9. Integration with Osirix DICOM viewer or any other FDA-cleared viewer (Optional)
Please check the phase for the priorities
Factors for consideration
1. Meet the basic project team requirement (Baseline)
2. Bidding price (50%)
3. Project profile (10%)
4. Upwork track records (10%)
5. Solution approach (30%)
In order to bid the project, candidate must provide following items:
1. Solution design & approach (With UI design)
2. Project profile and relevant experience (With existing screenshot as proof)
3. Any counter suggestion
4. Total project cost in USD with payment milestone
5. Project timeline once confirmed
6. Communication windows (e.g. from 10:00am to 6:00pm GMT+8)
Project background/ Pain points
We have a legacy PACS which the storage is about 21TB. And we are planning to migrate to
Orthanc server later.
We deployed an Orthanc server in trial and we pushed 700 studies for evaluation. However we
are suffering few critical issues. The performance of the listing page is very slow. It lists only 3-4
studies in a second. And the full list is NOT displayed at all.
1/5
We expect the data growth shall be 5TB per year and all the medical data must be stored for up
to 7 years. And it is possible that we acquire additional hardware servers as new DICOM nodes.
May be cluster should be formulated. Or simply add more harddisks.
It is also very difficult to adjust the study date range which normally, today studies should be
displayed. The datafield is too narrow.
Current configuration on hardware server
● VMWARE 7 ESXI
● Ubuntu LTS 22.04
● HP ProLiant DL380 Gen9
● Dual Intel(R) Xeon(R) CPU E5-2690 v4 @ 2.60GHz
● 128GB ECC-DDR4 RAM
● 2TB SSD x 4 in RAID 5
● 16 CPU cores assigned
● 48G RAM assigned
● 64GB + 1TB assigned
Expectation on the enhancement to Orthanc server
(Phase 1)
Enhance the UI of Orthanc server
Key identifiers for searching
● Patient Name (Support wildcard)
● Patient ID
● Patient DOB (Format should be YYYY-MM-DD)
● Patient Sex
2/5
● Modalities
● Study Date Range (Please make it wilder)
● Study Description
● Accession Number (Multiple dropdown selection)
Enhance the listing page performance
It lists only 3-4 studies in a second now and doesn’t display full list at all
Responsive web behavior
We expect that this web portal should support multiple web browser such as Safari in MACos,
chrome browser, Edge with different resolutions. Best optimal resolution should be FullHD, 4K
and standard laptop resolution 1366 x768
Default study date range should be “Today”
Listing page should show all items with pagination, default 30 items per page, allow options (30, 50,
100, 300, 500 and all)
Enable multilingualism by using a language dictionary design approach (.JSON) so that we
could add our translation on our own. Expected the language shall be 3 by default
Keep all functionalities
Rearrangement of UI in listing page
And rearrange the priorities in details as following:
1. Patient Name (Support wildcard* )
2. Patient ID
3. Patient DOB (Format should be YYYY-MM-DD)
4. Patient Sex
5. Accession Number
6. Modalities
7. Study Description
8. Study Date and Study Time (Please make it human readable)
9. Total number of images
10.Total number of series
3/5
11. Last update
12.Requesting Physician
13.Referring Physician
14.Institution Name
15.Patient Other IDs
16.Patient Other Studies
17.DICOM Disk size (MB)
18.Study Instance UID
And series listing
1. Series ID/ Series number
2. Series Description
3. Modality
4. Number of images
Download the zip (Mandatory) with encryption and passcode (Optional) **
Zip the passcode with dob (yyyymmdd)
View in OHIF viewer
Integration with OHIF viewer; Viewer is installed in same server.
Send to DICOM nodes **
Please show the listing directly once click the icon
Modify action
Keep it as it
Anonymize **
Keep it as it
Delete action **
Keep it as it
</>
Keep it as it.
Allow multiple bulk actions
4/5
Allow multiple batch action for item marked with **
For anonymize action, please just anonymize patient name and patient ID in random manner.
Patient ID should be in just random number with 16 characters no repetition.
Setting page
Allow end-users to add more DICOM nodes
Scalability or clustering upon multiple nodes and incremental storage required
As more DICOM images are stored, the performance and storage space is a concern, please advise
on following:
1. Possibilities on scale up by adding hot-swap harddisk in ESXI
2. Possibilities on clustering solution
3. Possibilities on redundancy (Primary and secondary server)
4. Possibilities on multiple location deployment
Some clients may have multiple imaging centers in different location
5. Possibilities on upgrade without service interruption
Further development of Orthanc server (Phase 2)
Integration with user permission of RIS
We are going to integrate this PACS to our RIS. In our RIS, we have a sophisticated user permission
leveling which caters for radiologists; radiographer, clinic manager, referral doctors etc…
Usual practise would be as following:
● Clinic manager as admin user could access all data
● Radiographers could view patient of certain modalities according to the assignment
● Radiologists could view only assigned patients.
● Chief radiologists could view all patients
● Referral doctors could view only those patients they are referring to the imaging centers.
Permission is set in our RIS database but NOT in Orthanc server.
Generally, we will give you a list of patients which could be assigned by certain users, probably a
view table in MySQL database.
And users could NOT directly access to study without proper permission
Security enhancement for internet access
As far as we understand, DICOM server doesn’t have any security protocol at all. Please propose an
implementation approach for hardening the data security so that we could release a web portal for
users outside the local network to access the images whatever. And we need a secured approach so
that it won’t be hacked.
But of course, DICOM server would still be installed as an intranet only (Local network) for the
DICOM transfer between modalities.
Integration with Osirix DICOM viewer or any other FDA-cleared viewer (Optional)
As title
5/5
