[{"content":"","date":"19 November 2026","externalUrl":null,"permalink":"/","section":"Premier Imaging Informatics","summary":"","title":"Premier Imaging Informatics","type":"page"},{"content":"","date":"16 November 2026","externalUrl":null,"permalink":"/tags/dicom/","section":"Tags","summary":"","title":"DICOM","type":"tags"},{"content":"A technologist at a CT console pulls up the worklist, finds the patient, and starts the scan. Most of what the scanner knows about that patient and that exam got there by crossing from one standard to another. At many of the sites I\u0026rsquo;ve worked with, it left the RIS as an HL7 v2 message, was picked up by a separate worklist service, and was handed to the modality as a DICOM C-FIND response. (In IHE\u0026rsquo;s model the RIS serves the worklist itself; more on that below.) Three representations of the same order, two translations at broker sites, and a dozen fields that each have to land in exactly the right place.\nWhen it works, nobody thinks about it. When it doesn\u0026rsquo;t, the symptom is usually downstream and misleading: a study that won\u0026rsquo;t reconcile, a prior that doesn\u0026rsquo;t prefetch, an accession number that doesn\u0026rsquo;t match the report. This post traces the crossing field by field so that when something arrives wrong at the scanner, you know which hop to look at.\nThe path # flowchart TB RIS[\"RIS / EHR\norder placed\nand scheduled\"] -- \"HL7, when a\nseparate broker\nserves the worklist\" --\u003e IE[\"Interface engine\"] IE -- \"HL7, possibly\ntransformed\" --\u003e MWL[\"Separate worklist SCP\n(a broker,\na PACS, or a VNA)\"] RIS \u003c-- \"MWL: modality sends\nC-FIND-RQ, worklist\nitems return as C-FIND-RSP\n(IHE model: the RIS\nis the worklist SCP)\" --\u003e MOD[\"Modality\"] MWL \u003c-- \"MWL: modality sends\nC-FIND-RQ, items return\nas C-FIND-RSP\" --\u003e MOD MOD -- \"C-STORE\" --\u003e PACS[\"PACS / archive\"] MOD -. \"MPPS N-CREATE /\nN-SET\" .-\u003e PPS[\"PPS Manager\n(the PACS\nor the RIS)\"] PPS -. \"status forwarded to RIS,\nimage and report managers\" .-\u003e RIS classDef sys fill:#1e293b,stroke:#64748b,color:#e2e8f0; class RIS,IE,MWL,MOD,PACS,PPS sys; The dotted lines are MPPS, Modality Performed Procedure Step: the modality reporting with N-CREATE and N-SET that an exam started, and then that it finished or was discontinued. In IHE\u0026rsquo;s model it goes to a Performed Procedure Step Manager, which can pass it on to the RIS, the image manager, and the report manager. At the sites I\u0026rsquo;ve worked with, that manager is usually the PACS, sometimes the RIS. What happens to the worklist entry next is local. In my experience, some worklists drop an entry when MPPS says completed, some when the RIS marks the exam done, some when the scheduled time has passed. Sites without a working path end up with worklists full of exams performed hours ago, and technologists who pick the wrong one.\nOrder, procedure, step # One thing gets lost when people describe the worklist as a translated order. Under the patient and the visit, DICOM\u0026rsquo;s worklist model has three levels (PS3.4, Section K.6):\nThe imaging service request, which is the order. Its identifier on the worklist is the accession number. One or more requested procedures under it, each with its own Requested Procedure ID and the Study Instance UID its images will carry. One or more scheduled procedure steps under each procedure, each with its own Scheduled Procedure Step ID, station, and start time. The worklist returns one entry per scheduled step. For a plain chest x-ray there\u0026rsquo;s one of each, so the three IDs can look interchangeable. They aren\u0026rsquo;t, and an interface that treats them as the same works until the first exam that isn\u0026rsquo;t simple.\nThe field map # Who fills each field matters as much as where it comes from. In IHE\u0026rsquo;s Scheduled Workflow, the RIS (IHE\u0026rsquo;s term is Department System Scheduler/Order Filler) isn\u0026rsquo;t a translator. It schedules the exam, generates the accession number, the requested procedure and step IDs, the Study Instance UID, the station, and the start time itself, and serves the worklist from its own database. The patient, visit and order data (identity, priority, reason for the exam, physicians, clinical alerts) come from the HL7 order; everything about scheduling is generated by the RIS (IHE RAD TF Vol 2x, Appendix B).\nWhen a separate broker serves the worklist instead, it has to get those RIS-generated values from an HL7 message the RIS sends downstream. IHE defines no feed to a separate worklist broker. The nearest message is Procedure Scheduled (RAD-4), sent the first time a study is scheduled, and Procedure Update (RAD-13) for every change after that, both from the RIS to the image manager and the report manager; in my experience, brokers are often fed a copy. It carries the IDs, the UID, the modality and the start time, but not the station AE title, which a broker has to assign itself. Where each value travels depends on the HL7 version. In the v2.3.1 form (an ORM), the accession is in OBR-18, the Requested Procedure ID in OBR-19, the step ID in OBR-20, the modality in OBR-24, and the Study Instance UID in component 1 of ZDS-1, a Z-segment IHE defines for it. In the v2.5.1 form (an OMI), the same values move to the IPC segment, in the first component of each field: IPC-1 accession, IPC-2 Requested Procedure ID, IPC-3 Study Instance UID, IPC-4 step ID, IPC-5 modality, IPC-6 protocol code (RAD TF-2, Section 4.4.4.1.2). A broker that copies a whole field puts component separators into a DICOM value. That\u0026rsquo;s the closest thing IHE gives a broker to a standard layout, and a broker configured to it is easy to reason about. Many of the order feeds I\u0026rsquo;ve seen predate it or ignore it, and the broker\u0026rsquo;s configuration decides which field it reads.\nSo the table below says who fills each attribute first, then where it travels in HL7 under IHE (v2.3.1 and v2.5.1 where they differ), then what you\u0026rsquo;ll find in the field. I\u0026rsquo;ve kept to the attributes that cause trouble. \u0026ldquo;Top\u0026rdquo; means top level of the worklist response; \u0026ldquo;SPS\u0026rdquo; means inside the Scheduled Procedure Step Sequence (0040,0100).\nDICOM worklist attribute Tag (where) Who fills it, and where it travels in HL7 What goes wrong Patient\u0026rsquo;s Name (0010,0010), top From the order: PID-5 Component order. HL7\u0026rsquo;s XPN is Family^Given^Middle^Suffix^Prefix; DICOM\u0026rsquo;s PN is Family^Given^Middle^Prefix^Suffix. The fourth and fifth components are swapped between the two standards, so an engine that copies the string through puts \u0026ldquo;JR\u0026rdquo; where DICOM expects \u0026ldquo;DR\u0026rdquo;. HL7\u0026rsquo;s degree component (XPN.6, \u0026ldquo;MD\u0026rdquo;) belongs in the DICOM suffix too, after the suffix (RAD TF-2x Appendix B, Note 10). Engines that reorder, truncate, or drop the caret separators do worse Patient ID (0010,0020), top From the order: PID-3, component 1, from the repetition whose assigning authority (PID-3.4) and identifier type (PID-3.5) mark it as the MRN PID-3 repeats: MRN, enterprise ID, insurance ID. \u0026ldquo;Take the first one\u0026rdquo; isn\u0026rsquo;t a rule; a registration change can reorder the repetitions, and every study lands under the wrong identifier Issuer of Patient ID (0010,0021), top From the order: PID-3.4.1 (namespace ID). PID-3.4.2 and 3.4.3 and PID-3.5 go into the Issuer of Patient ID Qualifiers Sequence (0010,0024) as Universal Entity ID, its Type, and Identifier Type Code (PS3.3 Table 10-18) HL7 carries the assigning authority as a structured value; DICOM splits it between Issuer of Patient ID and the Qualifiers Sequence. On the feeds I\u0026rsquo;ve seen, it\u0026rsquo;s often dropped entirely. Then the prior-matching problem begins Patient\u0026rsquo;s Birth Date (0010,0030), top From the order: PID-7 HL7 may carry a timestamp; DICOM DA wants YYYYMMDD. Engines that pass the time through produce an invalid DA, which some modalities reject Patient\u0026rsquo;s Sex (0010,0040), top From the order: PID-8 HL7 allows values DICOM doesn\u0026rsquo;t (U, A, N); DICOM\u0026rsquo;s enumerated values are M, F, O, or empty if unknown. IHE\u0026rsquo;s mapping is U to empty and A and N to O (RAD TF-2x Appendix B, Note 11). Engines without that mapping pass values the modality may reject Placer / Filler Order Number (0040,2016) / (0040,2017), top Placer: ORC-2, from the order. Filler: ORC-3, assigned by the RIS. IHE\u0026rsquo;s Note 4 (RAD TF-2x Appendix B) has each carry the number and its issuer; current DICOM puts the issuer in Order Placer / Order Filler Identifier Sequence (0040,0026) / (0040,0027) (PS3.3 C.4.12) Separate attributes from the accession in DICOM, even at sites that use the same value for both. Worth populating: they\u0026rsquo;re the link back to the order Accession Number (0008,0050), top Generated by the RIS. Under IHE: OBR-18 (Placer Field 1) in v2.3.1, IPC-1 in v2.5.1. On many EHR-native feeds I\u0026rsquo;ve seen: ORC-3 / OBR-3 (filler order number) The single most-argued field. On those feeds the accession sits in the filler order number and OBR-18 is empty. IHE itself expects IPC-1 to equal the filler order number in OBR-3 in most cases (RAD TF-2, 4.4.4.1.2.2.9); the trouble starts when OBR-18 or IPC-1 is empty and systems disagree which to read. DICOM gives it 16 characters, so a longer source number needs a mapping someone designed; silent truncation can give two orders the same accession. IHE also has the RIS fill the Issuer of Accession Number Sequence (0008,0051), which in v2.5.1 travels in IPC-1 components 2 to 4 under the Enterprise Identity Option (the v2.3.1 form has no place for it), and which matters for the same reason the issuer of patient ID does once two institutions share an archive. Which field the broker reads is configuration; if the RIS, the broker, and the PACS disagree, nothing reconciles Requested Procedure ID (0040,1001), top Generated by the RIS. Under IHE: OBR-19 (Placer Field 2) in v2.3.1, IPC-2 in v2.5.1; otherwise the broker derives one Not the procedure code: under IHE, OBR-44 carries the Requested Procedure Code, and OBR-4 components 1 to 3 keep the order\u0026rsquo;s code. This is an identifier for one requested procedure, the same in every OBR (v2.3.1) or IPC (v2.5.1) that belongs to it. Brokers that reuse the accession here are fine until one accession has two procedures Scheduled Procedure Step ID (0040,0009), SPS Generated by the RIS when it schedules. Under IHE: OBR-20 (Filler Field 1) in v2.3.1, IPC-4 in v2.5.1; otherwise generated by the broker It doesn\u0026rsquo;t exist when the order is placed, only once the exam is scheduled. The modality returns it in the MPPS, in the Scheduled Step Attributes Sequence (0040,0270); if the broker regenerates IDs on an order update, the receiver can\u0026rsquo;t match the MPPS to the scheduled step Study Instance UID (0020,000D), top Generated by the RIS. Under IHE: ZDS-1, component 1 (IHE\u0026rsquo;s Z-segment for exactly this) in v2.3.1, IPC-3 in v2.5.1; otherwise generated by the broker The UID the images will carry. If the RIS, the broker, and the modality can each mint one, you get the same exam under two UIDs and a reconciliation job that never ends. One system assigns it; everyone else copies it. That\u0026rsquo;s the scheduled case: an unscheduled exam has no worklist entry, so the modality mints the UID, and reconciliation has to attach the order to that UID rather than create another Scheduled Station AE Title (0040,0001), SPS Generated by the RIS from its scheduling of rooms and equipment; not in the order. A broker assigns it from its own station table Most modalities I\u0026rsquo;ve worked with filter on it. Wrong AE title here and the exam doesn\u0026rsquo;t appear on that scanner\u0026rsquo;s list. A room change that never reaches the worklist leaves the exam on the old scanner Scheduled Procedure Step Start Date/Time (0040,0002), (0040,0003), SPS Generated by the RIS when it schedules. Under IHE: ORC-7, fourth component (v2.3.1) or TQ1-7 (v2.5.1); OBR-36 on some feeds Timezone. HL7 timestamps may carry an offset; DICOM DA and TM don\u0026rsquo;t (only DT does, and Timezone Offset From UTC (0008,0201) is, in my experience, rarely populated on worklists). Converting to UTC isn\u0026rsquo;t wrong in itself; losing the local scheduling context is. A broker that converts to UTC and then serves the result as local time moves a 7 p.m. Central Standard Time exam to 01:00 the next day, onto tomorrow\u0026rsquo;s list. And OBR-7 is the observation date/time, not the scheduled one; engines confuse them Modality (0008,0060), SPS Determined by the RIS from the order\u0026rsquo;s content, in DICOM defined terms. Under IHE: OBR-24 (Diagnostic Service Section ID) in v2.3.1, IPC-5 in v2.5.1, already as the DICOM defined term On the non-IHE feeds I\u0026rsquo;ve seen it isn\u0026rsquo;t a direct copy; a mapping table decides that service section CT means modality CT. New procedure codes that miss the table fall through to a default or to nothing Requested Procedure Description (0032,1060), top Generated by the RIS with the requested procedure. Under IHE: OBR-44, component 5 when sent (it\u0026rsquo;s optional), with laterality from OBR-15 (v2.3.1) or OBR-46 (v2.5.1) appended. OBR-4\u0026rsquo;s text is the order\u0026rsquo;s service name, not this Free text. DICOM\u0026rsquo;s LO limits it to 64 characters, so a longer source description needs a deliberate shortening or mapping; silent truncation can drop clinically meaningful words Scheduled Protocol Code Sequence (0040,0008), SPS Generated by the RIS. Under IHE: OBR-4, components 4 through 6 in v2.3.1, IPC-6 in v2.5.1 Coded protocol for the step. A modality that supports protocol mapping can use it to preselect the acquisition protocol, but only if the codes agree on both ends. Most sites I\u0026rsquo;ve seen don\u0026rsquo;t populate it Referring Physician\u0026rsquo;s Name (0008,0090), top From the order: PV1-8 (Referring Doctor) Same component-order problem as patient name. The ordering provider (OBR-16 in IHE\u0026rsquo;s mapping; ORC-12 carries the same HL7 item) maps to a different attribute, Requesting Physician (0032,1032); sites I\u0026rsquo;ve seen that put it in both are guessing Admission ID (0038,0010), top From the visit: PV1-19 (Visit Number), falling back to PID-18 (Account Number) when PV1-19 is empty. That\u0026rsquo;s IHE\u0026rsquo;s rule (RAD TF-2x Appendix B, Note 6); the issuer goes in Issuer of Admission ID Sequence (0038,0014) Rarely needed on the worklist, frequently needed for reconciliation later; often not mapped One detail matters when you inspect a real response: not everything is at the top level. The station AE title, modality, step ID, start date and time, and protocol codes sit inside the Scheduled Procedure Step Sequence. A tool, or a person, looking for them at the top level reports them missing when they aren\u0026rsquo;t.\nThree general patterns run through that table. Names and dates are format problems: the data is right, the encoding isn\u0026rsquo;t. Identifiers and the accession are selection problems: HL7 offers several candidates, and the site has to pick one and make every system agree. The generated IDs are ownership problems: exactly one system should create each one, and every other system should copy it. Format problems show up at the scanner. The other two show up weeks later, when someone tries to match a study to a report.\nWhere the engine changes things # The interface engine in the middle is where most sites customize, and where much of the breakage lives, because the customizations are undocumented and were made by someone who left. The common ones:\nRepetition selection. Picking which PID-3 to forward. If the rule is \u0026ldquo;first one,\u0026rdquo; and a registration change reorders the repetitions, the MRN silently changes. Code translation. Mapping the RIS\u0026rsquo;s procedure codes to the broker\u0026rsquo;s, or to modality values. The table ages badly; every new procedure the RIS adds is a potential miss. Message filtering. Forwarding only NW (new order) and CA (cancel) control codes, and dropping XO (change). Then a changed order (a new time, a different scanner) never reaches the worklist, and the technologist performs the old version. IHE\u0026rsquo;s own downstream update, Procedure Update (RAD-13, to the image manager and report manager), uses XO for changes and CA or DC for cancellations; a filter that drops XO there has the same effect. (Between the order placer and the RIS, IHE changes an order by cancel and new order instead.) Field truncation and sanitization. Stripping characters the downstream system doesn\u0026rsquo;t like. Occasionally stripping the caret that separates name components. A worklist isn\u0026rsquo;t built once. Every reschedule, room change, and cancellation has to arrive too, in time for the technologist to see it.\nWhen a field arrives at the scanner wrong, compare it at each boundary: as the RIS sent it, as the engine passed it on, and as the worklist returned it. The hop where it changes is the system to look at. The engine is often that hop, but not always.\nTesting it end to end # The method that\u0026rsquo;s worked for me is a matrix rather than a checklist: order types across the rows (routine, stat, emergency with a temporary ID, outside or \u0026ldquo;foreign\u0026rdquo; order, order placed after the exam, exam moved to a different scanner after it was scheduled), modalities across the columns, and for each cell the fields that matter most for that combination. An emergency order on a trauma CT tests the temporary-patient-ID path and the later merge; a foreign order on an MR tests the issuer-of-patient-ID mapping; a routine CR tests the station AE title mapping, because in my experience CR rooms are where it\u0026rsquo;s most often wrong; a moved exam tests whether the reschedule reaches the worklist and the old scanner stops showing it.\nFor each cell:\nPlace the order in the RIS (or inject the order message at the engine, with the RIS\u0026rsquo;s blessing). Capture the HL7 as it leaves the RIS and as it leaves the engine, and diff them. Every difference is a transformation someone configured. Query the worklist SCP with the same C-FIND the modality sends: its calling AE title, its matching keys (station AE title, modality, date range, whatever it uses), and its return keys. DCMTK\u0026rsquo;s findscu -W or pynetdicom with the worklist SOP class will do it. Compare each returned attribute to the table above, including the ones inside the Scheduled Procedure Step Sequence. Perform the exam, or simulate MPPS with a tool. If the site uses MPPS, confirm the receiver recorded the start and the completion. Separately, confirm the entry leaves the worklist the way the site expects; that may or may not be MPPS\u0026rsquo;s doing. Store an image and check that the patient, accession, procedure, and study identifiers landed in the header as expected. Then check the PACS: did it file the study under the right patient and the right order? The header is what reconciliation works from; whether it worked is something you confirm in the receiving system. Step 3 is the one most sites skip. They test from the scanner, which only shows whether the exam appears, not whether every attribute behind it is correct. A worklist entry with the right name and the wrong issuer of patient ID looks perfect on the console and causes trouble for years.\nSources # IHE Radiology Technical Framework, Volume 2x, Appendix B, HL7 Order Mapping to DICOM MWL (Rev. 23.0, August 2025), for which worklist values come from the order and which the Department System Scheduler generates, and Notes 4, 6, 10 and 11 for order numbers, Admission ID, name and sex mapping: https://www.ihe.net/uploadedFiles/Documents/Radiology/IHE_RAD_TF_Vol2x.pdf. IHE Radiology Technical Framework, Volume 2 (Rev. 23.0, August 2025), Scheduled Workflow transactions (RAD-2 Placer Order Management, RAD-3 Filler Order Management, RAD-4 Procedure Scheduled, RAD-5 Query Modality Worklist, RAD-6/7 MPPS, RAD-13 Procedure Update): https://www.ihe.net/uploadedFiles/Documents/Radiology/IHE_RAD_TF_Vol2.pdf. The HL7 field positions for the generated values are from RAD-4, Section 4.4.4.1.2: the v2.3.1 form (ORM; Tables 4.4-4, 4.4-6 and 4.4-7 for ORC, OBR and ZDS) and the v2.5.1 form (OMI; Tables 4.4-12 to 4.4-16, including the IPC segment). OBR-44 for the Requested Procedure Code and Description and OBR-15/OBR-46 for laterality are in the same OBR tables. RAD-4 versus RAD-13 is in Section 4.4.4.1.1. IHE Performed Procedure Step Manager actor: https://wiki.ihe.net/index.php/Performed_Procedure_Step_Manager. DICOM PS3.4, Annex K, Basic Worklist Management Service, Section K.6 for the worklist information model and which attributes sit in the Scheduled Procedure Step Sequence: https://dicom.nema.org/medical/dicom/current/output/chtml/part04/sect_K.6.html. Annex F (Procedure Step SOP Classes), Section F.7 for MPPS, including the Scheduled Step Attributes Sequence (0040,0270): https://dicom.nema.org/medical/dicom/current/output/chtml/part04/sect_F.7.2.html. DICOM PS3.3 for the Modality Worklist attributes and the Patient, Visit, and Study modules they draw from, including Section 10.15, Issuer of Patient ID Macro, Section C.4.12, Imaging Service Request Module (placer and filler order numbers and their issuer sequences), and Section C.7.1.1, Patient Module: https://dicom.nema.org/medical/dicom/current/output/chtml/part03/sect_C.4.12.html. HL7 v2.5.1, Chapter 2A, XPN and CX data types, for name component order and the assigning authority; DICOM PS3.5, Section 6.2, PN value representation, for DICOM\u0026rsquo;s name order. HL7 v2.5.1, Chapter 4 (Order Entry) for ORM/OMI and the ORC, OBR, TQ1 and IPC segments, Chapter 3 for PID and PV1. The failure patterns and the test matrix are from my own engagements and are stated as experience. ","date":"16 November 2026","externalUrl":null,"permalink":"/posts/from-hl7-order-to-modality-worklist/","section":"Posts","summary":"","title":"From HL7 Order to Modality Worklist: Where Each Field Comes From","type":"posts"},{"content":"","date":"16 November 2026","externalUrl":null,"permalink":"/tags/hl7/","section":"Tags","summary":"","title":"HL7","type":"tags"},{"content":"","date":"16 November 2026","externalUrl":null,"permalink":"/tags/ihe/","section":"Tags","summary":"","title":"IHE","type":"tags"},{"content":"","date":"16 November 2026","externalUrl":null,"permalink":"/tags/integration/","section":"Tags","summary":"","title":"Integration","type":"tags"},{"content":"","date":"16 November 2026","externalUrl":null,"permalink":"/tags/methods/","section":"Tags","summary":"","title":"Methods","type":"tags"},{"content":"","date":"16 November 2026","externalUrl":null,"permalink":"/tags/modality-worklist/","section":"Tags","summary":"","title":"Modality Worklist","type":"tags"},{"content":"","date":"16 November 2026","externalUrl":null,"permalink":"/tags/mwl/","section":"Tags","summary":"","title":"MWL","type":"tags"},{"content":"","date":"16 November 2026","externalUrl":null,"permalink":"/posts/","section":"Posts","summary":"","title":"Posts","type":"posts"},{"content":"","date":"16 November 2026","externalUrl":null,"permalink":"/tags/ris/","section":"Tags","summary":"","title":"RIS","type":"tags"},{"content":"","date":"16 November 2026","externalUrl":null,"permalink":"/tags/","section":"Tags","summary":"","title":"Tags","type":"tags"},{"content":"","date":"14 November 2026","externalUrl":null,"permalink":"/tags/archives-revisited/","section":"Tags","summary":"","title":"Archives Revisited","type":"tags"},{"content":"","date":"14 November 2026","externalUrl":null,"permalink":"/tags/pacs/","section":"Tags","summary":"","title":"PACS","type":"tags"},{"content":"","date":"14 November 2026","externalUrl":null,"permalink":"/tags/prefetch/","section":"Tags","summary":"","title":"Prefetch","type":"tags"},{"content":"In March 2009 I wrote a short piece on prefetching for new PACS administrators. The whole argument fit in four short paragraphs: an order arrives from the RIS, the PACS pulls prior studies from the archive to local cache, and the radiologist opens the study with the right comparisons already there. Spend time with your radiologists on what \u0026ldquo;relevant\u0026rdquo; means, or lose that time at the reading station.\nI stand by the advice. I also wouldn\u0026rsquo;t write it that way now, because almost every noun in it means something different than it did. This is the first of what I expect will be several pieces revisiting the Archives with what I\u0026rsquo;ve learned since.\nWhat hasn\u0026rsquo;t changed # The purpose. A radiologist reading a chest CT needs the prior chest CT and probably the prior chest x-ray, and needs them before opening the study, not after a thirty-second wait. Report turnaround still depends on it. Hanging protocols still break without it. And the single most useful thing a PACS administrator can do about it is still a conversation with the radiologists about which priors matter for which exams. Software can apply relevance rules all day; it can\u0026rsquo;t decide what the rules should be for your radiologists.\nThe trigger, mostly. An inbound order still starts it: an HL7 v2 ORM, an OMI in newer interfaces, or, where FHIR is in play, a Subscription notification about a ServiceRequest. (ORM is HL7\u0026rsquo;s general order message, withdrawn in v2.7 but still what IHE Radiology\u0026rsquo;s HL7 v2.3.1 transactions use; OMI is the imaging order message HL7 defines for systems such as a RIS and a PACS.) Some systems also start from scheduling changes, status updates or worklist activity. Whatever the event, it carries or points to patient identity, the procedure, and sometimes a body part (an R4 Subscription notification may carry no payload, leaving the receiver to fetch the ServiceRequest), and the system uses those to decide what to look for.\nWhat changed # We still call it prefetching, but the word now covers several jobs. Sometimes it means moving DICOM objects ahead of time, the way it did in 2009. Just as often it means finding out which priors exist, deciding which ones matter, and telling a viewer where to get them. The clinical goal is the same; the work underneath it isn\u0026rsquo;t.\nThe archive stopped being a cache tier # In 2009 \u0026ldquo;prefetch\u0026rdquo; meant moving studies from slow storage (tape, optical, a nearline array) to fast storage (the PACS\u0026rsquo;s local disk) so the viewer wouldn\u0026rsquo;t stall. The archive was deep and the cache was shallow, and the whole point was crossing that gap ahead of time.\nMost of the enterprise archives I\u0026rsquo;ve worked on recently are flat: everything is on disk or object storage, and the difference between \u0026ldquo;online\u0026rdquo; and \u0026ldquo;nearline\u0026rdquo; is a few hundred milliseconds, not a tape mount. That removes most of the old storage-tier argument for prefetching. Most, not all. Fast storage isn\u0026rsquo;t the same as fast delivery: a two-thousand-image CT still has to cross the network, and a reading room two hundred miles from the data center feels every hop. And some archives I\u0026rsquo;ve seen push older studies to a cold cloud tier where a restore takes hours; for those, the 2009 logic applies unchanged.\nSo prefetching isn\u0026rsquo;t obsolete, but storage speed is no longer the main reason for it. The problem moved from storage latency to system boundaries.\nThe priors are in a different system # In 2009 the PACS and its archive were usually one product, or at least one vendor\u0026rsquo;s problem. The prefetch was a PACS asking its own archive for its own studies. In the environments I see today there\u0026rsquo;s a vendor-neutral archive holding everything, a PACS (or two, after a merger) holding a working set, a separate cardiology system, an enterprise viewer that reads from the VNA directly, and a reading worklist that may belong to none of them.\nThe prefetch now crosses products, and it\u0026rsquo;s two operations, not one. First the reading system has to find the prior: a DICOM C-FIND, or a DICOMweb search (QIDO-RS), against the VNA. Then it has to get it: C-MOVE or C-GET, or a DICOMweb retrieve (WADO-RS). Either can work while the other fails. The query comes back empty because it went out under the wrong patient ID, while the study sits in the VNA. Or the query finds the study and the retrieve fails. With C-MOVE, the archive refuses a destination AE title it doesn\u0026rsquo;t know, or can\u0026rsquo;t open the separate association back to it (a firewall, a wrong port). With any retrieve method, an AE restriction or access policy can block it. And both can succeed while the viewer still never puts the prior in front of the radiologist.\nAll of those reach me as the same sentence: \u0026ldquo;my priors aren\u0026rsquo;t there.\u0026rdquo; The first question is which step failed: finding, getting, or showing.\nPatient identity is the hard part now # The 2009 piece assumed one patient ID. After a decade of health system mergers, most of the archives I work on hold studies for the same person under several issuers of patient ID. Issuer of Patient ID (0010,0021) is the DICOM attribute that names the assigning authority behind a Patient ID, and it\u0026rsquo;s optional (Type 3), so DICOM doesn\u0026rsquo;t oblige a sender to fill it in. IHE Radiology makes it a required query key for DICOM image queries [RAD-14] only under its Enterprise Identity Option, and for every QIDO-RS Query [RAD-129]. A prefetch keyed on today\u0026rsquo;s MRN finds nothing from the hospital that was acquired in 2017 unless something, usually an EMPI or the VNA\u0026rsquo;s own patient reconciliation, maps the identifiers.\nThis is the number-one reason I see relevant priors fail in 2026, and I see it constantly in outside studies: imported from a CD or an exchange network under the outside institution\u0026rsquo;s identifiers, never reconciled to the local MRN, and then invisible to every prefetch that follows. It has nothing to do with prefetch logic. The logic is fine. The patient on the order and the patient in the archive are the same human with two identities, and nobody told the prefetch engine.\nThe reverse problem is worse. Two hospitals can each have an MRN 12345 that belongs to two different people. An archive that matches on Patient ID without the issuer can\u0026rsquo;t tell them apart, and then the failure isn\u0026rsquo;t a missing prior; it\u0026rsquo;s someone else\u0026rsquo;s.\nFixing either one doesn\u0026rsquo;t always mean rewriting headers. Some environments relabel imported studies with the local MRN. Others keep the original identifiers and maintain a cross-reference, so a query for one identity finds studies filed under the other; some also record the other identities in the header\u0026rsquo;s Other Patient IDs Sequence (0010,1002); in the IHE queries named above it is a required return key, not a matching key. IHE\u0026rsquo;s Patient Identifier Cross-referencing (PIX) profile describes the cross-reference approach. In Radiology, Import Reconciliation Workflow (IRWF) covers reconciling imported outside studies to local identifiers at import, and Patient Information Reconciliation (PIR) propagates patient merges, ID-space mergers, demographic updates and corrections, including for images acquired under a temporary or wrong identity. Knowing which approach your archive takes tells you where to look when a prior goes missing.\nRelevance got more interesting and less tractable # In 2009 relevance meant same modality, same body part, maybe a lookup table that said chest CT also wants chest x-ray. That still covers most of it.\nWhat\u0026rsquo;s new is that the body part is often wrong or missing in the header, procedure codes vary by site and by year, and the archive holds things few archives held in 2009: tomosynthesis stacks, enhanced multi-frame objects, dermatology photos, pathology slides, encapsulated PDFs of outside reports. \u0026ldquo;Relevant prior\u0026rdquo; for a breast MRI now plausibly includes a tomosynthesis study from another vendor, an ultrasound, and a scanned outside report. The lookup table needs to be a mapping layer, and the mapping layer needs to be maintained by someone who talks to the radiologists. Same advice as 2009; bigger table.\nAnd finding everything isn\u0026rsquo;t the same as finding what\u0026rsquo;s useful. A patient with twenty prior abdomen CTs doesn\u0026rsquo;t need all twenty queued for the comparison pane. The most recent one and an older baseline usually matter more than the eighteen in between, though an oncology follow-up may want the whole run. Relevance is now a question of order as well as a yes or no.\nThe viewer moved # In the products I\u0026rsquo;ve worked with, zero-footprint and server-side rendered viewers generally don\u0026rsquo;t keep a persistent diagnostic cache on the workstation. Depending on the product, they cache on a rendering tier, hold data in browser memory, or stream on demand and rely on the archive and the network being fast enough. Which brings us back to the first point. When the data is close and fast, the critical question is less \u0026ldquo;did we move the bytes\u0026rdquo; and more \u0026ldquo;does the viewer know the prior exists, recognize it as relevant, and load it in the comparison pane quickly enough to be useful.\u0026rdquo; Findable isn\u0026rsquo;t the same as ready: a large prior can show up in the study list and still take long enough to open that the radiologist reads without it. That\u0026rsquo;s a worklist and hanging-protocol integration problem, and it\u0026rsquo;s solved by the systems agreeing on identity, relevance and workflow. Fast storage alone solves none of those.\nWhat I\u0026rsquo;d write today # If I were giving the 2026 version of that advice to a new administrator:\nFind out where the priors physically are. VNA, legacy PACS, the cardiology system, the outside-image import box. If any of them are on tape or a cold cloud tier, the 2009 article applies to that one unchanged. Find out how many patient identifiers the archive knows about, and who reconciles them. If the answer is \u0026ldquo;nobody,\u0026rdquo; that\u0026rsquo;s your prefetch project, and it isn\u0026rsquo;t about prefetching. Trace one order end to end. Order arrives; what fires; what query goes to which archive with which patient ID, issuer and matching keys; what comes back; what retrieve follows, and to where; what the viewer does with it. Do this with a packet capture or the archive\u0026rsquo;s query log, not with the vendor\u0026rsquo;s architecture slide. Then have the relevance conversation with the radiologists. It is still the highest-value hour in the project, and it still comes after the plumbing is understood, not before. Check the result at the reading station. A prefetch job that reports success tells you a query ran and data moved. Open a handful of real exams the way a radiologist would, and see whether the right priors are there, in the right pane, when the study opens. The 2009 article ends by telling administrators to put that time in with the radiologists up front, especially for the abdomen, pelvis and chest, where several modalities compete to be the relevant prior. That\u0026rsquo;s the part that aged best. The bytes are easier to reach now. Knowing which ones matter, whose they are, and getting them in front of the radiologist before the study opens is the hard part.\nSources # The original: Understanding the PACS Prefetching Process, JS PACS, March 2009. DICOM PS3.3, Section 10.15, Issuer of Patient ID Macro, for Issuer of Patient ID (0010,0021) as the assigning authority and its Type: https://dicom.nema.org/medical/dicom/current/output/chtml/part03/sect_10.15.html. DICOM PS3.3, Section C.7.1.1, Patient Module, for Patient ID and the Other Patient IDs Sequence (0010,1002): https://dicom.nema.org/medical/dicom/current/output/chtml/part03/sect_C.7.html. DICOM PS3.4, Annex C, Query/Retrieve Service Class, for C-FIND, C-MOVE and C-GET: https://dicom.nema.org/medical/dicom/current/output/chtml/part04/PS3.4.html. DICOM PS3.18, Web Services, for the Search transaction (QIDO-RS, Section 10.6): https://dicom.nema.org/medical/dicom/current/output/chtml/part18/sect_10.6.html, and the Retrieve transaction (WADO-RS, Section 10.4): https://dicom.nema.org/medical/dicom/current/output/chtml/part18/sect_10.4.html. IHE Radiology, Import Reconciliation Workflow (IRWF): https://wiki.ihe.net/index.php/Import_Reconciliation_Workflow. IHE Radiology, Patient Information Reconciliation (PIR): https://wiki.ihe.net/index.php/Patient_Information_Reconciliation. IHE Radiology Technical Framework, Volume 2 (Rev. 23.0), Section 4.14.4.1.2.1 and Table 4.14-3 (Enterprise Identity Option) and Section 4.129.4.1.2 (QIDO-RS Query [RAD-129]), for Issuer of Patient ID as a required query key and Other Patient IDs Sequence as a required return key: https://www.ihe.net/uploadedFiles/Documents/Radiology/IHE_RAD_TF_Vol2.pdf. HL7 v2.5.1, Chapter 4, Order Entry: Section 4.4.12 (OMI, Imaging Order Message): https://www.hl7.eu/HL7v2x/v251/std251/ch04.html. HL7 v2.7, Chapter 4, Section 4.4.1, for ORM \u0026ldquo;retained for backwards compatibility only as of v2.4 and withdrawn as of v2.7\u0026rdquo;: https://www.hl7.eu/HL7v2x/v27/std27/ch04.html. HL7 FHIR R4, Subscription (server push notifications when a matching resource is created or updated): https://hl7.org/fhir/R4/subscription.html. IHE IT Infrastructure, Patient Identifier Cross-referencing (PIX): https://wiki.ihe.net/index.php/Patient_Identifier_Cross-Referencing. Observations about flat archives, outside studies, merged identifiers, and where prefetch fails in practice are from my own work and stated as experience. ","date":"14 November 2026","externalUrl":null,"permalink":"/posts/prefetching-revisited/","section":"Posts","summary":"","title":"Prefetching, Revisited: Relevant Priors in an Enterprise Archive","type":"posts"},{"content":"","date":"14 November 2026","externalUrl":null,"permalink":"/tags/relevant-priors/","section":"Tags","summary":"","title":"Relevant Priors","type":"tags"},{"content":"","date":"14 November 2026","externalUrl":null,"permalink":"/tags/vna/","section":"Tags","summary":"","title":"VNA","type":"tags"},{"content":"","date":"14 November 2026","externalUrl":null,"permalink":"/tags/workflow/","section":"Tags","summary":"","title":"Workflow","type":"tags"},{"content":"","date":"12 November 2026","externalUrl":null,"permalink":"/tags/c-echo/","section":"Tags","summary":"","title":"C-ECHO","type":"tags"},{"content":"\u0026ldquo;Echo works.\u0026rdquo; I have heard that sentence used to close a ticket, sign off a go-live, and end an argument with a vendor. It should not do any of those things.\nStrictly speaking, C-ECHO is a connectivity test. The standard defines Verification as exactly that: confirming that two DICOM application entities can communicate. What it isn\u0026rsquo;t is a test of whether those two systems can do the work you\u0026rsquo;re connecting them for. A successful C-ECHO proves that an association was accepted and that the far side answered a Verification request. That\u0026rsquo;s a real result, and it rules out a whole class of problems. But it says nothing about whether a single image will ever cross that connection, and the problems that actually stop images are almost all in the part echo doesn\u0026rsquo;t touch.\nThis is what echo tests, what it skips, and the sequence I use instead.\nWhat C-ECHO actually does # The Verification SOP Class (PS3.4, Annex A) is the simplest service in DICOM. The SCU opens an association proposing a Verification presentation context, which in a conformant SCU includes implicit VR little endian (the one transfer syntax every conformant implementation has to support, PS3.5 Section 10.1), sends a C-ECHO request with no data set, and the SCP responds with a status. Success is 0000.\nsequenceDiagram participant SCU as Your tool participant SCP as Target AE SCU-\u003e\u003eSCP: TCP connect to host:port SCU-\u003e\u003eSCP: A-ASSOCIATE-RQ\n(calling AE, called AE, Verification SOP Class) SCP--\u003e\u003eSCU: A-ASSOCIATE-AC SCU-\u003e\u003eSCP: C-ECHO-RQ SCP--\u003e\u003eSCU: C-ECHO-RSP, status 0000 SCU-\u003e\u003eSCP: A-RELEASE-RQ SCP--\u003e\u003eSCU: A-RELEASE-RP Every step in that diagram is something that can fail, so a green echo does establish something. It\u0026rsquo;s just narrower than it looks:\nA successful echo establishes It still leaves open A TCP connection to that host and port, from this machine, at this moment Whether other senders, other network paths, or the same path under load can connect The SCP accepted an association with this calling and called AE title Whether it checks AE titles at all. Some SCPs accept any calling AE, and some answer to more than one called AE, so a green echo doesn\u0026rsquo;t prove you reached the application you meant to The Verification presentation context was accepted Whether any storage, query/retrieve, or worklist context will be The Verification SCP processed a request Whether the storage, database, indexing, or routing behind it is healthy This AE can reach that one Whether that one can open an association back to you It\u0026rsquo;s still a useful list. The first two rows cover most of what a network team or a vendor engineer means by \u0026ldquo;connectivity,\u0026rdquo; and echo answers them in under a second.\nWhat it doesn\u0026rsquo;t touch # Now look at what a real transfer does that echo does not.\nPresentation context negotiation for the object you\u0026rsquo;re sending. Echo proposes Verification. Storage proposes CT Image Storage with specific transfer syntaxes. The SCP can accept the association and still reject the context you need, and it tells you so in the association accept, not with an error. Each proposed context comes back with a result: accepted, rejected by the user, rejected with no reason, abstract syntax not supported, or transfer syntaxes not supported (PS3.8, Section 9.3.3.2). A tool that only checks \u0026ldquo;did the association open\u0026rdquo; never sees it. An open association isn\u0026rsquo;t necessarily a usable one. This is the conformance statement failure made real: both sides speak DICOM, neither speaks the same SOP class, and echo says everything\u0026rsquo;s fine.\nTransfer syntax agreement. Same mechanism, one level down. The standard requires the association requester to offer implicit VR little endian in at least one presentation context for every SOP class it proposes, and forbids the acceptor from rejecting all of them because it supports none of the transfer syntaxes (PS3.5, Section 10.1), so a conformant pair can fall back to uncompressed. The failures come from the exceptions and the non-conformers. 10.1 waives this for a sender that has the pixel data only in lossy-compressed form, and for one whose lossless-compressed or encapsulated uncompressed pixel data is too long to encode in the default transfer syntax (unless it offers a pixel-data-reference syntax); such a sender may propose only its compressed or encapsulated syntax. And some senders propose only their compressed syntax whatever the standard says. If the receiver doesn\u0026rsquo;t accept it, that context comes back rejected, normally as transfer syntaxes not supported, and echo is still green.\nThe data set. Echo sends none. Storage sends a full object, and now the receiving application has to deal with it. Missing required attributes, wrong VRs, values that contradict each other, pixel data that doesn\u0026rsquo;t match what the header says it holds: some SCPs check for these during the C-STORE and return an error or warning status; others accept the object and find the problem later in their own processing. A modality that produces a slightly malformed header, an anonymizer that stripped a Type 1 attribute, a transfer syntax header that lies about its contents: all of these can fail, at the C-STORE or later, on a connection that echoes perfectly.\nSize and duration. Echo is a few hundred bytes and done in milliseconds. A large store runs for seconds or minutes and pushes megabytes to gigabytes through every network device between the two AEs. That exercises timeouts, long-lived TLS sessions and inspection appliances, buffering, and the receiver\u0026rsquo;s memory and disk. An echo over TLS proves the handshake succeeded and that each side accepted the other\u0026rsquo;s certificate as far as it is configured to check, but none of the rest. Maximum PDU length is negotiated in the association, and a correct sender splits a large object across as many PDUs as it needs, so a PDU setting is rarely the cause on its own. It\u0026rsquo;s worth reading in the association log, but in my experience the appliances and the timeouts are the likelier suspects.\nConcurrency and load. One echo on one association. In one department I\u0026rsquo;ve supported, production meant twelve modalities on forty associations at shift change. The SCP\u0026rsquo;s association limit, its thread pool, and its disk behave differently under that load, and echo tests none of it.\nStorage commitment and MPPS. A successful C-STORE response says the store succeeded. Storage commitment is a separate service that asks a separate question: will the archive take responsibility for keeping these objects? The sender issues an N-ACTION request, and the answer comes back as an N-EVENT-REPORT, which the SCP may send on a new association it opens back toward the sender (PS3.4, Annex J). On the modalities I\u0026rsquo;ve worked with, if deletion of local copies waits for commitment and the answer never arrives, the modality keeps them and eventually fills its disk. MPPS is a third service: the modality reports with N-CREATE and N-SET that a procedure started and then completed or was discontinued (PS3.4, Annex F). Each is its own SOP class on its own presentation context, and the echo proposed neither.\nThe return path. Echo is one-directional. Any workflow where the far side initiates (C-MOVE sub-operations, storage commitment events sent on a new association) needs the far side to be able to associate to you, which is a separate echo in the other direction that, in my experience, almost nobody runs. MPPS doesn\u0026rsquo;t have this problem, since the modality initiates every message in it.\nWhat to run instead # The sequence below is the one I settled on after building a few generations of test tools, first with the DCMTK command-line utilities and later in Python with pynetdicom. Each step assumes the one before it passed, and each one isolates a layer the previous step couldn\u0026rsquo;t see.\nflowchart TD A[\"1. Echo, plus the reverse\ndirection if the workflow needs it\"] --\u003e B[\"2. Associate with the real\nSOP classes and transfer\nsyntaxes; inspect the accept\"] B --\u003e C[\"3. Store one small,\nknown-good object\"] C --\u003e D[\"4. Store one large object\n(same SOP class, if you can)\"] D --\u003e E[\"5. Store in parallel at\nproduction concurrency,\nthen sustain it\"] E --\u003e F[\"6. Query it back; confirm\nwhat arrived is what left\"] F --\u003e G[\"7. Commitment / MPPS\nround trip, if in scope\"] classDef s fill:#1e293b,stroke:#64748b,color:#e2e8f0; class A,B,C,D,E,F,G s; 1. Echo, and the reverse direction if the workflow needs it. Yes, still first. It\u0026rsquo;s cheap and it clears the network and AE-title layer so that everything after it is about DICOM. If anything in scope has the far side opening an association back to you (C-MOVE destinations, storage commitment replies), echo from there to your AE as well. A modality that only pushes images doesn\u0026rsquo;t need it.\n2. Associate with the real contexts. Open an association proposing exactly the SOP classes and transfer syntaxes the production sender will propose, and read the accept. Every context comes back accepted or rejected with a reason. This single step catches the majority of go-live failures I\u0026rsquo;ve seen, and it takes a few seconds. DCMTK\u0026rsquo;s storescu with -d dumps the negotiated contexts and their results; pynetdicom gives you the accepted contexts as a list on the association object.\n3. One small object. A known-good file, a few hundred kilobytes, in a transfer syntax you confirmed in step 2. If this fails, the problem is in the storage operation itself, not the network, the AE titles, or the negotiation. The C-STORE status, the association log, and the receiver\u0026rsquo;s own log are what tell a rejected data set apart from a full disk or an application error.\n4. One large object. The biggest thing the modality produces: a tomosynthesis stack, an enhanced multi-frame MR, a long cine. Where you can, keep the SOP class and transfer syntax the same as in step 3, so size is the only thing that changed. This finds the path problems: timeouts, appliances that only inspect big flows, receivers that run out of something.\n5. Concurrency. Repeat the stores across several simultaneous associations against the production port. My tester ramps through five, ten, fifteen and twenty concurrent senders; pick numbers that match your busiest hour. Watch for association refusals (the SCP\u0026rsquo;s limit), response times that grow faster than the load, and the occasional object that fails under load but not alone. Then hold the load long enough to expose a backlog or a leak that a one-minute burst won\u0026rsquo;t. This is the test that most closely predicts seven in the morning. Run it against a test system, or in a quiet window agreed with the people who depend on the production one.\n6. Query it back. C-FIND for what you just stored, at the series or image level if the archive supports it, and compare the UIDs to what you sent; a study-level answer can\u0026rsquo;t tell you every instance arrived. A C-STORE success status confirms the store. It doesn\u0026rsquo;t promise the archive has indexed the object where a query will find it, and some archives hold or quarantine objects after the fact. When it matters that the pixels arrived intact, retrieve a few and compare. The C-FIND post covers what you can and can\u0026rsquo;t learn from that query.\n7. The round trip. Storage commitment and MPPS, if the modality uses them. Commitment is where the reverse path from step 1 earns its keep, but the reverse echo only proves the network path and that the modality accepts that AE title pair. When the archive sends the result on a new association, which every commitment SCP must be able to do, it opens that association using the same AE title, proposing Storage Commitment with a role-selection item asking for the SCP role. The modality has to accept the context and return that role. Read that accept too. MPPS needs its own context accepted by whatever receives it.\nEach step produces a yes or a no at one layer. A no at step 4 after a yes at step 3 narrows the search to what\u0026rsquo;s different about a large object before anyone opens a packet capture. That\u0026rsquo;s the whole value of the sequence: it localizes.\nWhen echo is the right test # To be fair to it. Echo is the right test when the question is \u0026ldquo;is the thing up,\u0026rdquo; and that\u0026rsquo;s a question worth asking often. A scheduled echo every few minutes against every AE you care about, with an alert on failure, is one of the cheapest pieces of monitoring an imaging department can run, and it catches the listener-is-down class of outage before the first tech calls. I\u0026rsquo;ve run it from a cron job and from a monitoring stack; either works.\nRead it for what it tells you, though. A failed echo means something is wrong on that path. A green one doesn\u0026rsquo;t mean the archive is healthy: it can keep answering echo through a full disk, a stalled queue, or a broken index. Watch those separately.\nIt\u0026rsquo;s the wrong test when the question is \u0026ldquo;will it work,\u0026rdquo; and the two questions get confused because the answer to the first one arrives so fast and so green.\nSources # DICOM PS3.4, Annex A, Verification Service Class: https://dicom.nema.org/medical/dicom/current/output/chtml/part04/chapter_A.html. DICOM PS3.4, Annex J, Storage Commitment Service Class, and Annex F, Modality Performed Procedure Step: https://dicom.nema.org/medical/dicom/current/output/chtml/part04/chapter_J.html, https://dicom.nema.org/medical/dicom/current/output/chtml/part04/chapter_F.html. DICOM PS3.5, Section 10.1, for the default transfer syntax every implementation must support: https://dicom.nema.org/medical/dicom/current/output/chtml/part05/chapter_10.html. DICOM PS3.4, Section J.3.3.1, for the commitment result on a new association, the same AE title, and SCP role selection: https://dicom.nema.org/medical/dicom/current/output/chtml/part04/sect_J.3.3.html. DICOM PS3.7, Section D.3.3.4, SCP/SCU Role Selection Negotiation: https://dicom.nema.org/medical/dicom/current/output/chtml/part07/sect_D.3.3.4.html. DICOM PS3.7, Message Exchange, for C-ECHO, C-STORE, and status codes: https://dicom.nema.org/medical/dicom/current/output/chtml/part07/PS3.7.html. DICOM PS3.8, Network Communication Support, Section 9.3.3.2, for the presentation context results in the association accept: https://dicom.nema.org/medical/dicom/current/output/chtml/part08/sect_9.3.3.2.html. DCMTK: https://dicom.offis.de/dcmtk. pynetdicom: https://pydicom.github.io/pynetdicom/. The test sequence and the failure patterns are from my own tooling and engagements, and are stated as experience. ","date":"12 November 2026","externalUrl":null,"permalink":"/posts/c-echo-is-not-a-connectivity-test/","section":"Posts","summary":"","title":"C-ECHO Is Not a Connectivity Test","type":"posts"},{"content":"","date":"12 November 2026","externalUrl":null,"permalink":"/tags/c-store/","section":"Tags","summary":"","title":"C-STORE","type":"tags"},{"content":"","date":"12 November 2026","externalUrl":null,"permalink":"/tags/testing/","section":"Tags","summary":"","title":"Testing","type":"tags"},{"content":"","date":"12 November 2026","externalUrl":null,"permalink":"/tags/troubleshooting/","section":"Tags","summary":"","title":"Troubleshooting","type":"tags"},{"content":"","date":"10 November 2026","externalUrl":null,"permalink":"/tags/conformance-statement/","section":"Tags","summary":"","title":"Conformance Statement","type":"tags"},{"content":"Somebody hands you a conformance statement the week before a new modality, archive, or viewer goes live, and asks whether it\u0026rsquo;ll work with what you have. The document is sixty to two hundred pages. You have an hour.\nThe good news is that a conformance statement is written to a template the standard dictates (PS3.2), so every one of them puts the same information in the same places. The better news is that the hour\u0026rsquo;s question, will these two systems talk, comes down to five things, and you can find all five in about fifteen minutes once you know where to look. The rest of the hour is for the questions the document can\u0026rsquo;t answer, which is where integrations actually fail.\nWhat a conformance statement is # It is a vendor\u0026rsquo;s declaration, in the standard\u0026rsquo;s own vocabulary, of exactly which parts of DICOM a product implements. Not what the product can do clinically; what it will negotiate and exchange on the wire. PS3.2 Section 7 (7.1.1 for DIMSE networking, 7.1.2 for DICOMweb) requires an implementation claiming conformance to \u0026ldquo;provide a Conformance Statement structured according to the rules and policies in this Part,\u0026rdquo; and it is the only vendor document whose structure the standard controls.\nTwo things it is not. It is not a test report; a statement says what the vendor claims, and nothing in the standard obliges anyone to have verified it against another product. And it is not a guarantee of interoperability. The template\u0026rsquo;s suggested Remarks text, which many statements reproduce, says it plainly: \u0026ldquo;DICOM by itself does not guarantee interoperability.\u0026rdquo; What the statement does, in the same paragraph\u0026rsquo;s words, is \u0026ldquo;facilitate a first-level comparison\u0026rdquo; between two products. The comparison is your job.\nThree generations of the template # The standard has rewritten the template twice, and the statements on your desk will span all three versions, so it pays to know which one you\u0026rsquo;re holding before you go looking for a section number.\nThe original template (PS3.2 through the 2001 edition, where it was also Annex A) numbered its chapters Introduction, Implementation Model, AE Specifications, Communication Profiles, Extensions, Configuration, Extended Character Sets, Codes and Controlled Terminology, Security Profiles. Vendor documents written to it number those 1 through 9. Some long-lived products still ship statements in this layout. The later Annex A template (introduced in the early 2000s, last normative in the 2022d edition, and the layout of nearly every statement you\u0026rsquo;ll be handed) moved the network material under a single \u0026ldquo;Networking\u0026rdquo; chapter. Its section numbers are prefixed A. in the standard and usually unprefixed in vendor documents: Implementation Model is A.4.1, AE Specifications A.4.2, Configuration A.4.4, Support of Character Sets A.7, Security A.8. Annex N (2022e onward) is the current normative template. It reorganizes again, by service rather than by AE (N.5 Service and Interoperability Description), with DIMSE, DICOMweb, media and real-time video as parallel sections, adds de-identification profiles (N.1.6), and retires the old template and all of the old sample statements (Annexes A through M are marked retired in the current edition). Implementation Model is N.4, the per-service specifications N.5, Configuration N.6, status codes N.7.3, Security N.8. The Annex A template called its numbering \u0026ldquo;a guideline\u0026rdquo;; Annex N asks authors to keep its numbering consistent. Vendors drift either way. Find sections by name. The table at the end of each question below gives the number in each generation for when you need it.\nThe five questions, and where they live # 1. Which Application Entities does the product have, and what does each one do? # The Implementation Model, starting with the application data flow diagram. It shows every AE the product exposes and which real-world activity drives each one. A PACS might have one AE that accepts storage, another that answers queries, and a third that sends. A modality might have one for worklist, one for MPPS, one for storage. This is where you learn that the product you think of as \u0026ldquo;the archive\u0026rdquo; is really four DICOM endpoints with separate behaviors, and the one you\u0026rsquo;re planning to query may not be the one that stores.\nWrite down the AE names. Everything else in the document is organized by them.\nOriginal template Annex A Annex N 2 Implementation Model A.4.1 Implementation Model N.4 Implementation Model 2. Which SOP classes does each AE support, as SCU or SCP? # The AE Specifications, one subsection per AE, and the SOP class table at the top of each. This is the table that decides most integrations. For a storage interface, it lists which object types (CT Image Storage, Enhanced MR, Breast Tomosynthesis, Encapsulated PDF, and so on) the AE will accept (SCP) or send (SCU). For a query interface, it lists which Query/Retrieve information models are supported, Patient Root or Study Root, and whether FIND, MOVE, and GET are each there.\nThe failure this table predicts: the new modality produces Enhanced CT objects, the archive\u0026rsquo;s SOP class table lists only the classic CT Image Storage. The archive will reject the presentation context for Enhanced CT, the modality will either fall back or fail, and the first anyone hears of it is a tech saying \u0026ldquo;it won\u0026rsquo;t send.\u0026rdquo; Thirty seconds with the two tables side by side would have caught it.\nTwo services in this table deserve a second look, because a match in the table doesn\u0026rsquo;t tell you the workflow will work.\nC-MOVE is two associations, not one. When your workstation sends a C-MOVE to the archive, the archive opens (or reuses) a separate association back to the destination AE you named and does C-STOREs over it. Both products can list Study Root C-MOVE and the retrieve can still fail, because the archive doesn\u0026rsquo;t know the destination AE title, can\u0026rsquo;t resolve its address, can\u0026rsquo;t reach it through the firewall, or doesn\u0026rsquo;t share a storage presentation context with it. C-GET does its sub-operations on the association you opened, which is why it\u0026rsquo;s the one that works through NAT, and in my experience the one most archives don\u0026rsquo;t support as SCP. Check the move destination\u0026rsquo;s own storage SCP table too; the archive is about to be a storage SCU to it.\nA C-STORE success is not a commitment. Storage Commitment is a separate SOP class (Storage Commitment Push Model), and a modality configured to wait for commitment before it deletes local copies will fill its disk and stop sending if the archive doesn\u0026rsquo;t offer it, even though every C-STORE returned success. If the modality\u0026rsquo;s table lists Storage Commitment as SCU, find it in the archive\u0026rsquo;s table as SCP, or plan to turn the modality\u0026rsquo;s expectation off.\nOriginal template Annex A Annex N 3 AE Specifications A.4.2 AE Specifications N.5 Service and Interoperability Description (N.5.1 maps services to AEs) 3. Which transfer syntaxes does each SOP class support? # The AE Specifications again, under each AE\u0026rsquo;s association policies, in the presentation context tables. Each row pairs a SOP class with the transfer syntaxes the AE will propose (SCU) or accept (SCP): implicit and explicit VR little endian, the JPEG family, JPEG 2000, RLE, and so on.\nIn my experience this is the second most common failure, and the one that doesn\u0026rsquo;t always show up as an error. Negotiation happens per presentation context, not per association. If the sender proposes CT Image Storage with JPEG 2000 lossless only and the receiver accepts CT only uncompressed, the association usually still opens; the receiver just rejects that one presentation context, and the sender has nothing it can put a CT image in. The standard doesn\u0026rsquo;t allow that sender. PS3.5 Section 10.1 requires the association requester to offer Implicit VR Little Endian in at least one presentation context for every SOP class it proposes. When the request does that, the receiver may not reject every context for that SOP class on the grounds that it supports none of the transfer syntaxes. It may still turn down the Implicit VR Little Endian context if it accepts another one, and it may still refuse the SOP class itself. Both rules are waived when the sending application has the pixel data only in lossy-compressed form (it may then propose only the matching lossy syntax), or when lossless-compressed or encapsulated uncompressed pixel data is too large to encode in Implicit VR Little Endian and no Pixel Data-reference (JPIP) syntax is offered. Offering a JPIP referenced syntax waives the receiver rule alone. A CT that proposes JPEG 2000 lossless alone for an ordinary image is out of conformance, and its presentation context table is where you\u0026rsquo;ll see it. A well-behaved sender proposes several contexts for the same SOP class, one per transfer syntax it can produce, including Implicit VR Little Endian unless a 10.1 waiver applies, so the receiver can pick one; a poorly behaved one proposes exactly one and, in the cases I\u0026rsquo;ve seen, reports a failure that looks like a network problem. Either way the association log shows the rejected context, which is why reading those logs is worth learning.\nWorse is the case where they do overlap but not on the syntax you expected: the archive accepts the compressed stream, stores it, and later serves it to a viewer that can\u0026rsquo;t decode it. The conformance statement predicted that too, in the viewer\u0026rsquo;s own table.\nCheck all three legs: sender to archive, archive to viewer, archive to any downstream system. Transfer syntax mismatches propagate.\nOriginal template Annex A Annex N 3 AE Specifications (per-AE presentation contexts) A.4.2.x.3 Association Initiation Policy / A.4.2.x.4 Association Acceptance Policy (Proposed / Accepted Presentation Contexts) N.5.2 DIMSE Services; N.7.2 Specifications 4. What are the association limits? # The association policies for each AE: General, Number of Associations, Asynchronous Nature, Implementation Identifying Information. Three numbers and two strings. Maximum PDU size, which affects throughput and occasionally compatibility with old equipment. Maximum simultaneous associations the AE will accept, which is the number that matters when twelve modalities all push at seven in the morning. And whether the AE supports asynchronous operations (multiple outstanding requests on one association), which in my experience is almost always \u0026ldquo;no\u0026rdquo; and occasionally the reason a bulk send is slower than the network suggests.\nThe two strings are the Implementation Class UID and Implementation Version Name. They appear in every association the product opens. When you\u0026rsquo;re reading a log from the other side and trying to work out which product and version was talking, this is the lookup, and it\u0026rsquo;s a different thing from both the product\u0026rsquo;s marketing version and the statement\u0026rsquo;s own revision number (more on that below).\nOriginal template Annex A Annex N 3 AE Specifications; 4 Communication Profiles A.4.2.x.2 Association Policies N.7.1 General; N.7.2 Specifications 5. What happens when something goes wrong? # The SOP-specific conformance subsections under each AE: status code tables and behavior descriptions. This is the section people skip and the one that separates a good statement from a thin one. For a storage SCP it should say what the AE does on receipt of a duplicate SOP instance, an object with a missing required attribute, or an unsupported element: accept, reject with which status, coerce, warn. For a storage SCU it should say how it handles each status the receiver might return, including the three warning statuses the standard defines for C-STORE, which are not the same thing: B000 means the receiver coerced data elements, B006 means it discarded some, and B007 means the data set didn\u0026rsquo;t match its SOP class but was accepted anyway. For Q/R it should list the matching keys supported at each level and whether relational queries are supported, which is exactly the information the C-FIND post said to go find here.\nThe coercion case matters more than its one-line status suggests. An archive can accept an object with success, and still rewrite the patient ID to match its master record, correct the accession number against the order, normalize the name, or quietly merge the study into an existing one. The statement may describe this under the storage SCP\u0026rsquo;s behavior, or under a \u0026ldquo;coercion\u0026rdquo; or \u0026ldquo;reconciliation\u0026rdquo; heading, or not at all. Whether it does is a good measure of the document.\nA statement that lists status codes without describing behavior is telling you the vendor filled in the template. In nearly twenty years I can count on one hand the times a production system handed me a status that pointed at the actual problem; it\u0026rsquo;s an A7xx \u0026ldquo;out of resources,\u0026rdquo; or a Cxxx \u0026ldquo;cannot understand,\u0026rdquo; and a trip to the logs. A statement that says what its AE does after a status, how many times it retries, what it logs, and when it gives up, is telling you someone engineered the product. Most don\u0026rsquo;t say.\nOriginal template Annex A Annex N 3 AE Specifications (per-SOP-class conformance) A.4.2.x.3.y.3 / A.4.2.x.4.y.3 SOP Specific Conformance N.5.2 DIMSE Services; N.7.3 Status Codes The order to read in # flowchart TD A[\"Implementation Model:\nlist the AEs\"] --\u003e B[\"AE Specifications:\nSOP class table per AE\"] B --\u003e C{\"Both sides share the\nSOP classes you need?\"} C -- no --\u003e X[\"Stop: gateway, config\nchange, or vendor ticket\"] C -- yes --\u003e D[\"Presentation context tables:\ntransfer syntax overlap on\nevery leg\"] D --\u003e E{\"Overlap on each leg?\"} E -- no --\u003e X E -- yes --\u003e F[\"Association limits and\nimplementation identifiers\"] F --\u003e G[\"Status handling and\nQ/R matching keys\"] G --\u003e H[\"Configuration, character\nsets, security\"] H --\u003e I[\"Now test it\"] classDef stop fill:#7f1d1d,stroke:#fca5a5,color:#fee2e2; class X stop; Configuration, character sets, and security come last not because they don\u0026rsquo;t matter but because they rarely decide go/no-go on their own. Configuration tells you what\u0026rsquo;s adjustable in the field, which answers \u0026ldquo;can we change the AE title and port\u0026rdquo; and \u0026ldquo;where does the called-AE whitelist live.\u0026rdquo; Character sets matter the moment a patient name arrives with a diacritic; if the two sides don\u0026rsquo;t share a supported character set, names get mangled or rejected. Security is the exception to \u0026ldquo;rarely\u0026rdquo;: TLS support, which profiles, which versions, and whether the product can be told to trust your certificate authority is now a go/no-go question for anything crossing a site boundary or going to a cloud archive, and it\u0026rsquo;s worth checking on the first pass rather than the last. If the product has a DICOMweb interface, Annex N gives it its own sections; the questions are the same (which transactions, which media types, which authentication) but the tables look different, and that\u0026rsquo;s a post of its own.\nWhat it won\u0026rsquo;t tell you # This is the part of the hour that matters.\nWhether the claims are true. A conformance statement is self-reported. I have read statements that listed SOP classes the shipped version didn\u0026rsquo;t support and matching keys that returned nothing. The document predicts; the test confirms. Nothing goes live on the strength of the statement alone.\nWhich version you have. Statements are per product version and often lag releases. There are three version numbers in play and they don\u0026rsquo;t move together: the product\u0026rsquo;s software version, the statement\u0026rsquo;s own revision (in the revision history at the front), and the Implementation Version Name the product sends on the wire. Check all three against what\u0026rsquo;s actually installed. A statement for 5.2 is useful history for 5.4, but it isn\u0026rsquo;t evidence about 5.4, and vendors do remove things.\nPerformance. Nothing in the template describes how fast a query returns, how many studies a day the storage SCP sustains, or what happens to the C-MOVE queue under load. The number of associations is the only capacity figure in the document, and it\u0026rsquo;s a limit, not a measurement.\nBehavior between the lines. The statement describes each service in isolation. It does not describe what the archive does when a storage commitment request arrives for a study that\u0026rsquo;s still being received, or how it reconciles a worklist entry against a study whose accession number was typed in by hand. The interactions between services are where production surprises come from. Annex N at least added a \u0026ldquo;Cross Service Considerations\u0026rdquo; heading for this; whether vendors put anything under it remains to be seen.\nWhich error you\u0026rsquo;ll actually get. The status table lists every code the AE can return. In my experience the one you see is the generic one, and the specific codes the standard took the trouble to define show up rarely. Plan on reading logs, not statuses.\nAnything about the other product. The statement is one side of a conversation. You need both, and you need to read them against each other, table by table. A single statement, however good, answers nothing on its own.\nWhether the site\u0026rsquo;s configuration matches it. The statement describes what the product can do. Half of it is switched off at any given installation. The SOP class the statement lists as supported may be disabled in the config; the transfer syntax may be de-prioritized; the association limit may have been set lower by someone in 2019 for a reason nobody remembers. The statement tells you the ceiling. The installed configuration is the floor you\u0026rsquo;re standing on.\nWhat I do with it # Both statements, side by side, five questions, a one-page matrix of SOP class and transfer syntax overlap per leg. It looks like this, for a new CT sending to an existing archive:\nRequirement CT (statement says) Archive (statement says) Verdict CT Image Storage SCU SCP Compatible Enhanced CT Image Storage SCU not listed Gap: configure CT for classic CT, or vendor ticket Transfer syntax, CT → archive JPEG 2000 lossless, Explicit VR LE (Implicit VR LE not listed) Explicit VR LE only (Implicit VR LE not listed) Overlap on Explicit VR LE, but both statements omit Implicit VR LE, which PS3.5 10.1 requires: ask both vendors Transfer syntax, archive → reading viewer — Explicit VR LE (Implicit VR LE not listed) Check the viewer\u0026rsquo;s statement for Explicit VR LE; same Implicit VR LE question for the archive vendor Storage Commitment Push SCU not listed Gap: disable commitment wait on the CT Modality Worklist SCU n/a (RIS provides) Check the RIS statement TLS supported, TLS 1.2 supported, TLS 1.2, site CA Compatible; test the handshake Anything that doesn\u0026rsquo;t overlap goes on a list with a proposed fix (gateway, configuration change, vendor ticket). Anything the statement is vague about goes on a second list: things to test before go-live rather than trust. Then the test, which is the subject of a later post.\nThe statement is the map. It is not the territory, and the vendor drew it.\nSources # DICOM PS3.2, Conformance, current edition: https://dicom.nema.org/medical/dicom/current/output/chtml/part02/PS3.2.html. Section 6 for the purpose of a statement; Section 7.1 for the requirement to provide one and to follow Annex N; Annex N for the current template (N.3.3 Remarks for the \u0026ldquo;does not guarantee interoperability\u0026rdquo; language; N.5.6 Cross Service Considerations). Annexes A through M, the older template and samples, are marked retired. DICOM PS3.2 2019e, Annex A, for the previous template that most statements in the field follow: https://dicom.nema.org/medical/dicom/2019e/output/chtml/part02/chapter_A.html. A.3.3 Remarks; A.4.1 Implementation Model; A.4.2 AE Specifications; A.4.4 Configuration; A.7 Support of Character Sets; A.8 Security. DICOM PS3.2 2001, Annex A, for the original template still used by some long-lived products: https://afni.nimh.nih.gov/pub/dist/doc/misc/DICOM/01_02PU.PDF (mirror of the 2001 PS3.2 PDF). DICOM PS3.4, Section B.2.3, Table B.2-1, for the C-STORE status values including the three warnings: https://dicom.nema.org/medical/dicom/current/output/chtml/part04/sect_B.2.3.html. DICOM PS3.4, Annex C (Query/Retrieve) for C-MOVE and C-GET sub-operation behavior, and Annex J for Storage Commitment: https://dicom.nema.org/medical/dicom/current/output/chtml/part04/PS3.4.html. DICOM PS3.5, Section 10.1, for the Default Transfer Syntax: the requirement to offer Implicit VR Little Endian for each proposed abstract syntax, the matching limit on rejecting those contexts, and the waivers for lossy-compressed pixel data, very large pixel data, and Pixel Data-reference (JPIP) transfer syntaxes: https://dicom.nema.org/medical/dicom/current/output/chtml/part05/chapter_10.html. Everything about what vendors actually put in statements, and what goes wrong in the field, is experience and is stated as such. Revised November 11, 2026: the transfer-syntax section now cites PS3.5 Section 10.1: the association requester must offer Implicit VR Little Endian for each SOP class, and the acceptor may not reject all of that SOP class\u0026rsquo;s contexts for want of a transfer syntax (with waivers for lossy, very large, and JPIP-referenced pixel data), so a CT that proposes only JPEG 2000 lossless for an ordinary image is itself out of conformance. The example matrix and the flowchart now treat a missing Implicit VR Little Endian as a vendor question. Also corrected: the template editions (Annex A was last normative in 2022d, Annex N from 2022e), what Annex N changed, two Annex A section numbers, and the PS3.2 7.1.1 citation; experience is now labeled as experience. Added PS3.5 to Sources.\n","date":"10 November 2026","externalUrl":null,"permalink":"/posts/how-to-read-a-dicom-conformance-statement/","section":"Posts","summary":"","title":"How to Read a DICOM Conformance Statement (and What It Won't Tell You)","type":"posts"},{"content":"","date":"10 November 2026","externalUrl":null,"permalink":"/tags/vendors/","section":"Tags","summary":"","title":"Vendors","type":"tags"},{"content":"","date":"9 November 2026","externalUrl":null,"permalink":"/tags/c-find/","section":"Tags","summary":"","title":"C-FIND","type":"tags"},{"content":"","date":"9 November 2026","externalUrl":null,"permalink":"/tags/migration/","section":"Tags","summary":"","title":"Migration","type":"tags"},{"content":"","date":"9 November 2026","externalUrl":null,"permalink":"/tags/query-retrieve/","section":"Tags","summary":"","title":"Query/Retrieve","type":"tags"},{"content":"Every migration, every archive assessment, and every \u0026ldquo;how big is this thing, really?\u0026rdquo; conversation I\u0026rsquo;ve been part of runs into the same wall early: the organization needs to know what\u0026rsquo;s in the archive, and the only access anyone will grant is a DICOM port.\nNo database login. No vendor report anyone trusts. Sometimes not even a conformance statement that matches the installed version. Just an AE title, an IP address, and permission to query.\nThat makes C-FIND the instrument. It\u0026rsquo;s a good one, but it was designed to find a patient\u0026rsquo;s studies for a reading workstation, not to inventory a petabyte. If you use it for the second job, you need to know exactly where the standard stops guaranteeing answers and starts leaving them to the vendor. This is a walk along that boundary, with the standard open beside me.\nThe model you are querying # DICOM Query/Retrieve is defined in PS3.4, Annex C. An archive that supports it exposes one or more information models. The two that matter in practice are Patient Root and Study Root. Patient Root is a hierarchy of four levels; Study Root is the same hierarchy with the top level removed:\nflowchart TD P[\"PATIENT\nPatient ID (0010,0020)\"] ST[\"STUDY\nStudy Instance UID (0020,000D)\"] SE[\"SERIES\nSeries Instance UID (0020,000E)\"] IM[\"IMAGE\nSOP Instance UID (0008,0018)\"] P --\u003e ST --\u003e SE --\u003e IM classDef lvl fill:#1e293b,stroke:#64748b,color:#e2e8f0; class P,ST,SE,IM lvl; Each level has a unique key (shown above), a short list of required keys the archive must be able to match on and return, and a longer list of optional keys it may or may not support. The standard spells these out in Section C.6. Study Root starts at STUDY and folds the patient attributes into that level, which is why most tools default to it. Patient Root is common on older archives; the method below works the same there, with one more level to walk and Patient ID as the unique key for it.\nThe word hierarchical is doing real work. A baseline query asks about one level at a time, and to go deeper you must supply the unique keys for every level above. To learn anything about the series in a study, you first have to have found the study. The standard defines relational queries that let you skip levels, but they\u0026rsquo;re an optional extension negotiated at association time; assume you don\u0026rsquo;t have them until the conformance statement and a live test both say you do.\nHow a query actually proceeds # Here is the shape of one STUDY-level query. Everything in it is the standard\u0026rsquo;s behavior, not a vendor\u0026rsquo;s.\nsequenceDiagram participant SCU as Your tool (SCU) participant SCP as Archive (SCP) SCU-\u003e\u003eSCP: A-ASSOCIATE-RQ (Study Root FIND SOP Class) SCP--\u003e\u003eSCU: A-ASSOCIATE-AC SCU-\u003e\u003eSCP: C-FIND-RQ\nLevel=STUDY, StudyDate=20240301-20240331,\nModalitiesInStudy=\"\", NumberOfStudyRelatedInstances=\"\" loop one response per matching study SCP--\u003e\u003eSCU: C-FIND-RSP, status Pending (FF00 or FF01)\n+ identifier with return keys filled in end SCP--\u003e\u003eSCU: C-FIND-RSP, status Success (0000) SCU-\u003e\u003eSCP: A-RELEASE-RQ SCP--\u003e\u003eSCU: A-RELEASE-RP Two details in that exchange decide whether your inventory is trustworthy.\nFirst, the identifier you send is both the question and the answer template. An attribute with a value is a matching key (\u0026ldquo;only studies in March 2024\u0026rdquo;). An attribute sent with zero length is a return key (\u0026ldquo;and tell me the modalities and instance count for each\u0026rdquo;). You get back only what you asked for, so an inventory tool has to know in advance every attribute it wants.\nSecond, the status on each pending response carries information most tools throw away. FF00 means \u0026ldquo;here\u0026rsquo;s a match.\u0026rdquo; FF01 means \u0026ldquo;here\u0026rsquo;s a match, but one or more of the optional keys you asked for are not supported\u0026rdquo; (PS3.4, Table C.4-1). The standard pairs that status with a rule about the identifier: an optional key the archive doesn\u0026rsquo;t support is left out of the response, while a supported key that has no value comes back present and zero-length (C.4.1.1.3.2). So on a conformant archive, absent means \u0026ldquo;can\u0026rsquo;t answer that\u0026rdquo; and empty means \u0026ldquo;answered: nothing there.\u0026rdquo; An archive that returns FF01 is telling you, on every response, that part of your question went unanswered. The reverse is not reliable: I\u0026rsquo;ve seen plenty of archives return FF00 with the unsupported attribute present and empty, which collapses the two cases into one. Record the status and whether each key came back at all. FF01 is a gift when you get it, and its absence is not a clean bill of health.\nThird, matching itself is less uniform than it looks. The standard lets the archive decide how to match a Patient\u0026rsquo;s Name: literally, case-sensitively, or ignoring some or all differences in case, accents, and encoding (C.2.2.2.1.1). Two conformant archives can return different result sets for SMITH^J*. Wildcards (* and ?), date ranges, and lists of UIDs are defined, but which of them a given archive honors on a given key is in its conformance statement, not the standard. For an inventory, stick to the matching the standard makes unambiguous: exact UIDs and date ranges.\nWhat the standard guarantees # At the STUDY level in Study Root, the required keys are short, and they are the reason C-FIND is useful for this at all. Every conformant archive will match and return:\nAttribute Tag What it buys you Study Date (0008,0020) Range matching, so you can walk the archive by day, month, or year Study Time (0008,0030) Range matching within a day Accession Number (0008,0050) Reconciliation against the RIS or EHR Patient\u0026rsquo;s Name (0010,0010) Wildcard matching Patient ID (0010,0020) The key you\u0026rsquo;ll join on Study ID (0020,0010) Rarely useful; often blank or duplicated Study Instance UID (0020,000D) The unique key, and the only durable identity a study has Range matching on dates is what makes enumeration possible. Query StudyDate = 20240301-20240331, collect the UIDs, move to April. Slow, deterministic, and it works against any archive that claims Q/R conformance.\nWhat the standard leaves optional # Now the part that matters for sizing. The attributes you actually want for an inventory are all optional at the STUDY level:\nAttribute Tag Why you want it Why you can\u0026rsquo;t count on it Modalities in Study (0008,0061) Mix of CT, MR, CR, US Optional; some archives populate it only for studies ingested after the feature was enabled Number of Study Related Series (0020,1206) Study shape Optional; often computed at ingest and never recomputed Number of Study Related Instances (0020,1208) The number everyone wants Optional; same problem, and it drifts Study Description (0008,1030) Human-readable context Optional, and free text \u0026ldquo;Optional\u0026rdquo; in DICOM means the archive may support it, and if it does, the conformance statement says so. It does not mean \u0026ldquo;usually works.\u0026rdquo; The pattern I see most often with the counts is that they\u0026rsquo;re derived values populated when the study arrived, and nothing re-derives them after a series is deleted, a study is split, or a migration lands only part of the images. The count you get back is the count the archive believed at some point in the past, and after a messy history it can be off by a large fraction.\nThen there\u0026rsquo;s the list of things no C-FIND attribute exists for at all. You cannot ask an archive:\nHow many bytes a study occupies. There is no size attribute at any level. Rows, Columns, Bits Allocated, and Number of Frames let you compute it, but they\u0026rsquo;re IMAGE-level attributes that the standard doesn\u0026rsquo;t list among the IMAGE-level query keys; an archive may support them as additional optional keys, and the conformance statement is where you find out. When it received the study. Study Date is the clinical date, set by the modality, so a study performed in 2009 and migrated in 2023 queries as 2009. The standard recently added Study Update DateTime (0008,041F), the time the archive last changed the study\u0026rsquo;s metadata, as an optional STUDY-level key (Table C.6-5); it isn\u0026rsquo;t an ingest timestamp, and I have yet to meet an archive that returns it, but if yours does it\u0026rsquo;s the closest thing you\u0026rsquo;ll get. Where it is stored, mostly. The standard does define Instance Availability (0008,0056), with the values ONLINE, NEARLINE, OFFLINE, and UNAVAILABLE, as something an archive \u0026ldquo;may, but is not required to\u0026rdquo; return on a match (C.4.1.1.3.2), along with the Retrieve AE Title or media file-set that holds the object. Ask for it; most archives answer ONLINE for everything or don\u0026rsquo;t answer at all. Which tier, which cloud bucket, and whether the study was deleted but left in the index: invisible. What you didn\u0026rsquo;t get. C-FIND returns matches. It never returns \u0026ldquo;and here are the studies I didn\u0026rsquo;t return because I cap results.\u0026rdquo; Caps are real and often undocumented. The first sign is usually that every window of your enumeration returns exactly the same round number. Sizing an archive anyway # Knowing the limits, here\u0026rsquo;s the method I use when C-FIND is all I have: three passes, each stepping down a level only where the one above left a gap.\nflowchart LR A[\"Pass 1\nSTUDY level\nby date range\"] --\u003e B{\"Counts and\nmodalities\nreturned?\"} B -- \"yes\" --\u003e D[\"Record study row\"] B -- \"no, FF01, or blank\" --\u003e C[\"Pass 2\nSERIES level\nper study UID\"] C --\u003e E{\"Instance count\nper series\nreturned?\"} E -- yes --\u003e D E -- no --\u003e F[\"Pass 3\nIMAGE level\nper series UID\"] F --\u003e D D --\u003e G[\"Size estimate\nfrom counts × typical\nobject size per modality\"] classDef pass fill:#1e293b,stroke:#64748b,color:#e2e8f0; class A,C,F pass; Pass 1 walks the calendar at STUDY level in windows small enough to stay under any cap (I start at one day and widen if the archive is thin), asking for the required keys plus the optional counts and Modalities in Study, and recording the status on every response. Pass 2 queries SERIES for every study where the counts came back blank or the status was FF01; Modality (0008,0060) is required at this level, so the modality mix becomes trustworthy here even when Modalities in Study wasn\u0026rsquo;t. Pass 3 enumerates instances only where Pass 2 still left counts unknown. It\u0026rsquo;s expensive, so it\u0026rsquo;s the exception.\nThen estimate: instances times a typical object size per modality lands within a usable tolerance of total storage, with the error dominated by the handful of large multi-frame and tomosynthesis objects, which you can go measure individually. Present it as what it is: an estimate derived from counts, with the per-modality assumptions written next to it.\nA few habits make this robust. Log every response status. Log the association parameters; the accepted presentation contexts are a conformance statement you can actually trust. Re-run one early window at the end to see whether the archive changed under you. Treat any window that returns a suspiciously round count as a cap, not a fact.\nWhat\u0026rsquo;s missing from this post # A worked run. I\u0026rsquo;ve described the method but not shown it with numbers: window sizes, response counts, how far the estimate landed from the truth. That\u0026rsquo;s deliberate; the archives I\u0026rsquo;ve run it against belong to clients, and the right way to show it is against an archive I own. That\u0026rsquo;s the next post, with the queries and the results in it.\nIf you\u0026rsquo;ve hit limits in C-FIND I haven\u0026rsquo;t mentioned, I\u0026rsquo;d like to hear about them: jsole@pii.services.\nSources # DICOM PS3.4, Annex C, Query/Retrieve Service Class: https://dicom.nema.org/medical/dicom/current/output/chtml/part04/chapter_C.html. Information models in C.2 and C.3; attribute matching, including the archive\u0026rsquo;s latitude on name matching, in C.2.2.2; hierarchical versus relational search in C.4.1.2; the identifier rules, Instance Availability, and Retrieve AE Title in C.4.1.1.3.2; status codes in Table C.4-1; required and optional keys per level in C.6, with the additional attributes such as the counts, Modalities in Study, and Study Update DateTime in Table C.3-1. DICOM PS3.6, Data Dictionary, for the attribute names and tags used above: https://dicom.nema.org/medical/dicom/current/output/chtml/part06/PS3.6.html. Everything about result caps, stale counts, and what archives actually do is from my own work and is stated as experience, not standard. Revised November 11, 2026: corrected two overstatements. The standard does define Instance Availability and Study Update DateTime as optional query attributes; the earlier text said neither existed. Added the standard\u0026rsquo;s rule on absent versus empty return keys, and a note on name-matching latitude. Patient Root has four levels, Study Root three; the earlier text said four for both.\n","date":"9 November 2026","externalUrl":null,"permalink":"/posts/what-c-find-can-and-cant-tell-you-about-an-archive/","section":"Posts","summary":"","title":"What C-FIND Can and Can't Tell You About an Archive","type":"posts"},{"content":"","date":"9 November 2026","externalUrl":null,"permalink":"/tags/meta/","section":"Tags","summary":"","title":"Meta","type":"tags"},{"content":"","date":"9 November 2026","externalUrl":null,"permalink":"/tags/site/","section":"Tags","summary":"","title":"Site","type":"tags"},{"content":"Welcome. This is the website of Premier Imaging Informatics, which is to say it\u0026rsquo;s mine. I\u0026rsquo;m John Sole, and I\u0026rsquo;ve spent the last thirty years in medical imaging: first behind a CT scanner, then running PACS inside hospitals, then on the vendor side, working out how an enterprise archive fits into everything a hospital already runs, and since 2018 as an independent consultant working with health systems on their imaging infrastructure.\nI\u0026rsquo;ve built this site for one reason: to write.\nMost of what I know, I learned by being the person who had to make something work when the documentation didn\u0026rsquo;t match the wire, or when two systems that were both \u0026ldquo;standards compliant\u0026rdquo; refused to talk to each other. That knowledge mostly lives in engagement notes and in my head, where it does nobody else any good. Writing it down is the fix.\nWhat to expect here\nA new piece every week or so, more often while the backlog is being written down, on topics like these:\nWhat the DICOM and HL7 standards actually say, as opposed to what vendors and folklore say they say, and how to find out for yourself. Methods for migrations, verifications, and archive analysis that don\u0026rsquo;t depend on a particular vendor\u0026rsquo;s tools. Field notes from production problems, written at the level of the protocol and the query, with the names filed off. I hold myself to a simple rule: where a claim would be challenged by someone who knows this field, I cite the standard or the paper. Where numbers appear, the method behind them is shown. The rest is experience, and I\u0026rsquo;ll say so when it is.\nThe Archives\nIf you want to see where this started, The Archives hold the articles I wrote from 2008 to 2010 on a site called JS PACS, when I was a working PACS administrator. Dated, lightly cleaned up, otherwise as they were. Nearly twenty years on, the problems have changed less than you\u0026rsquo;d think.\nThe first real piece is already up: What C-FIND Can and Can\u0026rsquo;t Tell You About an Archive. If you work with imaging systems and want to know when something new is posted, the RSS feed is the simplest way. I\u0026rsquo;m also at jsole@pii.services.\n","date":"9 November 2026","externalUrl":null,"permalink":"/posts/welcome/","section":"Posts","summary":"","title":"Welcome to pii.services","type":"posts"},{"content":"Originally published on JS PACS, August 31, 2010.\nIt is that time again for hi-res monitor replacement discussions between two highly competitive vendors. After a week of use with each of the monitors, and competitive pricing from both, I am looking to the JS PACS community for other experiences with either vendor. I am hoping to hear the good, the bad, and the ugly.\nI personally like both monitors, and each offers the latest array of fleet management along with remote calibration and reporting tools.\nAs with anything, it is hard to gauge what a device will actually do until you have stressed it for a year or more, so I am hoping to hear from those of you who have.\n","date":"31 August 2010","externalUrl":null,"permalink":"/archive/2010-08-31-hi-res-monitors-barco-and-image-systems/","section":"The Archives","summary":"","title":"Hi-Resolution Monitors: Barco and Image Systems","type":"archive"},{"content":"","date":"31 August 2010","externalUrl":null,"permalink":"/tags/monitors/","section":"Tags","summary":"","title":"Monitors","type":"tags"},{"content":"","date":"31 August 2010","externalUrl":null,"permalink":"/tags/reviews/","section":"Tags","summary":"","title":"Reviews","type":"tags"},{"content":"Take a walk through the archives. JS PACS was a site I ran from 2008 to 2010, when I was in the trenches as a PACS administrator, as a way of sharing what I was working on at the time. There may be a gem or two in here for new PACS admins, or a refresher for experienced ones, but mainly I\u0026rsquo;ve kept these for historical reasons.\nThey are republished as written and dated as they were. Dictation errors and typos have been cleaned up; the opinions, and the 2009 facts, have not.\n","date":"31 August 2010","externalUrl":null,"permalink":"/archive/","section":"The Archives","summary":"","title":"The Archives","type":"archive"},{"content":"","date":"21 April 2010","externalUrl":null,"permalink":"/tags/mobile/","section":"Tags","summary":"","title":"Mobile","type":"tags"},{"content":"Originally published on JS PACS, April 21, 2010.\niPads and imaging, what an exciting platform that will be when it develops. How many of you out there have your iPad yet? I have mine and I am eagerly awaiting some quality PACS applications for this new platform. OsiriX has the iPhone app, but as of today they haven\u0026rsquo;t written it to take advantage of the iPad\u0026rsquo;s great screen, and the iPhone app enlarged on the iPad just doesn\u0026rsquo;t cut it. I haven\u0026rsquo;t tried the Merge application on the iPad yet. I do have it on the iPhone and wasn\u0026rsquo;t overly impressed with its proprietary nature, and I won\u0026rsquo;t even consider trying it on the iPad until Merge puts out an iPad-specific application.\nIf you have your PACS viewers available on Citrix, you are already a good portion of the way there. We don\u0026rsquo;t support remote viewing over Citrix, so I can\u0026rsquo;t view images that way, but it is amusing to see a Windows application running on the iPad through Citrix. It is also nice to have access to the EMR through the iPad. We are a MediTech shop and it runs very nicely over the iPad Citrix receiver.\nThe iPad makes VPN configuration a simple process, and I think many organizations can expect to see an increasing number of requests to hook iPads into the system. We are preparing for it and are even considering offering some limited level of support for the OS X platform now that this new tool has come out.\nAnother way I am looking to use the iPad is for dashboards. How great would it be to walk the halls with all of your imaging systems\u0026rsquo; data right in the palm of your hand? Many web-based dashboard viewers are already primed to be viewed on the iPad, but remember that the iPad runs Apple\u0026rsquo;s Safari browser and some systems just don\u0026rsquo;t run right on it (I don\u0026rsquo;t blame that on Safari, though).\nThere are numerous ways to use the iPad in healthcare, especially in imaging. How are you using, or how would you use, the iPad in your daily activities?\n","date":"21 April 2010","externalUrl":null,"permalink":"/archive/2010-04-21-the-ipad-and-pacs/","section":"The Archives","summary":"","title":"The iPad and PACS","type":"archive"},{"content":"","date":"21 April 2010","externalUrl":null,"permalink":"/tags/viewers/","section":"Tags","summary":"","title":"Viewers","type":"tags"},{"content":"Originally published on JS PACS, December 31, 2009.\nWhat a busy year. The organization I am currently supporting has undergone some major changes.\nWe had a major upgrade to the MediTech HIS/RIS (Client Server), we\u0026rsquo;ve implemented digital mammography and voice-recognition dictation, and we just signed the order for our second-generation cardiology PACS. Oh yeah, another PACS merger as well. Because of all the projects, this was the first time I\u0026rsquo;ve missed the SIIM conference, but I will be returning next year up in Minneapolis and hope to provide live updates like I did from the 2008 conference in Seattle.\nBecause of the high volume of work, I have been lax in spending the needed time creating content to stimulate discussion on the JS PACS website. However, with the new year upon us, I am renewing my commitment to push this page forward and make it useful for the community.\nOur membership has grown from 75 in mid-2009 to 125 registered members today. With that many people, we should have enough to generate some interesting conversation, and I offer each of you the opportunity to post in our discussion forum or share a story that can be published on the front page of the site.\nSome topics I plan on writing about in the first few months of 2010 include:\nLessons learned from the voice-recognition dictation implementation. Review of the Hologic mammography project. Updates on the cardiology project we are about to embark on. Review of what happened to Emageon this past year. Discussion of the new hi-res color monitors on the market. Using Macs for PACS. Topics based on suggestions or contributions from other members. I hope this last post of 2009 finds your systems running well, you in good health, and facing good projections for 2010.\nHappy New Year!\nJohn\n","date":"31 December 2009","externalUrl":null,"permalink":"/archive/2009-12-31-happy-new-year-final-post-for-2009/","section":"The Archives","summary":"","title":"Happy New Year: Final Post for 2009","type":"archive"},{"content":"","date":"31 December 2009","externalUrl":null,"permalink":"/tags/year-in-review/","section":"Tags","summary":"","title":"Year in Review","type":"tags"},{"content":"","date":"7 August 2009","externalUrl":null,"permalink":"/tags/cad/","section":"Tags","summary":"","title":"CAD","type":"tags"},{"content":"","date":"7 August 2009","externalUrl":null,"permalink":"/tags/mammography/","section":"Tags","summary":"","title":"Mammography","type":"tags"},{"content":"Originally published on JS PACS, August 7, 2009.\nAs we progress through our digital mammography implementation, new questions are being raised every day. We are often provided answers by the vendor; however, I feel some vendors are quick to provide answers that steer us toward the path of least resistance for them.\nThe specific instance this time is the question of what to do with mammography CAD data. What is the standard of care in the mammography world regarding the use of CAD in digital mammography?\nAs we begin implementing a digital mammography department, we are faced with the decision of how to handle CAD markings on digital images. We are being told that nobody stores CAD markings, because of the liability: if CAD identifies a spot on an image, the spot is not worked up by the radiologist, and it proves to be positive, the radiologist can be held liable.\nNow, I am of the school of thought that if you make mention of a spot identified by CAD and the CAD overlay is not stored, we can also be held liable, since we cannot reproduce the image that identified the area of interest.\nWe have had this discussion with the risk management group in our organization, and it was stated that we have to identify the standard of care by evaluating what others who have been using such CAD systems are doing.\nSo I am interested in hearing how everybody is handling CAD overlays in their digital mammography environment.\n","date":"7 August 2009","externalUrl":null,"permalink":"/archive/2009-08-07-mammography-cad-standard-of-care/","section":"The Archives","summary":"","title":"Mammography CAD: Standard of Care","type":"archive"},{"content":"","date":"7 August 2009","externalUrl":null,"permalink":"/tags/policy/","section":"Tags","summary":"","title":"Policy","type":"tags"},{"content":"","date":"23 June 2009","externalUrl":null,"permalink":"/tags/dictation/","section":"Tags","summary":"","title":"Dictation","type":"tags"},{"content":"","date":"23 June 2009","externalUrl":null,"permalink":"/tags/implementation/","section":"Tags","summary":"","title":"Implementation","type":"tags"},{"content":"Originally published on JS PACS, June 23, 2009.\nI\u0026rsquo;m about to embark on an implementation of the MedQuist SpeechQ voice-recognition dictation product, and I\u0026rsquo;m interested in hearing how others who use the same system felt their implementation went.\n","date":"23 June 2009","externalUrl":null,"permalink":"/archive/2009-06-23-medquist-speechq-an-implementation-begins/","section":"The Archives","summary":"","title":"MedQuist SpeechQ: An Implementation Begins","type":"archive"},{"content":"","date":"12 June 2009","externalUrl":null,"permalink":"/tags/career/","section":"Tags","summary":"","title":"Career","type":"tags"},{"content":"","date":"12 June 2009","externalUrl":null,"permalink":"/tags/certification/","section":"Tags","summary":"","title":"Certification","type":"tags"},{"content":"","date":"12 June 2009","externalUrl":null,"permalink":"/tags/opinion/","section":"Tags","summary":"","title":"Opinion","type":"tags"},{"content":"Originally published on JS PACS, June 12, 2009.\nThere is an interesting discussion about the legitimacy of the PACS certification and recertification process on another PACS discussion board. Some see it as unnecessary for our profession. The following is my response to those who say it is not necessary or not worth it.\nIt is interesting to find that PACS administrators themselves don\u0026rsquo;t see the value of certification. Comments such as \u0026ldquo;money grab\u0026rdquo; and \u0026ldquo;not enough value to the cert to maintain it\u0026rdquo; all seem self-serving to me.\nI have started to notice more and more that when people complain about something, there is often an underlying reason it doesn\u0026rsquo;t serve them well, regardless of the overall benefit to the community.\nThe purpose of a certification, and the PACS certification in particular, is to demonstrate a basic aptitude in the PACS environment. Take a look at how far PACS administration has come. It used to be the individual from radiology who was \u0026ldquo;good with computers\u0026rdquo; who was put in charge of an internal system that served nobody but the radiology department. We have now grown to enterprise imaging, where the systems we manage encompass anything deemed a medical image. We have graduated from radiology to \u0026ldquo;-ology,\u0026rdquo; and we need to keep our knowledge up with the impressive evolution we face every day.\nHowever much our systems evolve and move into alignment with standardized healthcare IT, there is still something that separates imaging informatics from HIS, RIS, ED, pharmacy, and other clinical systems, and it is that distinction I think we all thrive on.\nThe certification process should be seen as a method by which we demonstrate that we can provide that extra level of expertise to a healthcare organization.\nSure, day-to-day activities such as server reboots, DICOM data editing for QA, and workstation management are all skills that can be assessed in an interview. But understanding why a particular device needs to be configured a certain way to successfully query a modality worklist, or knowing what to ask a vendor from both a clinical and a technical standpoint, is what certification helps represent.\nAs an organizational leader, wouldn\u0026rsquo;t you rather know that the individual you are hiring to implement your $2.5 million PACS knows the ins and outs of radiology, imaging, and IT before hiring him or her? Or would you rather wait until you are in the middle of RFP discussions to find that the individual you are expecting so much of can\u0026rsquo;t read a DICOM conformance statement to determine whether the DICOM objects created by your new high-tech equipment can even be sent into the PACS?\nTo the comment that \u0026ldquo;certification is not necessarily correlated with ability,\u0026rdquo; it can also be said that you can have all the skill in the world, but if you don\u0026rsquo;t have the degree or certification to demonstrate it, you won\u0026rsquo;t be considered.\nBetween ABII and PARCA, PACS certification isn\u0026rsquo;t even ten years old. Ten years from now, when an organization will not interview you without an imaging informatics certification, don\u0026rsquo;t find yourself unable to compete. Remember, this isn\u0026rsquo;t about you as an individual; it\u0026rsquo;s about supporting our profession and propelling us into an environment where we can demonstrate our knowledge.\n","date":"12 June 2009","externalUrl":null,"permalink":"/archive/2009-06-12-value-of-pacs-certification/","section":"The Archives","summary":"","title":"Value of PACS Certification and Recertification","type":"archive"},{"content":"Originally published on JS PACS, May 27, 2009.\nThe government recently released open-source software designed to allow federal agencies and private organizations to transfer healthcare information between their systems.\nI am a fan of open source, but I have some initial concerns about the government running various aspects of our proposed national healthcare record on open-source software.\nIf the software is open source, I fear it will be more difficult to protect the healthcare information transferred through it. More people would have access to the software, or be able to create hooks into it for various purposes. Additionally, could the resources needed to manage an open-source project like this become more expensive than privately developed software built under a government contract? Remember, open-source software has hidden costs in the specialized people needed to manage it.\nOn the other hand, open source certainly offers flexibility and ingenuity, as there can be many people working on various aspects of the system, designing robust and customized solutions for almost any scenario.\nAgain, I am a fan of open-source software, but without all the details yet, it is hard to know whether open source is really the right choice for the government. Regardless, it will be interesting to see how this develops in the next year or two.\n","date":"27 May 2009","externalUrl":null,"permalink":"/archive/2009-05-27-government-open-source-and-healthcare-it/","section":"The Archives","summary":"","title":"Government, Open Source, and Healthcare IT: Is It a Good Fit?","type":"archive"},{"content":"","date":"27 May 2009","externalUrl":null,"permalink":"/tags/healthcare-it/","section":"Tags","summary":"","title":"Healthcare IT","type":"tags"},{"content":"","date":"27 May 2009","externalUrl":null,"permalink":"/tags/open-source/","section":"Tags","summary":"","title":"Open Source","type":"tags"},{"content":"Originally published on JS PACS, May 22, 2009.\nI typically don\u0026rsquo;t like to discuss vendor-specific problems in front-page articles, but I\u0026rsquo;m going to break that rule today. I\u0026rsquo;m hoping this article reaches many people, but specifically cardiology PACS administrators who manage the Agfa HeartLab cardiology PACS. I\u0026rsquo;m currently managing this C-PACS and find some recurring behaviors that are not only problematic but result in significant manual work to keep the system in a usable state.\nWhat has been occurring in my implementation is routine loss of the DICOM services. If you\u0026rsquo;re familiar with Agfa as a cardiology solution, you\u0026rsquo;ll know that they run objects called DICOM Labs. Each DICOM Lab is responsible for image transfer from one particular imaging device. We have customized HeartLab in that we don\u0026rsquo;t store directly to the cardiology PACS; we store to the radiology PACS (which contains our enterprise archive) and forward a copy to the cardiology PACS for viewing. Since we only have one device sending to the cardiology PACS, we only have one DICOM Lab, and one would think that without the typical 10 or 15 DICOM Labs running simultaneously we would see high levels of performance. We do not.\nThe most frustrating problem I have with this system is that every so often (20 to 24 hours) the DICOM services hang on the server. There is really no indication that the services have hung, other than that an occasional spot check of our archive\u0026rsquo;s auto-router shows anywhere from 1,500 to 2,000 images pending transfer to HeartLab. Usually, logging on to the server and performing a stop and start of the DICOM services kicks all the processes back into motion. Sometimes, however, a complete reboot of the C-PACS server is necessary. While the resolution is manual, it is not overly lengthy; but the fact that it has to occur every day is unacceptable. Between the time the PACS administrator spends fixing the problem and the time lost by cardiologists waiting for image transfers, this cardiology solution significantly slows down workflow throughout the day.\nI\u0026rsquo;m curious to know whether other cardiology PACS administrators experience similar issues, specifically with the Agfa solution, and what types of resolutions you\u0026rsquo;ve developed.\n","date":"22 May 2009","externalUrl":null,"permalink":"/archive/2009-05-22-agfa-heartlab-performance-issues/","section":"The Archives","summary":"","title":"Agfa HeartLab: Performance Issues or Normal Behavior?","type":"archive"},{"content":"","date":"22 May 2009","externalUrl":null,"permalink":"/tags/cardiology-pacs/","section":"Tags","summary":"","title":"Cardiology PACS","type":"tags"},{"content":"Originally published on JS PACS, May 13, 2009.\nThe day of the vendor-provided workstation is coming to an end. For so long we have heard that we have to purchase our PACS workstations pre-built and pre-configured. Well, I think the time is upon us to take control of our workstations. Your organization can gain a lot by moving PACS workstation development in house. You can save money, standardize the workstation build, and use your organization\u0026rsquo;s own software, such as anti-virus and patch management.\nI am currently in the process of building a Centricity 1000 workstation from scratch, and I want to say that it is not the mysterious process the vendors would have you believe. We simply purchased a license, obtained the software, and bought the recommended hardware. In fact, we purchased a workstation well over the minimum specifications, so we know we\u0026rsquo;ll get great performance out of it.\nThe most arduous part of building this workstation so far consisted of two issues. The first was getting XP installed on the HP workstation (see the article on installing Windows XP on the HP xw series), and the other was getting the license. The license acquisition wasn\u0026rsquo;t difficult; it just took some time to get an account on the GE licensing system and register the Centricity serial number I had received in order to generate the license.\nWith the workstation up and running and the license file in hand, it was rather trivial to install the cardiology software. I have it all installed and configured, but I haven\u0026rsquo;t given it the true test of sending DICOM images to the workstation. I am not that worried about that portion of the testing, however, because from this point it is just a matter of tweaking settings.\nThe most important aspect of this process for me was a reaffirmation that an organization really can be successful building its own workstations, and that software-only solutions can be a viable part of the strategy for maintaining workstations and keeping them refreshed. The biggest advantages to purchasing, building, and maintaining your own workstations are that you can shop for the best prices, standardize your hardware, and align the software with your organization\u0026rsquo;s overall strategy (virus protection and so on).\n","date":"13 May 2009","externalUrl":null,"permalink":"/archive/2009-05-13-build-your-own-workstations/","section":"The Archives","summary":"","title":"Workstation Management: Build Your Own Workstations","type":"archive"},{"content":"","date":"13 May 2009","externalUrl":null,"permalink":"/tags/workstations/","section":"Tags","summary":"","title":"Workstations","type":"tags"},{"content":"Originally published on JS PACS, May 8, 2009.\nThis troubleshooting tip relates to rebuilding PACS workstations on the HP xw series platform. A lot of PACS workstations these days run on this platform, many of them the HP xw4300 or xw8600. There are many models in the series, but their price and performance have been very attractive, and they are one of our preferred platforms.\nThis issue doesn\u0026rsquo;t occur all the time, but some of these workstations hit you with the dreaded BSOD (Blue Screen of Death, with an error of 0x0000007B, which is a device-inaccessible error) when trying to install Windows XP Pro from the install disc.\nThe issue is related to the onboard RAID controller that some of these devices come with, or the lack of LSI drivers for the hard drive controller. Either will cause the Windows install to fail, but here are some steps to get through it.\nFirst, if you get the BSOD on the Windows install, check the BIOS, and under Storage Options disable the RAID controller, setting it to IDE Independent. This will allow the Windows installer to see the boot sector of the drive and prevent the install from failing.\nIf you still get the error, you may need to add the LSI drivers during the Windows install. There are two ways to do this. First, download the correct LSI drivers for your model from the HP website and extract them onto a workstation you have access to. You can then put them on a floppy, and during the Windows install there is a point where you will see \u0026ldquo;Press F6 to install third party SCSI drivers\u0026rdquo; at the bottom of the screen. Press F6 and you will be presented with a section that allows you to load those drivers into the install process. Given that not many workstations ship with floppy drives these days, the second method might be the better solution.\nThat second solution involves creating a new install disc that contains the LSI drivers. There is a great free product called nLite that will let you do this. There is good documentation on the nLite site, so I won\u0026rsquo;t go into the details of using the software, but suffice it to say that this tool lets you rebuild your install disc and include the drivers you need (such as the LSI drivers). As a side note, there are a lot of other things you can add to the install disc, such as service packs, additional programs, and registry edits, that will all be included in the install.\nOnce you have the disc built, pop it in the CD drive, fire up the workstation, and the install should go smoothly.\n","date":"8 May 2009","externalUrl":null,"permalink":"/archive/2009-05-08-installing-windows-xp-on-hp-xw-workstations/","section":"The Archives","summary":"","title":"PACS Troubleshooting Tips: Installing Windows XP on the HP xw Series Workstations","type":"archive"},{"content":"","date":"8 May 2009","externalUrl":null,"permalink":"/tags/windows/","section":"Tags","summary":"","title":"Windows","type":"tags"},{"content":"Originally published on JS PACS, May 5, 2009.\nOn April Fool\u0026rsquo;s Day, the world was set to absorb the wrath of the Conficker worm. After April 1 came and went, many thought the scope of the virus was a hoax, but in yesterday\u0026rsquo;s edition of Health Imaging \u0026amp; IT, an article reported that Conficker was beginning to make its presence known on medical imaging devices. The article started out making it sound like an MRI scanner was infected, then clarified by saying that engineers monitoring the internet had seen \u0026ldquo;an imaging machine used to review high-resolution images\u0026rdquo; reaching out over the internet for instructions, presumably from the programmers who created Conficker. That machine sounds like nothing more than the average 3D workstation that comes with many scanners these days, and that brings me to the point of this discussion: how do you handle virus protection and patch management on your PACS equipment and imaging devices?\nOften, actually almost always, vendors of medical imaging equipment don\u0026rsquo;t let you touch their products when it comes to putting your own software on them. This puts the organization in a precarious position. After some time, the trial anti-virus software installed on the workstation expires, leaving the device unprotected. Even when it is protected, the AV software isn\u0026rsquo;t regularly updated, so the virus definitions aren\u0026rsquo;t current. I think it is time for vendors to start allowing us to put our organizational anti-virus software on these devices.\nPatch management is also a problem. Microsoft released a security patch for the Conficker worm, but vendors often don\u0026rsquo;t supply users with such patches in a package that can be easily installed on their devices. As system administrators, we can go install them ourselves, but then we are faced with the vendor potentially withdrawing support because we installed unapproved software on the device.\nSo, is it the responsibility of the vendor to develop better methods of applying anti-virus protection and patch management, or do we, as system administrators, take it upon ourselves to deploy these protective measures on our equipment?\nReference: \u0026ldquo;Conficker computer virus snakes its way into medical devices,\u0026rdquo; HealthImaging.com, May 2009.\n","date":"5 May 2009","externalUrl":null,"permalink":"/archive/2009-05-05-patch-management-and-anti-virus-on-pacs-equipment/","section":"The Archives","summary":"","title":"PACS Equipment: Patch Management and Anti-Virus Software","type":"archive"},{"content":"","date":"5 May 2009","externalUrl":null,"permalink":"/tags/security/","section":"Tags","summary":"","title":"Security","type":"tags"},{"content":"Originally published on JS PACS, April 23, 2009.\nBe sure to develop a policy regarding the installation and maintenance of imaging devices and peripheral PACS equipment. Sometimes the line between organizational PCs and medical imaging equipment becomes blurred, and questions arise about who supports what. Consider anything attached to imaging equipment to be your domain, and take the stance that no equipment related to PACS can be worked on without your knowledge. I am not suggesting that you keep your organization\u0026rsquo;s technical services group from working on PCs around imaging equipment, just that they verify with the PACS team any work they are about to perform, to ensure it won\u0026rsquo;t impact workflow. Nobody wants to run a dictatorship over PACS, but having information pass through you will prevent issues from happening in your organization\u0026rsquo;s imaging informatics flow without your knowledge.\nScenario: an oncology PC used for treatment planning was having some issues, and the technical services team inadvertently altered its IP address, breaking DICOM communication. It took a day for the IS team to figure out that the IP address had to be reset to its original setting. Because of that, an entire day of work in the oncology department was lost, and some patients had to wait longer than normal since the department was down to one treatment planning device. Considering that this was a DICOM device, the PACS team was distressed to learn that oncology had been unnecessarily impacted for an entire day. The details of what required the modification of the device\u0026rsquo;s IP, and how it was done without the knowledge of the PACS team, are still being uncovered.\nWith an incident like this, it is clearly time to review policies and procedures with all parties involved, to ensure that the organization\u0026rsquo;s DICOM devices and medical imaging equipment are worked on by, or with oversight from, the PACS team.\nBe sure your organization has policies and procedures in place for the management of PACS-related equipment. Also be sure the policy is communicated to the organization (clinical department managers, IS, administration, and so on), as you never know where an issue with imaging informatics may surface. Whether it is a new imaging device, maintenance on an existing device, or a PC that interfaces with imaging devices, you need to know about it.\n","date":"23 April 2009","externalUrl":null,"permalink":"/archive/2009-04-23-pacs-asset-management/","section":"The Archives","summary":"","title":"PACS Policies and Procedures: PACS Asset Management","type":"archive"},{"content":"","date":"22 April 2009","externalUrl":null,"permalink":"/tags/cd-import/","section":"Tags","summary":"","title":"CD Import","type":"tags"},{"content":"Originally published on JS PACS, April 22, 2009.\nToday I had the opportunity to demo the Codonics Integrity CD importing device. If you haven\u0026rsquo;t seen it, there is information on it at the vendor\u0026rsquo;s site.\nIt is a device that looks similar to a Mac Mini, if you are familiar with that Apple product. There is no keyboard, mouse, or monitor. The operating system and the system and DICOM configuration files are kept on a thumb drive that plugs into the back of the Integrity. The box itself is nothing more than a CD/DVD reader and an 80 GB hard drive.\nThe beauty of this system is that it can be put anywhere, and all a user has to do is stick a DICOM CD or DVD in the drive. After it reads the disc and stores the images locally, it spits the disc back out for the user to return to the patient. The file-room staff can then navigate to the device in a web browser, reconcile the imported studies to the modality worklist or make manual patient edits as needed, and push the studies to PACS.\nThe device works wonderfully from a clinical perspective, offering ease of use and speed. It is in some of the IT aspects that I feel it falls short.\nThe device does allow you to configure it for DHCP, a nice change in the DICOM world of static TCP/IP configurations, and you can join it to your organization\u0026rsquo;s domain and use DNS to browse to it. Where I feel it comes up short is the user database. Some may think this is trivial, but given that it is a fairly advanced device, Active Directory authentication would certainly be a beneficial feature. Maintaining disparate user databases on DICOM equipment is time-consuming and tedious, so Codonics should consider developing that in a future release.\nI will close by saying this is a review and nothing more. I have not purchased this product, and I am not encouraging or discouraging others from purchasing it; I just wanted to share my thoughts after being able to demo the device today.\n","date":"22 April 2009","externalUrl":null,"permalink":"/archive/2009-04-22-codonics-integrity-a-review/","section":"The Archives","summary":"","title":"Codonics Integrity: A Review","type":"archive"},{"content":"","date":"23 March 2009","externalUrl":null,"permalink":"/tags/c-move/","section":"Tags","summary":"","title":"C-MOVE","type":"tags"},{"content":"Originally published on JS PACS, March 23, 2009.\nI was recently working on a PACSGear CD burner. The software was PACSGear MediaWriter version 1.0.2.25990, and when retrieving a study from PACS to burn to a CD I was constantly getting an error. The error from the MediaWriter logs was:\nThread MoveManager::Start-\u0026gt;An exception occurred while C-MOVE with AE C001.\nThis made me think there was a device somewhere with an AE title of C001. After looking for that AE in the configuration files, I started searching online and found that C001 was one of five error codes for C-MOVE operations.\nI found this information in a discussion about the Conquest DICOM server. The error codes are as follows:\nCode Meaning C001 No destination AE specified C002 Empty destination AE specified C003 Destination not found or allowed C004 Search error C005 Destination not available I am curious whether anybody else has encountered C-MOVE errors with the PACSGear MediaWriter similar to mine.\n","date":"23 March 2009","externalUrl":null,"permalink":"/archive/2009-03-23-dicom-troubleshooting-pacsgear-mediawriter/","section":"The Archives","summary":"","title":"DICOM Troubleshooting: PACSGear MediaWriter","type":"archive"},{"content":"","date":"7 March 2009","externalUrl":null,"permalink":"/tags/document-scanning/","section":"Tags","summary":"","title":"Document Scanning","type":"tags"},{"content":"Originally published on JS PACS, March 7, 2009. Part of the Radiology Workflow series. The two diagrams from the original post, a pros-and-cons table and a workflow chart, did not survive the archive.\nOne of the lesser-used functions of many PACS systems is a paperless radiology workflow. This page discusses some of the things you should consider when developing a paperless workflow for your radiology department. Paperless workflow can shave time off report turnaround, a very important metric for measuring quality in any radiology department.\nAn analysis of the documentation that travels through the radiology department turns up quite a few documents. The most common include:\nPatient questionnaires for MRI Contrast reaction forms for CT Consent forms Ultrasound worksheets Procedure requisitions All of these documents become part of the patient\u0026rsquo;s record or get turned in to the radiologist so that the study can be read. A radiologist who must wait to have documents in hand before reading a study loses time, which comes from the time it takes a technologist to get the documents to the radiologist.\nWhen a paperless solution is deployed, the radiologist has those same documents in PACS when they open a study to read, and a quicker report turnaround can be achieved.\nHow document scanning is deployed is a big decision in itself, since you gain certain benefits and pay certain prices with either an integrated or a third-party solution. Each has advantages and disadvantages.\nOnce you have figured out the type of document scanning you need, select it and then focus on the workflow.\nIt is up to the radiology department as a team to develop the best workflow around the paperless solution. It is up to you as the PACS administrator to make sure that everyone making the decision knows the pros and cons of each choice. Sometimes the choice is driven by the functionality of the PACS, other times by cost, and other times by radiology need. Think about the choices wisely and pick the scanning solution that best fits your needs, but do pick one. Your department cannot afford to be paper-driven.\n","date":"7 March 2009","externalUrl":null,"permalink":"/archive/2009-03-07-paperless-radiology-workflow/","section":"The Archives","summary":"","title":"Paperless Radiology Workflow: Considerations for the PACS Administrator","type":"archive"},{"content":"Originally published on JS PACS, March 7, 2009. Part of the Radiology Workflow series.\nA common question I hear new PACS administrators ask is, \u0026ldquo;What is meant by prefetching?\u0026rdquo;\nIn the PACS environment, a prefetch is when studies are retrieved from the permanent archive and restored to the local cache. This typically happens when an order for a particular patient is entered into the RIS. When that order comes through to the PACS via an HL7 message, the system goes and retrieves the appropriate prior studies on that same patient. These are typically of the same modality and body part as the current order. Advanced prefetching can be based on a combination of factors, such as modality and body part.\nAn example would be a chest x-ray. If a patient is having a chest x-ray today and in the past had some chest CT scans as well as chest x-rays, you would only want to prefetch the previous chest x-rays. Conversely, if that same patient was coming in for a chest CT, you would want to pull back from the archive all prior chest x-rays and chest CTs.\nSpending some time with your radiologists discussing which studies are considered relevant priors is important. If the time is not spent in advance, it will be lost at interpretation time. When a radiologist opens a study to read and the most relevant prior is not available, it has to be manually retrieved right then. That takes additional resources and slows down report turnaround time, which is an important radiology workflow metric. Another area affected by poorly planned retrieval is hanging protocols. If hanging protocols are built to include specific prior studies and those studies are not correctly retrieved from the archive, the hanging protocols will not work as well.\nAgain, spending time with the radiologists and having a thorough discussion of which relevant priors are needed for reading is imperative. Areas where extra time should be spent are the common multi-modality body parts such as the abdomen, pelvis, and chest.\n","date":"7 March 2009","externalUrl":null,"permalink":"/archive/2009-03-07-understanding-the-pacs-prefetching-process/","section":"The Archives","summary":"","title":"Understanding the PACS Prefetching Process","type":"archive"},{"content":"Originally published on JS PACS, March 7, 2009. Part of the Radiology Workflow series.\nWhen planning a radiology image QA program, you must make sure to provide the imaging technologists with the appropriate tools to do the work. This means installing video cards and monitors that can be calibrated and measured to the DICOM grayscale standard. Two-megapixel monitors at 21 inches are sufficient to show diagnostic-quality images for MRI, CT, ultrasound, and other modalities, with the exception of general x-ray and mammography. Monitors such as the Planar PX212 are sufficient and affordable enough to purchase and sprinkle throughout each area.\nFor general x-ray, you will want to purchase at least one three-megapixel monitor and place it in a central location for image evaluation. For mammography, the FDA requires a five-megapixel monitor for diagnostic viewing; there are numerous additional QA requirements in mammography that are outside the scope of this discussion.\nAs a PACS administrator, recommend to your leadership team that an image QA program be set up so that all technologists see images in a way similar to how the radiologist will see them. This helps ensure that by the time the images are available for the radiologist to read, they have already been viewed as they will appear to the radiologist. Also mention to your leadership team that there are various solutions available that allow you to build a quality program, which ultimately helps reduce turnaround time.\n","date":"7 March 2009","externalUrl":null,"permalink":"/archive/2009-03-07-basics-of-a-radiology-image-qa-program/","section":"The Archives","summary":"","title":"Basics of a Radiology Image QA Program","type":"archive"},{"content":"","date":"7 March 2009","externalUrl":null,"permalink":"/tags/qa/","section":"Tags","summary":"","title":"QA","type":"tags"},{"content":"Originally published on JS PACS, March 7, 2009. This introduced the Radiology Workflow series; the QA, paperless, and prefetching pieces that followed are also in the archive.\nRadiology workflow! It is where the money is in the PACS world. Even the most technically superior PACS will not deliver the expected ROI if a department can\u0026rsquo;t get its electronic processes right.\nAs a PACS administrator, understanding the processes within the department helps you know where to look when specific incidents occur. A solid understanding of how information travels through the department will also let you analyze your PACS and make improvements when you are not getting the performance you expected. Installing a new PACS? This information will be instrumental in preparing for it.\nAs you progress through this section, you will find information about how a typical imaging department operates from the time an order is entered until the final report is signed.\nIf you are the IT-born PACS administrator, this section is critical for you. For the rad-tech-born PACS administrator, some of it will be review, but some of it will also help you understand what is happening behind the scenes in the HIS/RIS and PACS.\nTopics in the Radiology Workflow series include order entry specifics, modality worklist selection, image acquisition, study reading, and report generation.\n","date":"7 March 2009","externalUrl":null,"permalink":"/archive/2009-03-07-radiology-workflow-for-the-pacs-administrator/","section":"The Archives","summary":"","title":"Radiology Workflow for the PACS Administrator","type":"archive"},{"content":"","date":"5 March 2009","externalUrl":null,"permalink":"/tags/it-skills/","section":"Tags","summary":"","title":"IT Skills","type":"tags"},{"content":"","date":"5 March 2009","externalUrl":null,"permalink":"/tags/networking/","section":"Tags","summary":"","title":"Networking","type":"tags"},{"content":"Originally published on JS PACS, March 5, 2009. Part of the PACS IT Skills series. The diagram from the original post did not survive the archive.\nThe IP address, or Internet Protocol address, is an address assigned to a computer so that it can talk to other computers on a network. An address needs to be unique to the network segment it is on, but that same address can exist on another network. A few addresses are designated to be unique to the world and exist only once.\nWhen troubleshooting network issues, such as an image that won\u0026rsquo;t send to the PACS server, you can use the ping utility, which uses the IP address. It simply sends a small packet of information to another computer, and if the other computer receives that ping, meaning it is on the network and working, it sends a response back telling you it is alive.\nIf it helps to visualize, the address of a device can be compared to your street address, which is unique to your town but not unique to your state or country. There may be many 1035 Union Street addresses in the country; consider each town its own network segment.\nThis protocol is found on the third layer of the OSI model.\nAn IP address is built from four octets (eight binary digits each), each octet being one byte in length. An entire address is therefore four bytes long.\nIn an upcoming article, we\u0026rsquo;ll review the various classes of networks and how they work into subnets.\n","date":"5 March 2009","externalUrl":null,"permalink":"/archive/2009-03-05-the-ip-address-defined/","section":"The Archives","summary":"","title":"The IP Address Defined","type":"archive"},{"content":"Originally published on JS PACS, March 5, 2009. Part of the PACS IT Skills series.\nOperating systems, also known by the acronym OS, are the next topic in the IT Skills section.\nMost people are familiar with the Microsoft Windows platform; however, not all PACS systems run on Windows. This is why, as a PACS administrator, you will need to understand the different systems.\nThe OS is the software on which any workstation, server, laptop, PDA, or other computing device runs. The OS is responsible for sharing and coordinating all of the hardware resources on the device and allowing them to talk to each other.\nThere are three major OSs in use today: Windows, Unix/Linux, and Macintosh OS X.\nEach has its advantages. Windows is the most widely used OS; Unix/Linux is open source, so you can use it for free; and Mac OS X is very stable and has outstanding graphics capabilities.\nEach also has distinct disadvantages. Windows crashes fairly easily and has many security vulnerabilities; Unix/Linux is not a mainstream system and is therefore more difficult to adapt to widespread use in an organization; and Mac OS X runs on proprietary hardware from Apple, meaning you can\u0026rsquo;t put OS X on any hardware you would like.\nSome lesser-known systems include Solaris, BSD, QNX, and VxWorks. To my knowledge, there are no PACS systems running on any of these.\nAs a PACS administrator, I would recommend focusing on the Microsoft Server, XP, and Vista platforms, and learning Unix and Linux when you have the opportunity. Learning to operate in the Unix/Linux environment is a great way to build text-based computing skills. Anybody working as a PACS administrator at an Emageon PACS site can attest to that.\n","date":"5 March 2009","externalUrl":null,"permalink":"/archive/2009-03-05-operating-systems/","section":"The Archives","summary":"","title":"Operating Systems","type":"archive"},{"content":"","date":"5 March 2009","externalUrl":null,"permalink":"/tags/operating-systems/","section":"Tags","summary":"","title":"Operating Systems","type":"tags"},{"content":"Originally published on JS PACS, March 5, 2009. This was the introduction to a series; the Operating Systems and IP Address pieces that followed are also in the archive.\nWhat PACS IT skills do you need?\nThere is a laundry list of IT skills that every PACS administrator must have. This site will cover all of those skills, but initially the focus will be on what you need to get through your day.\nSome very basic IT concepts you will need to understand include: Networking 101, Workstation Management, Server Management, and Storage Management.\n","date":"5 March 2009","externalUrl":null,"permalink":"/archive/2009-03-05-pacs-it-skills/","section":"The Archives","summary":"","title":"PACS IT Skills: The Essential IT Skills Every PACS Admin Should Know","type":"archive"},{"content":"Originally published on JS PACS, March 5, 2009. A reprint of my article from rt-image, vol. 21, no. 35, September 2008.\nPACS is ubiquitous. At one time or another, whether attending the Society for Imaging Informatics in Medicine (SIIM) conference, researching the latest technologies in imaging informatics, or evaluating PACS vendors, we have all heard statements to that effect.\nThat means a second round of PACS implementation, consisting of ripping out the old and putting in the new, is underway. There can be many reasons an organization may have lost faith in its initial PACS vendor: not providing adequate support, annual costs that are too high, or not improving the software in the direction that is needed.\nOr maybe a vendor\u0026rsquo;s product does not fit into an organization\u0026rsquo;s workflow. That is a surprising reason, but it is happening to some users. During early implementations of PACS, the goal was to get images stored into PACS without much thought given to the other work that occurred in obtaining the images.\nFor your next PACS implementation, be sure to fix your workflow woes by making sure you understand how to better integrate PACS into your imaging department\u0026rsquo;s workflow.\nLooking at Workflow Nuances\nBefore discussing the integration of PACS and radiology workflow, a review of imaging workflow basics is necessary. In its simplest form, the workflow consists of: order entry; receiving the patient; imaging; evaluating the images; releasing the patient; submitting the images for interpretation; interpreting the images (dictation); transcription of the report; and, finally, signing the report.\nThese steps seem pretty unremarkable until you analyze the nuances that occur at the transitions between each phase. It is at those transition points that imaging informatics can really improve the overall workflow.\nIn the interpretation process, technology can make enormous improvements both during the transitions and in the interpretation itself. Extra effort should go into completely documenting existing workflows from the very beginning of the imaging process (order entry) through the signing of the final report. Only then should the project to go from analog to digital workflow begin.\nEarly Oversights\nOne of the primary things PACS vendors failed to provide in the early versions of their systems was functionality for integrating the radiology workflow nuances into the PACS workflow. In its standard form, a PACS allowed studies to be in one of two statuses: unread and read.\nThe basic PACS workflow was to image a patient, send the studies to PACS in an unread status, and have the radiologist interpret the study, changing it to read. All the other workflow that occurred in radiology never changed.\nOrders were provided via written scripts and entered into a hospital information system/radiology information system (HIS/RIS). This generated a printed paper requisition that served as a transportation slip, patient identifier, a tickler indicating a study needed to be performed, and, ultimately, a document handed to the radiologist stating that a study was ready to be read.\nProperly Integrated PACS\nNow, with a fresh picture of how radiology workflow used to occur (or still does, for those who didn\u0026rsquo;t integrate it properly), and an understanding of the stages a study passes through in its lifespan, taking the paper out of the workflow and moving into the digital era should become clearer.\nHere is a scenario with a properly integrated PACS:\nThe study is ordered and the patient is processed into the department. After arrival is completed electronically, the technologist, viewing a RIS-based worklist, sees the order appear on screen. The technologist can optionally print a small card for transporting an inpatient to the study. If the patient is an emergency department patient or an outpatient, the technologist simply calls the patient back to the imaging room. The technologist finds the study on the imaging device\u0026rsquo;s modality worklist, selects the correct patient, and begins the exam. In a completely integrated system, initiating the study on the imaging device changes the order\u0026rsquo;s status in the RIS to \u0026ldquo;begin procedure\u0026rdquo; or \u0026ldquo;start procedure.\u0026rdquo; Images from the study are sent to PACS. Once they arrive, they are in a \u0026ldquo;performed\u0026rdquo; status. The technologist moves to a PACS workstation, finds the study on a worklist set to display only studies not yet marked reviewed, and opens it. The technologist reviews each image, ensuring it is in the proper sequence, at an appropriate window/level, and of overall diagnostic quality. While the study is open, the technologist scans any paper documents generated during the study (contrast questionnaires, etc.) and provides the radiologist with pertinent patient history through a \u0026ldquo;study notes\u0026rdquo; type of tool. After confirming the study is diagnostic, scanning in documents, and adding study notes, the technologist changes the study from \u0026ldquo;performed\u0026rdquo; to \u0026ldquo;reviewed.\u0026rdquo; This is the equivalent of handing the radiologist a piece of paper saying the study is ready for interpretation. The study disappears from the technologist\u0026rsquo;s worklist (set to show only performed studies) and appears on the radiologist\u0026rsquo;s worklist (set to show only reviewed studies). The radiologist opens the study for interpretation and, through properly deployed hanging protocols, sees not only the images but is automatically presented with the patient history and any scanned documents. Using voice recognition, the radiologist begins a dictation session from within the open study. After interpretation, the radiologist either reviews and signs the report immediately (placing the study in a \u0026ldquo;reported\u0026rdquo; status) or sends it to transcription for verification (placing it in a \u0026ldquo;dictated\u0026rdquo; status). Within a short period the review is completed and the report is sent back to the radiologist for signing, at which point the study moves to \u0026ldquo;reported.\u0026rdquo; Easier Said Than Done\nWhile it is easy to document such a system on paper, correct implementation is a completely different matter. There are multiple components that need to be in place to allow such tight integration. Migration to a workflow like the one above cannot happen solely upon the purchase of a PACS.\nAn appropriately functioning HIS/RIS, voice-recognition dictation, and a document scanning solution all must be part of the implementation. If members of your project team balk at the higher prices that come with this functionality, explain to them why it is needed to improve overall workflow.\nAfter reviewing the ten steps above, I hope it is easier to see that simply allowing a study to be marked read or unread does not fit the bill anymore. Vendors have to work toward providing a PACS that fits the needs of the radiology department.\nSince the first generation of mainstream PACS ten years ago, some vendors have realized the need for a multiple-step process for radiology studies. However, whenever I visit SIIM or RSNA and ask a new vendor whether they provide multiple statuses for radiology studies, they still respond, with a curious look on their face, \u0026ldquo;Well, of course we do. Look here. See? Read and unread.\u0026rdquo;\nI try to explain why I look for more than two statuses; but if, after the first iteration of what I just described, I still get a blank stare, you can bet the conversation is pretty much over.\nPoints to Ponder\nThrough this article, I hope to have accomplished two things. First, I hope I have put into print what many PACS administrators have been trying to convey to vendors over the past two years: \u0026ldquo;Please build us a system that can adapt to what we do.\u0026rdquo;\nSecond, I hope I have conveyed to PACS administrators, radiology managers, and IT directors how important it is to find a vendor whose system provides these finer points of functionality. It is definitely worth the extra money to purchase this up front.\nIt will save you time, effort, and even more money when you see a return on investment more quickly, and it prevents you from having to rework your PACS and radiology workflow two years after the initial purchase. If you don\u0026rsquo;t properly integrate your workflow up front, I will put my money on the fact that you will be reevaluating PACS vendors within three years.\n","date":"5 March 2009","externalUrl":null,"permalink":"/archive/2009-03-05-pacs-enhancing-radiology-workflow/","section":"The Archives","summary":"","title":"PACS: Enhancing Radiology Workflow — Integrating PACS Is Key","type":"archive"},{"content":"Originally published on JS PACS, August 9, 2008. First appeared in Health Imaging \u0026amp; IT.\nMany healthcare career paths are built on successive education, and there are different ways of indicating ascension into higher levels of your profession. An obvious method is the degrees you obtain. Another common method is obtaining certification along a logical progression of tasks or skill sets.\nAs the PACS administrator profession grows, so have the opportunities to obtain certification. Two organizations currently provide certification for PACS administrators: the American Board of Imaging Informatics (ABII) and the PACS Administrators Registry and Certification Association (PARCA). ABII offers the Certified Imaging Informatics Professional (CIIP) exam, and PARCA offers a track of exams that culminates in the Certified PACS System Manager. I have had the opportunity to obtain both the CIIP from ABII and the CPSA level of certification through PARCA. A comparison of these two methods of certification is an ongoing hot topic among PACS administrators in the field. Regardless of which side you take or which certification you prefer, there are unique aspects of each that warrant consideration.\nABII\nThe American Board of Imaging Informatics and the CIIP exam were introduced during the 2007 SIIM conference. This exam has many myths associated with it. One myth is that it is associated with the American Registry of Radiologic Technologists (ARRT). This is not true. Yes, the CIIP exam has undergone psychometric development similar to that of the ARRT exams, but it is in no way associated with the ARRT. The fact that the ARRT served as a model for building the exam should be a comfort to those who take it, in that it follows the many years of tradition the ARRT exam has developed. No one can deny that the ARRT is the obvious benchmark for testing in the medical imaging profession.\nAnother myth I hear debated among PACS administrators is that there is no way to prepare for the CIIP exam. This also is not true. The ABII website provides the test content outline, which is a clear definition of the subject matter that can be found on the exam. Understanding each of these topics will help a CIIP candidate prepare. There are multiple ways to prepare for the CIIP exam. The best way to study is to simply be a PACS administrator for a year or two, especially during an implementation, upgrade, or replacement of a major system such as PACS, voice recognition, or your HIS/RIS. Understanding and gaining experience in both clinical workflows and information system components is critical to being ready for this exam. Networking and attending seminars are also beneficial for gaining critical knowledge for your profession and for the exam.\nPARCA\nPARCA and the series of exams that make up the various levels of PARCA certification started a few years prior to the CIIP exam. This certification consists of a three-tiered exam system. The entry-level exam, Certified PACS Associate (CPAS), is made up of two tests. The first evaluates a PACS administrator on technical knowledge. The second evaluates clinical knowledge. These two tests can be taken in any order, but both are required to progress to level 2.\nUpon reaching level 2, an individual can take the Certified PACS Interface Analyst (CPIA) exam. The CPIA tests an individual\u0026rsquo;s understanding of DICOM and HL7, including troubleshooting in both areas. The second level 2 test is the Certified PACS Systems Analyst (CPSA), which tests an individual\u0026rsquo;s understanding of the various components of a PACS and of system administration. Again, both of these tests are required to pass to the level 3 exam.\nThe Certified PACS System Manager (CPSM) is the final and encompassing exam. Holding this certification demonstrates that an individual has an advanced understanding of all imaging informatics topics, including image quality, advanced DICOM and HL7, security, and systems integration.\nAs with the CIIP exam, there are myths associated with PARCA certification. The primary one I hear is that you must study with materials from a specific organization in order to pass. I can assure you this is not true; I have never purchased any study materials from that organization. All my preparation for the PARCA exams was based on my own experience and learning.\nConclusion\nBefore giving my personal opinions of both certifying organizations, I feel compelled to offer a disclosure. I am a member of the CIIP item review committee as well as a CIIP item writer. I\u0026rsquo;ll also reiterate that I hold both the CIIP and the CPSA certifications.\nBoth of these organizations offer positive things for PACS administrators. Primarily, both offer recognition that the individual has obtained a certain level of knowledge and understanding of the components and complexities of imaging informatics in today\u0026rsquo;s healthcare environment. Additionally, both offer an increased level of professionalism in the rapidly evolving PACS administrator career. I will say that I feel there are distinct aspects to each exam.\nI feel the CIIP demonstrates concrete knowledge of PACS and the various components that interface with it. Additionally, I think the individual who holds a CIIP certification assures an employer or organization of a higher level of survivability during the crisis moments that imaging informatics can sometimes bring. It does this by assuring an understanding of all aspects of PACS encountered in day-to-day operations.\nI feel the PARCA exam series also demonstrates concrete knowledge of PACS and all of the components involved. PARCA certification likewise assures an employer that an individual is qualified to operate autonomously in the imaging informatics field. Additionally, I would offer that the PARCA exams evaluate an individual on their understanding of all the aspects of imaging informatics a PACS administrator may encounter throughout a career.\nUltimately, both certifying organizations hold critical places in the PACS administrator profession. Perhaps as PACS administrators we should stop comparing and contrasting the two exams and work to obtain all the levels of certification that we can.\nABII and SIIM are registered trademarks of their respective organizations.\n","date":"9 August 2008","externalUrl":null,"permalink":"/archive/2008-08-09-pacs-certification-two-valid-options/","section":"The Archives","summary":"","title":"PACS Certification: Two Valid Options","type":"archive"},{"content":" I\u0026rsquo;m John Sole. Premier Imaging Informatics is my consulting practice, and it\u0026rsquo;s just me.\nI started in the scanner room. The Army trained me as a radiologic technologist in 1994; I spent the next decade doing x-ray, trauma imaging, and CT, and moved to the IT side in 2004 as a PACS analyst. For the next eight years I ran imaging systems inside hospitals: PACS, cardiology PACS, a RIS, speech recognition, and an early vendor-neutral archive. Then I crossed to the vendor side, spending six years as a solutions architect for the Acuo VNA (later Lexmark Healthcare) and Vital Images, working out how those systems fit into what health systems across the country already had running. In 2018 I went independent.\nThat path is the point. I\u0026rsquo;ve been the person who gets paged at 2 a.m. when the archive stops accepting studies, and I\u0026rsquo;ve been the person who drew the architecture that was supposed to prevent it. I understand what the radiologist needs, what the modality actually sends, and what the database is doing underneath.\nToday I work with health systems on enterprise medical imaging: implementing new PACS and archive systems, migrating data between them, and connecting imaging to everything around it, from modalities to the EHR. Most of that lives in the standards, DICOM, HL7 and IHE, and in the databases and interfaces beneath them. When a production problem needs someone to trace it to the protocol or the query, that\u0026rsquo;s the work I like most.\nMy clients are academic medical centers, cancer centers, and children\u0026rsquo;s hospitals. Most of my engagements come through healthcare advisory firms, and I\u0026rsquo;m always glad to hear directly from health systems and imaging teams.\nI sat the first CIIP exam in 2007 and later wrote exam items and served on the exam committee for ABII. I hold an MBA from Rockford College. I write SQL and Python when the problem calls for it.\nWriting # I publish here on imaging informatics: methods, standards, and things I\u0026rsquo;ve seen go wrong. Where a claim would be challenged by someone who knows the field, I cite the standard or the paper. Where numbers appear, the method behind them is shown. The rest is experience, stated as such.\nContact # jsole@pii.services\n","externalUrl":null,"permalink":"/about/","section":"Premier Imaging Informatics","summary":"","title":"About","type":"page"},{"content":"","externalUrl":null,"permalink":"/authors/","section":"Authors","summary":"","title":"Authors","type":"authors"},{"content":"","externalUrl":null,"permalink":"/tags/c-get/","section":"Tags","summary":"","title":"C-GET","type":"tags"},{"content":"","externalUrl":null,"permalink":"/categories/","section":"Categories","summary":"","title":"Categories","type":"categories"},{"content":"","externalUrl":null,"permalink":"/series/","section":"Series","summary":"","title":"Series","type":"series"}]