Administrative, Financial and Patient-Service Systems

Introduction and Context

Hospital information systems (HIS) are not limited to clinical documentation. They also coordinate the administrative, financial, logistical and patient-facing activities that make care accessible, sustainable and accountable. Registration creates the patient identity on which every subsequent transaction depends. Scheduling determines how scarce clinical capacity is used. Admission, discharge and transfer (ADT) processes establish the patient’s operational location and episode of care. Billing, insurance and revenue-cycle systems convert documented services into financial claims and receipts. Supply-chain, human-resource and asset-management systems ensure that people, products and equipment are available when required. Patient portals extend the hospital’s information environment beyond its physical boundaries.

For health-care managers, these systems are simultaneously operational tools, control mechanisms and sources of managerial intelligence. A technically functional system may still produce poor outcomes if workflows are badly designed, data are inaccurate, staff do not use the system consistently, or incentives encourage undesirable behaviour. The central managerial task is therefore to align information systems with patient pathways, regulatory obligations, financial sustainability, workforce capability and quality of care.

Learning Objectives

After studying this chapter, the learner should be able to:

1. Explain the role and interdependence of administrative, financial and patient-service systems.
2. Evaluate registration, scheduling and ADT processes from operational and governance perspectives.
3. Analyse billing, insurance and revenue-cycle activities using appropriate performance measures.
4. Assess supply-chain, human-resource and asset-management systems.
5. Evaluate patient portals in relation to access, engagement, equity, privacy and safety.
6. Recommend an integrated HIS architecture and implementation approach for a hospital.
7. Identify ethical, legal, cybersecurity and managerial risks in these systems.

1. The Administrative Information Backbone

1.1 Patient identity and registration

Registration is the controlled creation or retrieval of a patient record. It normally captures demographic information, contact details, identity evidence, emergency contacts, payer information, consent preferences and communication requirements. The process may occur at a reception desk, through a call centre, online, at a kiosk or through a referral interface.

The most important registration principle is that one person should have one authoritative enterprise identity. Duplicate medical record numbers can fragment allergies, previous diagnoses, billing histories and clinical results. Conversely, incorrectly merging two people can create a serious patient-safety event. Hospitals therefore use a master patient index (MPI), supported by deterministic or probabilistic matching. Deterministic matching requires exact agreement on selected identifiers. Probabilistic matching assigns weights to partial agreements, such as name, date of birth, telephone number and address, and routes uncertain matches for human review.

Registration quality is not merely a clerical concern. It affects:

• correct clinical-document and result association;
• eligibility verification and claims submission;
• patient communication and follow-up;
• population-health reporting;
• duplicate testing and avoidable administrative work.

Good practice includes standardised data definitions, identity-proofing rules, duplicate-record work queues, clearly assigned data stewardship and periodic MPI audits. Staff should avoid using a national identification number or social identifier as the sole matching key, because such identifiers may be absent, incorrectly entered or inappropriate for broad operational use.

1.2 Appointment and capacity management

Scheduling systems match demand for services with constrained resources: clinicians, rooms, diagnostic equipment, operating theatres and support staff. A schedule should represent more than an appointment time. It should include appointment type, expected duration, preparation requirements, resource dependencies, referral status, patient preferences and cancellation rules.

Appointment systems support several models:

• Fixed-slot scheduling: appointments are assigned to standard time blocks.
• Block scheduling: capacity is reserved for a clinic, procedure type or priority group.
• Open-access scheduling: selected capacity is held for near-term demand.
• Overbooking: appointments exceed nominal capacity to offset expected non-attendance; this requires reliable historical data and a safe escalation plan.
• Resource-constrained scheduling: an appointment is confirmed only when all required resources are available.

A useful managerial measure is the no-show rate:

The numerator counts appointments missed without timely cancellation, and the denominator includes the defined population of scheduled appointments. The organisation must define whether rescheduled appointments, provider cancellations and same-day cancellations are included. Without consistent definitions, comparisons between clinics are misleading.

Scheduling decisions involve trade-offs. Maximising utilisation may reduce flexibility for urgent cases and increase delays when visits run over time. A manager should therefore examine utilisation, access time, cancellation rates, patient waiting, staff overtime and clinical risk together rather than pursuing a single target.

1.3 Admission, discharge and transfer

ADT systems record movement through the hospital: admission, ward transfer, change in attending service, leave of absence and discharge. ADT data feed bed management, nursing assignments, dietary services, clinical systems, billing, infection prevention and regulatory reporting.

The operational rule is simple but critical: the patient’s current location and status must be accurate at the time they change. Delayed transfer entries can direct medication, meals, alerts or clinicians to the wrong location. A discharge entered prematurely can interrupt care; a delayed discharge can distort occupancy and billing records.

ADT workflows should distinguish clinical discharge from administrative closure. They should also support observation status, emergency encounters, same-day procedures, newborn episodes and transfers between campuses. Bed-management dashboards are useful only when the source events are timely and governed. A visually sophisticated dashboard cannot correct inaccurate ADT data.

A common performance measure is average length of stay (ALOS):

The calculation assumes a defined period and a consistent convention for counting inpatient days. It should be stratified by service, diagnosis, case complexity and discharge destination. A lower ALOS is not automatically better: premature discharge may increase readmission, harm or post-acute costs.

2. Financial, Insurance and Revenue-Cycle Systems

2.1 From service event to payment

The revenue cycle begins before care is delivered and ends when the account is resolved. Its stages commonly include pre-registration, eligibility verification, authorisation, charge capture, clinical documentation and coding, claim generation, claim submission, payment posting, denial management, patient billing and account closure.

A simplified process is:

Appointment or referral → eligibility and authorisation → service delivery → documentation and coding → charge capture → claim → adjudication → payment or denial → reconciliation and follow-up

Revenue-cycle management is not simply a finance department function. Clinical documentation, scheduling, registration, coding, utilisation review, contracting and patient communication all affect the outcome. The objective is accurate and timely payment for legitimate services, not the maximisation of charges irrespective of patient need.

2.2 Billing and coding integrity

Billing systems aggregate billable services, supplies, room charges, professional services and adjustments. Coding systems translate clinical documentation into standard diagnosis and procedure classifications. The exact coding standards vary by jurisdiction and payer, but the management principles are general:

• codes must be supported by documentation;
• services must be medically and contractually appropriate;
• duplicate or unbundled charges must be prevented;
• late entries and corrections must be auditable;
• coding changes must not be used to conceal poor documentation or inflate reimbursement.

Charge capture may be automated through interfaces from laboratory, pharmacy, imaging, operating-room and electronic medication systems. Interfaces reduce manual entry but create dependence on accurate configuration. A missing procedure code, an incorrect department mapping or a failed interface can produce systematic underbilling or erroneous claims.

2.3 Insurance and payer administration

Insurance functions include eligibility checking, benefit interpretation, referral and authorisation management, coordination of benefits, claim submission, adjudication and appeals. Payers may reimburse through fee-for-service, bundled payment, capitation, diagnosis-related groups, case rates or other contractual arrangements. Each model changes the organisation’s information requirements and financial risks.

Under a bundled arrangement, for example, the hospital must understand the cost and outcomes of an episode rather than only the charge for each encounter. Under capitation, population and risk adjustment data become especially important. Contract terms should be represented in a controlled payer master file; informal spreadsheet workarounds create inconsistent interpretations and weak auditability.

2.4 Revenue-cycle metrics

Important measures include days in accounts receivable, clean-claim rate, denial rate, net collection rate, point-of-service collection rate and cost to collect. Definitions must be explicit. For example, a denial rate may be calculated as denied claims divided by submitted claims, or denied monetary value divided by submitted monetary value. These are different measures and should not be conflated.

A general net collection rate can be represented as:

Here, adjusted contractual charges are gross charges less contractual allowances and other defined non-collectible adjustments. The measure assumes that charity care, bad debt, refunds and extraordinary items are treated consistently. A high collection rate does not prove that billing is ethical or efficient; it must be read alongside complaints, financial assistance decisions, denial patterns and access indicators.

A clean-claim rate is commonly expressed as:

The hospital must specify whether “accepted” means accepted by the clearinghouse or adjudicated without payer denial. Clearinghouse acceptance alone does not guarantee payment.

2.5 Worked application: interpreting a denial problem

An outpatient department submits 2,000 claims in a month. Of these, 1,760 are accepted without a denial on first adjudication. The initial clean-claim rate is therefore:

A review finds that 120 denials relate to missing authorisations and 80 relate to demographic or eligibility errors. The appropriate response is not merely to add billers. Management should redesign pre-service verification, create hard stops for high-risk services, improve payer-rule maintenance and monitor whether the intervention changes both the clean-claim rate and patient access. A hard stop should be used carefully: a system that prevents urgent care because a non-clinical field is incomplete creates a different risk.

3. Supply-Chain and Inventory Information Systems

Hospital supply chains cover forecasting, procurement, contracting, receiving, storage, distribution, implant tracking, recall management, expiry control and disposal. Inventory includes low-cost consumables, medicines, sterile instruments, blood products, implants and high-value equipment. Shortages can endanger care; excessive stock ties up capital and increases expiry and obsolescence.

A supply-chain system should connect clinical demand with item masters, suppliers, purchase orders, receipts, locations, lot or serial numbers and consumption. Item-master governance is foundational. The same product should not appear under multiple descriptions or units of measure, such as “syringe,” “each syringe” and “box of syringes,” without clear conversion rules.

3.1 Inventory control

A basic economic order quantity model is:

where D is annual demand in units, S is ordering cost per order, and H is annual holding cost per unit. EOQ assumes relatively stable demand, a known and constant ordering cost, a constant holding cost, instantaneous replenishment and no stockout penalty. These assumptions are often unrealistic in hospitals, particularly for critical, perishable or regulated items. EOQ is therefore a starting point, not an automatic purchasing instruction.

For items with variable demand or lead time, a reorder point may be expressed as:

The units of both terms must be the same, such as units or doses. Safety stock should reflect demand variability, lead-time variability, desired service level and the consequences of shortage. Critical supplies may justify a higher service level than non-critical stationery.

ABC analysis classifies items by annual consumption value, while criticality analysis considers the clinical consequence of shortage. Combining the two produces better governance than using financial value alone. A low-cost item may be clinically vital, and a high-cost item may be readily substitutable.

4. Human-Resource Information Systems

A human-resource information system (HRIS) supports recruitment, credentialing, rostering, attendance, payroll interfaces, training, performance management, leave, occupational health and workforce analytics. In hospitals, it must also manage professional licences, scope of practice, privileging, mandatory competencies and agency personnel.

Workforce data should be integrated with scheduling and access control but separated by role. A staffing manager may need assignment and competency information without needing confidential disciplinary or health data. Role-based access, audit trails and purpose limitation are essential.

Useful measures include vacancy rate, turnover, overtime, agency dependence, absenteeism, time to fill, training compliance and skill-mix coverage. These should be interpreted carefully. For example, low turnover may reflect a stable workforce or a failure to remove persistently unsafe practice. A workforce dashboard should connect staffing measures with patient outcomes, workload and employee well-being.

Rostering systems can identify coverage gaps and enforce rules such as rest periods, maximum hours and required qualifications. Automated rostering should not be treated as neutral: its objective function may prioritise cost over continuity, fairness or fatigue risk. Managers must review algorithmic recommendations and provide an escalation route for exceptional circumstances.

5. Asset and Facilities Management

Asset-management systems maintain the lifecycle record of equipment and facilities: acquisition, location, ownership, warranty, preventive maintenance, calibration, repair, downtime, utilisation, replacement and disposal. Assets may include imaging devices, ventilators, beds, sterilisation equipment, information technology and building systems.

A robust asset record links a unique identifier to location, responsible department, risk classification, maintenance schedule and service history. Barcode, radio-frequency identification and Internet-of-Things sensors can improve visibility, but technology does not replace governance. A device that is moved without updating its location remains invisible to the system regardless of tagging technology.

Managers should assess total cost of ownership rather than purchase price alone. This includes acquisition, installation, training, consumables, maintenance, energy, downtime, cybersecurity and disposal. Common indicators include preventive-maintenance compliance, mean time to repair, downtime, failure rate, utilisation and safety-event frequency.

The decision to replace equipment should combine condition, reliability, clinical importance, regulatory compliance, interoperability and lifecycle cost. Maximising utilisation is not always desirable for critical equipment because a contingency reserve may be necessary.

6. Patient Portals and Digital Patient Services

A patient portal provides secure access to selected information and services, such as appointment requests, results, medication lists, bills, statements, educational material, secure messaging, proxy access and telehealth. Portals can reduce telephone workload and improve convenience, but they also redistribute work to patients and caregivers.

Portal design should address:

• identity verification and strong authentication;
• accessibility for disability, language and literacy needs;
• proxy and adolescent access rules;
• release timing for sensitive results;
• message triage and response expectations;
• integration with scheduling, billing and clinical systems;
• digital inclusion for patients without devices, connectivity or confidence.

A portal is not merely a website. It is a governed service channel. If patients send urgent symptoms through a message queue that is checked only during office hours, the organisation must clearly communicate the limitation and provide safe alternatives. Automated responses should not imply clinical review when none has occurred.

Patient portals can support shared decision-making by presenting understandable information, but indiscriminate release of complex or alarming results may cause confusion. Organisations should use information design, explanatory content and clinician workflows rather than restricting access solely to avoid difficult conversations. Local law and policy govern access, consent, proxy rights and information blocking obligations.

7. Integration, Architecture and Data Governance

The systems described above are interdependent. Registration supplies identity to scheduling, ADT, billing, portals and reporting. ADT supplies encounter and location data. Clinical systems generate documentation and charges. HRIS supplies credential and staffing information. Supply-chain and asset systems support service delivery. Integration may use APIs, interface engines, health-information exchange standards or event messaging, depending on the environment.

Integration should be assessed at three levels:

1. Technical interoperability: systems can exchange messages and data.
2. Semantic interoperability: exchanged data have the same meaning, units and definitions.
3. Organisational interoperability: policies, responsibilities and workflows allow the information to be used safely.

A data-governance programme should define data owners, stewards, quality rules, retention schedules, access rights, master-data standards and escalation procedures. A useful quality framework examines accuracy, completeness, timeliness, consistency, uniqueness and validity. Data-quality dashboards should identify the responsible process, not merely report that a problem exists.

Managers should distinguish a system of record from a system of engagement and from an analytical warehouse. Replicating data into a warehouse can support analysis, but it does not make the warehouse authoritative for operational correction. Corrections should be made at the appropriate source and propagated through controlled processes.

8. Security, Ethics and Regulation

Administrative systems contain sensitive identity, financial, employment and health information. The security objectives of confidentiality, integrity and availability apply equally to a billing system and a clinical system. A ransomware attack that disables registration or scheduling can be a patient-safety event even if no clinical database is directly altered.

Core controls include least-privilege access, multi-factor authentication where appropriate, network segmentation, encryption, secure backups, patching, vulnerability management, audit logging, vendor risk assessment, phishing resistance and tested downtime procedures. Access should be reviewed when staff change roles or leave.

Ethical management requires more than legal compliance. Important issues include:

• equitable access when digital channels become the default;
• transparent financial estimates and assistance policies;
• avoidance of discriminatory payer or risk classifications;
• appropriate use of patient and workforce data;
• confidentiality in proxy accounts and shared devices;
• explainability and human oversight for automated decisions;
• non-retaliatory handling of safety and data-quality reports.

AI may assist with appointment forecasting, denial classification, demand prediction, coding support, inventory forecasting and patient-message routing. It should not silently make high-impact decisions about access, clinical urgency, employment or financial assistance. Before deployment, managers should define the intended use, training-data limitations, performance thresholds, subgroup evaluation, human review, incident reporting and model-change controls. AI-generated coding or documentation remains subject to professional verification and audit.

9. Implementation and Change Management

Administrative HIS projects fail when they are treated as software installations rather than organisational transformations. A disciplined approach includes:

1. mapping the current patient, financial and supply workflows;
2. identifying pain points, control failures and regulatory obligations;
3. defining future-state processes and measurable outcomes;
4. involving patients, clinicians, registration staff, finance, procurement, HR, IT and compliance;
5. cleansing master data before migration;
6. configuring rather than excessively customising where safe;
7. testing normal, exceptional and downtime scenarios;
8. training by role and workflow;
9. running pilot and parallel controls for high-risk functions;
10. monitoring benefits, unintended consequences and user feedback.

Implementation metrics should include adoption, data quality, processing time, denial patterns, patient experience, staff workload, safety events and financial performance. A project that meets its go-live date but increases duplicate records or portal messages without triage cannot be judged successful.

Illustrative Case: Integrated Revenue and Patient-Service Redesign

Background

Riverside Medical Centre, a fictional 350-bed hospital, experienced long registration queues, a 79% initial clean-claim rate, frequent duplicate patient records and poor visibility of outpatient appointment capacity. Patients received separate bills from the hospital and professional groups, while staff used spreadsheets to track authorisations.

Problem analysis

A process review found that registration staff could create a new record without a sufficiently strong duplicate search. Payer eligibility was checked after some services had begun. Authorisation requirements were stored in local spreadsheets and were not consistently updated. The scheduling system showed appointment times but not all equipment dependencies. Portal use was low because activation occurred only at discharge and the mobile interface was inaccessible to some patients.

Approach

The hospital established a governance group with operational, clinical, financial, patient and technical representatives. It introduced a tiered MPI work queue, standardised identity fields, pre-service eligibility checks for selected high-risk services and a controlled payer-rule master. Scheduling templates were redesigned to include room and equipment constraints. A portal was offered at registration and supported by interpreters and assisted activation. Staff received role-based training, and the hospital created downtime procedures for registration and authorisation.

Performance measures were defined before implementation: duplicate-record rate, registration waiting time, clean-claim rate, authorisation-related denials, portal activation, message response time and patient complaints. Importantly, the hospital did not make all missing fields hard stops; urgent clinical access remained possible, with retrospective completion and review.

Outcome

After six months, the centre reported fewer duplicate records, shorter average registration queues and improved first-pass claim acceptance. Portal activation increased, but message volume also rose. The organisation responded by publishing response expectations, adding nurse triage for clinical messages and redirecting emergencies to appropriate channels. The improvement programme therefore required a second cycle rather than ending at technical deployment.

Learning points

The case demonstrates that registration, scheduling, revenue cycle and patient portals are one service ecosystem. Data quality at the front end affects finance and care later. Controls must be risk-based rather than universally restrictive. Finally, a successful metric can expose a new operational burden: increased portal adoption creates value only when the organisation can respond safely.

Challenges and Limitations

First, integration increases both value and interdependence. A shared identity can improve coordination, but an incorrect identity can spread error across many systems. Second, performance indicators can create dysfunctional incentives. Pressure to reduce ALOS, increase collections or maximise utilisation may harm patient experience or safety if interpreted without context. Third, legacy systems and acquisitions often produce multiple item masters, payer rules and patient identifiers. Fourth, digital transformation may widen inequity when patients lack connectivity, language support or accessibility. Fifth, automation can obscure accountability: staff may assume that a system rule is correct because it is embedded in software.

Managers should therefore combine quantitative indicators with case review, patient feedback, staff experience, audit findings and safety surveillance. Governance should be continuous, especially after upgrades, mergers, payer changes, cyber incidents or introduction of AI.

Best-Practice Checklist

• Maintain a governed enterprise master patient index.
• Define data ownership and operational definitions for every major metric.
• Verify eligibility and authorisation before appropriate services without blocking urgent care.
• Reconcile clinical documentation, coding, charges and payments.
• Use supply criticality as well as monetary value in inventory control.
• Link HR credentials and competency data to safe scheduling.
• Maintain complete asset lifecycle and preventive-maintenance records.
• Design portals for accessibility, proxy governance and safe message triage.
• Apply least privilege, strong authentication, audit logging and tested downtime procedures.
• Evaluate AI for bias, drift, explainability and human accountability.
• Measure unintended consequences after implementation.

Chapter Summary

Administrative, financial and patient-service systems form an integrated operational backbone for hospitals. Registration and the master patient index establish trustworthy identity; scheduling and ADT coordinate access, capacity and patient location; billing, insurance and revenue-cycle systems connect documented services with legitimate payment. Supply-chain, HR and asset systems ensure that materials, people and equipment support care. Patient portals extend services while creating obligations for accessibility, privacy and safe communication.

Effective management depends on interoperability, master-data governance, clear process ownership and balanced performance measurement. Quantitative indicators such as ALOS, clean-claim rate, no-show rate and inventory control measures are useful only when definitions and assumptions are explicit. Security, ethics and regulation must be designed into the system, not added after deployment. Finally, technology and AI should augment accountable human processes rather than replace professional judgement.

Key Terms

Master patient index: A governed directory linking a person to an enterprise patient identity.

Registration: The process of creating or retrieving a patient record and collecting administrative data.

Appointment scheduling: Allocation of patient visits to time, staff, rooms and equipment.

Admission, discharge and transfer (ADT): Events recording a patient’s entry, movement and exit from care.

Average length of stay: Total inpatient days divided by the number of discharges for a defined period.

Revenue cycle: The processes from pre-service registration through claim resolution and payment.

Charge capture: Recording services, supplies and procedures for billing.

Clean claim: A claim accepted without a correctable submission or adjudication problem, according to the organisation’s definition.

Denial management: Identification, prevention, correction and appeal of rejected or denied claims.

Contractual allowance: The amount not collectible because of a payer agreement.

Supply-chain management: Planning and control of procurement, inventory, distribution and replenishment.

Economic order quantity: A model estimating an order size that balances ordering and holding costs under stated assumptions.

Safety stock: Additional inventory held to protect against demand or lead-time uncertainty.

Human-resource information system: A system supporting workforce records, credentials, scheduling and employment processes.

Asset management: Lifecycle governance of equipment, facilities and related costs.

Patient portal: A secure digital channel through which patients access information and services.

Interoperability: Ability of systems to exchange and meaningfully use information.

Data stewardship: Operational responsibility for data quality, definitions and appropriate use.

Role-based access control: Restriction of system functions and data according to authorised roles.

Master data: Shared reference data, such as patients, products, suppliers, payers and locations.

Review Questions

Short Answer Questions

1. Why is the master patient index important to both patient safety and revenue-cycle performance?
2. Distinguish a clean-claim rate from a denial rate.
3. What information should an ADT system maintain?
4. State two assumptions of the economic order quantity model.
5. Identify three governance requirements for a patient portal.

Long Answer Questions

1. Explain how registration, scheduling, ADT and billing form an integrated administrative workflow.
2. Evaluate the advantages and risks of using automated appointment overbooking in a hospital.
3. Discuss how a hospital can combine ABC inventory analysis with clinical criticality.
4. Analyse the ethical and managerial implications of AI-assisted coding and denial management.
5. Design a governance framework for integrating HR, asset-management and clinical systems.

Analytical / Application Questions

1. A hospital’s clean-claim rate falls from 91% to 82% after a payer changes authorisation rules. Develop a diagnostic plan, identify data required and recommend corrective actions.
2. A portal implementation increases patient access but doubles message volume and produces delayed responses. Analyse the causes and propose a safe operating model.
3. A hospital has frequent shortages of low-cost sterile supplies despite a high-value inventory-control programme. Explain why the programme failed and design a revised classification and replenishment approach.

Multiple Choice Questions with Answers

Question 1

Which system is primarily responsible for maintaining a hospital-wide patient identity across applications?

A. Master patient index

B. Asset-management system

C. Payroll system

D. Inventory ledger

Correct Answer: A. Master patient index

Question 2

A hospital schedules 1,500 appointments and 120 are missed without timely cancellation. What is the no-show rate?

A. 8%

B. 10%

C. 12%

D. 13%

Correct Answer: A. 8%

Question 3

Which event most directly updates a patient’s operational location?

A. Charge posting

B. ADT transfer

C. Payroll approval

D. Inventory receipt

Correct Answer: B. ADT transfer

Question 4

A clean-claim rate measures claims that are:

A. Paid at the highest possible amount

B. Accepted without a defined initial submission or adjudication problem

C. Submitted only by private insurers

D. Never reviewed by a payer

Correct Answer: B. Accepted without a defined initial submission or adjudication problem

Question 5

In the EOQ model, H represents:

A. Annual demand

B. Ordering cost per order

C. Annual holding cost per unit

D. Expected shortage quantity

Correct Answer: C. Annual holding cost per unit

Question 6

Which combination is most appropriate for hospital inventory classification?

A. Colour and package size only

B. Annual consumption value and clinical criticality

C. Supplier location and invoice format only

D. Shelf appearance and storage temperature only

Correct Answer: B. Annual consumption value and clinical criticality

Question 7

Which is an appropriate patient-portal safety control?

A. Treating every portal message as an emergency call

B. Removing authentication for convenience

C. Publishing response expectations and escalation routes

D. Allowing unrestricted proxy access

Correct Answer: C. Publishing response expectations and escalation routes

Question 8

Which principle restricts staff access according to their authorised duties?

A. Least privilege

B. Open access

C. Data duplication

D. Universal configuration

Correct Answer: A. Least privilege

Question 9

Why should average length of stay be interpreted with other indicators?

A. It has no relationship to hospital operations

B. A lower value may reflect premature discharge or case-mix differences

C. It can only be calculated for outpatient visits

D. It automatically measures patient satisfaction

Correct Answer: B. A lower value may reflect premature discharge or case-mix differences

Question 10

Which statement best describes semantic interoperability?

A. Systems use identical computer hardware

B. Systems exchange data using the same network cable

C. Exchanged data retain consistent meaning and definitions

D. All users receive identical access rights

Correct Answer: C. Exchanged data retain consistent meaning and definitions