AMIA AHIC: Applied Health Informatics Preparation Guide Study Guide

Apply it

An encounter import contains one missing patient identifier and another identifier absent from the patient table. NOT NULL rejects the missing identifier; the foreign key rejects the nonexistent patient relationship. Resolve both before loading the encounters.

Apply it

A life insurer requests an applicant's hospital records for underwriting. With no other applicable disclosure permission or requirement, obtain and validate the individual's authorization, including information covered, authorized parties, expiration, signature, and revocation provisions, before releasing records within its scope.

Apply it

A required encounter duration must be zero or greater. Define both a non-null requirement and a nonnegative check; test a missing duration separately from a negative duration during import validation before accepting the dataset.

Apply it

Two systems exchange a laboratory observation without parsing errors, but one displays a local test code as an unrelated analyte. Examine terminology identity and mapping before changing the network connection or message transport settings.

Apply it

An application receives an observation referencing a patient and an encounter. Its integration test checks that these references resolve appropriately and that the observation can be associated with the intended clinical context before display to users.

Apply it

Two vendors both support Observation, but the receiving registry requires a coded category and specified terminology. Validate the sending resource against the agreed profile and version, then resolve any missing required content before deployment.

Apply it

An interface receives the code 123 from two laboratories using different local systems. Retain each system identifier and resolve mappings separately, rather than merging observations because their short code strings happen to match in the incoming feeds.

Apply it

A warehouse proposes combining a general screening concept with a specific confirmatory test under one target code. Review the source meanings and intended analysis, preserving distinctions when the target would imply information the source never established.

Apply it

A validation review finds 80 true detected cases, 20 missed cases, and 40 false reports. Sensitivity is 80 divided by 100, or 80%; predictive value positive is 80 divided by 120, about 67%.

Apply it

A city dashboard receives complete records from large hospitals but none from community clinics. Before describing citywide patterns, assess which neighborhoods and patient groups rely on those clinics and how their absence could distort the observed distribution.

Apply it

A medication interaction rule fires repeatedly even when the documented management plan already addresses the interaction. Review the contextual information available to distinguish cases needing new action from cases already managed, then test the revised behavior with clinicians.

Apply it

An organization reviews two reminders: an immediate ordering hazard and a routine review due next month. It tests an interruptive presentation for the time-sensitive hazard and a noninterruptive task reminder for the later review, measuring appropriate responses.

Apply it

After a terminology update, a screening reminder stops identifying eligible records. The content owner compares the deployed value set and rule version with the approved specification, tests corrected cases, and monitors firing behavior after the controlled release.

Apply it

A support intervention costs 20 resource units and yields a benefit valued at 100 units when successful. With a 30% success probability, its expected net benefit is 30 minus 20, or 10 resource units.

Apply it

Two services each report a 50% reduction in a recorded event rate. One falls from 20% to 10%, the other from 2% to 1%. Compare the absolute changes before estimating workload or the number of events potentially avoided.

Apply it

A hospital comparison proposes adjusting for a complication that developed after treatment began. The measure team examines whether that complication reflects the care under evaluation before including it, while separately considering appropriate baseline patient characteristics in the model.

Apply it

A program's overall completion rate rises, but leaders suspect unequal access. Report completion by language group and location with denominators and uncertainty, then examine whether the apparent improvement occurred across groups or only in the largest group.

Apply it

A results-follow-up project measures completed follow-up as its outcome, assignment of an accountable clinician as a process measure, and staff time spent resolving duplicate messages as a balancing measure during each small test of the workflow.

Apply it

One clinician tests a revised handoff form during one shift, predicting fewer clarification calls. The team records calls and omitted information, studies the mismatch between prediction and observation, and revises the form before a larger test.

Apply it

Sixteen weekly waiting times in minutes are 12, 13, 9, 14, 8, 15, 16, 17, 18, 11, 9, 8, 7, 6, 5, 4. The middle two sorted values are 9 and 11, giving a median of 10. The final six observations are all below 10, satisfying this IHI method's shift criterion. Investigate the apparent improvement alongside intervention timing, case mix, and other process changes.

Apply it

Referral completion is slow despite rapid electronic submission. Mapping reveals that requests queue without an assigned reviewer. The team tests explicit ownership and escalation rules before investing in a faster referral-entry screen that does not address the queue.

Apply it

A referral message reaches a specialty inbox but remains unreviewed. The organization adds acceptance tracking, an accountable reviewing role, and escalation for unresolved referrals, then checks whether the patient receives a documented disposition rather than only a delivered message.

Apply it

A patient sees an amended result in a portal but receives no explanation. The follow-up workflow assigns a clinician to communicate the change, confirm the required next step, and document contact attempts through an accessible communication method.

Apply it

A laboratory interface passes its parser tests, but the clinical display associates a result with the wrong encounter. Run an integrated order-to-result scenario that checks identifiers and associations through each participating system before approving the interface for release.

Apply it

A new discharge module saves records correctly, but nurses cannot document an exception needed for home support. Acceptance testing captures that scenario and compares it with agreed requirements before leaders decide whether the module is ready for clinical use.

Apply it

An upgrade modifies order routing and authentication. The release team tests both in a representative environment, confirms support coverage and recovery steps, and verifies the deployed configuration before exposing the changed workflows to all clinical users.

Apply it

The integration dashboard shows a live connection, but results have accumulated in a rejected-message queue. Staff investigate rejection causes, assess affected patients, and verify safe reprocessing rather than treating the green connection indicator as evidence of successful delivery.

Apply it

A medication screen is evaluated only by informatics specialists. The team expands testing to intended clinical users who perform realistic ordering and correction tasks, observing where they hesitate, misinterpret information, or select an unintended item during use.

Apply it

An unauthenticated export endpoint exposes ePHI. Restrict access or isolate the endpoint, correct the configuration, and test that unauthorized requests fail. Backups address recovery but do not prevent this disclosure; logging supports detection and investigation.

Apply it

A hospital rehearses an unplanned EHR outage during an evening shift. Staff test access to downtime materials, identify patients, communicate urgent results, and document orders, then revise the plan where handoffs or supplies fail during the exercise.

Apply it

A service must return within two hours, with no more than fifteen minutes of data loss. Its recovery test restores operation in ninety minutes but uses a six-hour-old backup, meeting the restoration target while failing the data currency target.

Apply it

After an outage, a paper order and a delayed electronic order represent the same request. The recovery team reconciles their status before re-entry or queue release, confirming what was already performed and what still requires action for the patient.

Apply it

Registration finds two records with the same name and birth date but different addresses and histories. Staff follow the uncertain-match review process and verify additional identifying information instead of choosing whichever record appears first in the search results.

Apply it

A chart contains two incompatible surgical histories belonging to different people. Treat the event as a possible overlay, protect current care, and involve trained identity staff to separate and correct information rather than merging another chart into it.

Apply it

An unidentified patient receives imaging under a temporary record. After identification, staff reconcile the record and verify the imaging system, outstanding orders, specimen labels, and result routing so that ongoing care continues under the confirmed identity without losing prior work.

Apply it

An ordering clinician leaves the organization while pending results remain. The system assigns an authorized covering role, tests routing of subsequent and amended results, and tracks unresolved follow-up instead of allowing messages to accumulate in the inactive clinician's inbox.

Apply it

Three vendors demonstrate referral management using the same scenarios, including missing information, staff absence, and unresolved follow-up. Evaluators score observed performance against agreed criteria and examine interface and support requirements before selecting an option for the organization's implementation needs.

Apply it

Finance and operations define an active patient differently. A designated governance group approves purpose-specific definitions and owners, while stewards update the dictionary and reporting rules so users can understand why the resulting counts differ between the two measures.

Apply it

Two analysts produce different monthly follow-up rates. They compare definitions of eligible patients, completed follow-up, date attribution, exclusions, and measure version, then identify that one report uses order date while the other uses completion date for the denominator.

Apply it

A registry value differs from the source EHR. The analyst traces its source resource, transformation activity, responsible software agent, and relevant versions to determine whether the difference arose from source correction, mapping logic, or a later processing step.

Apply it

An import contains valid timestamps and existing encounter keys, but discharge precedes admission for several records. Quarantine those records for temporal review while separately checking row counts and required relationships before allowing the dataset into operational reporting or downstream analysis.

Apply it

A proposed research extract removes names but retains full admission dates. It does not meet Safe Harbor. Evaluate documented Expert Determination or, if appropriate, a limited data set: PHI with specified direct identifiers excluded, restricted to research, public health, or health care operations under a data use agreement. See [45 CFR 164.514](https://www.ecfr.gov/current/title-45/subtitle-A/subchapter-C/part-164/subpart-E/section-164.514).

Apply it

A patient table joins to three contact records per patient, tripling rows. To calculate a patient-level completion rate, define one outcome per eligible patient or aggregate contacts appropriately rather than counting joined rows as separate eligible people in the measure.

Apply it

An analyst selects predictive variables using all labeled records, then cross-validates the classifier. Move feature selection inside the training pipeline for each fold so held-out labels cannot influence which variables the model receives during its evaluation in that fold.

Apply it

A model will predict next month's new admissions, but its test set contains later encounters from patients already represented in training. Reconsider patient overlap and use an appropriate future evaluation period to estimate the performance needed for the deployment decision.

Apply it

A model ranks patients well, but among those assigned 20% risk, only about 5% experience the outcome in local evaluation. Investigate calibration before using the displayed probability to trigger a resource-intensive service based on a 15% risk threshold.

Apply it

A team can review forty alerts daily. Local evaluation shows one threshold produces thirty alerts and another produces two hundred. Compare missed cases, true alerts, and review burden before selecting and testing a threshold with the people responsible for responding.

Apply it

A model developed in a referral center is proposed for community clinics. Before adoption, evaluate local input availability, outcome definitions, subgroup performance, calibration, and the ability of clinic teams to act on predictions within the intended decision window.

Apply it

After a laboratory coding change, many model inputs become missing while outcome labels will take months to mature. The monitoring team investigates the input pipeline immediately and assesses whether use should be limited while later performance evidence accumulates.

Apply it

An outreach model identifies patients similarly across groups, but only patients with portal access receive follow-up. Leaders evaluate the full service pathway and add accessible contact options, recognizing that equitable model scores do not guarantee equitable access to the intervention.

Apply it

A procurement committee member has a paid consulting relationship with a finalist. The member discloses the relationship before evaluation, and the organization determines participation limits so that vendor scoring and the final recommendation remain appropriately independent of that relationship.

Apply it

Leaders propose a referral platform to reduce unresolved referrals. The business objective specifies a baseline completion rate, a defined patient population, accountable owners, and follow-up measures, linking platform implementation to the service outcome the investment is intended to improve.

Apply it

A scheduling redesign moves verification tasks from registration to nurses. Early workshops include both groups and patients, allowing the team to test responsibility, staffing, and access implications before configuration fixes the new workflow and makes later changes more costly.

Apply it

A results-management project initially covers outpatient laboratory follow-up. Its charter names the sponsor, accountable team, intended outcome, and excluded imaging workflows, giving the team a clear basis to evaluate a later request to expand the project to imaging.

Apply it

During implementation, a sponsor asks for an additional reporting feed. The project manager documents the request, assesses interface and testing dependencies, estimates schedule and cost effects, and obtains the authorized decision before updating the delivery plan and assigning the work.

Apply it

Training is scheduled before workflow configuration is finalized. The project manager identifies the dependency, assesses the risk of teaching an obsolete process, and adjusts sequencing or content approval rather than preserving a date that would undermine readiness for the actual release.

Apply it

Two systems have different license prices. The team compares a common five-year scope including migration, interface maintenance, staff backfill, training, hosting, and support, then documents which benefits depend on changes in workflow or service utilization after implementation.

Apply it

A platform's financial benefit depends heavily on staff time saved. The team varies adoption and time-savings assumptions across plausible values, finds the investment is unfavorable at modest adoption, and strengthens the implementation plan before recommending funding for the proposed system.

Apply it

A new referral system gives schedulers, clinicians, and supervisors different responsibilities. Training uses role-specific cases and cross-role handoffs, then checks whether each group can complete ordinary and exception workflows in the configured environment before independent use of the system.

Apply it

Staff demonstrate referral completion in training but lack that function in production. Confirm the duty is authorized, approve the specific role permission, and verify task completion. Preserve restrictions on unrelated records and administrative functions, and remove obsolete permissions after reassignment.