Patient admission, outpatient clinics, inpatient care, the laboratory, the pharmacy, and billing all depend on the same HBYS database. When the system stops, patient admission stops with it, and test results, prescriptions, and the notifications sent to Ministry of Health systems are delayed. The servers, database, network, and backups underneath the HBYS therefore have to be built around a hospital that never closes.
Turkish regulations use "health information management systems" (SBYS) as the umbrella term; HBYS is the type used in hospitals. Whichever vendor's HBYS you use, we build and operate the infrastructure it runs on.
When you need it
- Your HBYS server runs in a server room inside the hospital and the hardware is ageing.
- You do not know when you last checked that a database backup actually restores.
- Medical devices, staff computers, and guest Wi-Fi share the same network.
- Records of who accessed which patient record, and when, are not collected in one place.
- The image archive (PACS) grows every year and you do not know when storage will run out.
- You run several hospitals or medical centers and each one's servers are managed separately.
Rules that shape the infrastructure
Health data is a special category of personal data under KVKK, Turkey's personal data protection law (Law No. 6698). We build the infrastructure around the rules below and check the current text of the regulations with you before installation.
- Regulation on Health Information Management Systems: Data is kept in Turkey, in approved environments. Activity logs are retained for set periods and protected with time stamps. Restores from backup are tested at regular intervals, and a copy of the backup is kept at a different physical location.
- Regulation on Personal Health Data: Data created at a health facility is sent to the Ministry's central systems without delay, so the HBYS's external connection has to stay up.
- The KVKK Board's decision on special categories of data (2018/10): It expects encryption, logging of access, regular security testing, two-factor authentication for remote access, and transfer over secure channels.
Scope
- Server environment. We set up the HBYS application and database servers and patch them on a schedule. We confirm virtualization, CPU, and memory requirements in the HBYS vendor's documentation before installation.
- Database. We install, maintain, and monitor the Microsoft SQL Server or Oracle Database server the HBYS uses. If another database engine is in use, we first confirm the requirements with the vendor.
- High availability. So that patient admission keeps running when a server fails, we can set up an optional HA cluster and tie failover and failback to a written outage plan.
- Backup and restore testing. We keep backups in the isolated backup area on ARGE Cloud. We agree with you where the copy at a different physical location is kept, and we report each restore test result to you in writing.
- Image archive (PACS). We measure how fast the archive grows and plan storage capacity accordingly. Together we decide which images stay at the hospital and which go to ARGE Cloud, based on how fast they need to be read.
- Network separation. We separate medical device, staff, and guest networks with VLANs and limit traffic between them with firewall rules. For guest Wi-Fi, ErişimPark can keep the access logs required under Law No. 5651.
- Access logs. We collect server, database, and firewall logs in a central log system (SIEM) and set retention periods to match the regulations.
- Remote access. For hospital management, on-call staff, and the vendor's support team, we set up access with two-factor authentication through ARGE ZTNA or SSL VPN.
- Monitoring. We monitor disk, memory, the database service, backup results, and the connection to Ministry systems; monitoring hours and response scope are written in the contract.
Out of scope and limits
We do not sell HBYS licenses or provide installation, version upgrades, or functional support, and we are not an official partner of HBYS vendors. The software side of notifications to Ministry of Health and Social Security Institution (SGK) systems such as e-Nabız and MEDULA is the HBYS vendor's responsibility; we provide the network and access those connections run on. Setting up and certifying an information security management system is not part of this service.
How we work
- We map where the HBYS servers run today, the database, backups, network layout, and connections to Ministry systems.
- We confirm the vendor's hardware and virtualization requirements in its documentation and propose a design in writing, including the logging and backup arrangements the regulations expect.
- We plan the migration for the hospital's quietest hours and take a backup and test the restore before moving anything.
- After migration, we report backup results, restore tests, and capacity trends; the reporting frequency is written in the contract.
Service models
- On ARGE Cloud: The HBYS servers run in the Istanbul data center, in a VPC dedicated to you, and the data stays in Turkey. We confirm the vendor's requirements before installation.
- In your environment: We build and operate the servers, database, network, and backups in the hospital's server room.
- Combined: Part of the HBYS or PACS runs at the hospital, while backups and the archive run on ARGE Cloud.
The main hospital, its outpatient clinics, and affiliated medical centers all work on the same HBYS. They can be linked over your carrier's MPLS line, a private line that keeps traffic off the internet, and the same line can be extended to ARGE Cloud so the HBYS servers there are reached without crossing the internet. A medical center without MPLS connects through an SD-WAN capable router and firewall, over an encrypted tunnel on its existing internet line. Our page on connecting head office and branches explains which option suits which site.
Technologies we use: Windows Server · Linux · Microsoft SQL Server · Oracle Database · VLAN · IPsec · SSL VPN · ARGE ZTNA · SIEM
For the sector's wider IT needs, see our healthcare page.
Frequently asked questions
Does our patient data leave Turkey? No. Data for systems running on ARGE Cloud is kept in the Istanbul data center, in a VPC dedicated to you. When the infrastructure runs in your hospital's server room, the data never leaves the building.
What happens to patient admission if a server fails? With the optional HA cluster, the workload moves to the second server. Without a cluster, we agree in a written outage plan what is done, within what time, and by whom.
Can you work with our HBYS vendor? Yes. Installation, upgrades, and functional support stay with the vendor. On the infrastructure side we work with the vendor's team and give them the access they need with two-factor authentication.
How often do you test restores from backup? We write the test frequency into the contract based on what the regulations expect and what you need. We report every test result to you in writing.
Can we keep PACS images on ARGE Cloud? You can, but because images are large, read speed and line capacity decide. We measure first and then decide with you which images stay at the hospital and which go to ARGE Cloud.