DijitalPi
TREN
Contact
Home/ AI Solutions
Patient admissions and referral units · Inter-organisational document workflows

AI System for Administrative Checks of Patient Referral Documents

We design a document system that checks identity fields, dates, the sending organisation and attachments without deciding whether a referral is medically necessary. The workflow checks the referral form, identity fields, organisation details and attachment list against their sources, then prepares a missing-field report for the referral. No record or operational process changes until a patient admissions officer and authorised healthcare professional have completed their review.

Representative referral document ops panel with a work queue, checks and an audit trail: referral attachment review queue
Referral attachment review queue Representative interface — contains no real data. Identities are anonymised. The panel does not decide diagnosis, treatment or the clinical need for referral.

The problem

In day-to-day operations, missing attachments can delay admission. When the referral form, identity fields, organisation details and attachment list are scattered across different screens, documents or team records, problems do not become visible in time.

Fragmented data delays preparation of the missing-field report and forces staff to search manually for supporting evidence again. Before making a decision, the patient admissions officer and authorised healthcare professional have to complete missing fields and verify inconsistencies one by one.

A common exception is that attachments may be completed later in an emergency process. Incomplete or incorrect automation that overlooks this context could lead to a valid referral being rejected or an incomplete file being accepted, so the output cannot be applied directly.

What we set out to improve

  • Number of confirmed missing administrative fields
  • Rate of outputs corrected or rejected by the patient admissions officer and authorised healthcare professional
  • Time between the source record and the review output

How the system works

  1. 01 Define the scope of the review and the authorised patient admissions officer and healthcare professional roles
  2. 02 Collect the inputs: referral form, identity fields, organisation details and attachment list
  3. 03 Check source identity, date, version and data freshness
  4. 04 Check the document version and identity
  5. 05 Compare the listed attachments with the files
  6. 06 Check the exception: attachments may be completed later in an emergency process
  7. 07 Place low-confidence or inconsistent records in a separate human review queue
  8. 08 Write the source identity, rule, output and time to the audit trail
  9. 09 Have the patient admissions officer and authorised healthcare professional approve, correct, defer or reject the output

Methods we used

  • Validation of the template and attachment list
  • Source, format, version and required-field checks for the referral form, identity fields, organisation details and attachment list
  • A missing-data warning instead of an estimate when inputs are missing or inconsistent
  • Checking exceptions separately from the main rule
  • Storing the source identity, rule result, referral missing-field report and human decision together

Where people stay involved

The system stops after preparing the referral missing-field report. The patient admissions officer and authorised healthcare professional review the sources and the exception, then approve, correct or reject the output. Direct application is disabled because it could lead to a valid referral being rejected or an incomplete file being accepted; the system does not replace specialist judgement.

Data and security

Access to the referral form, identity fields, organisation details and attachment list is limited to the minimum permissions required for each role. Identifiers and sensitive fields are masked where possible, and only the necessary section is sent to the model rather than the entire raw file. Access, outputs and decisions by the patient admissions officer and authorised healthcare professional are recorded; the system does not enter production until the organisation has approved the retention period and data location.

Who this suits

A good fit

  • Organisations processing standard referrals

Not a good fit

  • Organisations expecting medical referral decisions

Frequently asked questions

Which inputs are used?

The system uses the referral form, identity fields, organisation details and attachment list. If a required field is unavailable, it does not produce a definitive result and presents the missing source for review by the patient admissions officer and authorised healthcare professional.

At what point does a person make the decision?

The workflow stops when the referral missing-field report is ready and waits for approval from the patient admissions officer and authorised healthcare professional. The specialists may correct, defer or reject the output and record their reasons.

Can the output be audited?

The system is designed to store the source identity, applied rule, exception, output and human decision together. This makes it possible to review later how the source data led to a particular recommendation.

Project led by:DijitalPi

✦ PI ASSISTANT · ARTIFICIAL INTELLIGENCE

online

Ask the DijitalPi AI Assistant your question

No need to fill in a form and wait for a reply — write your question and let Pi, trained on DijitalPi's 20 years of know-how, answer within seconds.

  • Instant answers, 24/7
  • Service-specific context — no generic replies
  • Can connect you to a free consultation if you wish
Hi! 👋 I'm Pi — DijitalPi's AI assistant. Write whatever you'd like to know about AI System for Administrative Checks of Patient Referral Documents and I'll answer right away.

Pi Assistant answers are for information purposes; for a proposal get in touch.

ASK AI ABOUT DIJITALPI

Let an AI explain what DijitalPi does.

Opens your chosen assistant with a ready research prompt. It reads the site live and answers.