Chronic Care / Hospital Operations6 min read

Chronic Disease Registry Software for Saudi Hospitals: From Patient List to Working Follow-Up

By

A hospital chronic disease registry is a live, defined list of patients with a condition, together with their key measures, next due dates and gaps in care, so teams can act on who is overdue instead of only counting who exists. Saudi Arabia has run web-based registries for years: the Saudi National Diabetes Registry was designed in 2001 and began with 26 collaborating hospitals.

Key takeaways

  • The Saudi National Diabetes Registry was designed in 2001 by King Saud University's University Diabetes Center with King Faisal Specialist Hospital and Research Centre; Phase I involved 26 collaborating hospitals, and each hospital could access only its own patients.
  • A diabetes registry at Prince Sultan Military Medical City collected data from February 2019 to February 2020, and HbA1c rose from baseline to last visit for 24.7% of patients, a reminder that a registry is most useful when someone acts on what it shows.
  • A registry that only reports is a research tool. A hospital registry also has to drive recall, show care gaps and name an owner for each gap.
  • For a multi-branch group, the buying questions are cohort rules, branch and role access, recall tools, integration and governance, not the number of charts in a dashboard.
Illustrative chronic disease registry connecting patient cohorts, care-gap checks and hospital branches
On this page

What Saudi registries already prove

The idea is not new in the Kingdom. The Saudi National Diabetes Registry was designed in 2001 by the University Diabetes Center at King Saud University with King Faisal Specialist Hospital and Research Centre. It was built as a web-based system with a central database, where each institution has a code and users can reach only their own hospital's patients, while a national registrar can see across participating sites. Phase I involved 26 hospitals.

Registries also exist inside hospital groups. The Kidney Disease in the National Guard (KIND) registry identified patients through ICD-10 codes across five National Guard hospitals. A type 2 diabetes registry at Prince Sultan Military Medical City ran its database from February 2019 to February 2020, with data collected by trained diabetes nurse specialists. These registries show what is possible when cohort rules, data collectors and governance are in place. Most of them were designed to describe a population. A hospital operations team has a second question: who needs to be called this week?

A registry is not the same as the EHR, or a spreadsheet

The Agency for Healthcare Research and Quality describes a disease registry as a tool for tracking the clinical care and outcomes of a defined patient population. Three things follow from that definition.

  • Defined population. The registry has a rule for who is in it. A chart search done once is not a registry.
  • Tracked over time. It holds the measures that matter for each patient and the dates they are due.
  • Used for care. It produces exception lists, for example patients with no visit in the interval the clinician set.

An electronic health record holds each patient's chart. A spreadsheet can hold a list but breaks when several branches edit it. A registry sits across charts and shows the cohort.

What to ask for when you evaluate software

Treat these as a buyer's checklist for any vendor, including us.

  1. Cohort rules you can edit. Can a clinical lead define a cohort from diagnosis codes, lab values and medicines, and see who enters and leaves? The KIND registry's use of ICD-10 codes is one example of a rule-based cohort.
  2. Measures and due dates per patient. Last result, next due date, last contact, owner.
  3. Care-gap lists. A daily or weekly list of patients who are overdue, with the reason and the owner. This is the difference between a registry and a report.
  4. Recall and reminder tools. Reminders in Arabic and English, consent captured, and a record of what was sent.
  5. Branch and role access. The Saudi National Diabetes Registry separated hospital data by institution code. A group needs the same principle by branch and by role, with a group-level view for leadership.
  6. Integration. How the registry receives data from the EHR, lab and pharmacy, and how it supports national interoperability requirements. Ask the vendor to show it, not describe it.
  7. Governance. Who can change cohort rules, who can export, how changes are logged.
  8. Reporting by branch. Comparison across sites, with the same definitions at every site.
  9. Data protection. Consent, access logs, hosting and retention under Saudi Arabia's Personal Data Protection Law.

Pick one condition first

Registries fail when they try to cover every disease at once. Start with one condition that already has clinical ownership and a clear follow-up rule. Examples already in our library include heart failure remote follow-up, diabetic foot ulcer follow-up and remote monitoring for diabetes and hypertension. Rare conditions have their own registry needs; see our article on a rare disease patient registry platform.

A step-by-step start

  1. Name the clinical lead and the operations owner. One of each.
  2. Write the cohort rule in one sentence. If it needs a paragraph, narrow the condition.
  3. Choose five measures. Only those that trigger an action.
  4. Set the recall rule. The clinician decides the interval. The registry applies it.
  5. Load the cohort and read the gaps. The first list is usually a surprise.
  6. Assign every gap to a person. A gap with no name will stay.
  7. Review monthly. Fix the rule, then add a second condition.

Where this goes wrong

  • Data entered twice. If staff retype from the chart, the registry will be out of date within weeks. Feed it from source systems wherever possible.
  • No owner for gaps. The list exists; nobody calls.
  • Different definitions per branch. Comparisons become arguments.
  • Dashboards without action. Counting patients is not following them.
  • Consent as an afterthought. Reminders and data sharing must follow the patient's consent and the hospital's policy.

An illustrative scenario

This is a hypothetical example. A hospital group with four branches in the Eastern Province wants to follow patients with type 2 diabetes. The clinical lead defines the cohort by diagnosis code and recent HbA1c. The first load shows patients with no HbA1c recorded in the interval the lead set, branch by branch. Each branch coordinator receives their list on Sunday morning, calls the patients, and records the outcome. By the next monthly review the group can see how many gaps were closed and where the process stalled. The cohort rule did not change. What changed is that the list became somebody's job.

Frequently asked questions

What is a chronic disease registry in a hospital?

It is a defined list of patients with a condition, with their measures, due dates and care gaps, kept up to date and used to organise follow-up.

What are patient registries used for?

They are used to track care and outcomes for a defined group, to find patients who are overdue for care, to compare sites and to support quality improvement and research.

How do you create a patient registry?

Start with one condition, a clinical lead and an operations owner. Write a cohort rule, choose a few measures that trigger action, set a recall rule and load the cohort from your source systems.

What is the difference between a registry and an EHR?

The EHR holds each patient's chart. A registry sits across charts to show a cohort, its measures and who is overdue.

Do we need a registry for every chronic disease?

No. Start with one condition that has clear clinical ownership, then add others once the routine works.

Sources

Book a CareSync demo