Allied Health & Imaging · Independent exam preparation
CIIP Preparation Guide: ABII IIP Certification Test Study Guide
Practise image reconciliation, interoperability, clinical safety, privacy, security, recovery, capacity planning and service decisions across ABII's ten domains.
By CertMedbry · Updated 31 October 2026
Learn to protect image identity, diagnose integration failures, evaluate modality workflows, secure imaging information and make defensible operational decisions. This guide develops 60 selected concepts across all ten ABII domains, with original scenarios, calculation practice and recall cards. The official [ABII Test Content Outline](https://www.abii.org/docs/Test-Content-Outline-2024.pdf) defines the full examination scope; this selective guide does not replace it. Domain emphasis follows the official scored-question allocations.
Try 20 free practice questionsWhat is the exam format?
Check the question types, timing and outline before planning your revision.
Are the IIP test and the CIIP credential different certification pathways?
No. ABII awards the Certified Imaging Informatics Professional designation to individuals who pass its Imaging Informatics Professional certification test. This guide prepares for that pathway. ABII sponsors the certification program; Pearson VUE provides examination delivery.
American Board of Imaging Informatics · About the IIP Certification Test
How many questions are scored, and how long is the test?
The examination contains 170 questions: 130 scored questions and 40 pilot questions. ABII allows 170 minutes for the test. Its current test page separately provides eight minutes for a tutorial, two minutes for the nondisclosure agreement and ten minutes for the concluding survey.
About the IIP Certification Test · Test Content Outline — Implementation Date March 2024
Which blueprint applies to this guide?
This guide uses ABII Test Content Outline V 2022.08.15, approved in August 2022 and implemented in March 2024. ABII's outline page still designated the March 2024 outline as current on October 30, 2026. The approval date and implementation date describe different milestones.
ABII Test Content Outline · Test Content Outline — Implementation Date March 2024
How are the ten domains weighted?
Of 130 scored questions, Procurement has 5; Project Management 7; Operations 16; Communications 7; Training and Education 5; Image Management 23; Information Technology 16; Systems Management 20; Clinical Engineering 13; and Medical Imaging Informatics 18. These are scored-question allocations, not allocations of the 40 pilot questions. Study emphasis should reflect both these allocations and individual weaknesses.
How is the test delivered, and is it adaptive?
ABII describes delivery at Pearson VUE professional centers or at home with a remote proctor, subject to eligibility and location restrictions. The cited issuer pages do not establish an adaptive testing algorithm. Pearson VUE personnel may call the appointment an ARRT test because ARRT contracts with Pearson VUE on ABII's behalf; that scheduling terminology does not change the certification pathway.
What item styles do these practice questions represent?
These are 20 independent, four-option, single-best-answer learning questions. ABII links sample questions described as similar in format to examination questions, but the cited issuer information does not establish a complete item-style inventory. This practice set does not simulate adaptive delivery or predict a passing result.
What fees are currently stated by ABII?
As of October 30, 2026, ABII's test page lists a $500 registration fee and a $250 retake fee. It allows three attempts in 12 months. These administrative details may change; use ABII's current registration information when arranging an examination.
Which technical versions and publication statuses matter in this guide?
FHIR examples explicitly use R5, with labeled R4 comparisons where relevant. The patient-administration message example uses HL7 v2.5.1. IHE Import Reconciliation Workflow, IRWF.b Revision 1.2, is treated as a Trial Implementation supplement. DICOM references use its current online standard. A standard's capabilities must still be checked against each product's implemented capabilities and tested workflow.
HL7 FHIR R5 — ImagingStudy · HL7 FHIR R5 — DiagnosticReport · IHE Radiology Domain · IHE Import Reconciliation Workflow (IRWF.b) — Revision 1.2, Trial Implementation · DICOM PS3.2 — Conformance Statement Remarks
ABII names the examination the Imaging Informatics Professional (IIP) certification test; passing earns the Certified Imaging Informatics Professional (CIIP) designation. This is one professional certification pathway. These independent educational materials are not official ABII questions. Technical explanations distinguish DICOM, IHE and FHIR responsibilities, including version and publication-status boundaries.
Outline used: ABII Test Content Outline V 2022.08.15; approved August 2022; implemented March 2024; confirmed as the current linked outline on 2026-10-13. The workbook label Certified Imaging Informatics Professional (CIIP) names the credential awarded after passing ABII's Imaging Informatics Professional (IIP) certification test. These names map to the same certification pathway; the assigned slug is preserved.
60 key concepts: understand, apply and avoid the traps
Work through the questions by exam domain. Explain the answer in your own words, try the example, then check the common pitfall.
Procurement5/130 scored questions
1.How does a needs assessment become a testable procurement requirement?
A needs assessment connects a current workflow problem to a measurable capability. Describe the affected users, transaction volume, operating conditions and consequence of failure before selecting a product feature. A useful requirement states what must work and how acceptance will be demonstrated. Separate mandatory patient identity and availability requirements from preferences. The discriminating cue is traceability: a proposed capability should address an observed need and have an observable acceptance result.
Apply it
A department reports slow access to prior examinations. Interview readers, measure retrieval delays and identify peak demand. Specify an agreed retrieval target under a defined concurrent workload, then require a demonstration using representative studies.
Common pitfall: A vendor's feature list can sound comprehensive while leaving the actual workflow problem unmeasured. Product labels alone do not define successful acceptance.
2.What belongs in a comparable total cost of ownership estimate?
Total cost of ownership compares solutions over the same planning horizon and workload assumptions. Include acquisition, implementation, interfaces, migration, infrastructure, training, support, upgrades and eventual transition costs. Identify recurring versus one-time charges and document volume-dependent pricing. A lower purchase price can coexist with higher ownership cost. The useful decision is whether each proposal meets the same requirements at an understood lifecycle cost, rather than which initial invoice is smallest.
Apply it
Two archives each meet the acceptance criteria. Over five years, one costs $200,000 plus $60,000 annually; the other costs $300,000 plus $25,000 annually. Before additional costs, their totals are $500,000 and $425,000.
Common pitfall: Comparing different contract periods or excluding mandatory interface charges creates a false bargain. An ownership estimate also needs explicit assumptions about growth and support.
Project Management7/130 scored questions
3.How should a project handle a requested scope change?
A scope baseline defines approved deliverables and acceptance criteria. A requested change should be recorded, evaluated for schedule, cost, dependencies and operational risk, and decided by the designated authority. Approval updates the baseline and related plans; rejection preserves the agreed scope. The key distinction is between correcting work that fails an existing requirement and adding a new requirement. Both need visibility, but they have different implications for commitments and resources.
Apply it
During archive deployment, a service requests a new specialty viewer. Compare it with the approved requirements, estimate integration and training work, and present the impact before changing the committed launch date or assigning implementation resources.
Common pitfall: An apparently small interface addition can introduce testing, licensing and support obligations. Informal agreement does not establish an updated project baseline or acceptance criteria.
4.Why do dependencies matter more than task duration alone?
A project schedule represents both task effort and prerequisite relationships. The critical path is the longest dependent sequence determining the earliest possible completion under the stated assumptions. Delaying a task on that path delays completion unless the plan changes. A long task with available float may be less urgent than a short prerequisite with none. Review dependencies when resources, delivery dates or acceptance activities change, rather than prioritizing work solely by its visible size.
Apply it
A viewer installation takes two days but cannot start until network access is approved. That approval gates every remaining acceptance task. Escalating the approval dependency may protect the launch date more effectively than accelerating unrelated documentation.
Common pitfall: Starting many tasks simultaneously does not necessarily shorten delivery. Missing prerequisites and shared resource limits can make an apparently parallel schedule impossible to execute.
5.How does a useful risk register guide project action?
A risk is an uncertain event that could affect objectives; an issue has already occurred. A useful risk entry identifies the event, likely consequence, probability or likelihood assessment, impact, owner, mitigation and trigger for contingency action. Ranking supports proportionate attention rather than implying precise prediction. A mitigation reduces likelihood or impact before the event; a contingency describes what to do if the trigger occurs. Ownership makes follow-through accountable.
Apply it
A migration depends on an aging export server. Record failure during bulk export as a risk, assign an owner to verify recoverability, and define the condition that would trigger alternate export arrangements before the final cutover.
Common pitfall: Listing 'vendor risk' without an event, owner or response does little to change outcomes. A problem already blocking export belongs in issue management.
Operations16/130 scored questions
6.What makes an operational KPI interpretable?
A key performance indicator needs a defined numerator, denominator, measurement interval and data source. Specify exclusions and the event that starts and stops the clock. Rates make comparisons more meaningful when workload changes, while raw counts describe absolute burden. A useful KPI connects to a service objective and an accountable response. Without stable definitions, an apparent improvement may reflect changed counting rules or case mix rather than better performance.
Apply it
One month has 20 failed transfers among 10,000 attempts; the next has 25 among 20,000. Failures increased in count, but the failure rate fell from 0.20% to 0.125%, prompting investigation of both burden and reliability.
Common pitfall: A declining error count can conceal worsening reliability if workload falls faster. Compare matching populations and intervals before concluding that a service has improved.
7.Why can a mean response time conceal a service problem?
A mean summarizes total elapsed time divided by observations, but it can hide a slow subgroup or a long tail. Percentiles describe the time within which a specified proportion of observations finish. Evaluate them alongside failure rates, workload and workflow segments. A low average with a poor upper percentile suggests that many users receive acceptable service while a smaller group experiences substantial delay. The next decision is where that slow group occurs.
Apply it
An archive reports a two-second mean retrieval time, yet clinicians describe repeated delays. Separate recent from older studies and inspect the 95th percentile. A slow older-study subgroup may reveal an archive-tier problem hidden by frequent cache hits.
Common pitfall: A percentile does not identify the cause of delay. Changing case mix, workload and failed requests can alter interpretation unless measurement definitions remain consistent.
8.How does change control reduce operational disruption?
Change control makes a planned alteration assessable before it reaches production. Define the reason, affected services, dependencies, validation evidence, implementation owner, timing and rollback criteria. Approval should reflect the change's likely impact, including clinical workflow effects. After implementation, verify the intended outcome and monitor for unexpected effects. The discriminating cue is reversibility with evidence: a technically successful installation is insufficient if users cannot complete the required workflow afterward.
Apply it
An interface update changes order handling. Test representative orders and corrections, identify downstream systems, schedule the change with service owners, and establish rollback triggers based on message failures and missing worklist entries after implementation.
Common pitfall: A maintenance window does not itself make a change safe. A rollback plan that has never been checked may fail when the service needs it.
9.Which service agreement terms make availability commitments actionable?
An actionable service agreement defines the covered service, availability calculation, support hours, severity criteria, response expectations, restoration targets and escalation route. Clarify planned maintenance exclusions and the evidence used to establish downtime. Response time means acknowledgement or engagement; restoration means usable service has returned. These are different commitments. A useful agreement aligns vendor responsibilities with local dependencies so an outage does not become an unresolved dispute over who owns the failing component.
Apply it
A vendor promises a 30-minute response but gives no restoration target. Before signing, distinguish acknowledgement from recovery, define severity for unavailable image viewing, and identify who coordinates network, archive and viewer investigations during an outage.
Common pitfall: A rapid support callback does not establish rapid service restoration. Availability percentages are also misleading when exclusions and the measurement period remain undefined.
10.How do incident management and problem management differ?
Incident management restores an interrupted or degraded service and limits current impact. Problem management investigates the underlying cause of one or more incidents and reduces recurrence. A workaround may restore service before the cause is known, so successful incident closure does not prove permanent correction. Record symptoms, timing, affected components and actions in a way that supports later analysis. The decision depends on whether the immediate objective is restoration or prevention.
Apply it
Restarting a gateway clears a transfer queue, but the same failure returns nightly. Restore the queue through the approved procedure, preserve relevant evidence, and open a problem investigation into the recurring trigger rather than treating each restart as resolution.
Common pitfall: Calling a workaround a root-cause correction discourages further investigation. Conversely, exhaustive analysis should not unnecessarily delay an available, controlled route to restoring service.
11.What should an imaging downtime workflow preserve?
A downtime workflow preserves necessary service while maintaining patient identity, order traceability and a controlled path back to normal operation. Define how users recognize the outage, obtain authorized access, record temporary activity and reconcile records afterward. Assign ownership for both activation and recovery. Notifications should identify the affected function, practical impact, approved workaround, contact and next update time; announce restoration after verification. The workflow must address the entire interruption, including its backlog.
Apply it
During a scheduling outage, staff use an approved temporary identification process. On recovery, a designated team reconciles each temporary examination to its verified patient and order, checks for duplicates, and records completion before closing the downtime event.
Common pitfall: A paper fallback can maintain activity while creating identity ambiguity. Temporary identifiers need controlled reconciliation rather than informal replacement by whichever user notices first.
Test Content Outline — Implementation Date March 2024 · NIST CSRC — Contingency Planning
12.How should a retention policy guide image deletion?
Retention decisions apply the organization's approved requirements to identifiable records, relevant dates and exceptions. The policy must account for applicable legal, contractual and operational obligations rather than assume one universal period for every study. Deletion should be authorized, auditable and suspended when a relevant hold applies. Distinguish removal from a fast access tier from destruction of the retained record. A storage pressure alert is a capacity issue, not permission to shorten retention.
Apply it
An archive reaches its capacity threshold. Before deleting older studies, confirm the governing retention rule, relevant holds and whether the proposal merely moves data to another tier. Use a reviewed lifecycle action with documented authorization and verification.
Common pitfall: Study age alone cannot establish eligibility for destruction. A migrated or cached copy also does not automatically satisfy the approved record retention requirement.
13.How can a small improvement cycle establish whether a workflow changed?
A practical improvement cycle defines a problem, measures a baseline, tests a specific change and examines results before broader adoption. State the expected mechanism and use comparable measurements before and after the intervention. Include a balancing measure to detect unintended effects, such as extra staff effort or downstream delays. Improvement is more convincing when the targeted failure decreases without simply moving it elsewhere. A favorable anecdote is useful feedback but cannot establish the overall effect.
Apply it
A team introduces a worklist verification step to reduce demographic corrections. Compare corrections per 1,000 examinations before and after the trial, while also measuring acquisition delay to detect whether the added step creates an unacceptable operational burden.
Common pitfall: Changing several processes simultaneously makes attribution difficult. A lower correction count is inconclusive if examination volume, case mix or reporting practices also changed substantially.
Communications7/130 scored questions
14.How does SBAR turn an outage report into an actionable message?
SBAR organizes communication as Situation, Background, Assessment and Recommendation or Request. State the immediate problem, relevant context, your assessment and the action needed. The structure helps recipients distinguish observations from interpretation and understand the requested decision. For an imaging outage, include affected services and the current workflow consequence rather than only technical symptoms. A concise recommendation identifies what the recipient should do next, including when a response is needed.
Apply it
An on-call analyst reports unavailable prior images, notes the archive upgrade earlier that evening, describes failures confined to older studies, and requests activation of the agreed alternate retrieval workflow while the storage team investigates the affected archive tier.
Common pitfall: Sending background logs without a clear situation or request leaves the recipient to infer urgency. SBAR structures communication but does not replace verified technical evidence.
15.How should clinical terminology distinguish the examination, its indication and its findings?
The requested procedure describes the examination sought; the performed procedure describes what actually occurred. Modality identifies the imaging method, body site identifies the anatomy and laterality identifies the relevant side. The indication explains why imaging was requested, while a finding or impression describes what the examination showed or how it was interpreted. These meanings belong in different fields. FHIR R5 ImagingStudy separates modality, procedure, reason, bodySite and laterality, while DiagnosticReport carries findings and interpretation.
Apply it
An order requests left-knee MRI for pain. 'MRI' identifies modality, 'left knee' supplies anatomy and side, and 'pain' is the indication. A subsequent reported abnormality is a finding. If the received series says right knee, investigate the discrepancy rather than treating the indication as proof of the imaged side.
Common pitfall: An indication is not a confirmed diagnosis, and an order description does not establish what was acquired. Resolve conflicting procedure or laterality information with the responsible clinical team.
ImagingStudy - FHIR v5.0.0 · DiagnosticReport - FHIR v5.0.0 · Test Content Outline — Implementation Date March 2024
16.How do report codes, finding codes and record identifiers differ?
A clinical code represents a concept within a named coding system; a record identifier distinguishes a particular record or object. In FHIR R5 DiagnosticReport, code names the diagnostic report and has a preferred LOINC binding, while conclusionCode represents the clinical conclusion and has an example SNOMED CT Clinical Findings binding. These bindings have different strengths and purposes. A local procedure code also needs its coding-system context and an explicitly reviewed mapping; matching display text does not establish semantic equivalence.
Apply it
A partner needs to distinguish the kind of radiology report from its clinical conclusion. Map the report name to DiagnosticReport.code and the coded conclusion to conclusionCode. Keep the accession and Study Instance UID as identifiers, and verify any local-to-standard code mapping against the intended procedure and meaning.
Common pitfall: Placing an accession number in a clinical-code field confuses identity with meaning. A preferred or example terminology binding should not be described as a universal requirement to use that coding system.
DiagnosticReport - FHIR v5.0.0 · ImagingStudy - FHIR v5.0.0 · Test Content Outline — Implementation Date March 2024
Training and Education5/130 scored questions
17.How should a training objective describe competent performance?
A training objective states an observable task, the conditions under which it is performed and the criterion for acceptable performance. Begin with a needs assessment: determine whether the gap concerns knowledge, skill, workflow design or system access. Training can address a skill gap but cannot repair a missing permission or defective interface. Match objectives to each role's actual responsibilities. A measurable objective makes both lesson design and assessment more precise than a broad aim to understand the system.
Apply it
Following import errors, require designated staff to reconcile a simulated external study to the correct local patient using the approved workflow, resolve an identity conflict and preserve valid, internally consistent identifiers before the examination becomes available for use.
Common pitfall: An objective such as 'know PACS' gives no observable success criterion. Repeated education will not correct a workflow failure caused by unavailable permissions or broken software.
18.Which assessment demonstrates that training transferred into practice?
Assessment should match the intended performance. A knowledge quiz checks recognition or explanation; an observed workflow task checks execution under specified conditions. Attendance and satisfaction measure participation and reaction, not competence. Use representative cases, predefined criteria and feedback tied to observed errors. Follow-up operational measures can show whether learning persists in practice, although other workflow changes may also affect those measures. Choose evidence that directly tests the objective rather than the easiest metric to collect.
Apply it
After downtime training, staff complete a simulated examination from temporary registration through recovery reconciliation. An assessor checks identity handling and documentation against predefined criteria, then schedules targeted practice for steps that were missed during the exercise.
Common pitfall: A favorable course survey cannot establish that learners can execute a critical workflow. A written quiz alone may miss errors in navigation, sequencing or coordination.
Image Management23/130 scored questions
19.Why must patient identifiers be interpreted with their assigning authority?
A patient identifier is meaningful within the namespace of its assigning organization or authority. The same identifier value can refer to different people at different institutions, while one person can hold several identifiers. Matching therefore requires appropriate identifier context and corroborating identity information. A name match alone is insufficient. The key decision is whether the external identity has been reliably linked to the correct local patient before imported images enter a local clinical workflow.
Apply it
Two hospitals send studies labeled with patient identifier 45678. Import staff compare assigning authorities and verified demographics rather than merging on the numeric value. Each external identity is linked to the appropriate local record through the approved reconciliation process.
Common pitfall: Treating an identifier as globally unique can place another person's images in a chart. Similar names or matching birth dates do not independently resolve every conflict.
IHE Import Reconciliation Workflow (IRWF.b) — Revision 1.2, Trial Implementation · DICOM PS3.4 — K.6 SOP Class Definitions
20.How do study, series and instance identifiers organize imaging objects?
DICOM imaging organization distinguishes a study, its series and individual SOP instances. Study and series UIDs express grouping, while a SOP Instance UID identifies an individual object. Human-readable labels, descriptions and accession numbers serve different purposes and should not replace these identifiers. This hierarchy supports retrieval, reconciliation and validation. The discriminating cue is the level of the question: patient association, study grouping, series grouping and object identity are related but separate checks.
Apply it
A migration report shows matching study totals but missing content. Compare the series and SOP instances within sampled studies. Matching accession numbers establish neither identical object membership nor successful transfer of every required instance to the new archive.
Common pitfall: Equal study counts can conceal missing series or instances. Replacing object identity checks with matching descriptions or accession numbers leaves important integrity failures undetected.
HL7 FHIR R5 — ImagingStudy · IHE Import Reconciliation Workflow (IRWF.b) — Revision 1.2, Trial Implementation
21.How does Modality Worklist reduce manual acquisition errors?
DICOM Modality Worklist lets an acquisition system query scheduled procedure information and associated patient information. Selecting the appropriate worklist entry reduces repeated manual entry and helps align acquired objects with the intended procedure. It does not independently verify the person present or guarantee that every scheduling change has reached every system. The decision remains whether the selected scheduled task matches the verified patient and examination before acquisition begins.
Apply it
A technologist finds two similar patient names on the modality worklist. The correct action is to verify the patient and intended procedure using the local identification process, then select the matching entry rather than choosing the first name displayed.
Common pitfall: Worklist availability does not prove identity correctness. A stale or incorrectly selected entry can propagate consistently wrong demographics more efficiently than manual entry.
22.How should external images be reconciled to a local patient?
Import reconciliation establishes the correct local patient and procedure context for externally produced imaging information. Verify the identity link, inspect conflicting demographics and apply the defined conflict-resolution workflow before clinical availability. IHE IRWF.b preserves valid, internally consistent object UIDs during demographic reconciliation and permits correction of incorrect or inconsistent UIDs with referential integrity maintained. The objective is a trustworthy local association with traceable handling of external information.
Apply it
An outside study arrives with an unfamiliar patient identifier and a differing surname. Staff verify the local identity using approved evidence, review the discrepancy, and complete controlled reconciliation before exposing the imported examination in the local patient's imaging history.
Common pitfall: Automatically trusting either the external label or the local chart can conceal an identity conflict. Reconciliation requires evidence of the relationship between both records.
IHE Import Reconciliation Workflow (IRWF.b) — Revision 1.2, Trial Implementation
23.When should an import preserve or correct existing object identifiers?
Under IHE IRWF.b section 4.61.4.1.1.1, preserve valid, internally consistent Study, Series and SOP Instance UIDs when reconciling demographics. Changing the local patient association alone does not justify new object identities. If UIDs are incorrect or inconsistent, investigate the defect; correction or regeneration is permitted, but affected references must be updated coherently to maintain referential integrity. The decision therefore depends on UID validity and consistency as well as the purpose of the change.
Apply it
A repeated import has valid, consistent UIDs, so preserve them to support duplicate recognition. A different import contains inconsistent referenced identifiers; establish the intended relationships and apply a coordinated correction to the affected objects and references before release.
Common pitfall: Blanket regeneration disrupts continuity, while blanket preservation can perpetuate invalid relationships. Correcting one UID without updating its dependent references leaves the imported set inconsistent.
IHE Import Reconciliation Workflow (IRWF.b) — Revision 1.2, Trial Implementation
24.Why does successful storage differ from Storage Commitment?
A successful DICOM storage response confirms the outcome of a storage operation; it is not equivalent to an explicit Storage Commitment undertaking. Storage Commitment reports whether the receiving system accepts responsibility for safekeeping specified SOP instances under its documented behavior. Evaluate the result for the referenced objects, including failures, before applying a source deletion policy. The discriminating cue is an explicit commitment result tied to the instances, rather than a successful network transfer alone.
Apply it
A modality has transmitted an examination successfully and is nearing local capacity. Before deleting source copies, its workflow checks the archive's Storage Commitment result for the transmitted instances and handles any failed references through the established exception process.
Common pitfall: Successful transmission alone does not establish the same safekeeping assurance. Storage Commitment also does not promise permanent retention regardless of the receiving system's documented policies.
25.How can an archive verify examination completeness?
Completeness requires comparison against an expected set, not simply confirmation that a study record exists. Define the expected series and SOP instances using the relevant workflow evidence, then identify missing, failed or unexpected objects. Counts are useful but cannot establish identity by themselves: equal counts may contain different objects. Combine identifier-level comparison with retrieval and usability checks appropriate to the workflow. The decision is whether the intended examination content is available, not whether its study label appears.
Apply it
A receiving archive lists an imported examination with 600 instances, matching the sender's total. An identifier comparison reveals five missing objects and five unintended objects. The team resolves the mismatch before declaring the examination complete and ready for routine use.
Common pitfall: Matching totals can conceal substitution, duplication or incorrect grouping. A visible thumbnail or study entry proves only that some content reached the receiving application.
Test Content Outline — Implementation Date March 2024 · HL7 FHIR R5 — ImagingStudy
26.How should archive tiers balance access and retention?
Archive tiers place content on resources with different cost, performance and availability characteristics. A fast cache can improve common retrievals while a slower tier retains less frequently accessed studies. Moving content between tiers changes access behavior, not necessarily its retention status. Define expected retrieval performance and test cache misses, recalls and tier failures. A useful tiering decision accounts for actual clinical access patterns and recovery requirements rather than assuming older examinations are never needed promptly.
Apply it
Most current studies open quickly, but older priors require a delayed recall. Measure access patterns, test uncached retrievals and determine whether targeted prefetching or a larger fast tier would better support scheduled examinations requiring those prior studies.
Common pitfall: A cache hit demonstration can conceal poor archive retrieval performance. Removing data from the fast tier must not be confused with authorized destruction of the retained record.
Test Content Outline — Implementation Date March 2024 · NIST CSRC — Contingency Planning
27.What does metadata de-identification need to address?
DICOM confidentiality profiles specify handling of identifying attributes rather than treating de-identification as deletion of a few obvious fields. Relevant information may occur in sequences, descriptions, private attributes and referenced objects. Select the appropriate profile and options for the intended use, then validate the result. Removing names alone does not establish confidentiality. The key decision is how to remove or transform identifiers while preserving the information and relationships required for the approved secondary use.
Apply it
A research export removes patient names and identifiers but retains free-text descriptions and private attributes. Review the selected confidentiality profile, examine those additional locations and validate the resulting objects before releasing the dataset to the authorized research environment.
Common pitfall: A blank patient name is an incomplete confidentiality test. Unexamined nested, private or free-text attributes may retain identifying information after the most visible fields are cleared.
28.Why must research exports inspect pixel content?
Identifying text can be embedded in image pixels, independently of metadata attributes. A metadata confidentiality process therefore cannot guarantee that the visible image is free of identifiers. DICOM confidentiality options distinguish pixel cleaning from attribute handling. Apply a suitable process for the image types involved and validate its effectiveness, including whether image modification compromises intended use. The discriminating cue is information rendered into the image itself, which cannot be removed by changing only header fields.
Apply it
An ultrasound research collection has clean metadata, but some frames display patient names within the image. Apply an approved pixel-cleaning process, inspect representative and exception cases, and verify that the required image content remains usable before release.
Common pitfall: A dataset can pass metadata checks while visibly exposing identifiers. Automated text removal also needs validation because missed text and removal of useful content are both possible.
29.How can replacement identifiers preserve research relationships?
Consistent replacement identifiers allow related objects to remain linked after identifying values are transformed. A confidentiality process must handle repeated identifiers and references coherently across the export set. Randomly replacing each occurrence independently can break study membership, longitudinal relationships or object references. Where re-identification is authorized, protect the mapping separately under appropriate access control. The decision is which relationships the approved research use requires and how to preserve them without exposing the original identity.
Apply it
A longitudinal project needs two examinations from each participant linked together. Use a controlled, consistent participant replacement across the authorized export and update relevant references coherently, while restricting the original-to-replacement mapping to the designated authorized custodians.
Common pitfall: Uncoordinated random replacements can make a confidential dataset scientifically unusable. A replacement code also remains sensitive when its mapping to an identifiable person is accessible.
Information Technology16/130 scored questions
30.How should storage calculations distinguish payload from provisioned capacity?
Start with expected data production using explicit units, then apply the stated retention, growth and copy assumptions. Raw image payload is not automatically equal to required provisioned capacity: redundancy, metadata, working space and operational reserve may add requirements. Keep decimal and binary units consistent and avoid assuming compression savings without evidence. The discriminating cue is what the problem asks you to calculate. A payload estimate and an infrastructure purchase estimate answer different questions.
Apply it
A service produces 800 studies daily at 250 MB per study. Using decimal units, 365 days and no compression, annual payload is 73,000,000 MB, or 73 TB. Replication and reserve must be calculated separately from that payload.
Common pitfall: Multiplying payload by an unexplained overhead factor obscures assumptions. Mixing MB with MiB or counting a replica twice can produce a misleading capacity requirement.
31.How do bandwidth calculations establish a transfer-time lower bound?
Transfer time equals data volume divided by effective throughput when units match. Network rates commonly use bits per second, while file sizes use bytes, so convert with eight bits per byte. Nominal link speed gives an ideal lower bound; protocol overhead, contention, latency and storage performance can increase elapsed time. The important distinction is between a theoretical minimum and measured end-to-end performance. Improving the link will not resolve a bottleneck elsewhere in the path.
Apply it
A 6 GB decimal dataset contains 48 gigabits. At an effective throughput of 400 megabits per second, transfer takes 120 seconds. If measured time is much longer, investigate actual throughput, contention and sending or receiving storage performance.
Common pitfall: Dividing gigabytes directly by megabits produces an eightfold unit error. A link's advertised rate also does not establish the throughput available to one imaging transfer.
32.When does a LEFT JOIN preserve the records an audit needs?
An inner join returns matching row combinations; a left outer join also preserves rows from its left table when no right-side match exists, filling right-side fields with nulls. This makes it useful for finding orders without corresponding studies. A later filter requiring a right-side value can remove unmatched rows. Join through validated relationship keys and define the intended row grain: joining studies to multiple series produces multiple rows per study, so joined-row counts need not equal examination counts.
Apply it
An audit starts with every scheduled order and seeks those without images. Left join orders to studies using the defined relationship, then select rows whose non-nullable right-side match identifier is null. For a separate examination total, account for any one-to-many relationships before counting studies.
Common pitfall: An inner join hides the missing matches the audit seeks. Joining on patient names or counting multiplied rows can produce a plausible report that answers the wrong question.
PostgreSQL Documentation — Joins Between Tables · Test Content Outline — Implementation Date March 2024
33.How do file, block and object storage change an imaging architecture choice?
File storage exposes named files in directories; NAS commonly supplies this through SMB or NFS. Block storage exposes addressed blocks for a host to organize and is commonly delivered through a SAN. Object storage exposes data objects with identifiers and metadata through an object interface. Choose an access model the application supports, then assess performance, resilience and operating cost. Neither SAN nor object storage is automatically faster for every workload. See [IBM's storage comparison](https://www.ibm.com/think/topics/file-storage) and [NAS architecture guidance](https://www.ibm.com/think/topics/network-attached-storage).
Apply it
An archive requires an NFS directory tree, while its database requires a supported block volume. A NAS export fits the archive interface; a SAN block volume may fit the database. An object store is a candidate only if the archive supports its interface or a validated gateway supplies the required file behavior.
Common pitfall: Equal capacity does not make storage interfaces interchangeable. Buying a larger object store cannot directly satisfy an application that requires file access; presenting shared block storage also requires appropriate host and filesystem coordination.
34.How should troubleshooting separate network reachability from application success?
A network test establishes only the behavior it actually exercises. Reaching a host does not prove that the required application service is listening, that security rules permit the needed port or that the imaging association will negotiate successfully. Test progressively across the path and compare results with the actual failing workflow. A useful investigation narrows the boundary: name resolution, routing, transport connection, application negotiation and object handling can fail for different reasons.
Apply it
A modality can reach an archive host but cannot send images. Check the configured destination and application connection, then examine association negotiation and supported storage capabilities instead of concluding that successful host reachability proves the imaging service is working.
Common pitfall: A successful basic connectivity test does not validate DICOM storage. Conversely, an application failure does not by itself prove that the physical network is defective.
Test Content Outline — Implementation Date March 2024 · DICOM PS3.2 — Conformance Statement Remarks
35.Why are redundancy and backup different protections?
Redundancy maintains service or data availability when a component fails, while a backup provides a recoverable copy for defined recovery needs. Replication may rapidly propagate deletion or corruption, so multiple live copies do not automatically provide historical recoverability. Evaluate independent failure modes, recovery points and tested restoration procedures. The decision is which threat the protection addresses: hardware continuity, site loss and recovery from a damaging change are related but distinct requirements.
Apply it
An archive replicates to a second site, and an erroneous deletion reaches both copies. The recovery plan relies on a protected recoverable version and a tested restoration process rather than assuming the second live site can reverse the deletion.
Common pitfall: Two synchronized copies can share the same logical failure. Backup existence also does not prove recoverability unless the required data and restoration procedure are validated.
NIST CSRC — Contingency Planning · NIST CSRC Glossary — Recovery Point Objective
36.How do LANs, WANs, VLANs and routing affect an imaging connection?
A LAN connects devices in a limited area; a WAN connects networks across larger areas. A VLAN creates a logical Layer 2 segment within switched infrastructure. Layer 2 switching connects devices within that segment, while communication between different VLANs requires routing. The routing function may be implemented in a multilayer switch. Physical proximity alone does not establish the network path. See [Cisco's LAN explanation](https://www.cisco.com/site/us/en/learn/topics/networking/what-is-a-lan-local-area-network.html) and [VLAN configuration guidance](https://www.cisco.com/c/en/us/td/docs/routers/access/isr1100/software/configuration/guide/isr1100-sw-config/configuring_ethernet_switchports.html).
Apply it
A modality and archive plug into the same switch but occupy different VLANs. Investigate their addressing, VLAN membership and routed path rather than replacing a cable solely because they cannot communicate. For a remote archive across a WAN, measure the actual end-to-end throughput instead of using the local switch-port rate.
Common pitfall: A VLAN does not encrypt its traffic. A fast local link does not establish remote-path performance, and connecting devices to the same physical switch does not place them in the same logical network.
37.Why should infrastructure planning map shared dependencies?
An imaging service depends on more than its visible archive and viewer. Authentication, name resolution, databases, storage, network paths and power can become common failure points. Map dependencies to understand which component failures can affect several apparently separate systems. Redundant application servers do not provide independent service if both rely on one unavailable database. The useful decision is whether proposed redundancy removes the relevant shared failure or merely duplicates a component above it.
Apply it
Two viewers are deployed on separate servers, but both require the same database service. During resilience planning, the team tests database failure and provides an appropriate recovery arrangement rather than treating server duplication as complete service redundancy.
Common pitfall: Counting servers is not the same as assessing service resilience. Shared infrastructure can defeat an otherwise plausible failover design unless its behavior is included in testing.
NIST CSRC — Contingency Planning · Test Content Outline — Implementation Date March 2024
Systems Management20/130 scored questions
38.What does a recovery time objective constrain?
A recovery time objective expresses the targeted elapsed time for restoring a system or function after disruption, in relation to acceptable operational impact. Define the service boundary and the point considered restored, because server startup may precede usable imaging workflow. Select strategies capable of meeting that objective and test them under relevant conditions. RTO concerns the duration of interruption; it does not define how much recently created data may be unavailable after recovery.
Apply it
An imaging service has a two-hour RTO. A recovery exercise starts the servers in 50 minutes but restores usable image access after three hours. The service misses its objective despite the relatively fast infrastructure startup.
Common pitfall: Measuring only server boot time can understate recovery duration. An objective is a target requiring demonstrated capability, not evidence that the current recovery design can achieve it.
39.What does a recovery point objective constrain?
A recovery point objective identifies the point in time to which data must be recovered after disruption. It describes tolerable exposure to lost recent changes, rather than the time allowed to restore service. Backup frequency, replication behavior and recovery consistency influence whether the objective is achievable. A frequent copying schedule alone is insufficient if copies are incomplete or unusable. Assess the latest trustworthy recoverable point for all data needed by the service.
Apply it
A service has a 30-minute RPO, but its latest verified recoverable backup predates the failure by four hours. Rapid restoration from that backup may meet a time target while failing the required data recovery point.
Common pitfall: A short recovery duration does not compensate for excessive data loss. Copy timestamps are also insufficient if the resulting dataset cannot be restored consistently.
40.What permits a HIPAA-regulated support vendor to handle identifiable imaging information?
A vendor handling ePHI on a covered entity's behalf for system support generally functions as a business associate. The applicable business-associate agreement must establish permitted uses, disclosures and safeguards; an ordinary support contract or encrypted connection alone is insufficient. Scope the disclosure to the minimum necessary for troubleshooting. The exception for disclosures to or requests by a healthcare provider for treatment does not extend to vendor maintenance simply because the system supports care. See [HHS business-associate guidance](https://www.hhs.gov/hipaa/for-professionals/privacy/guidance/business-associates/index.html) and [minimum-necessary guidance](https://www.hhs.gov/hipaa/for-professionals/privacy/guidance/minimum-necessary-requirement/index.html).
Apply it
Before sending examinations, verify the business-associate arrangement covers the support activity. Identify the relevant cases and fields, justify any necessary identifiers, and limit the transfer accordingly. Use a validated de-identified test set when it satisfies the troubleshooting purpose, checking both metadata and pixels.
Common pitfall: A business-associate agreement does not authorize unrelated reuse or unlimited dataset access. The treatment-disclosure exception does not remove minimum-necessary scoping from this vendor-support disclosure.
Test Content Outline — Implementation Date March 2024 · DICOM PS3.15 — Attribute Confidentiality Profiles
41.How does a migration preserve more than image bytes?
An imaging migration must preserve patient association, study and series organization, valid object identity and relevant references. Define the expected inventory, destination representation, exception handling and acceptance criteria before cutover. Compare identifiers and counts, investigate mismatches, and retrieve representative examinations, including unusual content. Copying payload files alone does not establish integrity or usability. Acceptance needs both inventory reconciliation and evidence that the required destination workflows operate correctly.
Apply it
A destination receives every source file but groups some studies under incorrect patients. Treat this as an integrity failure, correct the association process, reconcile affected identifiers and repeat targeted retrieval tests before authorizing the content for routine use.
Common pitfall: Equal totals can conceal different missing and unintended objects. Testing only recent, simple examinations can overlook failures concentrated in older or unusual content.
Test Content Outline — Implementation Date March 2024 · HL7 FHIR R5 — ImagingStudy · IHE Import Reconciliation Workflow (IRWF.b) — Revision 1.2, Trial Implementation
42.How do encryption in transit and encryption at rest address different exposures?
Encryption in transit protects data while crossing a communication path; encryption at rest protects stored data against access without the required keys. Assess each separately for archives, exported files, backups and temporary storage. An encrypted network session does not establish that its downloaded file remains encrypted. Key access and recoverability are essential: users or services with valid decryption access can still expose data, and loss of required keys can make protected backups unusable. NIST SP 800-57 Part 1 Revision 5 addresses key protection, backup, archival and recovery.
Apply it
An authorized image export travels over an encrypted connection but is saved to unencrypted portable storage. Address the stored-copy exposure separately, restrict decryption access and verify that required recovery keys remain available through the approved recovery process.
Common pitfall: Encryption does not replace recipient authorization, access control or de-identification. A backup recovery exercise that omits key recovery can overstate the organization's ability to restore service.
Test Content Outline — Implementation Date March 2024 · nist.sp.800-57pt1r5.pdf
43.How do integration, regression and acceptance testing differ?
Integration testing checks interactions between components; regression testing checks that previously working behavior still works after change; acceptance testing evaluates agreed requirements for approval. One scenario can contribute to several purposes, but its objective should remain explicit. Load testing adds specified concurrency, study sizes and cache conditions to evaluate performance under demand. Use representative data, observable expected results and recorded outcomes rather than treating a successful connection as proof of every requirement.
Apply it
After an interface change, test order delivery, repeat established correction scenarios and demonstrate the agreed workflow. Test concurrent incoming examinations and uncached priors as well when peak-load performance is an acceptance requirement.
Common pitfall: A passing connection test does not establish workflow acceptance. One fast cached retrieval does not establish performance under concurrent acquisition, viewing and background activity.
Test Content Outline — Implementation Date March 2024 · DICOM PS3.2 — Conformance Statement Remarks
44.How should access controls and audit records support accountable imaging access?
Authentication establishes identity; authorization limits permitted actions. HIPAA technical safeguards include unique user identification, audit controls and protected access. Scope privileges to the task and make activity individually attributable. The HHS guidance identifies encryption and automatic logoff as addressable implementation specifications; implementation decisions require assessment and documentation rather than a claim that every organization must use one identical technology. See [HHS Technical Safeguards](https://www.hhs.gov/sites/default/files/ocr/privacy/hipaa/administrative/securityrule/techsafeguards.pdf).
Apply it
For temporary vendor maintenance, assign limited individual access, record relevant activity and terminate access afterward. These are the scenario's operational controls. Confirm that the records support identifying the actor and affected examinations.
Common pitfall: A shared administrator account obscures attribution. Logging does not itself narrow privileges; addressable safeguards require a reasoned assessment rather than automatic omission.
45.How should incident response balance containment and continuity?
When a damaging event threatens service or data, incident response should limit further impact while preserving necessary continuity through approved arrangements. Establish the affected boundary, coordinate authorized containment and document actions needed for recovery and investigation. A compromised or corrupted live copy should not automatically become the recovery source. The decision is which controlled action reduces ongoing harm without losing sight of essential workflow, trustworthy recovery data and accountable coordination across teams.
Apply it
Unexpected mass changes appear in archive records. The response team limits the affected pathway, activates the approved continuity workflow and identifies a trustworthy recovery point, rather than immediately restoring service from a synchronized copy that may contain the same changes.
Common pitfall: Restoring availability from unverified data can reproduce the incident. Uncoordinated containment can also disable critical dependencies and complicate recovery if its effects are not understood.
NIST CSRC — Contingency Planning · NIST CSRC Glossary — Recovery Point Objective
46.Which monitoring thresholds support action before service failure?
Monitoring is useful when measurements connect to defined actions and enough lead time remains to respond. For capacity, consider consumption rate and provisioning time as well as current free space. For queues, measure age and growth alongside count. Define who receives an alert, how severity changes and what response is expected. The discriminating cue is whether a threshold predicts a meaningful operational consequence, rather than simply marking an arbitrary percentage on a dashboard.
Apply it
An archive has 20 TB free and grows by 1 TB daily; adding capacity takes 30 days. Escalate now because the remaining runway is only 20 days, even though the current free-space percentage has not reached the old alarm threshold.
Common pitfall: A fixed percentage ignores growth rate and procurement lead time. Excessive alerts without owners or response criteria can make the important signal easier to overlook.
Clinical Engineering13/130 scored questions
47.How should DICOM conformance statements guide device integration?
A DICOM conformance statement describes a product's implemented services, roles, supported objects and relevant behavior. Compare the capabilities needed on both sides of the proposed connection, including transfer syntaxes and workflow assumptions. A shared DICOM label does not establish interoperability. Conformance comparison identifies plausible compatibility and test requirements; representative integration testing verifies the actual pair of products and configuration. The decisive clue is overlap in the specific required capability, not general standards branding.
Apply it
A new modality and archive both claim DICOM support. Compare their required storage SOP classes, roles and transfer syntaxes, then test actual acquisition and receipt with representative objects before accepting the integration for routine departmental use.
Common pitfall: Matching conformance claims do not eliminate testing. Optional features, implementation behavior and configuration can still prevent the intended workflow from operating correctly between products.
48.What does a DICOM Transfer Syntax determine?
A Transfer Syntax specifies how a DICOM dataset is encoded for exchange, including relevant encoding rules and, where applicable, pixel data compression. During association negotiation, compatible transfer syntax support is needed for the proposed presentation context. This is separate from whether the receiving system supports the required object or service. The discriminating cue is an encoding mismatch: a destination may understand the object type yet reject the offered representation of its data.
Apply it
An archive supports a modality's storage object type but accepts none of the transfer syntaxes the modality offers for that presentation context. Configure a mutually supported encoding and retest rather than changing patient identifiers or display calibration settings.
Common pitfall: A common SOP class does not guarantee a common encoding. Transfer syntax negotiation also does not establish patient correctness, archive retention behavior or display suitability.
49.How should modality-specific data shape integration acceptance?
Acceptance cases should reflect the actual content a modality produces and the functions users require. A CT examination with multiple reconstruction series needs checks of grouping, completeness and navigation; an ultrasound examination containing still images and a multiframe cine object needs checks of both static display and frame playback. Where measurements are required, verify their units and presentation. Confirm compatible service roles, object support and encodings before testing; a generic image transfer cannot establish all these capabilities.
Apply it
A test ultrasound study contains still images, a cine object and required measurement information. The archive receives the study, but the viewer shows only a still frame. Record a failed cine-viewing requirement and investigate object and viewer support.
Common pitfall: One visible thumbnail does not prove that every frame or required measurement is usable. A CT series count also cannot establish that the intended reconstruction content is present.
Test Content Outline — Implementation Date March 2024 · DICOM PS3.2 — Conformance Statement Remarks · ImagingStudy - FHIR v5.0.0
50.What does the Grayscale Standard Display Function standardize?
DICOM's Grayscale Standard Display Function defines a standardized relationship intended to support perceptually consistent grayscale presentation across display systems. It addresses grayscale response rather than prescribing every requirement for a diagnostic display. Calibration to the GSDF does not independently establish sufficient resolution, luminance capability or fitness for a particular clinical task. Assess ambient illumination and reflections in the actual viewing environment, including after relocation, because the environment affects perceived presentation.
Apply it
Two workstations are calibrated to the GSDF but have different hardware capabilities. One moves beside a bright window. Assess task requirements and the new viewing conditions rather than assuming shared calibration or the prior location's checks establish equivalent suitability.
Common pitfall: GSDF conformance is not a universal diagnostic certification. It cannot compensate for unsuitable hardware characteristics or an environment that prevents the intended visual information from being perceived.
51.Why must ancillary imaging workflows retain patient and procedure context?
Ancillary records, such as contrast administration documentation or dose-related information, need an explicit association with the correct patient and performed procedure. Image receipt alone does not establish that these records reached their intended destination or remained correctly linked. Trace the separate data path, including identifier mapping, timing, corrections and exception handling. Acceptance also checks patient, body site and laterality across the order, acquisition and display; a mapping discrepancy requires verification of what actually occurred before labels are corrected.
Apply it
In a test case, images reach the examination but laterality conflicts with the order and contrast documentation points to another encounter. Hold the affected workflow, verify acquired content and documentation with clinical owners, correct the mappings and retest. Clinical staff determine whether any repeat acquisition is necessary.
Common pitfall: Matching a name or nearby timestamp can attach data to the wrong examination. Relabeling merely to match an order may conceal an acquisition error; successful image transfer does not validate ancillary data.
Test Content Outline — Implementation Date March 2024 · DICOM PS3.4 — K.6 SOP Class Definitions
52.How should physical imaging hazards be recognized and controlled?
MRI avoids ionizing radiation, but its static magnetic field can turn magnetic objects into projectiles. Screen people and equipment before entry; unknown device MRI safety status is treated as MR Unsafe, and MR Conditional devices require their stated conditions. Gradient fields create acoustic and nerve-stimulation risks; radiofrequency energy can cause heating and burns. Also recognize implant malfunction, moving-table injuries, contrast reactions and sedation risks described in [FDA MRI guidance](https://www.fda.gov/radiation-emitting-products/mri-magnetic-resonance-imaging/benefits-and-risks). Ionizing-radiation work requires appropriate time, distance and shielding controls; patient transfers require suitable assistance and equipment, as explained in [OSHA radiology guidance](https://www.osha.gov/etools/hospitals/clinical-services/radiology).
Apply it
A technician proposes bringing an unverified oxygen cylinder into the MRI room. Keep it outside and obtain screened equipment through MRI staff. For a difficult patient transfer, obtain the required assistance rather than improvising a manual lift. Report damaged equipment and keep transfer routes clear.
Common pitfall: Absence of ionizing radiation does not establish MRI safety. A working interface cannot establish equipment safety, and an MR Conditional label is meaningful only when its specified conditions are satisfied.
Benefits and Risks | FDA · Test Content Outline — Implementation Date March 2024
Medical Imaging Informatics18/130 scored questions
53.How do standards, IHE actors and conformance claims define an integration workflow?
Standards define information structures and communication capabilities; IHE profiles coordinate their use for defined workflows. Actors are functional roles and transactions are their interactions; one product may implement multiple actors. Map required actors, transactions and options to products, then compare relevant DICOM services, objects and encodings in their conformance statements. This connects workflow responsibilities with implemented capabilities. Neither a shared profile name nor a general standards claim guarantees that the configured products will work together.
Apply it
An organization evaluates scheduling through acquisition and storage. Map each profile responsibility to the participating products, identify missing options, compare required DICOM capabilities and test both normal exchanges and correction scenarios. Evaluate FHIR metadata exchange separately where it is part of the architecture.
Common pitfall: Actor count is not server count. Support for one profile role does not imply support for every workflow, and documentary compatibility still requires representative integration testing.
IHE Radiology Technical Framework, Volume 1 — Revision 23.0 · DICOM PS3.2 — Conformance Statement Remarks · HL7 FHIR R5 — ImagingStudy
54.When is critical-result communication complete?
Report availability establishes that information can be accessed; it does not establish that the responsible clinician received and understood a critical result. A closed communication loop identifies the recipient, conveys the finding and urgency, obtains explicit acknowledgement and confirms understanding. Record the sender, recipient, result, contact attempts and times. Define acknowledgement deadlines and alternate recipients in the organization's escalation policy. [AHRQ's check-back guidance](https://www.ahrq.gov/teamstepps-program/curriculum/communication/tools/checkback.html) explains how receiver confirmation and sender verification close the loop.
Apply it
A local policy requires acknowledgement within ten minutes and escalation to the covering clinician if none occurs. A result enters the EHR and a notification is sent, but no clinician acknowledges it. Keep the communication task open, contact the covering clinician at the deadline, confirm the message through check-back and document the handoff.
Common pitfall: A final report, delivery receipt or interface acknowledgement does not prove clinical acknowledgement. Closing communication also does not independently prove that the subsequent clinical action has occurred; track that separately when required.
Test Content Outline — Implementation Date March 2024 · AHRQ TeamSTEPPS — Tool: SBAR
55.Why must scheduled workflow preserve identity across system boundaries?
Scheduling, acquisition, storage and reporting exchange related information but do not share one automatic guarantee of correctness. A workflow must maintain the relationship among the patient, requested procedure, scheduled task and acquired examination as information crosses systems. Modality Worklist supplies scheduled information at acquisition; integration profiles coordinate broader responsibilities. The important decision is where a mismatch first appears and which responsible workflow can correct it without creating inconsistent downstream identities or duplicate examinations.
Apply it
A corrected registration appears in the scheduling application but not at the modality. Trace the information through the defined workflow and verify the refreshed worklist before acquisition, rather than manually changing several downstream systems independently without reconciling their relationships.
Common pitfall: Correct information in one application does not establish agreement everywhere. Independent manual fixes can leave orders, images and reports with conflicting patient or procedure associations.
IHE Radiology Technical Framework, Volume 1 — Revision 23.0 · DICOM PS3.4 — K.6 SOP Class Definitions
56.What does FHIR R5 ImagingStudy represent?
FHIR R5 ImagingStudy represents DICOM study organization and metadata, including series, instances and access endpoints; it does not carry the complete pixel payload. Endpoint purpose matters: QIDO-RS queries imaging information, WADO-RS retrieves native or rendered image content, and IHE Invoke Image Display invokes a viewer. Select the endpoint matching the required operation and apply authorization. A series-level endpoint takes precedence over a study-level endpoint with the same connection type.
Apply it
A portal discovers a study and its identifiers through metadata exchange. To download its DICOM instances, use the authorized WADO-RS endpoint; to launch an integrated viewer, use the implemented viewer-invocation arrangement.
Common pitfall: A successful metadata query does not retrieve the image instances. Viewer invocation may display images without supplying the downloading client with their native content.
57.How does FHIR R5 DiagnosticReport complement ImagingStudy?
FHIR R5 DiagnosticReport represents report status, findings and interpretation. DiagnosticReport.study can reference the associated ImagingStudy; DiagnosticReport.result references atomic Observation findings. For a finalized report, status is final. The conclusion holds the concise interpretation or impression, while presentedForm carries an attachment representing the entire report as issued, such as a PDF. ImagingStudy describes the imaging study and does not replace these report responsibilities.
Apply it
For report dr7 about ImagingStudy/ct7, use status = final, study[0].reference = ImagingStudy/ct7, result[0].reference = Observation/finding7, conclusion = the impression, and presentedForm[0] = the issued report attachment. Include the other required DiagnosticReport elements.
Common pitfall: A PDF attachment alone does not provide atomic results or a structured study association. Setting ImagingStudy.status to available also does not establish that the interpretive report is final.
58.Which concrete mapping changes when a report moves between FHIR R4 and R5?
FHIR R4 associates imaging through DiagnosticReport.imagingStudy; R5 uses DiagnosticReport.study, whose permitted targets include ImagingStudy. For the same association, R4 uses imagingStudy[0].reference = ImagingStudy/ct7, while R5 uses study[0].reference = ImagingStudy/ct7. In both releases, status describes report state, result references atomic Observations, conclusion gives the interpretation and presentedForm represents the entire issued report. Compare release-specific types and constraints as well as renamed elements.
Apply it
When converting an R5 final report for an R4 partner, map its ImagingStudy reference from study to imagingStudy, retain the appropriate report status and content, and validate the complete instance against the partner's R4 requirements.
Common pitfall: Copying the R5 study element unchanged into an R4 report does not produce the defined R4 association. Successful JSON parsing cannot establish release conformance.
HL7 FHIR R5 — DiagnosticReport · DiagnosticReport - FHIR v4.0.1 · Diff - FHIR v5.0.0
59.How should FHIR R5 represent a standalone non-DICOM clinical photograph?
FHIR R5 ImagingStudy directs non-DICOM images, video and audio to DocumentReference. DocumentReference represents the photograph and relevant metadata, such as subject, body site and clinical context. Its content.attachment structure supplies the content through a URL or inline base64 data, with the appropriate contentType. For a JPEG photograph, content.attachment.contentType is image/jpeg. Media was removed in R5 in favor of DocumentReference; it belongs only in an explicitly earlier-release comparison.
Apply it
Represent a standalone wound photograph using DocumentReference with the verified patient association and relevant context. Provide its JPEG through content[0].attachment.url or attachment.data, rather than inventing DICOM Study, Series and SOP Instance UIDs.
Common pitfall: Visual content does not automatically require ImagingStudy. Using the earlier-release Media resource in an R5 exchange violates the release boundary.
HL7 FHIR R5 — ImagingStudy · DocumentReference - FHIR v5.0.0 · Diff - FHIR v5.0.0
60.How do HL7 v2.5.1 demographic updates differ from patient-record merges?
In HL7 v2.5.1, ADT A08 updates patient information, such as a name or address, when a more specific trigger does not apply. A40 signals merging records filed under two patient identifiers: PID-3 carries the surviving target and MRG-1 the prior source identifier. A merge changes record association rather than merely replacing a displayed name. The exact receiving-system effects require an agreed interface implementation. See the primary [HL7 v2.5.1 Chapter 3 specification, sections 3.3.8 and 3.3.40](https://www.hl7.eu/HL7v2x/v251/std251/ch03.html).
Apply it
Registration identifies duplicate records OLD123 and KEEP456 for the same verified patient. In the agreed A40 exchange, PID-3 identifies KEEP456 and MRG-1 identifies OLD123, including the applicable identifier context. Test that the receiving imaging system associates the prior examinations with the surviving patient; a corrected surname alone would instead call for the appropriate demographic-update workflow.
Common pitfall: Sending A08 with a new name does not express an A40 merge. Reversing PID-3 and MRG-1 reverses source and target, and successful message delivery alone does not prove correct downstream reconciliation.
What to focus on during revision
The following are CertMedbry study suggestions. Use the official outline to check the full scope of your examination.
- Use the official [ABII outline](https://www.abii.org/docs/Test-Content-Outline-2024.pdf) as the full study map; this 60-concept guide is selective. Prioritize Image Management, Systems Management and Medical Imaging Informatics without neglecting the smaller domains or outline topics beyond these lessons.
- Separate patient identity, order identifiers, study grouping and SOP instance identity. Preserve valid, internally consistent import UIDs; correct defective UIDs and their references coherently.
- Distinguish storage receipt from Storage Commitment, redundancy from recoverability, and recovery time from recovery point.
- Practise decimal storage and bandwidth calculations with explicit units, copy assumptions, effective throughput and operational reserve. Compare file, block and object access models and trace LAN, VLAN and routed WAN paths.
- Read SQL joins in terms of preserved populations, missing matches and the entity represented by each row.
- Connect procurement requirements, acceptance evidence, operational KPIs, training assessment and controlled change to observable workflow outcomes.
- Distinguish requested and performed procedures, indications and findings, clinical codes and record identifiers. Test modality-specific content, ancillary associations and laterality exceptions.
- Recognize MRI projectile, thermal, acoustic and device hazards alongside ionizing-radiation and patient-handling risks; choose controls appropriate to the actual hazard.
- Apply business-associate permitted-use limits and minimum-necessary scoping to vendor support. Evaluate access privileges, auditability, encryption in transit, stored-copy protection and key recovery.
- Keep DICOM services, IHE profiles, HL7 v2 messages and FHIR resources within their defined responsibilities. Practise A08 versus A40, critical-result acknowledgement and escalation, and explicit R4-to-R5 report mappings.
A practical preparation plan
1. Build an outline-based baseline
Mark every official domain as strong, developing or unfamiliar. Use the scored-question allocations to plan study time, then increase attention where your explanations reveal gaps. Track topics beyond this selective guide directly against the official outline.
2. Trace one examination end to end
Draw patient registration, ordering, scheduling, worklist selection, acquisition, storage, viewing and reporting. At each boundary, identify the responsible system, identifiers, relevant standard and evidence of successful completion. Add an external import, an A08 demographic update, an A40 merge and an ancillary record. Follow a critical result through acknowledgement and policy-defined escalation.
3. Work the quantitative and data questions
Calculate payload, growth runway and transfer time using written assumptions. Sketch a small orders-and-studies dataset to predict inner and left join results, including one-to-many relationships and missing matches. Compare an NFS archive, a block-backed database and an object archive, then trace their required local and remote network paths.
4. Design recovery and migration evidence
For a hypothetical archive, define RTO, RPO, required dependencies and a usable-service test. Restore representative data, verify identity and access, measure elapsed time and establish the trustworthy recovery point. Include recovery keys where encryption is used. Specify migration inventory checks, exceptions and acceptance criteria.
5. Explain each practice decision
Complete the 20 questions independently. For each option, explain why it fits or fails the scenario's decisive cue. Record the underlying misconception rather than memorizing an option position. Include vendor-support disclosure criteria, access controls and physical clinical hazards in subsequent case practice.
6. Rehearse recall and communication
Use the cards for spaced recall, then practise an SBAR outage message, a clear shift handoff and an observed training assessment. Classify a procedure, indication and finding, explain their coding and identifier roles, and rehearse a critical-result check-back. Revisit weak concepts until you can apply them to a different case.
Use your sample score as a starting point
The free set contains 20 original practice questions. It is a small learning sample, not an official examination or a validated pass prediction. Review each explanation and its source before moving to another topic.
Start the free sampleOfficial sources and updates
- American Board of Imaging Informatics
- About the IIP Certification Test
- ABII Test Content Outline
- Test Content Outline — Implementation Date March 2024
- DICOM PS3.4 — K.6 SOP Class Definitions
- DICOM PS3.4 — Storage Commitment Service Class
- DICOM PS3.15 — Attribute Confidentiality Profiles
- DICOM PS3.14 — Scope and Field of Application
- DICOM PS3.5 — Transfer Syntaxes
- DICOM PS3.2 — Conformance Statement Remarks
- IHE Radiology Domain
- IHE Radiology Technical Framework, Volume 1 — Revision 23.0
- IHE Import Reconciliation Workflow (IRWF.b) — Revision 1.2, Trial Implementation
- HL7 FHIR R5 — ImagingStudy
- HL7 FHIR R5 — DiagnosticReport
- PostgreSQL Documentation — Joins Between Tables
- NIST CSRC Glossary — Recovery Time Objective
- NIST CSRC Glossary — Recovery Point Objective
- NIST CSRC — Contingency Planning
- AHRQ TeamSTEPPS — Tool: SBAR
- ImagingStudy - FHIR v5.0.0
- DiagnosticReport - FHIR v4.0.1
- Diff - FHIR v5.0.0
- DocumentReference - FHIR v5.0.0
- get_pdf.cfm
- ImagingStudy - FHIR v5.0.0
- ImagingStudy - FHIR v5.0.0
- DiagnosticReport - FHIR v5.0.0
- DocumentReference - FHIR v5.0.0
- nist.sp.800-57pt1r5.pdf
- Benefits and Risks | FDA
Confirm current eligibility, fees, scheduling and policies directly with the examination provider. CertMedbry is independent and is not endorsed by these organisations. How we handle content and corrections.