4.2 Administrative and Financial Applications
Key Takeaways
- ADT and registration are the identity and location spine: master patient index person, encounter, patient class, and current bed or department for every downstream clinical system.
- MPI duplicates and overlays are administrative failures with clinical harm; identity integrity is a source-system process, not a warehouse cleanup.
- HIM coding translates authenticated documentation into ICD-10-CM/PCS and CPT/HCPCS; the claim is an administrative view and is not a license to invent a diagnosis.
- Revenue-cycle systems own charges, claims, remittances, and denials; they consume clinical evidence and do not replace the EHR, CPOE, or BCMA.
- Cost accounting estimates internal resource use; charges are charge-description-master list prices and payments are remittances—the three are not interchangeable.
4.2 Administrative and Financial Applications
Quick Answer: Administrative and financial applications manage identity, location, scheduling, coding, claims, and cost. ADT and registration are the identity and location spine. Revenue-cycle and HIM systems consume clinical documentation; they do not replace the EHR as the clinical record, and the charge master is not a cost-accounting system.
Why this class matters
Clinical applications fail in public; administrative applications fail in the master patient index, the wrong bed, and the denial work queue. Domain I B.1 expects a CPHIMS professional to know that ADT is not a clerical afterthought. Every clinical and ancillary system that needs a patient identifier, an encounter number, or a current location is a customer of registration and ADT.
ADT and registration: the identity and location spine
Registration creates or selects the person in the master patient index (MPI) and opens an encounter (inpatient, emergency, observation, ambulatory). ADT—admit, discharge, transfer—then publishes changes in patient class, attending, service, and location.
Treat ADT as the identity and location spine:
- Who is this person (enterprise MPI, medical record number)?
- Which visit is this (account or encounter identifier)?
- Where are they right now (unit, room, bed, or outpatient department)?
- What is their patient class (inpatient, emergency, observation, outpatient)?
Downstream subscribers typically include the EHR census, pharmacy, LIS, RIS, dietary, transport, nurse call, and often the portal’s admission view. Classic integration uses HL7 ADT event messages (admit, transfer, discharge, cancel, merge). The exam cares about the role, not a vendor’s interface engine and not memorizing every event code.
Patient class is not trivia. Observation versus inpatient changes order sets, status-board icons, utilization review, and billing. A class that never updates after a conversion is simultaneously a clinical-census defect and a revenue-cycle defect.
MPI duplicates (“two charts, one person”) split allergies, results, and histories. Overlays (“one chart, two people”) mix identities and can harm the wrong patient. Both are administrative-application failures with clinical consequences. CPHIMS-level response is an identity-integrity process—probabilistic or deterministic matching, a trained MPI team, and a merge/unmerge protocol—not “the nurse can just pick the first John Smith,” and not “the warehouse will sort it out tonight.”
Scheduling
Enterprise scheduling, or a constellation of departmental schedulers, allocates slots, rooms, equipment, and sometimes referrals and authorizations. Scheduling is an administrative application even when clinicians see it inside the EHR.
Design issues that show up on exams and in operations:
- Overlapping systems (central versus radiology versus infusion versus operating room)
- Referral and authorization checks before the visit
- No-show and overbook rules
- Downstream linkage so a scheduled MRI becomes a registered encounter and a CPOE or RIS order
A consumer self-scheduling app (Section 4.3) is a channel. The scheduling system of record is still the administrative application. A slot booked under the wrong MPI record is an identity event, not a digital-front-door success.
HIM, coding, and the legal record
Health information management (HIM) applications support release of information, deficiency analysis, coding, and often the organization’s definition of the legal medical record. Coding translates clinical documentation into ICD-10-CM/PCS, CPT/HCPCS, and other code sets used for billing, quality, and risk adjustment.
Hold these layers apart:
- The EHR note and problem list are clinical documentation.
- The coded claim is an administrative view of that documentation.
- Clinical documentation integrity (CDI) queries close gaps between the two; they do not invent diagnoses.
HIM also decides what is in the designated record set when counsel or a patient asks for “the chart.” That set is built from source clinical and administrative systems. It is not “whatever is on the portal” and not “whatever is in last quarter’s data mart.”
Revenue cycle and claims
The revenue cycle is the chain from scheduling and registration through charge capture, claim generation, payer adjudication, remittance, denial management, and patient billing.
Typical application pieces:
- Charge description master (CDM) and charge capture, including some clinical charge triggers
- Eligibility and benefits verification
- Claims editor and clearinghouse submission
- Contract management and expected reimbursement
- Denial and underpayment work queues
- Patient estimates and statements
Claims are administrative transactions. A claim diagnosis list is not a substitute for the EHR problem list when you design CDS. A remittance advice explains payment; it does not document that the antibiotic was given. Charge capture can be clinical-adjacent—infusion start and stop times, implant logs, emergency acuity—without turning the billing system into a medication-administration system.
Denial work often looks like an IT ticket. Separate causes:
- Eligibility and coverage (registration and payer)
- Medical-necessity or documentation (clinical record and HIM)
- Coding mismatch (HIM)
- Timely filing or technical claim edits (revenue-cycle operations)
Throwing every denial at “the EHR vendor” is an application-class error.
Cost accounting
Cost accounting estimates what it costs the organization to deliver a service—labor, supplies, overhead, and sometimes activity-based or relative-value allocations. It is an internal managerial application.
Do not confuse three numbers that finance will put on the same slide:
- Charges — list prices in the CDM
- Payment — what payers and patients actually remitted
- Cost — internal resource consumption
A service line with high charges and low cost is not the same as one with high cost and poor payment. CPHIMS items that mention cost accounting are testing this vocabulary. They are not asking you to defend a particular costing methodology or to treat the CDM as the official CMS cost report.
How administrative apps depend on clinical apps—and vice versa
| Administrative application | Owns | Depends on clinical systems for |
|---|---|---|
| ADT / registration / MPI | Identity, encounter, location, patient class | Clinical safety of every downstream feed |
| Scheduling | Slots and resources | Orderability, prep protocols, device time |
| HIM / coding | Codes, ROI, legal-record status | Complete, authenticated documentation |
| Claims / revenue cycle | Bills, remits, denials | Codes, charges, medical-necessity evidence |
| Cost accounting | Internal cost | Utilization, length of stay, supply and labor feeds |
The spine still starts at ADT. A perfect CPOE build on a duplicate MPI will look successful in a demo and fail in production. A perfect warehouse will not publish the transfer that pharmacy needed forty minutes ago.
Scenarios and exam traps
Trap: “Registration is just the front desk.” A transfer ADT that posts forty minutes late means BCMA, laboratory labels, and the emergency track board still think the patient is in the previous bed.
Trap: using claims as the clinical problem list. Risk-adjustment and quality extracts often start from coded claims, but a design that writes claim codes back over the EHR problem list corrupts CDS.
Trap: charge master as cost. Cutting a “high-cost” clinic because its charges are high is a category error.
Trap: HIM can code what nursing “meant.” Coders code the record. CDI may query. They do not silently upgrade a note.
Trap: the warehouse will reconcile the MPI. Downstream matching can detect duplicates. It does not make ADT correct at the bedside.
A patient moves from the emergency department to an inpatient bed. Forty minutes later, pharmacy still prints labels for the emergency cubicle and the nurse’s BCMA worklist shows the old location. Which application class failed to act as the identity and location spine?
A coder assigns a complication code that is not supported in the operative note, because a claims analyst says the higher-weighted DRG will otherwise be lost. What is the CPHIMS-correct relationship between HIM coding and the clinical record?
Finance asks HIT to flag “our most expensive DRGs” using the charge description master’s list prices, then to cut those services. What distinction should a CPHIMS professional introduce?