[{"data":1,"prerenderedAt":83},["ShallowReactive",2],{"insights-list":3},[4],{"id":5,"title":6,"body":7,"date":74,"description":75,"extension":76,"meta":77,"navigation":78,"path":79,"seo":80,"stem":81,"__hash__":82},"insights\u002Finsights\u002Fgenerating-pdfs-from-radiology-reports-in-mirth-connect.md","Generating PDFs from Radiology Reports and Key Images in Mirth Connect",{"type":8,"value":9,"toc":65},"minimark",[10,15,19,22,26,29,32,35,39,42,45,49,52,55,59,62],[11,12,14],"h2",{"id":13},"the-problem","The Problem",[16,17,18],"p",{},"Radiology workflows generate two things that referring physicians need: the report text and the key images. In most environments, these live in separate systems. The report comes out of the dictation\u002Ftranscription platform. The key images come from the PACS. Getting both into a single, clean PDF that can be delivered to a referring provider's EHR or fax system is a problem that sounds simple and isn't.",[16,20,21],{},"Most organizations solve this by bolting on a separate application - a report distribution service, a third-party document generation tool, or a manual process where someone exports the data and assembles the PDF by hand. Each of these adds a moving part. Another service to license, another server to maintain, another thing that breaks at 2 AM when nobody is watching.",[11,23,25],{"id":24},"why-this-is-harder-than-it-looks","Why This Is Harder Than It Looks",[16,27,28],{},"The report text isn't just plain text. Depending on the source system, it might arrive as HL7-encoded segments with embedded formatting, as structured XML, or as HTML with inconsistent encoding. Line breaks, special characters, section headings and impression markers all behave differently across dictation platforms. A solution that works perfectly for one customer's report format will break on the next customer's data.",[16,30,31],{},"Key images add another layer. They arrive in different formats, different resolutions, different encoding schemes. Some systems send them as part of the HL7 message. Others require a separate query to pull them from the PACS. The solution needs to handle both pathways.",[16,33,34],{},"Then there's the formatting itself. A radiology PDF isn't a generic document. It needs to look professional, include the right headers, handle variable-length content gracefully, and render correctly across different viewing environments. Customer-specific formatting requirements mean the solution needs to be configurable without rebuilding it for every deployment.",[11,36,38],{"id":37},"our-approach","Our Approach",[16,40,41],{},"We built the entire solution inside the Mirth Connect environment. No external services. No separate application server. No additional infrastructure to maintain. The PDF generation happens as part of the existing interface workflow - when a report and its associated key images are ready, the channel produces the PDF dynamically and routes it to the appropriate destination.",[16,43,44],{},"The solution is configurable per client. Different report formats, different image sources, different output layouts - all handled through configuration rather than code changes. This means rolling it out to a new facility is a deployment exercise, not a development project.",[11,46,48],{"id":47},"what-this-means-for-operations","What This Means for Operations",[16,50,51],{},"Because it runs inside Mirth, it inherits all the operational benefits of the interface engine: monitoring, alerting, message reprocessing, audit trails. If a PDF fails to generate, it shows up in the same dashboard your interface team already watches. There's no separate log to check, no separate service to restart.",[16,53,54],{},"Rollback is straightforward. The PDF generation runs as a configurable destination within existing channels. Turning it off for a specific customer doesn't affect anything else in the workflow.",[11,56,58],{"id":57},"the-result","The Result",[16,60,61],{},"We've deployed this solution across multiple teleradiology customers, each with their own report formats, image handling requirements and delivery destinations. The initial build was a fixed-scope project. Subsequent deployments are configuration exercises that go live quickly.",[16,63,64],{},"If your organization is dealing with this problem - assembling radiology reports and key images into deliverable PDFs - and you'd rather solve it inside your existing Mirth environment than add another application to your stack, we should talk.",{"title":66,"searchDepth":67,"depth":67,"links":68},"",2,[69,70,71,72,73],{"id":13,"depth":67,"text":14},{"id":24,"depth":67,"text":25},{"id":37,"depth":67,"text":38},{"id":47,"depth":67,"text":48},{"id":57,"depth":67,"text":58},"2026-04-03","How we built a solution inside Mirth Connect to dynamically generate PDF documents combining radiology report text and key images, with no external services required.","md",{},true,"\u002Finsights\u002Fgenerating-pdfs-from-radiology-reports-in-mirth-connect",{"title":6,"description":75},"insights\u002Fgenerating-pdfs-from-radiology-reports-in-mirth-connect","XwexvG3cv2oOqqBRkA_pEGDStGoG8vOL7B1zMNLcjFY",1775415946944]