# Flux Inc — Complete Site Content > https://fluxinc.co | Generated 2026-10-08 --- URL: https://fluxinc.co/about --- title: About Flux Inc description: Secure software for healthcare and enterprise - Trusted by 3,000+ organizations worldwide since 2007 keywords: medical imaging software, DICOM solutions, healthcare IT, secure AI, RAG, on-prem AI sitemap: changefreq: monthly --- # About Us Founded in 2007, Flux Inc. has grown into a dual-focused technology provider, delivering specialized solutions for both healthcare and AI. Our name represents two affiliated companies: - Flux Software LLC, established in 2021 and based in Marietta, GA - Flux Software Inc, our Canadian headquarters in Toronto For over 15 years, we've developed secure software that handles sensitive data with precision and care. Our expertise spans medical imaging workflows with DICOM and HL7 integration to organization-aware AI that respects data privacy and security. ### Medical Solutions Our medical division has partnered with leading medical imaging equipment manufacturers worldwide, developing innovative solutions for diagnostic imaging workflows. Our flagship product, DICOM Capacitor, has revolutionized medical image management across mammography, cardiology, and general radiology departments, serving as a critical component in modern medical imaging infrastructure. ### Secure AI Our newest offering, Flux Mentor, provides on-premises AI capabilities using Retrieval-Augmented Generation (RAG) to deliver context-aware responses while keeping your data secure. This technology allows organizations to leverage the power of AI while maintaining complete control over their sensitive information. ### Custom Consulting & Application Development We provide specialized consulting and custom development for organizations with complex requirements: - **Medical Systems Integration**: Custom DICOM, HL7, and FHIR solutions - **Knowledge Management**: Secure organization-aware AI integration - **Specialized AI Solutions**: On-premise RAG systems for data-sensitive industries - **Process Automation**: Workflow optimization and automated data processing Our consulting model emphasizes deep domain knowledge, rigorous requirements analysis, and collaborative development. We excel where standard off-the-shelf solutions fall short, designing systems that address unique challenges. ### Expert Team Our team includes specialists in DICOM and HL7, database engineers, AI developers, security experts, and advanced processing techniques. We maintain strict adherence to security standards and thoroughly test all technologies to deliver solutions that combine innovation with reliability. [Get in touch](/contact) --- URL: https://fluxinc.co/ai/clawdapus --- title: clawdapus — Agent Containment Infrastructure description: Open-source infrastructure for deploying autonomous AI agents as governed, untrusted workloads. Behavioral contracts, credential starvation, governed tool presentation, and ambient memory — the orchestration layer below agent frameworks. head: meta: - name: 'og:title' content: 'clawdapus — Agent Containment Infrastructure' - name: 'og:description' content: 'Open-source Docker-based orchestration for autonomous AI agents. Behavioral contracts, credential starvation, governed tool presentation, and ambient memory.' - name: 'og:type' content: 'website' - name: 'twitter:card' content: 'summary_large_image' sitemap: changefreq: monthly --- ::FullWidthSection{variant="custom" padding="sm" className="bg-transparent" backgroundOverlayClass="bg-gradient-to-br from-zinc-900/95 via-zinc-800/90 to-primary-900/80"} ![clawdapus logo](/images/ai/clawdapus.png){width="400" class="my-8"} ::RotatingText{items="Contain Untrusted Agents.|Enforce Behavioral Contracts.|Govern Tool Access.|Deploy AI at Scale." tag="p" rootClass="text-xl text-white md:text-2xl"} :: ::ProseButtonGroup ::ProseButton{to="https://github.com/mostlydev/clawdapus" variant="primary" :external=true} View on GitHub :: ::ProseButton{to="https://clawdapus.dev" variant="outlineInvert" :external=true} Read the Docs :: ::ProseButton{to="/contact?interest=clawdapus" variant="outline"} Talk to Flux :: :: :: **Swarm is for agents that work *for* you. clawdapus is for agents that work *as* you.** Most agent frameworks assume the agent is a trusted process. They handle orchestration, memory, and tool use — but they leave governance, credential management, identity projection, and cost containment to the application developer. That's fine for controlled experiments. It's not fine for production deployments where agents operate with real identities, real budgets, and real consequences. clawdapus is the infrastructure layer below your agent framework. It treats agents as untrusted workloads — the same way a container orchestrator treats application containers — and wraps them in a governed, auditable execution environment. MIT licensed. Built in the open. Flux Inc. is a contributing organization and production implementation partner. ## The Core Insight Autonomous agents deployed in healthcare, finance, or enterprise settings aren't just code — they're proxies for organizational intent. They post to feeds, reply on chat platforms, query databases, and execute actions under your organization's identity. The risk isn't just "the agent does something wrong." The risk is: **the agent does something wrong under your name, with your credentials, in your regulated environment.** clawdapus addresses this with four interlocking mechanisms: ::TwoColumn #left ### Behavioral Contracts Every agent is bound by a read-only **behavioral contract** — a structured AGENTS.md file defining the agent's purpose, constraints, and rules of engagement. The contract is bind-mounted from the host at the infrastructure layer. The agent cannot modify it. It cannot override it. It survives container compromise. Contracts compose: organization-wide mandates, department-level overlays, and role-specific refinements stack through `INCLUDE` directives with `enforce`, `guide`, and `reference` modes. ### Credential Starvation Agents never hold real API keys, database credentials, or service tokens. Instead, they receive dummy bearer tokens. The **[cllama governance proxy](/ai/cllama)** — running as a separate sidecar — holds the real credentials and swaps them at inference time. Even a fully compromised agent cannot bypass governance, because it lacks the credentials to do so. #right ### Governed Tool Presentation Tools aren't just available or not — they're *mediated*. In **native mode**, clawdapus governs which tools an agent can see and call, with per-agent tool manifests compiled at deploy time. In **mediated mode**, the cllama proxy injects, executes, and handles tool results transparently — the agent participates in tool use without having direct access to the underlying service. The result: an agent can query a database without holding a connection string. It can post to Slack without holding an OAuth token. Capability without credential exposure. ### Identity Trust Agents have declared, infrastructure-managed identities — Discord handles, Telegram usernames, Slack user IDs. These are provisioned at deploy time via the `HANDLE` directive, broadcast as environment variables across the pod, and used to establish peer-discovery and messaging allowlists. Identity is infrastructure-owned. Agents don't configure it. They inherit it. :: ## The Anatomy of a Governed Agent clawdapus extends Docker with two purpose-built formats: - **Clawfile** — an extended Dockerfile that declares an agent's capabilities, identity, and governance requirements - **claw-pod.yml** — an extended docker-compose.yml that defines governed agent fleets, surfaces, and behavioral defaults The `claw` CLI compiles these into standard OCI images and Docker Compose files. You can eject from clawdapus at any time — your artifacts remain plain Docker. No vendor lock-in.
01
Contract
Behavioral contracts bind-mounted read-only at deploy time. Agents inherit their purpose. They cannot modify it.
02
Contain
Agents hold dummy tokens. The cllama proxy holds real credentials. No agent can reach a provider directly.
03
Govern
Tool access mediated, memory managed, session history written at the infrastructure layer — not inside the agent.
## Key Concepts ### Ambient Memory Plane Infrastructure-owned memory services that derive durable state from session history. Rather than agents managing their own memory — which they could corrupt, selectively forget, or exfiltrate — the ambient memory plane provides pluggable backends (semantic search, graph, rolling summaries) behind a stable interface. The governance proxy automatically injects relevant derived context into future turns. The agent receives memory. It doesn't control it. ### Session History as Infrastructure Every inference transaction is written to an append-only JSONL ledger at the proxy boundary — independent of the agent runtime. Session history records normalized request/response pairs, token usage, cost, interventions, and tool execution traces. It persists across container restarts. It's the substrate for memory plane backfill, drift scoring, and compliance audit. Agents cannot modify session history. They can't selectively delete transactions. It's infrastructure-owned. ### Drift Scoring How far does an agent's behavior diverge from its contract? Drift is measured by proxy telemetry — intervention counts, error rates, response amendments, cost anomalies — not by self-report. The **Master Claw** (an autonomous governor agent in the pod) reads this telemetry and makes fleet decisions: quarantining drifting agents, reallocating budgets, or escalating to human operators. ### Surfaces and Capability Discovery Services in a clawdapus pod declare their capabilities through `claw.describe` descriptors — feeds they publish, tools they expose, endpoints they serve. The pod compiler wires subscriptions at deploy time. Every agent receives an auto-generated `CLAWDAPUS.md` infrastructure map listing what it can reach, who its peers are, and what skills it has available. Agents discover their environment. They don't configure it. ## Flux Inc. and clawdapus Flux Inc. is a contributing organization to the clawdapus project and provides production implementation expertise for organizations deploying the framework in regulated environments. Our **[Model Governance Layer](/medical/model-governance-layer)** is built on the cllama sidecar standard that clawdapus pioneered — adapted for healthcare and enterprise customer deployment with pre-configured behavioral contracts, HIPAA-adjacent audit logging, and Active Directory integration. ::ContentBox{variant="dark"} ### Deployment Expertise for Regulated Environments clawdapus is MIT-licensed and freely available. But deploying agent containment infrastructure in a hospital system, financial institution, or government agency requires more than running `claw up`. Flux provides: - Pre-configured behavioral contract templates for healthcare and enterprise contexts - Identity trust integration with existing IAM and Active Directory infrastructure - HIPAA-adjacent audit logging and compliance reporting - Ongoing governance tuning and fleet oversight - Support for the full clawdapus platform as it evolves ::ProseButtonGroup ::ProseButton{to="/contact?interest=clawdapus_deployment" variant="primary"} Talk to Flux About Deployment :: ::ProseButton{to="/medical/model-governance-layer" variant="outline"} See Our MGL Implementation :: :: :: ## Open Source References ::TwoColumn #left **clawdapus** — Agent containment infrastructure MIT License · [github.com/mostlydev/clawdapus](https://github.com/mostlydev/clawdapus) Documentation at [clawdapus.dev](https://clawdapus.dev) **cllama** — The governance proxy standard Part of the clawdapus project [Read the cllama overview](/ai/cllama) #right **Manifesto** — The philosophy behind governed agent deployment [clawdapus.dev/manifesto](https://clawdapus.dev/manifesto) **Quickstart** — Get a governed agent running in minutes [clawdapus.dev/guide/quickstart](https://clawdapus.dev/guide/quickstart) :: ::EmphasisBox ## Ready to Contain Your Agents? Whether you're deploying autonomous agents for the first time or scaling a fleet that's outgrown prompt-level governance, we can help you architect the right containment strategy. ::ProseButtonGroup ::ProseButton{to="/contact?interest=clawdapus" variant="primary"} Talk to Flux :: ::ProseButton{to="https://clawdapus.dev" variant="outline" :external=true} Explore the Docs :: ::ProseButton{to="/ai/cllama" variant="outline"} Learn About cllama :: :: :: --- URL: https://fluxinc.co/ai/cllama --- title: cllama — The LLM Governance Proxy description: The blood-brain barrier for autonomous agents. cllama is an open standard and reference implementation for context-aware, bidirectional LLM governance — credential starvation, policy enforcement, cost metering, and audit at the infrastructure layer. head: meta: - name: 'og:title' content: 'cllama — LLM Governance Proxy | Open Standard' - name: 'og:description' content: 'Credential starvation, bidirectional policy enforcement, cost metering, and audit at the infrastructure layer. The open standard for governed LLM deployment.' - name: 'og:type' content: 'website' - name: 'twitter:card' content: 'summary_large_image' sitemap: changefreq: monthly --- ::FullWidthSection{variant="gradient" padding="sm" className="bg-transparent" patternOverlay="true" gradientColor="teal-600"} ![cllama logo](/images/ai/cllama-logo.png){width="360" class="mx-0 my-8"} ::RotatingText{items="The Governance Proxy.|Credential Starvation.|Bidirectional Policy Enforcement.|Infrastructure-Layer Audit." tag="p" rootClass="text-xl text-white md:text-2xl"} :: ::ProseButtonGroup ::ProseButton{to="https://github.com/mostlydev/cllama" variant="primary" :external=true} View on GitHub :: ::ProseButton{to="https://clawdapus.dev" variant="outlineInvert" :external=true} clawdapus Docs :: ::ProseButton{to="/contact?interest=cllama" variant="outline"} Talk to Flux :: :: :: **The blood-brain barrier for autonomous agents.** Application-layer governance — prompt engineering, system messages, "don't do X" instructions — is fragile. A sufficiently long context, a sufficiently clever user, or a model update can break it. cllama takes governance out of the prompt and puts it where it belongs: in a separate process, at the infrastructure layer, between your agents and the outside world. cllama is an open standard and reference implementation for LLM governance proxies. It is part of the [clawdapus](/ai/clawdapus) project (MIT licensed) and is the engine behind Flux's [Model Governance Layer](/medical/model-governance-layer) customer deployments. ## What cllama Does cllama is a single binary that exposes an **OpenAI-compatible API endpoint** to agent runtimes, and proxies their requests to the real LLM provider — intercepting both directions.
01
Intercept
Agent requests arrive with dummy bearer tokens. Identity is resolved, policy loaded, real credentials swapped in.
02
Enforce
Policy evaluated outbound. Response validated inbound. Non-compliant responses retried automatically with corrective context.
03
Audit
Every inference logged as structured JSONL at the proxy boundary — independent of the agent, append-only, tamper-evident.
To the agent, cllama looks exactly like an LLM provider. To the provider, cllama looks like a standard API client. Everything in between — identity verification, policy enforcement, credential management, cost tracking, and audit logging — happens transparently. ## Core Mechanisms ### Credential Starvation This is the foundational security property of cllama. Agent containers are provisioned with **unique dummy bearer tokens** — random strings that identify the agent to the proxy but are useless for anything else. The real API keys — for Anthropic, OpenAI, Azure, or any other provider — are held exclusively by cllama. The agent can't bypass governance by calling the provider directly. It doesn't have the credentials to do so. Even a fully compromised agent, running as root inside its container, cannot exfiltrate API keys it was never given. This is not a soft control. It's a hard architectural guarantee. ### Identity Resolution A single cllama instance serves an entire pod of multiple agents. Each agent has a unique bearer token, which cllama resolves to an identity at request time — loading that agent's behavioral contract, budget allocation, permitted models, and tool manifest from a shared context volume. One proxy. Many agents. Zero credential sharing. ### Bidirectional Policy Enforcement cllama intercepts both directions of inference traffic: - **Outbound (agent → provider):** Prompts are evaluated against the agent's behavioral contract. Context is decorated with organizational identity and policy. Tool manifests are injected or filtered based on per-agent authorization. - **Inbound (provider → agent):** Responses are evaluated against MUST-priority compliance rules before delivery. Non-compliant responses are retried with corrective context. Only a compliant response — or an explicit escalation — reaches the agent or end user. Neither the agent nor the provider knows this is happening. ### Cost Metering and Budget Enforcement Every inference transaction is metered: token counts are multiplied by current provider pricing tables, and cost is tracked per `(agent, provider, model)` tuple. Hard budget caps can be enforced — when an agent hits its spend limit, cllama can throttle, downgrade the model, or block further requests entirely. cllama can also **silently route model requests** — an agent requesting `anthropic/claude-opus-4` can be transparently served `claude-haiku-4-5` if the budget is exhausted. The agent sees a valid response. It never knows its model was changed. ### Structured Audit at the Proxy Boundary Session history is written as a structured JSONL ledger at the proxy boundary — not inside the agent runtime, not in the application layer. Every record contains: timestamp, agent ID, model, provider, latency, status, token counts, cost (USD), and any intervention reason. This ledger is append-only. Agents cannot modify it. It persists across container restarts. It's the authoritative record of what your AI actually did — suitable for compliance review, drift scoring, and incident investigation. ## The cllama Standard cllama is defined as an **open standard**, not just a single implementation. Any container image that: - Exposes an OpenAI-compatible proxy endpoint - Accepts clawdapus context (via environment variables and volume mounts) - Emits standardized structured logs ...qualifies as a cllama proxy. The reference implementation (`cllama-passthrough`) is a pure proxy with credential starvation and audit logging. Policy modules add bidirectional interception, response amendment, and drift scoring on top. This means the governance architecture is auditable, replaceable, and extensible — properties that matter in regulated environments. ## Deployment Variants ::TwoColumn #left ### cllama-passthrough The reference implementation. Pure credential starvation, identity resolution, cost metering, and audit logging. No cognitive intervention — requests and responses pass through unmodified (except for credential swap). The minimum viable governance proxy. Suitable for: organizations starting with basic audit and cost control. ### cllama-policy Adds bidirectional interception, behavioral contract enforcement, and response governance. Evaluates outbound prompts against MUST/SHOULD rules. Retries non-compliant responses. Records interventions in session history. Powers the full MGL compliance loop. Suitable for: regulated environments with MUST-priority behavioral constraints. #right ### Flux MGL Deployment Flux Inc.'s production implementation of cllama for healthcare and enterprise customers. Includes pre-configured behavioral contract templates, HIPAA-adjacent audit log formatting, Active Directory identity integration, and operator tooling for policy management. [Learn about the Model Governance Layer →](/medical/model-governance-layer) ### Self-Hosted / Custom cllama is MIT-licensed. You can run the reference implementation yourself, build policy modules against the open standard, or deploy it as part of a clawdapus agent pod. [Get started at clawdapus.dev →](https://clawdapus.dev/guide/quickstart) :: ## Relationship to clawdapus and MGL cllama originated as the governance proxy component of the [clawdapus](/ai/clawdapus) agent containment framework — the piece responsible for separating agent capability from agent credentials. It was later formalized as a standalone open standard, recognizing that the governance proxy pattern is useful far beyond the clawdapus pod context. Flux's [Model Governance Layer](/medical/model-governance-layer) is a production-hardened implementation of cllama for enterprise and healthcare customers: pre-integrated with organizational identity systems, pre-configured with compliance-oriented behavioral contracts, and supported by Flux's implementation expertise. The three layers compose: | Layer | What it does | |-------|-------------| | **clawdapus** | Orchestrates and contains agent fleets — surfaces, identity topology, behavioral contracts, session history | | **cllama** | Governs inference traffic — credential starvation, policy enforcement, cost metering, audit | | **MGL** | Flux's production deployment — enterprise/healthcare integration, compliance contracts, support | ## Flux's Role Flux Inc. is a contributing organization to the clawdapus project and the primary commercial implementation partner for organizations deploying cllama in regulated environments. We helped develop the credential starvation architecture, contributed to the governed tool presentation specification, and operate cllama in production for healthcare customers today. ::ContentBox{variant="dark"} ### Open Source, Production-Grade Implementation The open-source nature of cllama is a feature, not a limitation. In regulated environments, governance infrastructure that can't be audited isn't governance — it's a promise. cllama's open standard means your auditors can inspect how credential starvation works, how behavioral contracts are enforced, and how session history is written. Flux provides the production expertise: deployment, integration, tuning, and ongoing support. :: ::EmphasisBox ## Govern Your Inference Traffic Ready to put credential isolation and policy enforcement at the infrastructure layer instead of the prompt layer? ::ProseButtonGroup ::ProseButton{to="/contact?interest=cllama" variant="primary"} Talk to Flux :: ::ProseButton{to="/medical/model-governance-layer" variant="outline"} See the Model Governance Layer :: ::ProseButton{to="https://github.com/mostlydev/clawdapus/tree/master/cllama" variant="outline" :external=true} View on GitHub :: :: :: --- URL: https://fluxinc.co/case-studies --- title: Case Studies description: Explore real-world implementations of Flux technologies keywords: case studies, medical imaging, enterprise solutions --- # Case Studies Flux Inc. delivers powerful solutions across a range of industries. Our case studies showcase our expertise in both medical imaging and enterprise applications. We approach each project with: - Deep domain expertise - Rigorous requirements analysis - Collaborative development approach - Thorough testing and validation - Ongoing support and maintenance ## Artificial Intelligence - [DenseBreast-AI Chatbot](/case-studies/densebreast-ai-chatbot) ## Medical Imaging Solutions Our core expertise is in medical imaging workflows and DICOM integration. DICOM Capacitor powers routing, format conversion, tag harmonization, and store-and-forward delivery across dozens of healthcare facilities. ::ProseButtonGroup ::ProseButton{to="/medical/dicom-capacitor/use-cases" variant="primary"} View All DICOM Capacitor Use Cases :: :: ## Enterprise Applications Beyond healthcare, we develop sophisticated solutions for business operations and analytics: ### Business Operations - [Manufacturing Scheduler Platform](/case-studies/enterprise/manufacturing-scheduler) - [Call Center Metrics Platform](/case-studies/enterprise/call-center-metrics) ::ProseButtonGroup ::ProseButton{to="/contact" variant="primary"} Discuss Your Project :: ::ProseButton{to="/about"} About Our Company :: :: --- URL: https://fluxinc.co/case-studies/densebreast-ai-chatbot --- title: Case Study | AI Chatbot for Dense Breast Information description: Learn how Flux Mentor powers an AI chatbot to make critical information about dense breasts from densebreast-info.org accessible and understandable through conversation, with adaptive communication and multilingual support. keywords: case study, AI chatbot, dense breast, densebreast-info.org, Flux Mentor, RAG, conversational AI, patient education, clinical support, multilingual AI, adaptive AI ogImage: /images/flux-inc-logo-color.png sitemap: changefreq: monthly --- ::FullWidthSection{variant="light" padding="md"} # Case Study: Empowering through Conversation ## AI-Powered Access to Dense Breast Information Navigating complex medical topics like breast density can be challenging for patients and even time-consuming for healthcare providers seeking specific details. The esteemed resource, [DenseBreast-info.org (DB-I)](https://densebreast-info.org/), provides comprehensive, medically-vetted information. Flux Inc. developed a demonstration AI chatbot, powered by Flux Mentor, to make this vital knowledge more accessible. ::ProseButtonGroup ::ProseButton{to="https://densebreast.fluxinc.co/" variant="primary" :external="true" target="_blank"} Try the Demo Chatbot :: ::ProseButton{to="/flux-mentor" variant="secondary"} Learn about Flux Mentor :: :: :: ::FullWidthSection{variant="white" padding="md"} ## The Challenge: Bridging the Information Gap DenseBreast-info.org offers a wealth of information, including detailed articles, research, and guidelines. However, users might: - Find it overwhelming to locate specific answers within extensive content. - Require information presented in simpler terms or different languages. - Need to understand how different pieces of information connect. The goal was to provide a tool that could offer instant, conversational access to DB-I's knowledge base, tailored to individual user needs. :: ::FullWidthSection{variant="primary-subtle" padding="md"} ## The Solution: A Flux Mentor-Powered Chatbot Leveraging **Flux Mentor**, our organizationally-aware AI, we created a chatbot that ingests and understands the content from [DenseBreast-info.org](https://densebreast-info.org/). Users can ask questions in natural language and receive clear, context-aware answers. **Key capabilities showcased in this demo:** ::TwoColumn #left ### Sourced & Trustworthy Responses Every piece of information provided by the chatbot is directly sourced from the DB-I website. Crucially, responses include direct links to the original articles and even specific PDFs on DenseBreast-info.org, ensuring transparency and allowing users to verify information and delve deeper. ### Adaptive Communication Flux Mentor can tailor its explanations to the user's level of understanding. Whether it's a patient seeking basic information or a clinician looking for nuanced details, the chatbot adapts its language and depth, making complex topics more digestible. #right ### Multilingual Support To broaden accessibility, Flux Mentor enables the chatbot to understand and respond in multiple languages. This feature is critical for reaching diverse populations and ensuring everyone can benefit from this important health information. ### Efficient Information Retrieval Powered by advanced Retrieval-Augmented Generation (RAG) and technologies like [Morphik](https://www.morphik.ai/), Flux Mentor quickly finds the most relevant information within the vast DB-I knowledge base, providing timely and accurate answers. :: :: ::FullWidthSection{variant="white" padding="md"} ## Impact: Enhanced Accessibility & Understanding The Dense Breast AI Chatbot demonstrates how Flux Mentor can transform access to specialized knowledge: - **Empowers Patients**: Provides easy-to-understand, sourced answers to their questions about breast density, helping them prepare for discussions with their doctors. - **Supports Clinicians**: Offers a quick way to reference specific information from DB-I guidelines and resources. - **Increases Reach**: Multilingual and adaptive capabilities make the information accessible to a wider audience. - **Builds Trust**: Transparent sourcing to the authoritative DB-I website reinforces the reliability of the information. This demonstration highlights Flux Mentor's potential in various fields where making complex, critical information accessible and understandable is paramount. :: ::FullWidthSection{variant="gradient" gradientColor="primary-500" padding="md" patternOverlay="true"} ## Explore Flux Mentor Discover how Flux Mentor can bring secure, organizationally-aware AI to your enterprise. ::ProseButtonGroup ::ProseButton{to="/flux-mentor" variant="secondary"} Flux Mentor Features :: ::ProseButton{to="/contact?product=FluxMentor" variant="primary"} Request a Consultation :: :: :: --- URL: https://fluxinc.co/case-studies/enterprise --- title: Enterprise Case Studies | Flux Inc description: Explore how our secure AI has helped organizations across industries enhance knowledge management and information retrieval. keywords: secure AI case studies, RAG implementation, on-prem AI, organizational knowledge sitemap: changefreq: monthly --- # Enterprise Case Studies ## Ready to transform your organization? Flux Mentor is designed with security and efficiency at its core. Discover how this secure AI solution can help your organization leverage its knowledge while maintaining complete control over your data. ::ProseButtonGroup ::ProseButton{to="/flux-mentor" variant="primary"} Learn About Flux Mentor :: ::ProseButton{to="/contact?product=FluxMentor" variant="secondary"} Contact Us :: :: See how organizations across industries have leveraged Flux Mentor to transform their operations, protect sensitive data, and improve productivity. ## [Manufacturing Scheduling Optimization](/case-studies/enterprise/manufacturing-scheduler) A leading manufacturing company uses our secure AI solution to optimize their complex production scheduling, resulting in faster information retrieval and enhanced decision-making. ::ProseButtonGroup ::ProseButton{to="/case-studies/enterprise/manufacturing-scheduler" variant="primary"} Read Case Study :: :: ## [Call Center Metrics and Performance](/case-studies/enterprise/call-center-metrics) A multi-national customer service provider implemented Flux Mentor to securely process customer interaction data, improving agent performance while maintaining strict compliance with data privacy regulations. ::ProseButtonGroup ::ProseButton{to="/case-studies/enterprise/call-center-metrics" variant="primary"} Read Case Study :: :: --- URL: https://fluxinc.co/case-studies/enterprise/call-center-metrics --- title: Call Center Knowledge Management | Flux Inc description: How a major call center leveraged Flux Mentor to improve agent performance and customer satisfaction keywords: secure AI, call center, knowledge management, customer service, AI implementation --- # Call Center Knowledge Management ## Client Profile A large business process outsourcing (BPO) company with over 3,000 call center agents handling customer support for multiple enterprise clients across diverse industries. ## Challenge The client was struggling with several critical issues in their customer service operations: - Agents spent an average of 30% of call time searching for information across multiple knowledge bases - Training new agents required 4-6 weeks before they reached acceptable performance levels - Knowledge was fragmented across wikis, PDFs, emails, and unstructured documents - Different clients had different requirements, protocols, and knowledge bases - Data privacy regulations required strict handling of customer information ## Solution We implemented Flux Mentor to create a secure knowledge retrieval system that could: - Unify access to all knowledge resources through a single AI interface - Provide context-aware responses based on the specific client and inquiry type - Maintain complete data privacy and security on the company's premises - Deliver information to agents in real-time during customer calls ## Implementation Process 1. **Knowledge Audit**: We conducted a comprehensive assessment of all existing knowledge sources, including: - Client-specific support documentation - Internal training materials - Historical support tickets and resolutions - Procedure manuals and troubleshooting guides 2. **Secure Integration**: Flux Mentor was deployed on the client's infrastructure, ensuring all data remained within their security perimeter and complied with data protection regulations. 3. **User Interface Development**: We created a streamlined agent interface that integrated directly into their existing call center platform, providing immediate AI-assisted knowledge retrieval during calls. 4. **Training and Adoption**: We delivered a comprehensive training program to help agents effectively use the new system, including query techniques and interpretation of AI responses. ## Results After implementing Flux Mentor, the client experienced: - **42% reduction** in average handle time for complex support issues - **67% faster** information retrieval during customer calls - **Training time reduced by 50%** for new agents - **23% improvement** in customer satisfaction scores - **19% increase** in first-call resolution rates - **$2.3M annual savings** in operational costs ## Client Feedback > "Flux Mentor has revolutionized how our agents access information. What used to take minutes of searching now happens in seconds. Our agents can focus on the customer instead of digging through multiple knowledge bases, resulting in faster resolutions and happier customers. The fact that all data stays within our infrastructure gave us the confidence to fully embrace this AI solution." > > — VP of Customer Operations ::ProseButtonGroup ::ProseButton{to="/flux-mentor" variant="primary"} Learn About Flux Mentor :: ::ProseButton{to="/contact?product=FluxMentor" variant="secondary"} Contact Us :: :: --- URL: https://fluxinc.co/case-studies/enterprise/manufacturing-scheduler --- title: Manufacturing Scheduling Optimization | Flux Inc description: How a leading manufacturer used Flux Mentor to improve production scheduling and operational efficiency keywords: secure AI, manufacturing, production scheduling, AI implementation, on-prem AI --- # Manufacturing Scheduling Optimization ## Client Profile A large manufacturing company producing precision components for aerospace and automotive industries, with 5 plants and over 2,500 employees. ## Challenge The client faced significant challenges with their complex production scheduling: - Production planners spent 15+ hours per week searching through documentation - Critical manufacturing knowledge was fragmented across emails, documents, and tribal knowledge - Scheduling decisions took too long and were often based on incomplete information - New planners required 6+ months to become proficient, limiting operational flexibility ## Solution We implemented Flux Mentor to create a secure, organization-aware AI system that could: - Index all production documentation, specifications, maintenance records, and historical schedules - Create a unified knowledge base accessible through natural language queries - Provide context-aware responses to production questions based on the organization's specific processes - Keep all data secure on the client's premises ## Implementation Process 1. **Assessment**: We evaluated the client's knowledge ecosystem, conducting workshops with production planners to understand their information needs. 2. **Knowledge Base Development**: Our team indexed over 400,000 documents, including: - Manufacturing specifications - Equipment maintenance records - Historical production schedules - SOPs and best practices - Email archives related to production issues 3. **Secure Deployment**: We implemented Flux Mentor within the client's secure environment, ensuring all data remained on-premises and integrated with their existing authentication systems. 4. **User Training**: We conducted comprehensive training sessions for all production planners, focusing on effective query techniques and system capabilities. ## Results After six months of implementation, the client reported: - **75% reduction** in time spent searching for production information - **52% faster** onboarding for new production planners - **28% improvement** in on-time deliveries due to more efficient scheduling - **37% reduction** in unplanned equipment downtime through better maintenance scheduling - **$1.2M annual savings** through improved operational efficiency ## Client Feedback > "Flux Mentor has transformed how we access and utilize our organizational knowledge. Our production planners can now get immediate answers to complex questions about capacity, equipment specifications, and historical performance. The system's ability to understand our specific context and processes has made it an invaluable tool for our scheduling team." > > — Director of Operations ::ProseButtonGroup ::ProseButton{to="/flux-mentor" variant="primary"} Learn About Flux Mentor :: ::ProseButton{to="/contact?product=FluxMentor" variant="secondary"} Contact Us :: :: --- URL: https://fluxinc.co/case-studies/medical/cardiac-us --- title: Cardiac Ultrasound Measurement Harmonization description: Standardize cardiac ultrasound measurements across vendors for consistent clinical evaluation keywords: cardiac ultrasound, DICOM, measurement harmonization, echocardiography, PACS integration, vendor standardization --- # Cardiac Ultrasound Measurement Harmonization ::ContentBox{bgColor="primary" bgShade="100" borderColor="primary" borderShade="500" shadow=true} Cardiac measurements face critical workflow challenges due to vendor-specific identifiers and formats. Our solution harmonizes measurements across systems while preserving accuracy. :: ## The Challenge Healthcare facilities face several challenges with cardiac measurements: - Measurement identifiers vary between vendors (SC2000 vs iE33) - Manual re-entry of measurements wastes time and risks errors - Different naming conventions break trending/reporting - Structured reporting integration fails due to identifier mismatches - Need for consistent measurement hierarchies - Quality assurance requirements ## How It Works
01
Map
Translate vendor-specific measurement identifiers to a common schema.
02
Normalize
Apply value scaling and unit conversions across vendors.
03
Validate
Check that all required measurements are present and in range.
04
Align
Restructure the output to match the reporting system's expected format.
## The Solution ::TwoColumn #left Capacitor provides sophisticated measurement mapping: - Automatically translates measurement identifiers between vendors - Maps SC2000 measurements to match iE33 format (or vice versa) - Preserves all measurement values and precision - Ensures correct units and reference ranges - Maintains proper measurement hierarchies - Validates data consistency #right ### Example Results For common cardiac measurements: - EF calculations maintain consistency - Chamber measurements map correctly - Doppler values preserve units and sites - Strain analysis results integrate properly - Trending works across vendors :: ::EmphasisBox ## Value Delivered - Consistent measurements across vendor systems - Improved diagnostic reliability - Increased reporting efficiency - Better patient care through more reliable tracking - Enhanced diagnostic confidence - Simplified workflow for cardiologists and sonographers ::ProseButtonGroup ::ProseButton{to="/contact" variant="primary"} Schedule a Demo :: ::ProseButton{to="/medical/dicom-capacitor/use-cases"} View All Use Cases :: :: :: --- URL: https://fluxinc.co/case-studies/medical/ct-protocols --- title: Cross-Vendor CT Protocol Harmonization description: Standardize CT protocol naming and parameters across different vendor systems for consistent imaging keywords: CT protocols, DICOM, cross-vendor standardization, protocol harmonization, medical imaging, radiology --- # Cross-Vendor CT Protocol Harmonization ::ContentBox{bgColor="primary" bgShade="800" borderColor="primary" borderShade="800" shadow=false} Multi-vendor CT environments face challenges with inconsistent protocol naming and organization. Our solution ensures standardization across all systems. :: ## The Challenge Healthcare facilities face several challenges with CT protocols: - Inconsistent protocol naming between scanners - Different series numbering conventions - Varying reconstruction descriptions - Incompatible hanging protocols due to naming differences - Complex integration requirements - Quality assurance needs ## How It Works
CT Vendor A BONE
CT Vendor B SHARP
CT Vendor C B70f
→
Capacitor
→
Enterprise PACS Standardized Protocol
## The Solution ::TwoColumn #left Capacitor provides real-time protocol standardization: - Normalizes series descriptions across vendors - Standardizes reconstruction naming - Ensures consistent series ordering - Maps protocol codes to facility standards - Validates protocol compliance - Maintains audit trail #right ### Example Transformations - "BONE" → "Standard Reconstruction" - "SHARP" → "Standard Reconstruction" - "B70f" → "Standard Reconstruction" - Consistent numbering scheme - Unified display protocols :: ::FullWidthSection{variant="gradient" patternOverlay="false"} ## Value Delivered - Consistent reading experience across all vendors - Reliable hanging protocol application - Simplified protocol management - Better integration with reporting systems - Enhanced workflow efficiency - Improved quality assurance :: ::ProseButtonGroup ::ProseButton{to="/contact" variant="primary"} Schedule a Demo :: ::ProseButton{to="/medical/dicom-capacitor/use-cases"} View All Use Cases :: :: --- URL: https://fluxinc.co/case-studies/medical/density-reporting --- title: Breast Density Reporting description: Automate breast density assessment and reporting for mammography with standardized integration keywords: breast density, mammography, DICOM, structured reporting, BIRADS, radiology, women's health --- # Breast Density Reporting ::ContentBox{bgColor="primary" bgShade="800" borderColor="primary" borderShade="800" shadow=false} Breast density information needs to be clearly communicated and integrated into studies. Our solution automates the process while ensuring consistency and compliance. :: ## The Challenge Healthcare facilities face several challenges with breast density reporting: - Need for clear communication of density information - Integration with existing mammography workflows - Compliance with reporting requirements - Consistency across different systems - Efficient report generation - Quality assurance needs ## How It Works
01
Extract
Pull density values from the raw mammography study.
02
Generate
Build the density report card from extracted measurements.
03
Attach
Embed the completed report back into the DICOM study.
04
Validate
Confirm report integrity and completeness before delivery.
## The Solution ::TwoColumn #left Capacitor provides comprehensive density reporting: - Generates BI-RADS density report cards - Extracts structured density data from DICOM - Attaches reports as additional images in study - Ensures consistent formatting and presentation - Automates report generation - Validates data accuracy #right ### Key Features - Automated extraction - Standardized reporting - DICOM compliance - Quality validation - Workflow integration - Audit logging :: ::EmphasisBox ## Value Delivered - Consistent density reporting across facilities - Better patient communication about breast density - Improved compliance with regulatory requirements - Simplified workflow for radiologists and technologists - Enhanced patient care through appropriate follow-up - Reduced liability through consistent documentation ::ProseButtonGroup ::ProseButton{to="/contact" variant="primary"} Schedule a Demo :: ::ProseButton{to="/medical/dicom-capacitor/use-cases"} View All Use Cases :: :: :: --- URL: https://fluxinc.co/case-studies/medical/distribution --- title: Intelligent Image Distribution & Compression description: Optimize DICOM image delivery and storage with intelligent compression and distribution solutions keywords: DICOM compression, image distribution, JP2K, JPEG 2000, PACS integration, tomosynthesis, bandwidth optimization --- # Intelligent Image Distribution & Compression ::ContentBox{bgColor="primary" bgShade="800" borderColor="primary" borderShade="800" shadow=false} Healthcare facilities face multiple challenges with image distribution, from growing study sizes to network bandwidth constraints. Our intelligent distribution solution optimizes image delivery while ensuring diagnostic quality. :: ## The Challenge Healthcare facilities face multiple challenges with image distribution: - Growing study sizes, particularly in tomosynthesis and advanced imaging - Network bandwidth constraints affecting study delivery - Rising storage costs for long-term archives - Different systems (PACS, CAD, workstations) need images in different formats - Varying compression requirements per destination ## How It Works
Modality
→
Capacitor
→
Primary PACS JP2K Compressed
Legacy Workstation JPEG Lossless
Vendor Viewer Native Format
AI / CAD System Custom Format
## The Solution ::TwoColumn #left Capacitor provides comprehensive image distribution management: - Off-device JPEG 2000 lossless compression - Intelligent routing based on image type - DICOM tag manipulation for each destination - Destination-specific compression policies - Automatic format selection based on receiving system capabilities - Background compression that doesn't impact clinical workflow - Automatic attribute correction #right ### Example: Breast Tomosynthesis - Original size: 2GB - After JP2K compression: 1.3GB - Primary PACS receives JP2K compressed images - Legacy workstations receive standard JPEG lossless - Vendor-specific viewers receive native formats - Each destination receives optimized metadata and attributes :: ::EmphasisBox ## Value Delivered - Reduced storage costs (35% savings on average) - Faster image delivery across WAN links - Lower network bandwidth requirements - Optimized viewing experience per workstation - No impact on diagnostic quality - Ensures each system receives images in its preferred format without manual intervention ::ProseButtonGroup ::ProseButton{to="/contact" variant="primary"} Schedule a Demo :: ::ProseButton{to="/medical/dicom-capacitor/use-cases"} View All Use Cases :: :: :: --- URL: https://fluxinc.co/case-studies/medical/format-conversion --- title: Legacy Format Conversion description: Seamlessly convert legacy medical image formats to modern DICOM standards for improved compatibility keywords: DICOM format conversion, legacy medical images, PACS integration, format standardization, medical imaging --- # Legacy Format Conversion ::ContentBox{bgColor="primary" bgShade="800" borderColor="primary" borderShade="800" shadow=false} Older image formats like Siemens CTO and Hologic SCO aren't compatible with modern PACS systems. Our solution provides seamless conversion while preserving all diagnostic information. :: ## The Challenge Healthcare facilities face several challenges with legacy formats: - Older image formats (Siemens CTO, Hologic SCO) aren't compatible with modern PACS - Critical diagnostic information must be preserved during conversion - Need to support both real-time and migration scenarios - Legacy equipment still produces valuable diagnostic data - Complex metadata mapping requirements ## How It Works
Legacy Device Hologic SCO / Siemens CTO
Archive Legacy Format
→
Capacitor
→
Modern PACS BTO Format
VNA Storage Converted
## The Solution ::TwoColumn #left Capacitor offers comprehensive format conversion: - Real-time conversion from Siemens CTO/Hologic SCO to modern BTO format - Preservation of all diagnostic information - Support for both real-time and migration scenarios - Seamless integration with existing workflows - Automatic metadata mapping and harmonization - Quality validation of converted images #right ### Key Features - Zero loss of diagnostic data - Maintains image quality - Preserves study relationships - Supports batch migration - Real-time conversion option - Validation reporting :: ## Value Delivered ::ContentBox{bgColor="primary" bgShade="50" borderColor="primary" borderShade="200" shadow=true} - Extends the life of older equipment - Ensures compatibility with modern PACS systems - Preserves access to historical studies - Reduces migration complexity - Maintains diagnostic quality - Supports phased equipment upgrades :: ::ProseButtonGroup ::ProseButton{to="/contact" variant="primary"} Schedule a Demo :: ::ProseButton{to="/medical/dicom-capacitor/use-cases"} View All Use Cases :: :: --- URL: https://fluxinc.co/case-studies/medical/mobile-workflows --- title: "Mobile Imaging Workflows" description: How Flux Box and DICOM Capacitor support mobile imaging programs — mammography, CT, ultrasound, X-ray, and more — with local worklists, site-aware routing, and real-time or policy-based delivery. keywords: mobile imaging, mobile mammography, mobile CT, mobile ultrasound, mobile X-ray, mobile MRI, mobile imaging van, PACS gateway, worklist caching, geolocation routing, Flux Box, DICOM Capacitor --- # Mobile Imaging Workflows ::ContentBox{bgColor="primary" bgShade="800" borderColor="primary" borderShade="800" shadow=false} This is the operational companion to [Mobile Imaging](/medical/mobile-imaging). Flux Box and DICOM Capacitor sit between the mobile unit and hospital systems to keep workflows stable across changing networks — for any modality. - **Keeps** local worklists available on the vehicle - **Caches** studies to encrypted local storage - **Delivers** in real time over wireless or later by site policy - **Routes** each study to the correct destination automatically The modality talks only to Capacitor. Capacitor handles connectivity, retries, routing, integrity, and delivery so technologists can keep scanning instead of babysitting network sends. :: ## Why Mobile Imaging Needs More Control Mobile imaging vehicles operate where network connectivity is **intermittent**, **unreliable**, or entirely **unavailable** for stretches of the day. That is manageable for small studies. It becomes much more serious as study sizes grow — large CT volumes, multi-sequence MR, digital breast tomosynthesis — and downstream workflows become less forgiving: - **Cellular signals** drop mid-transfer - **VPN tunnels** time out - **LTE throughput** fluctuates wildly between stops Without an intermediary, these conditions lead to failed sends at the modality, partial studies in PACS, duplicated exams, patient-matching risk, and technologists managing retransmissions instead of patients. DICOM Capacitor absorbs these problems without changing the technologist workflow. ## Typical Mobile Imaging Setup
Modality CT / Mammo / US / X-ray
→
Capacitor
→
Network Cellular / VPN / Wi-Fi
→
Hospital PACS
The modality talks only to Capacitor. Capacitor worries about connectivity, retries, integrity, and delivery. --- ## How the Workflow Holds Together ### Study Acquisition - Modality sends the study to Capacitor via standard **DICOM C-STORE** - Capacitor is on the local network, so transfer completes at **LAN speed** — effectively instant - **No waiting**, no failed sends on the modality console, no technologist intervention required ### Local Caching and Validation Once received, Capacitor: - **Writes** the study to local encrypted storage - **Validates** SOP completeness, image count, and DICOM header integrity - **Queues** the study for delivery At this point the study is safe, even if the vehicle loses signal entirely. ### Connectivity-Aware Transmission When a network path is available and the current delivery policy allows it, Capacitor begins transmitting queued studies to PACS asynchronously: - **Automatic retries** on failure - **Bandwidth throttling** to avoid saturating the link - **Resume-on-failure** — picks up exactly where it left off - **No corruption**, no duplicates, no human involvement required ### Interrupted Transfer Resume Transmission batch size is fully configurable: - **By count** — a specific number of images at a time - **By size** — a defined amount in megabytes or gigabytes - **By study** — entire studies as a unit - **Single or multiple associations** — Capacitor manages both If the connection drops, Capacitor tracks exactly which images were successfully acknowledged and resumes by sending only the **balance of undelivered images**. Nothing is resent unnecessarily, and nothing is lost. ### Guaranteed Delivery A study is marked complete only when: - PACS sends a successful **DICOM acknowledgment** - All **SOP instances** are confirmed delivered Until then, the study remains queued and retries continue automatically. ::InfoBox For full configuration details on batch sizes, retry behavior, transfer syntax options, and process scheduling, see the [DICOM Capacitor documentation](https://docs.fluxinc.co/dicom-capacitor/). :: --- ## Worklist Caching In mobile environments, the modality needs access to a worklist to pull scheduled orders — but the worklist server is back at the facility, on the other side of an unreliable link. Capacitor solves this by acting as a **local worklist proxy**. ::TwoColumn #left ### Cache and Sync - Modality queries Capacitor for a worklist — Capacitor serves results from its **local cache** - At a configurable interval, Capacitor repeats the query against the facility's worklist server whenever **connectivity is available** - Each reconnection pulls an **expanded list** of orders — not just the specific one the scanner requested - Modality always has access to the **last best worklist**, even when the vehicle is completely offline #right ### Real-Time Worklist Correction Capacitor also provides automatic worklist cleanup: - **Sanitizing** special characters - **Standardizing** procedure codes - **Correcting** attribute mapping issues - **Ensuring** compatibility with downstream systems This reduces failed DICOM queries and eliminates manual worklist corrections at the modality. :: --- ## Zero-Configuration Destination Management In many mobile programs, a single vehicle travels between multiple facilities. Each facility has its own PACS, and images from one site must never be delivered to another. Capacitor supports a **zero-configuration mode**: - Modality sends to one destination — the **local Capacitor** - Capacitor manages all downstream **routing automatically** - Uses **geolocation**, **network detection** via IP address, and **node detection** to determine the current facility - **Switches destinations** automatically when the vehicle moves - Optionally **isolates the cache** so studies from the previous stop don't straggle to the new location - Each facility receives **exactly and only** the images that belong to it --- ## Flexible Delivery Policies Some programs want studies moving over wireless immediately. Others prefer to hold them for a known network or scheduled window. Capacitor supports both while preserving the same **fire-and-forget** experience for technologists: ::TwoColumn #left ### Real-Time Wireless Delivery - **Begins transmission immediately** when the available wireless link supports it - **Retries automatically** on failures and resumes from the last acknowledged image - **Keeps images moving** toward PACS and downstream readers as soon as they are acquired - **Requires no technologist action** beyond sending to the local box #right ### Docked or Scheduled Delivery - **Holds queued studies** until a known Wi-Fi, wired network, or scheduled delivery window is available - **Reduces cellular usage** when that is the program's operating preference - **Starts transfer automatically** when policy conditions are met - **Keeps the technologist workflow unchanged** with no end-of-day send step :: These policies can be combined. Studies are still validated, queued, and deduplicated regardless of when delivery occurs. The technologist workflow stays the same: acquire the exam, send to Capacitor, move on. --- ## Adaptive Network Intelligence Capacitor continuously monitors network conditions and **self-tunes** for best-effort delivery: - **Detects** current transmission speed in real time - **Reconfigures** timeout values and retry intervals on the fly - **Widens tolerances** on slow, intermittent connections to maximize delivery within each connectivity window - **Tightens parameters** when throughput improves to move studies faster - **Learns** from its own success and failure rates — no manual tuning required This adaptive behavior extends to time-to-live values for queued images. Network conditions change from stop to stop, and study sizes vary widely — from lightweight ultrasound to large CT or DBT acquisitions. Capacitor adjusts automatically. --- ::FullWidthSection{variant="dark" padding="lg"} ## Mobile Workflow Risks It Reduces | Challenge | What Capacitor Does | |---|---| | Cellular drops mid-study | Buffers locally, resumes automatically | | Technologist has to resend manually | Eliminates all manual resend workflows | | Partial studies reach PACS | Blocks incomplete delivery until all SOPs confirmed | | Slow or degraded LTE | Throttles, adapts timeouts, resumes on failure | | Duplicate exams in PACS | Deduplicates SOPs; sends only unacknowledged images | | Lost exams | Guarantees delivery with persistent local queue | | Worklist unavailable on vehicle | Serves cached worklist locally; syncs when connected | | Vehicle moves between facilities | Auto-detects location and routes to correct PACS | | Network conditions change constantly | Self-tunes timeouts and retry parameters in real time | | Delivery policy varies by program | Sends immediately over wireless or waits for Wi-Fi/schedule, depending on policy | | Tech must manually transmit at end of day | Fire-and-forget; Capacitor delivers automatically based on network or schedule | :: --- ::EmphasisBox ## Where It Fits - **Reduces** failed exams and PACS support calls - **Eliminates** manual resend workflows - **Protects** revenue and regulatory compliance - **Works** even when the vehicle is fully offline Works across modalities: mammography, CT, ultrasound, X-ray, MRI, and others. *Available as software or as pre-configured [Flux Box hardware](/medical/flux-box).* ::ProseButtonGroup ::ProseButton{to="/contact" variant="primary"} Schedule a Demo :: ::ProseButton{to="/medical/mobile-imaging"} Mobile Imaging Overview :: ::ProseButton{to="https://docs.fluxinc.co/dicom-capacitor/" variant="outline"} Technical Docs :: :: :: --- URL: https://fluxinc.co/case-studies/medical/mr-sequences --- title: MR Sequence Normalization description: Standardize MR sequence naming and parameters across different vendors for consistent imaging protocols keywords: MR sequences, magnetic resonance, DICOM, protocol standardization, radiology, imaging harmonization --- # MR Sequence Normalization ::ContentBox{bgColor="primary" bgShade="800" borderColor="primary" borderShade="800" shadow=false} MRI studies often have vendor-specific sequence naming and inconsistent organization. Our solution ensures standardized presentation across all systems. :: ## The Challenge Healthcare facilities face several challenges with MR sequences: - Vendor-specific sequence naming - Inconsistent series numbering - Missing or non-standard orientation codes - Varying contrast phase descriptions - Complex display protocol requirements - Quality assurance needs ## How It Works
01
Standardize
Normalize sequence names across scanner vendors and sites.
02
Order
Sort series into the correct clinical display order.
03
Orient
Correct image orientation metadata for consistent display.
04
Validate
Confirm the study passes workstation acceptance checks.
## The Solution ::TwoColumn #left Capacitor automatically: - Standardizes sequence descriptions - Corrects plane descriptions - Normalizes contrast phase labeling - Ensures proper series ordering - Validates sequence completeness - Maintains audit trail #right ### Example Transformations - "tse_T2" → "T2 TSE Axial" - Standardizes SAG/COR/TRA descriptions - Normalizes contrast timing labels - Consistent numbering scheme - Unified display protocols :: ::FullWidthSection{variant="gradient" patternOverlay="false"} ## Value Delivered - Consistent display protocols across vendors - Better integration with AI/post-processing - Reduced manual series selection - Enhanced reading experience - Simplified protocol management ::ProseButtonGroup ::ProseButton{to="/contact" variant="primary"} Schedule a Demo :: ::ProseButton{to="/medical/dicom-capacitor/use-cases"} View All Use Cases :: :: :: --- URL: https://fluxinc.co/case-studies/medical/nuclear-med --- title: DICOM Capacitor for Nuclear Medicine description: Optimize nuclear medicine workflows with reliable DICOM routing and storage for PET/CT, SPECT, and gamma cameras keywords: nuclear medicine, DICOM routing, PET/CT, SPECT, SUV calculation, phase labeling, medical imaging --- # Nuclear Medicine Study Completion ::ContentBox{bgColor="primary" bgShade="800" borderColor="primary" borderShade="800" shadow=false} Nuclear Medicine studies require complex organization and validation. Our solution ensures accurate quantification and consistent presentation. :: ## The Challenge Healthcare facilities face several challenges with Nuclear Medicine studies: - Complex multi-phase organization - Time point standardization needs - SUV calculation validation requirements - Cross-vendor protocol matching - Quality assurance requirements - Research data consistency ## How It Works
01
Label
Assign correct phase labels to each acquisition frame.
02
Validate
Confirm time point data is present and internally consistent.
03
Verify
Check SUV values against expected ranges for the protocol.
04
Normalize
Standardize protocol naming for PACS display and reporting.
## The Solution ::TwoColumn #left Capacitor provides: - Automated phase and time point labeling - SUV calculation verification and correction - Standard uptake time validation - Protocol name normalization - Study completeness validation - Research data support #right ### Key Features - Phase organization - Time point tracking - SUV validation - Protocol matching - Quality assurance - Research support :: ## Value Delivered ::ContentBox{bgColor="primary" bgShade="50" borderColor="primary" borderShade="200" shadow=true} - Consistent quantitative measurements - Reliable temporal study organization - Improved reading efficiency - Better research data consistency - Enhanced quality assurance - Simplified workflow management :: ::ProseButtonGroup ::ProseButton{to="/contact" variant="primary"} Schedule a Demo :: ::ProseButton{to="/medical/dicom-capacitor/use-cases"} View All Use Cases :: :: --- URL: https://fluxinc.co/case-studies/medical/prefetch --- title: "Intelligent DICOM Prefetch with Capacitor" description: Worklist-driven prior study prefetch that retrieves, filters, converts, and stages relevant priors before the patient arrives — eliminating workflow delays keywords: DICOM prefetch, prior study retrieval, worklist prefetch, mammography priors, PACS query retrieve, DICOM Capacitor, intelligent prefetch, prior image routing, Flux Inc --- # Intelligent DICOM Prefetch ::ContentBox{bgColor="primary" bgShade="800" borderColor="primary" borderShade="800" shadow=false} Radiologists need prior studies available during the exam — not after. But built-in prefetch on most workstations doesn't retrieve priors until the patient is already positioned, pulls everything indiscriminately, and can't coordinate across archives. DICOM Capacitor monitors the worklist, **triggers prefetch hours or days before the exam**, filters by relevance, converts formats inline, and stages priors so they're ready when the patient arrives. :: ## The Problem with Traditional Prefetch Most prefetch solutions — whether built into acquisition workstations or offered as standalone routers — share the same fundamental limitations: ### Timing - Prefetch triggers only at **study commencement** — patient already positioned - Technologists must **wait** for prior transfers to complete - On slow or congested networks, this delay makes prefetch **impractical** ### Filtering - All prior studies are retrieved, **regardless of relevance** - Non-mammography images (chest X-rays, ultrasounds) are unnecessarily transferred - **Network bandwidth** and **local storage** consumed by irrelevant data - Large transfers further **increase waiting time** ### Vendor Lock-In - Many prefetch solutions are **tied to a single vendor's ecosystem** - Limited to specific PACS or workstation platforms - No format conversion — proprietary images stay proprietary - Upgrading or migrating means re-implementing prefetch from scratch The result: technologists either wait too long or skip priors entirely. --- ## How Capacitor Solves It ### Worklist-Based Early Trigger The key innovation is **automated prefetch initiation** based on the worklist, not study commencement: - Capacitor **monitors** the DICOM Worklist for upcoming appointments - When new appointments appear, it **automatically initiates** prefetch - Starts the process **hours or days** before the exam - Transfers scheduled during **off-peak hours** (typically overnight) - Prior images are **ready before the patient arrives** - **Zero workflow delay** for technologists
Worklist Server upcoming appointments
→
Capacitor queries overnight
→
Archive / VNA filtered priors
→
PACS / Workstation staged, ready on arrival
### Smart Filtering Capacitor dynamically filters studies based on configurable rules: - **Modality** — only mammography images, not chest X-rays - **Study age** — e.g., last 5 years only - **Body part** — relevant anatomy only - **Protocol** — specific exam types - **Any DICOM attribute** — fully configurable filter expressions This **dramatically reduces** unnecessary data transfer, preserves network bandwidth, and prevents local storage overflow. ### Multi-Source Coordination Many facilities store older studies in long-term archives, requiring multi-step retrieval: 1. **Find** archived studies that need to be retrieved 2. **Move** studies from archive to main PACS (often overnight) 3. **Transfer** from PACS to the workstation 4. **Verify** everything is staged and ready Capacitor manages this entire chain: - **Coordinates** across archive, PACS, and workstation - **Tracks** when studies arrive at each stage - **Handles** VNAs, tiered storage, and multiple PACS systems - **Ensures** all priors are ready when needed --- ## Format Conversion on Prefetch Prior studies from external sources or legacy archives often arrive in proprietary formats. Capacitor converts inline during prefetch: - **SCO → BTO** — Hologic proprietary tomosynthesis format to DICOM standard - **CTO → BTO** — Siemens legacy single-frame tomosynthesis to standard multi-frame - **DICOM tag harmonization** — corrects metadata inconsistencies across PACS sources - **Compression** — JPEG 2000 to optimize storage and transfer Radiologists see standard BTO regardless of the original format. No manual intervention, no broken displays. [Format conversion details →](/case-studies/medical/sco-bto-conversion) --- ::FullWidthSection{variant="dark" padding="lg"} ## Traditional Prefetch vs. Capacitor | Capability | Traditional Prefetch | Capacitor Prefetch | |---|---|---| | Trigger timing | At study commencement | Hours/days before exam | | Filtering | None or basic — retrieves everything | By modality, age, body part, protocol, any DICOM attribute | | Multi-source | Single PACS or vendor-specific | Archive, VNA, multiple PACS — vendor-neutral | | Format conversion | None | SCO/CTO → BTO inline | | Scheduling | Immediate only | Off-peak, overnight, or on-demand | | Network impact | Full bandwidth during clinical hours | Scheduled to avoid congestion | | Storage management | Fills storage indiscriminately | Filtered — only relevant priors | | Vendor compatibility | Tied to one ecosystem | Any PACS, any modality, any vendor | | Optimization | Static configuration | Flux tunes per site over time | :: --- ## Ongoing Optimization Flux maintains active partnerships with customers to continuously optimize prefetch: - **Regular consultation** — review effectiveness, update filtering rules based on technologist feedback - **Schedule tuning** — adjust transfer windows to match facility workflows - **PACS compatibility** — proactively test against new PACS versions, update protocols as needed - **Network optimization** — fine-tune bandwidth utilization parameters - **Site-specific customization** — each deployment is tailored to local workflow, storage, and network constraints Prefetch configuration is not a one-time setup — Flux engineers remain available to adjust as needs evolve. ::InfoBox For configuration details on prefetch triggers, filter expressions, scheduling windows, and multi-source coordination, see the [DICOM Capacitor documentation](https://docs.fluxinc.co/dicom-capacitor/). :: ::EmphasisBox ## Get Started Whether you need prefetch for mammography, CT, or multi-modality workflows — Capacitor retrieves the right priors, at the right time, in the right format. ::ProseButtonGroup ::ProseButton{to="/contact" variant="primary"} Schedule a Demo :: ::ProseButton{to="/medical/flux-box"} Flux Box Hardware :: ::ProseButton{to="/medical/dicom-capacitor/use-cases"} View All Use Cases :: :: :: --- URL: https://fluxinc.co/case-studies/medical/routing --- title: Multi-Destination Routing & Transformation description: Intelligently route and transform DICOM studies to multiple destinations with automated workflows keywords: DICOM routing, multi-destination, PACS integration, format conversion, DICOM compression, medical imaging workflow --- # Multi-Destination Routing & Transformation ::ContentBox{bgColor="primary" bgShade="800" borderColor="primary" borderShade="800" shadow=false} Different systems need images in different formats with different attributes. Our solution ensures each destination receives optimized images without manual intervention. :: ## The Challenge Healthcare facilities face several challenges with multi-destination routing: - Different systems need images in different formats - Each destination requires specific DICOM attributes - Manual routing leads to errors and delays - Complex compression requirements per destination - Need for real-time format conversion - Varying metadata requirements ## How It Works
Modality
→
Capacitor
→
Primary PACS Format A
AI System Format B
VNA Archive Format C
Workstation Format D
## The Solution ::TwoColumn #left Capacitor provides comprehensive routing management: - Intelligent routing based on image type - DICOM tag manipulation for each destination - Compression optimization per destination - Automatic attribute correction - Real-time format conversion - Destination-specific metadata mapping #right - Rule-based routing - Format validation - Error recovery - Audit logging - Performance monitoring - Quality assurance :: ::EmphasisBox ## Value Delivered - Eliminates manual routing errors - Ensures optimal image format per destination - Reduces workflow complexity - Improves system integration - Enhances data consistency - Supports complex workflows ::ProseButtonGroup ::ProseButton{to="/contact" variant="primary"} Schedule a Demo :: ::ProseButton{to="/medical/dicom-capacitor/use-cases"} View All Use Cases :: :: :: --- URL: https://fluxinc.co/case-studies/medical/sco-bto-conversion --- title: "SCO & CTO to BTO Conversion for Mammography" description: Convert proprietary Hologic SCO and Siemens CTO tomosynthesis formats to standard DICOM BTO for PACS interoperability, migrations, and prior study access keywords: SCO to BTO, CTO to BTO, Hologic SCO conversion, Siemens CTO conversion, breast tomosynthesis object, DICOM mammography migration, PACS interoperability, tomosynthesis format conversion, DICOM Capacitor --- # SCO & CTO to BTO Conversion ::ContentBox{bgColor="primary" bgShade="800" borderColor="primary" borderShade="800" shadow=false} Modern PACS systems expect mammography tomosynthesis data in **BTO format** — the DICOM standard (Breast Tomosynthesis Object). But many facilities have years of studies stored in proprietary formats that no longer display correctly. DICOM Capacitor converts both **Hologic SCO** and **Siemens CTO** formats to standard BTO — inline during routing, on prefetch, or as a managed bulk migration. :: ## The Format Problem Breast tomosynthesis was adopted by vendors before the DICOM standard caught up. The result is three incompatible formats in the wild: ### BTO — Breast Tomosynthesis Object (Standard) - **DICOM Supplement 125** — ratified in 2008 - **Multi-frame** MG object with enhanced multi-frame structure - **SOP Class** `1.2.840.10008.5.1.4.1.1.13.1.3` - What every modern PACS, viewer, and CAD system expects ### SCO — Secondary Capture Object (Hologic) - Produced by Hologic Selenia and Dimensions systems - **Proprietary format** — real pixel data is hidden in private DICOM attributes (`7E01,1010`) - Visible pixel data is **meaningless placeholder** content - Internal compression uses **JPEG-LS** (near-lossless, error tolerance of 4) - Cannot be displayed by standard PACS — requires explicit extraction and re-encoding ### CTO — Computed Tomography Object (Siemens) - Produced by Siemens Mammomat Inspiration, optionally by Revelation - **Single-frame-per-instance** — each tomo slice is a separate CT-class DICOM object - Uses CT SOP Class instead of MG - Modern PACS may **refuse** these objects or hang them incorrectly
Hologic SCO
Siemens CTO
⇄
Capacitor
⇄
DICOM BTO
## Why This Matters Now Facilities hit this problem during: - **PACS migrations** — legacy archive contains SCO/CTO studies that won't display on the new system - **Multi-vendor environments** — Hologic gantry sends SCO, but the PACS only supports BTO - **Prior study retrieval** — outside priors arrive in SCO from referring facilities - **CAD integration** — iCAD, Transpara, and Volpara require BTO input - **Archive consolidation** — merging data from multiple facilities with different scanner vendors Without conversion, these studies are **invisible** to radiologists — they exist in the archive but cannot be displayed, compared, or processed. --- ## How Capacitor Handles It ### Inline Conversion During Routing - Capacitor sits between the modality and PACS - As studies arrive, Capacitor **detects** the format (SCO, CTO, or BTO) - Non-standard formats are **converted to BTO** in transit before delivery to PACS - No separate migration step — conversion happens as part of normal routing - **Bidirectional** — Capacitor can also convert BTO back to SCO or CTO when a downstream system requires it ### Conversion on Prefetch - When Capacitor [prefetches prior studies](/case-studies/medical/prefetch) from an archive or external source, incoming priors may arrive as SCO or CTO - Capacitor **converts inline** before delivering to the workstation - Radiologists see standard BTO regardless of the original format - No manual intervention required ### Managed Bulk Migration For facilities with large archives of legacy SCO or CTO data, Flux provides managed migration: - **Site assessment** — analyze archive contents, identify format distribution - **Pilot conversion** — convert a sample batch, validate against PACS and CAD - **Bulk processing** — convert the full archive with progress tracking and validation - **Ongoing conversion** — Capacitor continues converting new incoming priors automatically --- ## What Gets Converted Capacitor handles the full complexity of each format: ::TwoColumn #left ### SCO → BTO - **Extracts** real pixel data from private attributes (`7E01,1010` or `7E01,1011`) - **Decodes** JPEG-LS compressed data with correct error tolerance - **Reconstructs** as multi-frame BTO with proper MG attributes - **Preserves** all patient, study, and series metadata - **Maintains** StudyInstanceUID linkage for CAD, SR, and PR objects #right ### CTO → BTO - **Collects** individual single-frame CT instances into a single study - **Restructures** into multi-frame BTO with enhanced multi-frame functional groups - **Remaps** CT SOP Class to Breast Tomosynthesis SOP Class - **Corrects** Image Type, Modality, and other MG-specific attributes - **Preserves** spatial positioning and slice ordering :: --- ::FullWidthSection{variant="dark" padding="lg"} ## Scanner and Format Compatibility | Scanner | Vendor | Output Format | Capacitor Conversion | |---|---|---|---| | Selenia | Hologic | SCO | SCO → BTO | | Selenia Dimensions | Hologic | SCO | SCO → BTO | | 3Dimensions | Hologic | SCO or BTO | SCO → BTO (when needed) | | Mammomat Inspiration | Siemens | CTO | CTO → BTO | | Mammomat Revelation | Siemens | CTO or BTO | CTO → BTO (when needed) | | B.Brilliant | Siemens | BTO | No conversion needed | Capacitor also handles **reverse conversion** (BTO → SCO, BTO → CTO) for facilities that need to route studies back to legacy systems. :: --- ## Integration with CAD and AI Converted BTO studies work with all major mammography CAD and AI platforms: - **iCAD** PowerLook / ProFound AI - **Transpara** (ScreenPoint Medical) - **Volpara** density and risk assessment - **GE** SenoIris / Centricity - **Hologic** SecurView (via reverse conversion when required) Capacitor ensures that CAD, SR, and PR objects remain **properly linked** to their parent studies after conversion — no ghost studies, no broken references. ::EmphasisBox ## Get Started Whether you need inline conversion for day-to-day routing, format conversion on prefetch, or a managed archive migration — Capacitor handles it. ::ProseButtonGroup ::ProseButton{to="/contact" variant="primary"} Schedule a Demo :: ::ProseButton{to="/medical/flux-box"} Flux Box Hardware :: ::ProseButton{to="https://docs.fluxinc.co/dicom-capacitor/" variant="outline"} Technical Docs :: :: :: --- URL: https://fluxinc.co/case-studies/medical/securview --- title: SecurView Integration description: Optimize mammography workflows with seamless SecurView integration and automated data synchronization keywords: SecurView, mammography, DICOM, breast imaging, Hologic, PACS integration, radiology --- # SecurView Integration ::ContentBox{bgColor="primary" bgShade="800" borderColor="primary" borderShade="800" shadow=false} SecurView systems have specific requirements for image format and metadata. Our solution ensures seamless integration and optimal image presentation. :: ## The Challenge Healthcare facilities using SecurView face several challenges: - Specific format requirements for optimal viewing - Need for consistent image descriptions - Complex image stacking and ordering rules - Metadata harmonization requirements - Integration with existing workflows - Quality assurance needs ## How It Works
01
Convert
Translate proprietary format to SecurView-compatible DICOM.
02
Harmonize
Align metadata fields to SecurView expectations.
03
Stack
Organize image series into correct display stacks.
04
Validate
Verify output against SecurView acceptance criteria.
## The Solution ::TwoColumn #left Capacitor offers comprehensive SecurView integration: - Format conversion optimized for SecurView - Consistent image descriptions - Correct image stacking and ordering - Automated metadata harmonization - Real-time processing - Quality validation #right ### Key Features - Automatic format optimization - Metadata standardization - Study validation - Error correction - Performance monitoring - Workflow integration :: ::FullWidthSection{variant="gradient" patternOverlay="false"} ## Value Delivered - Seamless SecurView integration - Optimal image presentation - Reduced manual intervention - Improved workflow efficiency - Enhanced diagnostic quality - Better user experience ::ProseButtonGroup ::ProseButton{to="/contact" variant="primary"} Schedule a Demo :: ::ProseButton{to="/medical/dicom-capacitor/use-cases"} View All Use Cases :: :: :: --- URL: https://fluxinc.co/case-studies/medical/tag-harmonization --- title: Advanced DICOM Tag Harmonization description: Standardize DICOM attributes across multiple vendors for consistent display and workflow keywords: DICOM tags, attribute harmonization, modality worklist, PACS integration, medical imaging standards --- # Advanced DICOM Tag Harmonization ::ContentBox{bgColor="primary" bgShade="800" borderColor="primary" borderShade="800" shadow=false} Mammography systems produce DICOM tags that can be inconsistent or non-standard. Our solution ensures consistent, standardized tags across all systems. :: ## The Challenge Healthcare facilities face several challenges with DICOM tags: - Inconsistent tags between software versions - Non-standard view codes or descriptions - Missing critical sequence information - Invalid characters or formatting - Complex integration requirements - Quality assurance needs ## How It Works
01
Standardize
Normalize view codes to DICOM standard across all vendors.
02
Sequences
Add required sequence data where it is absent.
03
Correct
Replace non-conformant codes with correct standard values.
04
Validate
Confirm the study passes DICOM conformance checks.
## The Solution ::TwoColumn #left Capacitor provides sophisticated tag manipulation: - Standardizes view descriptions - Adds missing sequences - Corrects view position codes - Ensures consistent series descriptions - Validates tag compliance - Maintains audit trail #right ### Example Transformations - "BTO_TOMO, L-CC, PRIME" → "L CC Tomosynthesis" - Adds spot compression and magnification sequences - Corrects XCCL coding - Standardizes naming across vendors :: ::FullWidthSection{variant="gradient" patternOverlay="false"} ## Value Delivered - Improved reading workflow with standardized naming - Better integration with third-party AI and CAD systems - Reduced errors in image display order - Consistent appearance in PACS worklists - Enhanced data consistency - Simplified system integration ::ProseButtonGroup ::ProseButton{to="/contact" variant="primary"} Schedule a Demo :: ::ProseButton{to="/medical/dicom-capacitor/use-cases"} View All Use Cases :: :: :: --- URL: https://fluxinc.co/case-studies/medical/tomosynthesis --- title: Advanced Tomosynthesis Integration description: Optimize breast tomosynthesis workflows with standardized organization and consistent display protocols keywords: tomosynthesis, breast imaging, DICOM, 3D mammography, PACS integration, radiology --- # Advanced Tomosynthesis Integration ::ContentBox{bgColor="primary" bgShade="800" borderColor="primary" borderShade="800" shadow=false} Modern tomosynthesis workflows require standardized organization and consistent display protocols. Our solution ensures optimal presentation and workflow efficiency. :: ## The Challenge Healthcare facilities face several challenges with tomosynthesis: - Complex sequence organization requirements - Inconsistent compression view labeling - Non-standardized naming conventions - Varying display protocols - Integration with multiple systems - Quality assurance needs ## How It Works
01
Organize
Sort tomosynthesis sequences into correct acquisition order.
02
Standardize
Normalize view codes to enterprise PACS expectations.
03
Optimize
Trim and correct metadata for faster PACS ingestion.
04
Validate
Confirm the complete study passes enterprise PACS validation.
## The Solution ::TwoColumn #left Capacitor automatically: - Enhances sequence organization - Standardizes view descriptions - Optimizes metadata for display - Ensures enterprise-wide consistency - Validates study completeness - Maintains audit trail #right ### Key Features - Automated organization - Standardized naming - Display optimization - Quality validation - System integration - Performance monitoring :: ::EmphasisBox ## Value Delivered - Complete study information for proper diagnosis - Consistent display protocols - Improved workflow efficiency - Better integration with existing systems - Enhanced reading experience - Reduced manual intervention ::ProseButtonGroup ::ProseButton{to="/contact" variant="primary"} Schedule a Demo :: ::ProseButton{to="/medical/dicom-capacitor/use-cases"} View All Use Cases :: :: :: --- URL: https://fluxinc.co/case-studies/medical/worklist --- title: DICOM Capacitor for Worklist Enhancement description: Ensure reliable DICOM worklist queries with automatic data cleaning and standardization for medical imaging workflows keywords: DICOM worklist, modality worklist, MWL, RIS integration, worklist error correction, medical scheduling, worklist standardization --- # Worklist Integration Enhancement ::ContentBox{bgColor="primary" bgShade="800" borderColor="primary" borderShade="800" shadow=false} Worklist entries often contain inconsistencies that can disrupt workflow. Our solution ensures clean, standardized data flow between systems. :: ## The Challenge Healthcare facilities face several challenges with worklist integration: - Inconsistent patient/study information - Characters that cause parsing errors - Missing or incorrect procedure codes - Incompatible attribute formats - Integration with multiple systems - Quality assurance requirements ## How It Works
01
Sanitize
Strip non-ASCII characters and encoding artifacts from patient fields.
02
Standardize
Normalize procedure codes to the modality's expected vocabulary.
03
Map
Translate RIS attribute names to DICOM MWL field mappings.
04
Deliver
Send the cleaned worklist to modalities on the local network.
## The Solution ::TwoColumn #left Capacitor provides real-time worklist correction: - Sanitizes special characters and invalid formatting - Standardizes procedure codes and descriptions - Corrects attribute mapping issues - Ensures compatibility with mammography systems - Validates data consistency - Maintains audit trail #right ### Key Features - Real-time processing - Character sanitization - Code standardization - Attribute mapping - Error correction - Performance monitoring :: ::FullWidthSection{variant="gradient" patternOverlay="false"} ## Value Delivered - Reduced manual worklist corrections - Fewer failed DICOM queries - More reliable modality scheduling - Better integration between RIS and PACS - Enhanced workflow efficiency - Improved data consistency :: ::ContentBox{bgColor="light" borderColor="primary" borderShade="200" shadow=false} ### Testing & Development Need to test your worklist integration before deploying in production? Try our [Public Test DICOM Modality Worklist](/posts/public-test-dicom-modality-worklist) - a free resource for testing DICOM worklist connectivity and functionality. :: ::ProseButtonGroup ::ProseButton{to="/contact" variant="primary"} Schedule a Demo :: ::ProseButton{to="/medical/dicom-capacitor/use-cases"} View All Use Cases :: :: --- URL: https://fluxinc.co/contact --- title: Contact Us description: Get in touch with Flux Inc's DICOM experts for technical support, sales inquiries, or custom healthcare solutions keywords: DICOM support, medical imaging help, technical support, healthcare IT consulting, medical software solutions sitemap: changefreq: monthly --- # Contact Us We'd love to hear from you. Reach out to discuss how Flux Inc can transform your healthcare technology. ## Get in Touch - **Email**: [info@fluxinc.co](mailto:info@fluxinc.co) - **Phone**: [+1 (470) 890-1007](tel:+14708901007) ## Request a Demo Interested in seeing our products in action? Please contact us to schedule a demo. - **Sales Email**: [sales@fluxinc.co](mailto:sales@fluxinc.co) - **Sales Phone**: [+1 (470) 890-1007](tel:+14708901007) ## Technical Support For technical support inquiries: - **Support Email**: [support@fluxinc.co](mailto:support@fluxinc.co) - **Support Phone**: [+1 (470) 890-1007](tel:+14708901007) - **Phone Hours (off-contract hours)**: 6am - 9pm EST, Monday - Friday ## Accounts Payable and Receivables For accounts payable and receivables inquiries: - **Email**: [accounts@fluxinc.co](mailto:accounts@fluxinc.co) - **Phone**: [+1 (470) 890-1007](tel:+14708901007) ### Office Locations Flux Software LLC, dba Flux Inc
1225 Johnson Ferry Road, Suite 530
Marietta, GA 30068
USA Flux Software Inc.
100 Broadview Ave, Suite 300
Toronto, ON M4M 3H3
Canada ### Mail Correspondence and Returns To: Flux Software LLC
6595 Roswell Rd, G2457
Atlanta, GA 30328
USA Flux Software Inc.
2967 Dundas St. W. #444D
Toronto, ON M6P 1Z2
Canada --- URL: https://fluxinc.co/flux-mentor --- title: Flux Mentor | On-Prem AI with RAG | Flux Inc description: Secure, on-premises AI solution with Retrieval-Augmented Generation (RAG) that keeps your organizational knowledge private while providing powerful AI capabilities. keywords: RAG, retrieval augmented generation, on-prem AI, secure AI, organizational knowledge, enterprise AI, privacy-focused AI ogImage: /images/flux-inc-logo-color.png sitemap: changefreq: monthly --- ::FullWidthSection{variant="custom" padding="sm" className="bg-transparent" backgroundImage="/images/hero.webp" backgroundOverlayClass="bg-gradient-to-br from-primary-500/80 via-pink-700/100 to-indigo-500/90"} # Flux Mentor :: ## Secure On-Prem AI Powerful AI capabilities with your data staying on your premises. Flux Mentor uses Retrieval-Augmented Generation (RAG) to provide context-aware responses based on your organization's unique knowledge base. ::ProseButtonGroup ::ProseButton{to="/contact?product=FluxMentor" variant="primary"} Request a Demo :: ::ProseButton{to="/case-studies/densebreast-ai-chatbot" variant="secondary"} View Our Case Study :: :: ## Get Control of Your Data Flux Mentor provides advanced AI capabilities without sending your sensitive data to external services:
RIS patient records & schedules
PACS imaging studies
Documents reports, PDFs, notes
⇄
Flux Mentor on-premises
→
Answer cited, traceable
::TwoColumn # left ### On-Premise Deployment Deploy Flux Mentor entirely within your infrastructure. Your data never leaves your premises, ensuring maximum security and compliance with data privacy regulations. ### Secure Knowledge Integration Connect Flux Mentor to your existing document repositories, databases, intranets, and knowledge bases with granular conversational access controls. ### Complete Access Control Define precisely which users, groups, and systems can access specific information. Implement role-based permissions that integrate with your existing authentication systems. ### Conversational Configuration You shouldn't have to be a developer to configure Flux Mentor. Flux Mentor is designed to be configured through natural language. Mentor responds to management instructions in a hierarchical, human-like, and precise manner. # right ### Context-Aware Responses Flux Mentor understands your organization's unique terminology, processes, and information landscape, providing responses that reflect your specific context. ### Traceable Results Every AI response includes citations and references to your internal documents, ensuring transparency and traceability in decision-making. ### Continuous Learning Flux Mentor improves over time by learning from interactions while respecting privacy boundaries you define. Performance analytics help you optimize without compromising security. :: ## How Flux Mentor Works Retrieval-Augmented Generation (RAG), powered by technologies like [Morphik](https://www.morphik.ai/), combines information retrieval with generative AI to provide accurate, context-aware responses. 1. **Index Your Knowledge**: Flux Mentor securely indexes your organizational documents, databases, and knowledge repositories. 2. **Query Understanding**: When a user asks a question, Flux Mentor analyzes it to understand the intent and context. 3. **Relevant Retrieval**: The system retrieves the most relevant information from your knowledge base. 4. **Contextual Generation**: Using retrieved information as context, Flux Mentor generates accurate responses based on your organizational knowledge. 5. **Continuous Improvement**: The system learns from interactions to improve retrieval and response quality over time. Our use of cutting-edge technologies like [Morphik](https://www.morphik.ai/) is instrumental in delivering these advanced RAG features, and we extend our gratitude to the Morphik team for their innovative contributions. ## Key Features - **Secure Deployment**: On-premises installation with no data leaving your network - **Flexible Integration**: Connect to document repositories, databases, wikis, and more - **Enterprise-Grade Security**: Role-based access control, audit logging, and encryption - **Multi-Format Support**: Process text, PDFs, spreadsheets, presentations, and code - **Semantic Search**: Understand concepts, not just keywords - **Conversation Memory**: Maintain context across multi-turn conversations - **Version Control**: Track changes to your knowledge base over time - **Performance Analytics**: Monitor usage, performance, and improvement opportunities ## Ideal For - Legal teams needing to search through case law and contracts - Technical organizations with extensive documentation - Healthcare providers navigating complex regulatory information - Financial institutions with compliance requirements - Manufacturing companies with detailed process documentation - Any organization with valuable internal knowledge to leverage ::ProseButtonGroup ::ProseButton{to="/contact?product=FluxMentor" variant="primary"} Schedule a Consultation :: :: --- URL: https://fluxinc.co/information --- title: Information Hub | Flux Inc description: Knowledge center with case studies, technical guides, and implementation resources for Flux Inc's medical imaging and secure AI solutions keywords: case studies, technical guides, DICOM tutorials, medical imaging workflows, secure AI implementation, knowledge base, technical resources sitemap: changefreq: weekly --- # Information & Knowledge Center Flux Inc's comprehensive resource hub provides in-depth case studies, technical guides, and implementation resources. Whether you're exploring our medical imaging solutions or considering secure AI implementation, you'll find detailed information to support your decision-making and implementation process. ## [Medical Case Studies](/case-studies) > Real-world implementations across healthcare environments Our medical case studies showcase how healthcare facilities use our DICOM solutions to optimize workflows, improve efficiency, and solve complex integration challenges. From mobile mammography to multi-vendor environments, these stories demonstrate practical applications of our technology. ::ProseButtonGroup ::ProseButton{to="/case-studies" variant="primary"} Explore Medical Cases :: ::ProseButton{to="/medical/dicom-capacitor/use-cases" variant="outline"} DICOM Capacitor Cases :: :: --- ## [Enterprise Case Studies](/case-studies/enterprise) > Secure AI transforming organizational knowledge Discover how organizations across industries leverage Flux Mentor to transform their operations while maintaining complete data security. These case studies highlight the power of on-premises AI for knowledge management and decision support. ::ProseButtonGroup ::ProseButton{to="/case-studies/enterprise" variant="primary"} View Enterprise Cases :: ::ProseButton{to="/case-studies/enterprise/manufacturing-scheduler" variant="outline"} Manufacturing Example :: ::ProseButton{to="/case-studies/enterprise/call-center-metrics" variant="outline"} Call Center Example :: :: --- ## [How-To Guides](/how-to) > Technical tutorials and configuration guides Our technical resource center provides step-by-step guides for implementing and optimizing Flux solutions. These guides are designed for IT professionals and system administrators who need detailed configuration instructions. ::ProseButtonGroup ::ProseButton{to="/how-to" variant="primary"} Browse All Guides :: ::ProseButton{to="/posts/printing-to-film-using-dicom-printer-2" variant="outline"} DICOM Printing Guide :: ::ProseButton{to="/posts/dicom-routing-using-capacitor" variant="outline"} Routing Configuration :: :: --- ## Featured Technical Content Get started with our most popular implementation guides: ::TwoColumn #left ### DICOM Printer 2 Series - [Printing to Film Using DICOM Printer 2](/posts/printing-to-film-using-dicom-printer-2) - Learn basic film printing setup and configuration - [Adding a Logo to DICOM Printer 2 Output](/posts/adding-a-logo-to-dicom-printer-2-output) - Customize your documents with facility branding - [Automating DICOM Printer 2](/posts/automating-dicom-printer-2) - Configure paperless workflows for document processing - [Multiple PACS and Print Destinations](/posts/multiple-pacs-and-print-destinations-using-dicom-printer-2) - Handle multiple output destinations ### Product Selection - [Which DICOM Printer Do I Need?](/medical/dicom-printer) - Compare features and choose the right solution #right ### DICOM Capacitor Guides - [DICOM Routing using Capacitor](/posts/dicom-routing-using-capacitor) - Configure conditional routing and compression - [Intelligent Study Prefetch](/case-studies/medical/prefetch) - Optimize workflow with automatic prior retrieval - [Multi-Destination Routing](/case-studies/medical/routing) - Send studies to multiple systems automatically ### Specialized Solutions - [Mobile Imaging Workflows](/case-studies/medical/mobile-workflows) - Routing, worklist caching, and delivery controls for mobile fleets - [Legacy Format Conversion](/case-studies/medical/format-conversion) - Modernize older imaging equipment - [Cross-Vendor Protocol Harmonization](/case-studies/medical/ct-protocols) - Standardize multi-vendor environments :: ## AI & Knowledge Management Resources for implementing secure, on-premises AI solutions: ::TwoColumn #left ### Success Stories - [Manufacturing Scheduling Optimization](/case-studies/enterprise/manufacturing-scheduler) - Production planning transformation - [Call Center Knowledge Management](/case-studies/enterprise/call-center-metrics) - Improving agent performance with AI - [DenseBreast-AI Chatbot](/case-studies/densebreast-ai-chatbot) - Medical information accessibility #right ### Implementation Resources - [Flux Mentor Overview](/flux-mentor) - Understand our secure AI platform - Contact our team for custom consultation - Schedule a demonstration of Flux Mentor capabilities :: --- ## Industry Expertise Our solutions serve diverse healthcare and enterprise environments: ### Healthcare Specialties - **Radiology**: PACS integration, image routing, workflow optimization - **Mammography**: Mobile units, breast density reporting, tomosynthesis workflows - **Cardiology**: Measurement harmonization, structured reporting - **Nuclear Medicine**: Multi-phase studies, SUV validation, protocol standardization ### Enterprise Applications - **Manufacturing**: Production scheduling, equipment maintenance, quality management - **Legal**: Case law research, contract analysis, compliance documentation - **Financial**: Regulatory compliance, policy management, audit support - **Healthcare Administration**: Protocol management, training materials, regulatory guidance ::EmphasisBox ### Need personalized guidance? Our specialists are available to discuss your specific technical requirements, from DICOM integration challenges to secure AI implementation planning. ::ProseButton{to="/contact" variant="primary"} Contact Our Experts :: :: ## Why Choose Flux Inc - **Deep Domain Expertise**: 15+ years in medical imaging and AI - **Security-First Approach**: On-premises solutions that protect your data - **Proven Solutions**: 3,000+ customers worldwide across multiple industries - **Comprehensive Support**: From initial consultation to ongoing optimization - **Innovation Focus**: Early adopters of new technologies with practical applications ::ProseButtonGroup ::ProseButton{to="/about" variant="secondary"} Learn About Our Company :: ::ProseButton{to="/medical" variant="primary"} Explore Medical Solutions :: ::ProseButton{to="/flux-mentor" variant="primary"} Discover Secure AI :: :: --- URL: https://fluxinc.co/medical --- title: Medical Products | Flux Inc description: Medical imaging software for healthcare professionals, including DICOM tools, PACS integration, and specialized solutions for radiology workflows. keywords: medical imaging software, DICOM, PACS, medical software, healthcare solutions, HL7, ORM, worklist, BMD, bone density, GE LUNAR sitemap: changefreq: monthly --- # Our Products Flux Inc. started off as a medical consulting and software provider and this activity forms the core of our business. We specialize in customized solutions for electronic health and produce a growing set of DICOM, HL7, and data warehousing applications. ## [DICOM Printer 1](/medical/dicom-printer-1) > Original DICOM Drop Folder and Virtual Printer Our original Windows-based virtual PACS printer and DICOM workflow processor. DICOM Printer 1 can store and print to film, allowing you to send reports and images to PACS and print reports and images to film. ::ProseButtonGroup ::ProseButton{to="/medical/dicom-printer-1" variant="primary"} Learn More :: ::ProseButton{to="https://store.fluxinc.ca/cart/product/DP1" variant="outline"} Buy Now :: ::ProseButton{to="https://store.fluxinc.ca/files/DP1/latest" variant="outline"} Download Trial :: :: --- ## [DICOM Printer 2](/medical/dicom-printer-2) > Advanced DICOM Drop Folder and Virtual Printer Enhanced Windows-based virtual PACS printer and automatic DICOM workflow processor. DICOM Printer 2 can query, store, and print to film with advanced features. Our customers use it to send reports and images to PACS, print reports and images to film, save encapsulated PDF to PACS, and store PDF using HL7 to RIS. ::ProseButtonGroup ::ProseButton{to="/medical/dicom-printer-2" variant="primary"} Learn More :: ::ProseButton{to="https://store.fluxinc.ca/cart/product/DP2" variant="outline"} Buy Now :: ::ProseButton{to="https://store.fluxinc.ca/files/DP2/latest" variant="outline"} Download Trial :: :: --- ## [DICOM Capacitor](/medical/dicom-capacitor) > Store and Forward Router DICOM Capacitor can cache, compress, route, and transform DICOM using simple rules. Typical applications include mobile store and worklist cache, traffic shaping, DICOM header repair, and vendor compatibility. ::ProseButtonGroup ::ProseButton{to="/medical/dicom-capacitor" variant="primary"} Learn More :: ::ProseButton{to="https://store.fluxinc.ca/cart/product/DCP" variant="outline"} Buy Now :: ::ProseButton{to="https://store.fluxinc.ca/files/DCP/latest" variant="outline"} Download Trial :: :: --- ## [DICOM Gobbler](/medical/dicom-gobbler) > Import DICOM CD and USB to PACS Gobbler pops up automatically when you insert a DICOM CD or USB, it asks for an MRN, and then quietly stores the contents to your local PACS. Gobbler imports in the background so you can get on with your work. ::ProseButtonGroup ::ProseButton{to="/medical/dicom-gobbler" variant="primary"} Learn More :: ::ProseButton{to="https://store.fluxinc.ca/cart/product/DGB" variant="outline"} Buy Now :: ::ProseButton{to="https://store.fluxinc.ca/files/DGB/latest" variant="outline"} Download Trial :: :: --- ## [DICOM7](/medical/dicom7) > Complete DICOM and HL7 Integration Suite DICOM7 is a comprehensive suite of services for converting between DICOM and HL7 formats. With three specialized components, it enables seamless bidirectional communication between imaging modalities, PACS, RIS, and HIS systems, ensuring your healthcare data flows effortlessly across your entire ecosystem. ::ProseButtonGroup ::ProseButton{to="/medical/dicom7" variant="primary"} Learn More :: ::ProseButton{to="/contact?product=DICOM7" variant="outline"} Request Early Access :: ::ProseButton{to="/contact?product=DICOM7&demo=true" variant="outline"} Schedule Demo :: :: --- ## [TuPACS](/medical/tupacs) > Scan to PACS TuPACS gets things from your document scanner, lets you search your DICOM modality worklist, and sends them directly to PACS. ::ProseButtonGroup ::ProseButton{to="/medical/tupacs" variant="primary"} Learn More :: ::ProseButton{to="https://store.fluxinc.ca/cart/product/TPX" variant="outline"} Buy Now :: ::ProseButton{to="https://store.fluxinc.ca/files/TPX/latest" variant="outline"} Download Trial :: :: --- ## [EnCore Exporter](/medical/encore-exporter) > Export LUNAR BMD and Body Composition Data to Excel EnCore Exporter is an easy-to-use tool that lets you export GE Prodigy Bone Mineral Density (BMD) and Body Composition data from an enCore lunar.mdb database to Microsoft Excel-compatible CSV files. Exports of this sort are essential when conducting research using bone densitometry data. ::ProseButtonGroup ::ProseButton{to="/medical/encore-exporter" variant="primary"} Learn More :: ::ProseButton{to="https://store.fluxinc.ca/cart/product/BMDE1" variant="outline"} Buy Now :: ::ProseButton{to="https://store.fluxinc.ca/files/BMDE1/latest" variant="outline"} Download Trial :: :: --- ## [Model Governance Layer](/medical/model-governance-layer) > AI-powered context enrichment for LLM requests The Model Governance Layer is a proxy that enriches Large Language Model (LLM) requests. It adds valuable context, including current user information, user permissions for resource access, and user preferences. This ensures that LLM interactions are secure, personalized, and compliant with relevant preferences and policies. ::ProseButtonGroup ::ProseButton{to="/medical/model-governance-layer" variant="primary"} Learn More :: ::ProseButton{to="/contact?product=ModelGovernanceLayer" variant="outline"} Request Early Access :: ::ProseButton{to="/contact?product=ModelGovernanceLayer&demo=true" variant="outline"} Schedule Demo :: :: --- ## Consulting Services Our expert team ensures smooth implementation and integration with your existing systems. - Comprehensive needs assessment - Customized implementation plan - Data migration services - Staff training and education - Go-live support - Ongoing optimization ::ProseButtonGroup ::ProseButton{to="/contact" variant="primary"} Contact Us :: :: --- URL: https://fluxinc.co/medical/dicom-capacitor --- title: DICOM Capacitor description: Advanced DICOM routing, tag manipulation, and reliable study delivery across networks keywords: DICOM gateway, store and forward, medical imaging, mobile clinics, unreliable networks, PACS integration, DICOM routing, header manipulation, compression head: meta: - name: 'og:title' content: 'DICOM Capacitor - Advanced Medical Imaging Gateway' - name: 'og:description' content: 'Advanced DICOM routing, tag manipulation, and reliable study delivery across networks' - name: 'og:type' content: 'product' - name: 'twitter:card' content: 'summary' - name: 'twitter:title' content: 'DICOM Capacitor - Advanced Medical Imaging Gateway' - name: 'twitter:description' content: 'Advanced DICOM routing, tag manipulation, and reliable study delivery across networks' - name: 'product:price:amount' content: '1900.00' - name: 'product:price:currency' content: 'USD' - name: 'canonical' content: 'https://fluxinc.co/medical/dicom-capacitor' --- ::FullWidthSection{variant="custom" padding="sm" className="bg-transparent" backgroundImage="/images/hero.webp" backgroundOverlayClass="bg-gradient-to-br from-emerald-700/80 via-emerald-700/100 to-emerald-700/60"} # DICOM Capacitor ::RotatingText{items="Store forward router.|Images. Delivered. Fast.|Route studies right.|Secure mobile cache." tag="p" rootClass="text-xl text-white md:text-2xl"} :: ::ProseButtonGroup ::ProseButton{to="https://store.fluxinc.ca/files/DCP/latest" variant="outlineInvert"} Download :: ::ProseButton{to="https://store.fluxinc.ca/cart/product/DCP" variant="outline"} Buy Now :: :: :: DICOM Capacitor transforms medical imaging workflows. It routes studies to multiple destinations, manipulates DICOM headers, compresses images, and ensures reliable delivery across any network connection. [Explore detailed use cases →](/medical/dicom-capacitor/use-cases) ## When to Use Capacitor - **Multi-destination routing**: Send studies to multiple systems with format customized for each - **DICOM header manipulation**: Standardize tags, correct errors, and harmonize metadata - **Compression**: Reduce file sizes with JPEG 2000 while preserving diagnostic quality - **Mobile imaging**: Enable reliable operation on truck-mounted units with intermittent connectivity - **Remote sites**: Manage bandwidth constraints with scheduled transfers - **Unreliable networks**: Prevent transmission failures with automatic retries ## How It Works Capacitor sits between your imaging device and destination systems: 1. Point your modality to Capacitor instead of directly to PACS 2. Capacitor receives, processes, and queues studies 3. Based on rules you define, Capacitor routes and formats studies for each destination 4. Studies reach destinations reliably, even across poor connections Your workflow stays simple while Capacitor handles complex routing, formatting, and delivery tasks. ## Impact on Staff - **Streamlined workflow**: One storage operation handles all destinations - **Fewer errors**: Automatic tag correction prevents display issues - **Network independence**: Technologists work without connectivity concerns - **Better productivity**: Faster device turnaround with local storage - **Reduced stress**: Eliminating manual workarounds and retry processes ## Key Features - **Intelligent routing**: Sends different study types to their proper destinations - **Format customization**: Tailors images for each receiving system's needs - **Tag manipulation**: Corrects and standardizes DICOM headers - **Efficient compression**: Reduces storage costs and transmission times - **Fault-tolerant design**: Ensures successful delivery despite network problems - **Simple updates**: Most upgrades complete in minutes with minimal disruption - **Dynamic multi-threading**: Automatically scales processing across available CPU cores for optimal performance ## Performance Benchmarked natively on an Apple M4 with full screening mammography studies (avg 1.5 GiB per study):
~9s
per study
~6s
per GiB
168
MiB/s
with JPEG 2000 lossless compression
~14s
per study
+5s
overhead
73%
smaller
*Dynamic multi-threading scales across available CPU cores. Performance varies with study size and hardware.* ::TwoColumn #left ## Deployment Options - **On-premises**: Deploy on your own hardware - **Operating System**: Windows, Linux, MacOS, or Docker - **Hardware**: Any x86_64 or ARM64 machine - **Cloud**: Use any secure cloud service like AWS, Azure, or Google Cloud - **[Flux Box](/medical/flux-box)**: Pre-configured compact appliance for mobile and remote operations - **Turnkey** — ships ready to deploy - **Low power consumption**: under 15W typical - **Compact**: 7.7 in × 7.7 in × 1.4 in, rack-mountable #right ![DICOM Capacitor Hardware](/images/products/flux-box-hardware.webp){width="500"} :: ## Minimum System Requirements - **Architecture**: x86_64 or ARM64 - **Operating System**: Windows 10+, Linux (Ubuntu 22.04+, Debian 12+, RHEL 9+), macOS 14+, or Docker - **Processor**: dual-core Intel Core i3 / Apple M1 / equivalent ARM64 - **Memory**: 4 GB RAM (8 GB recommended for mammography, CT/MR) - **Storage**: 100 GB available (500 GB for mammography, CT/MR) - **Network**: 100 Mbps or higher (1 Gbps recommended) ::EmphasisBox ## Learn More About DICOM Capacitor Discover how healthcare facilities are using DICOM Capacitor to solve real-world challenges: ::ProseButtonGroup ::ProseButton{to="/medical/dicom-capacitor/use-cases" variant="primary"} View Use Cases & Implementation Examples :: ::ProseButton{to="https://docs.fluxinc.co/dicom-capacitor/" variant="outline"} Documentation :: ::ProseButton{to="/contact"} Contact Our DICOM Specialists :: :: :: --- URL: https://fluxinc.co/medical/dicom-capacitor/use-cases --- title: DICOM Capacitor Use Cases description: Explore real-world implementations of DICOM Capacitor for routing, worklist caching, format conversion and more keywords: DICOM use cases, medical imaging workflows, PACS integration, DICOM routing, modality worklist, healthcare connectivity --- # DICOM Capacitor Router Use Cases ::FullWidthSection{background="light" padding="lg"} Capacitor is more than just a DICOM router - it's a platform that leverages Flux's deep expertise in medical imaging workflows and systems integration. While the following use cases highlight common applications, every implementation is customized to address site-specific challenges and requirements. Our team provides: - Workflow analysis and optimization - Integration with existing systems - Migration planning and execution - Ongoing monitoring and support - Regular updates to address new requirements :: Whether you're dealing with complex multi-vendor environments, planning a major migration, or looking to optimize specific workflows, Capacitor combines powerful technology with Flux's hands-on expertise to ensure success. ::ContentBox{variant="primary"} ## Featured: Mobile Mammography Workflow control for mobile mammography coaches. Capacitor keeps worklists local, routes by facility, and supports real-time or policy-based delivery without burdening technologists. - **Offline operation** — acquire with local cache continuity when the link drops - **Worklist caching** — serve patient lists locally, sync when connected - **Flexible delivery** — send immediately over wireless or defer until docked - **Site-aware routing** — detect facility context and apply the right rules ::ProseButtonGroup ::ProseButton{to="/case-studies/medical/mobile-workflows" variant="primary"} Read the Mobile Workflow Guide :: :: :: ## Use Cases ::TwoColumn #left ### Image Management - **[Study Prefetch & Archive Integration](/case-studies/medical/prefetch)** — worklist-driven prior retrieval with smart filtering - **[SCO & CTO to BTO Conversion](/case-studies/medical/sco-bto-conversion)** — Hologic SCO and Siemens CTO to DICOM standard - **[Image Distribution & Compression](/case-studies/medical/distribution)** — JPEG 2000 compression with multi-destination delivery - **[Legacy Format Conversion](/case-studies/medical/format-conversion)** — migrate obsolete formats to current DICOM standards ### Workflow Enhancement - **[Multi-Destination Routing](/case-studies/medical/routing)** — rule-based study distribution with per-destination formatting - **[SecurView Integration](/case-studies/medical/securview)** — automated CAD workstation delivery - **[Breast Density Reporting](/case-studies/medical/density-reporting)** — density analysis integration with structured reports #right ### Advanced Integration - **[Cardiac Ultrasound Harmonization](/case-studies/medical/cardiac-us)** — cross-vendor measurement normalization - **[DICOM Tag Harmonization](/case-studies/medical/tag-harmonization)** — standardize metadata across multi-vendor environments - **[Worklist Integration](/case-studies/medical/worklist)** — worklist bridging, caching, and transformation - **[Tomosynthesis Integration](/case-studies/medical/tomosynthesis)** — DBT routing with slice management - **[CT Protocol Harmonization](/case-studies/medical/ct-protocols)** — cross-vendor protocol standardization - **[MR Sequence Normalization](/case-studies/medical/mr-sequences)** — harmonize sequence naming and parameters - **[Nuclear Medicine Study Completion](/case-studies/medical/nuclear-med)** — multi-phase study assembly and delivery :: ::FullWidthSection{class="bg-primary-500/10 py-12"} ### Support & Services For each use case, Flux provides: - Remote installation assistance - Ongoing technical support - Regular software updates - Hardware warranty - Customization for site-specific needs The solution is available in several configurations to match different facility needs and budgets, from our starter package to our comprehensive enterprise solution. :: ::ProseButtonGroup ::ProseButton{to="/contact" variant="primary"} Contact Sales :: ::ProseButton{to="/medical/dicom-capacitor"} Back to Product Details :: :: --- URL: https://fluxinc.co/medical/dicom-gobbler --- title: DICOM Gobbler description: Easily import DICOM studies from CDs, USB drives, and folders to your PACS system keywords: DICOM import, CD import, PACS import, medical imaging, DICOM viewer, study import, radiology workflow sitemap: changefreq: monthly head: meta: - name: 'og:title' content: 'DICOM Gobbler - Streamlined DICOM Import Solution' - name: 'og:description' content: 'Easily import DICOM studies from CDs, USB drives, and folders to your PACS system' - name: 'og:type' content: 'product' - name: 'twitter:card' content: 'summary' - name: 'twitter:title' content: 'DICOM Gobbler - Streamlined DICOM Import Solution' - name: 'twitter:description' content: 'Easily import DICOM studies from CDs, USB drives, and folders to your PACS system' - name: 'product:price:amount' content: '600.00' - name: 'product:price:currency' content: 'USD' - name: 'canonical' content: 'https://fluxinc.co/medical/dicom-gobbler' --- ::FullWidthSection{variant="custom" padding="sm" className="bg-transparent" backgroundImage="/images/hero.webp" backgroundOverlayClass="bg-gradient-to-br from-emerald-700/80 via-emerald-700/100 to-emerald-700/60"} # DICOM Gobbler ::RotatingText{items="Import CDs and USB drives.|Import folders.|Streamline DICOM workflow." tag="p" rootClass="text-xl text-white md:text-2xl"} :: ::ProseButtonGroup ::ProseButton{to="https://store.fluxinc.ca/files/DGB/latest" variant="outlineInvert"} Download :: ::ProseButton{to="https://store.fluxinc.ca/cart/product/DGB" variant="outline"} Buy Now :: :: :: Our DICOM import utility helps you get studies from any source into your PACS. Simply drag and drop folders, insert CDs, or configure automatic USB imports. ## Key Features - **Automatic detection** of DICOM media when inserted - **Simple MRN entry** for patient identification - **Background processing** for uninterrupted workflow - **Comprehensive format support** for various DICOM CD formats - **DICOM validation** ensures data integrity - **Multiple PACS destinations** for flexible routing ## Use Cases ::TwoColumn #left ### Patient-Provided Media - Import external studies from CDs and USB drives - Easily incorporate outside studies into patient records - Reduce manual steps in the import process ### Legacy Data Migration - Batch import studies from archived media - Consolidate historical studies into your current PACS - Preserve complete patient imaging history #right ### Inter-facility Exchange - Streamline importing studies from referring facilities - Process incoming studies with minimal staff intervention - Maintain consistent patient identifiers :: ## How It Works 1. **Insert** a DICOM CD or connect a USB drive 2. **Gobbler activates** automatically and scans for DICOM files 3. **Enter** the patient MRN when prompted 4. **Gobbler imports** the studies to your PACS in the background 5. **Continue working** while Gobbler handles the transfer ## Benefits - **Save time** with automated detection and import - **Reduce errors** by minimizing manual steps - **Improve workflow** by eliminating wait times - **Enhance patient care** by incorporating outside studies - **Simplify training** with an intuitive interface ::EmphasisBox **Need multi-site deployment?** Gobbler can be configured for enterprise-wide deployment with centralized management. ::ProseButton{to="/contact" variant="primary"} Contact Us :: :: --- URL: https://fluxinc.co/medical/dicom-printer --- title: 'Which DICOM Printer Solution Is Right For You?' description: 'Compare DICOM Printer 1 and DICOM Printer 2 features to find the perfect medical imaging connectivity solution for your healthcare environment' keywords: DICOM printer comparison, DICOM Printer 1, DICOM Printer 2, virtual DICOM printer, PACS integration, film printing, medical imaging --- # Choosing the Right DICOM Printer Solution ::InfoBox DICOM Printer enables seamless connectivity between your documents and your PACS or DICOM imaging systems. Both versions offer powerful features, but which one fits your workflow best? :: ::TwoColumn #left ## DICOM Printer 1 Perfect for single-user environments where manual control over the DICOM communication process is preferred. DP1 gives you hands-on control of your document-to-PACS workflow. ::ProseButtonGroup ::ProseButton{variant="primary" to="https://store.fluxinc.ca/cart/product/DP1"} Buy Now :: ::ProseButton{to="https://store.fluxinc.ca/files/DP1/latest"} Download DP1 Trial :: :: #right ## DICOM Printer 2 Ideal for busy healthcare environments requiring automated DICOM connectivity. DP2 handles the query and store processes automatically, saving valuable clinical time. ::ProseButtonGroup ::ProseButton{variant="primary" to="https://store.fluxinc.ca/cart/product/DP2"} Buy Now :: ::ProseButton{to="https://store.fluxinc.ca/files/DP2/latest"} Download DP2 Trial :: :: :: ::EmphasisBox ### Key Differences at a Glance - **DP1**: Manual control, perfect for radiologists and specialists who want hands-on control of their DICOM workflow - **DP2**: Automated processes, ideal for busy hospitals, imaging centers, and multi-user environments - **Same price**: Both products cost $750 USD, choose based on your workflow needs, not your budget :: ## Feature Comparison ::ContentBox{bgColor="primary" bgShade="900" borderColor="primary" borderShade="500" shadow=true} | Feature | DICOM Printer 1 | DICOM Printer 2 | | --- | --- | --- | | PACS connectivity via virtual printer | ✓ | ✓ | | PACS connectivity via drop folder | ✓ | ✓ | | DICOM Imager connectivity (e.g., AGFA Axys) | ✓ Manual | ✓ Automatic | | DICOM Worklist query | ✓ Manual | ✓ Automatic | | DICOM PACS query | ✓ Manual | ✓ Automatic | | Document text extraction for DICOM tags | ✓ | ✓ Automatic | | DICOM document annotation | ✓ | ✓ | | Logo integration with DICOM objects | ✓ | ✓ | | DICOMDIR creation for portable media | ✓ | ✓ | | Scriptable DICOM operations | ✓ | ✓ | | Background DICOM re-query functionality | | ✓ | | Multi-destination DICOM sending | ✓ | ✓ | | Document-type-based DICOM routing | | ✓ | :: ::WarningBox Not sure which DICOM Printer is right for your healthcare environment? [Contact our DICOM specialists](/contact) for personalized guidance on integrating with your existing PACS, RIS, or HL7 infrastructure. For detailed specifications and integration guides, visit our [how-to guides](/how-to). :: ## Related Products ::EmphasisBox ### Looking for DICOM CD import solutions? If you're handling external DICOM studies from CDs and USB drives, consider our [DICOM Gobbler](/medical/dicom-gobbler) solution for automated import to your PACS system. :: ::ProseButtonGroup ::ProseButton{to="/medical/dicom-gobbler" variant="primary"} Learn About DICOM Gobbler :: :: ::ProseButtonGroup{class="justify-between"} ::ProseButton{to="/posts/multiple-pacs-and-print-destinations-using-dicom-printer-2" class="hidden md:inline-flex"} ← Multiple PACS and Print Destinations :: ::ProseButton{to="/posts/multiple-pacs-and-print-destinations-using-dicom-printer-2" class="md:hidden"} ← Previous :: ::ProseButton{to="/posts/dicom-routing-using-capacitor" variant="primary" class="hidden md:inline-flex"} DICOM Routing using Capacitor → :: ::ProseButton{to="/posts/dicom-routing-using-capacitor" variant="primary" class="md:hidden"} Next → :: :: ::ProseButtonGroup ::ProseButton{to="/medical/dicom-printer-1"} DICOM Printer 1 Overview :: ::ProseButton{to="/medical/dicom-printer-2"} DICOM Printer 2 Overview :: :: --- URL: https://fluxinc.co/medical/dicom-printer-1 --- title: DICOM Printer 1 description: Print to PACS and film with our original virtual DICOM printer for seamless medical imaging workflow keywords: DICOM print, PACS integration, document conversion, medical imaging, virtual printer, radiology printing, film output sitemap: changefreq: monthly head: meta: - name: 'og:title' content: 'DICOM Printer 1 - Essential Virtual DICOM Printer' - name: 'og:description' content: 'Print to PACS and film with our original virtual DICOM printer for seamless medical imaging workflow' - name: 'og:type' content: 'product' - name: 'twitter:card' content: 'summary' - name: 'twitter:title' content: 'DICOM Printer 1 - Essential Virtual DICOM Printer' - name: 'twitter:description' content: 'Print to PACS and film with our original virtual DICOM printer for seamless medical imaging workflow' - name: 'product:price:amount' content: '750.00' - name: 'product:price:currency' content: 'USD' - name: 'canonical' content: 'https://fluxinc.co/medical/dicom-printer-1' --- ::FullWidthSection{variant="custom" padding="sm" className="bg-transparent" backgroundImage="/images/hero.webp" backgroundOverlayClass="bg-gradient-to-br from-emerald-700/80 via-emerald-700/100 to-emerald-700/60"} # DICOM Printer 1 ::RotatingText{items="Windows Print to PACS.|DICOM Worklist query.|Attach documents to exams." tag="p" rootClass="text-xl text-white md:text-2xl"} :: ::ProseButtonGroup ::ProseButton{to="https://store.fluxinc.ca/files/DP1/latest" variant="outlineInvert"} Download :: ::ProseButton{to="https://store.fluxinc.ca/cart/product/DP1" variant="outline"} Buy Now :: :: :: Our original virtual DICOM printer converts Windows print jobs into DICOM format for PACS or film. Send documents directly to PACS or print them to DICOM film with one simple workflow. [Explore detailed use cases →](/case-studies/medical) ## Key Features - **Print from any Windows app** directly to PACS or DICOM printers - **Link patient data manually** through a simple interface - **Get true-size prints** on any DICOM-compliant film printer - **Choose your destination** - PACS storage or film printing - **Handle standard documents** with basic PACS integration - **Streamline your workflow** with simple processing options ## Use Cases ### Medical Reports Integration - Send reports from any software to PACS - Convert office documents and scans to DICOM format - Add documents to patient studies ### Legacy Equipment Support - Add basic DICOM features to non-DICOM equipment - Connect traditional systems to your DICOM network - Extend the functionality of older devices ### Film Printing Workflow - Print to DICOM film from any Windows application - Maintain good sizing for quality prints - Simplify printing process ## How It Works 1. **Print** from any Windows application 2. **Enter** patient data manually 3. **Convert** documents to DICOM format 4. **Send** to PACS or film printer 5. **Confirm** successful delivery ## Benefits - **Simplify your workflow** by integrating reports with images - **Use with any software** that can print in Windows - **Choose your output** based on clinical needs - **Streamline document handling** in medical settings - **Affordable solution** for smaller practices ::EmphasisBox **Choose the right DICOM Printer** DICOM Printer 1 suits smaller practices with basic document-to-PACS needs. Simple interface, focused features, affordable pricing. Need automation, worklist queries, or HL7/RIS integration? See [DICOM Printer 2](/medical/dicom-printer-2). :: ::InfoBox **Ready to upgrade to DICOM Printer 2?** For advanced features like HL7/RIS integration, DICOM worklist queries, and DICOM CD creation, consider upgrading to DICOM Printer 2. ::ProseButton{to="/medical/dicom-printer-2" variant="primary"} Learn More About Version 2 :: :: --- URL: https://fluxinc.co/medical/dicom-printer-2 --- title: DICOM Printer 2 description: Print to PACS and film with our virtual DICOM printer for seamless medical imaging workflow keywords: DICOM print, film printing, radiology printing, PACS integration, DICOM worklist, virtual printer head: meta: - name: 'og:title' content: 'DICOM Printer 2 - Advanced Virtual DICOM Printer' - name: 'og:description' content: 'Print to PACS and film with our virtual DICOM printer for seamless medical imaging workflow' - name: 'og:type' content: 'product' - name: 'twitter:card' content: 'summary' - name: 'twitter:title' content: 'DICOM Printer 2 - Advanced Virtual DICOM Printer' - name: 'twitter:description' content: 'Print to PACS and film with our virtual DICOM printer for seamless medical imaging workflow' - name: 'product:price:amount' content: '750.00' - name: 'product:price:currency' content: 'USD' - name: 'canonical' content: 'https://fluxinc.co/medical/dicom-printer-2' --- ::FullWidthSection{variant="custom" padding="sm" className="bg-transparent" backgroundImage="/images/hero.webp" backgroundOverlayClass="bg-gradient-to-br from-emerald-700/80 via-emerald-700/100 to-emerald-700/60"} # DICOM Printer 2 ::RotatingText{items="Automatic Print to PACS.|Automatic Print to Film.|Automatic Worklist query.|True Size images." tag="p" rootClass="text-xl text-white md:text-2xl"} :: ::ProseButtonGroup ::ProseButton{to="https://store.fluxinc.ca/files/DP2/latest" variant="outlineInvert"} Download :: ::ProseButton{to="https://store.fluxinc.ca/cart/product/DP2" variant="outline"} Buy Now :: :: :: Our virtual DICOM printer converts Windows print jobs into DICOM format for PACS or film. Send documents directly to PACS or print them to DICOM film with one simple workflow. [Explore detailed use cases →](/case-studies/medical) ## Key Features - **Print from any Windows app** directly to PACS or DICOM printers - **Link patient data automatically** through DICOM worklist queries - **Get true-size prints** on any DICOM-compliant film printer - **Choose your destination** - PACS storage, film printing, or DICOM CD - **Handle PDF documents** with PACS and HL7/RIS integration - **Automate your workflow** with customizable processing rules ::ContentBox{type="tip"} **Testing worklist functionality?** Try our [Public Test DICOM Modality Worklist](/posts/public-test-dicom-modality-worklist) for development and integration testing. :: ## Use Cases ### Medical Reports Integration - Send reports from any software to PACS - Convert office documents and scans to DICOM format - Match documents with the right patient studies ### Legacy Equipment Support - Add DICOM features to non-DICOM equipment - Modernize older devices with DICOM capabilities - Connect traditional systems to your DICOM network ### Film Printing Workflow - Print to DICOM film from any Windows application - Maintain accurate sizing for diagnostic quality - Simplify printing with automatic formatting ## How It Works 1. **Print** from any Windows application 2. **Match** patient data through DICOM queries 3. **Convert** documents to DICOM format 4. **Send** to PACS, film printer, or create a CD 5. **Confirm** successful delivery ## Benefits - **Simplify your workflow** by integrating reports with images - **Use with any software** that can print in Windows - **Choose your output** based on clinical needs - **Reduce errors** through automation - **Extend the life** of older equipment ::EmphasisBox **Choose the right DICOM Printer** DICOM Printer 2 serves hospitals and larger practices needing advanced integration. Features DICOM worklist queries, automatic matching, HL7/RIS integration, and CD creation. Want a simpler solution? Try [DICOM Printer 1](/medical/dicom-printer-1). :: ::InfoBox **Need a custom solution?** We'll help you integrate DICOM Printer 2 with your specific systems and workflows. ::ProseButton{to="/contact" variant="primary"} Contact Us :: :: --- URL: https://fluxinc.co/medical/dicom7 --- title: DICOM7 description: Comprehensive suite for converting between DICOM and HL7 formats for seamless healthcare system integration keywords: DICOM, HL7, medical imaging, healthcare integration, DICOM to HL7, HL7 to DICOM, ORM, ORU, Modality Worklist, healthcare informatics head: meta: - name: 'og:title' content: 'DICOM7 - Complete DICOM and HL7 Integration Suite' - name: 'og:description' content: 'Comprehensive suite for converting between DICOM and HL7 formats for seamless healthcare system integration' - name: 'og:type' content: 'product' - name: 'twitter:card' content: 'summary' - name: 'twitter:title' content: 'DICOM7 - Complete DICOM and HL7 Integration Suite' - name: 'twitter:description' content: 'Comprehensive suite for converting between DICOM and HL7 formats for seamless healthcare system integration' - name: 'product:price:amount' content: '750.00' - name: 'product:price:currency' content: 'USD' - name: 'canonical' content: 'https://fluxinc.co/medical/dicom7' --- ::FullWidthSection{variant="custom" padding="sm" className="bg-transparent" backgroundImage="/images/hero.webp" backgroundOverlayClass="bg-gradient-to-br from-emerald-700/80 via-emerald-700/100 to-emerald-700/60"} # DICOM7 ::RotatingText{items="Bridge DICOM and HL7.|Automatic Worklist.|Deploy in One Hour.|Seamless Integration." tag="p" rootClass="text-xl text-white md:text-2xl"} :: DICOM7 connects DICOM and HL7 systems with minimal configuration. Three powerful components provide seamless integration, deployable in under an hour. ::ProseButtonGroup ::ProseButton{to="/contact?product=DICOM7&demo=true" variant="outline"} Schedule Demo :: :: :: ## Key Features - **Complete integration solution**: Three specialized components covering all DICOM/HL7 conversion needs - **Windows 10 compatibility**: Runs smoothly on modern Windows environments - **Independent component installation**: Choose only the services you need - **Automated service management**: Windows services with automatic startup - **Detailed logging**: Comprehensive activity tracking for troubleshooting and auditing - **Minimal configuration required**: Simple YAML files with straightforward options - **Rapid deployment**: Full setup and configuration in under 60 minutes - **Zero learning curve**: Intuitive design means no lengthy training sessions ## Components ### DICOM to ORM Service (DICOM2ORM) - Queries DICOM worklists and converts new orders to HL7 ORM messages - Enables sending DICOM study information to RIS/HIS systems as orders - Automatically populates patient demographics from DICOM worklist into HL7-only systems - Configurable polling intervals to match your workflow needs ### DICOM to ORU Service (DICOM2ORU) - Converts DICOM C-Store datasets to HL7 ORU (Result) messages - Listens for incoming DICOM connections and generates corresponding HL7 messages - Perfect for sending results and reports to clinical systems that speak HL7 ### ORM to DICOM Service (ORM2DICOM) - Transforms HL7 ORM messages into DICOM Modality Worklist entries - Listens for HL7 ORM connections and provides a DICOM Worklist service - Populates patient data into DICOM worklist from HL7 orders for DICOM-only modalities - Makes order information from HL7 systems available to any DICOM modality ## Who DICOM7 Is For ### Healthcare Providers - **Hospitals and Imaging Centers**: Bridge the gap between radiology and other clinical departments - **Laboratory Systems**: Connect lab results to imaging records with minimal configuration - **Multi-vendor Environments**: Create seamless workflows between systems from different vendors ### Vendors and Developers - **Imaging Equipment Manufacturers**: Add HL7 capabilities to DICOM-only devices - **Healthcare Software Companies**: Extend HL7 systems with DICOM connectivity - **System Integrators**: Simplify complex integration projects with pre-built components ### IT Departments - **Healthcare IT Teams**: Implement a proven integration solution without custom development - **Biomedical Engineers**: Connect medical devices to information systems quickly - **Clinical Engineering**: Enable DICOM equipment to participate in HL7 workflows ## How It Works DICOM7 creates a seamless bridge between your DICOM and HL7 systems:
DICOM Systems
⇄
DICOM7
⇄
HL7 Systems
1. Install only the components you need for your specific workflow (under 5 minutes) 2. Configure each component using the intuitive YAML configuration files (15-30 minutes) 3. Components run as Windows services, starting automatically with your system 4. Begin processing DICOM and HL7 data immediately—no complex setup required 5. Your healthcare systems communicate seamlessly regardless of their native protocols ## Benefits for Healthcare Organizations - **Protocol-agnostic integration**: Connect any system regardless of whether it uses DICOM or HL7 - **Reduced implementation costs**: No need for expensive custom integration development - **Same-day deployment**: Be up and running in under an hour, not days or weeks - **Minimal IT involvement**: Simple enough for clinical staff to configure and maintain - **Improved workflow efficiency**: Eliminate manual data entry and protocol conversion - **Enhanced data accuracy**: Prevent transcription errors and information loss - **Simplified IT management**: Standard Windows services are easy to monitor and maintain - **Future-proof architecture**: Add new systems without reworking your entire infrastructure ::EmphasisBox ## Learn More About DICOM7 Discover how healthcare facilities are using DICOM7 to create seamless integration environments: ::ProseButtonGroup ::ProseButton{to="/contact"} Contact Our Integration Specialists :: :: :: --- URL: https://fluxinc.co/medical/encore-exporter --- title: EnCore Exporter description: Export LUNAR BMD and body composition data from GE LUNAR Prodigy databases to Excel-compatible files for research and analysis keywords: bone mineral density, LUNAR EnCore, BMD export, DEXA, bone density data, body composition, medical research sitemap: changefreq: monthly head: meta: - name: 'og:title' content: 'EnCore Exporter - BMD Data Export Solution' - name: 'og:description' content: 'Export LUNAR BMD and body composition data from GE LUNAR Prodigy databases to Excel-compatible files for research and analysis' - name: 'og:type' content: 'product' - name: 'twitter:card' content: 'summary' - name: 'twitter:title' content: 'EnCore Exporter - BMD Data Export Solution' - name: 'twitter:description' content: 'Export LUNAR BMD and body composition data from GE LUNAR Prodigy databases to Excel-compatible files for research and analysis' - name: 'product:price:amount' content: '946.00' - name: 'product:price:currency' content: 'USD' - name: 'canonical' content: 'https://fluxinc.co/medical/encore-exporter' --- ::FullWidthSection{variant="custom" padding="sm" className="bg-transparent" backgroundImage="/images/hero.webp" backgroundOverlayClass="bg-emerald-700"} # EnCore Exporter ::RotatingText{items="Extract BMD Data.|Export to Excel.|Research Excellence.|LUNAR Prodigy Integration." tag="p" rootClass="text-xl text-white md:text-2xl"} :: ::ProseButtonGroup ::ProseButton{to="https://store.fluxinc.ca/files/ECEX/latest" variant="outlineInvert"} Download :: ::ProseButton{to="https://store.fluxinc.ca/cart/product/ECEX" variant="outline"} Buy Now :: :: :: Encore Exporter software extracts bone density and body composition data from GE Lunar systems, making it accessible for research, electronic health records, and custom applications. [Explore detailed use cases →](/case-studies/medical) ## Key Features - **Efficient data extraction** from GE LUNAR Prodigy databases - **Customizable exports** with filtering options - **Excel-compatible output** in CSV format - **Low memory usage** for optimal performance - **Simple user interface** requiring minimal training - **Fast, zero-configuration updates** via single installer ## Use Cases ::TwoColumn #left ### Clinical Research - Export specific datasets for academic research - Analyze bone density patterns across patient populations - Extract data for longitudinal studies on osteoporosis ### Data Analysis - Perform statistical analysis on bone density measurements - Generate custom reports beyond standard software capabilities - Build comprehensive research databases #right ### Quality Assurance - Monitor equipment performance with data exports - Analyze trends in measurement consistency - Support quality control initiatives with raw data ### Teaching - Extract anonymized data for educational purposes - Create teaching datasets for medical education - Support evidence-based training materials :: ## How It Works The user-friendly interface allows you to: 1. **Select data type** - Choose between BMD or Body Composition data 2. **Set date ranges** - Target specific investigation periods 3. **Filter by gender** - Export males, females, or both 4. **Choose regions of interest** - Include or exclude specific ROIs 5. **Export to CSV** - One click to generate Excel-compatible files ## Benefits - **Save time** with automated data extraction - **Improve research efficiency** by eliminating manual data entry - **Enhance data integrity** with direct database exports - **Support research initiatives** with complete datasets - **Simplify data analysis** with structured output format ::InfoBox **Ready for research excellence?** EnCore Exporter is the tool of choice for research institutions and clinical practices working with GE LUNAR Prodigy systems. ::ProseButton{to="/contact" variant="primary"} Contact Us :: :: --- URL: https://fluxinc.co/medical/flux-box --- title: "Flux Box — Turnkey DICOM Appliance" description: Pre-configured compact appliance running DICOM Capacitor for mobile imaging, store-and-forward routing, and managed PACS integration keywords: Flux Box, DICOM appliance, Mac mini DICOM, ASUS NUC DICOM, ARM64, mobile mammography hardware, store and forward router, DICOM Capacitor hardware, medical imaging appliance, Flux Inc head: meta: - name: 'og:title' content: 'Flux Box — Turnkey DICOM Appliance' - name: 'og:description' content: 'Pre-configured compact appliance running DICOM Capacitor for mobile imaging, store-and-forward routing, and managed PACS integration' - name: 'og:type' content: 'product' - name: 'canonical' content: 'https://fluxinc.co/medical/flux-box' --- ::FullWidthSection{variant="custom" padding="xl" className="bg-transparent" backgroundImage="/images/flux-box-mobile.jpg" backgroundImageFit="cover" backgroundImageClass="object-[center_8%] xl:object-[center_22%] 2xl:object-[center_28%]" backgroundOverlayClass="bg-gradient-to-br from-zinc-950/88 via-primary-950/45 to-zinc-950/92"} # Flux Box ::RotatingText{items="Plug in. Configure. Done.|Store-forward DICOM router.|Zero-touch imaging relay.|Hardware that just works." tag="p" rootClass="text-xl text-white md:text-2xl"} :: ::ProseButtonGroup ::ProseButton{to="/contact?product=FluxBox" variant="outlineInvert"} Request a Quote :: ::ProseButton{to="https://docs.fluxinc.co/dicom-capacitor/" variant="outline"} Documentation :: :: :: Flux Box is a compact, pre-configured appliance running [DICOM Capacitor](/medical/dicom-capacitor) software. Most units ship as a Mac mini M4, though ASUS NUC and other ARM64 platforms are available depending on deployment requirements. Connect it to the network, configure your PACS destinations, and it starts routing. - **No server infrastructure** required - **No OS installation** or software setup - **No IT overhead** — managed remotely by Flux ## What's Inside ::TwoColumn #left ### Hardware - **Platform** — Apple Mac mini or ASUS NUC, depending on SKU - **Processor** — Apple M-series (M4 or later) or
Intel Core i5 (12th gen or later) - **Memory** — 16 GB or 32 GB - **Storage** —1 TB to 4 TB SSD depending on workload - **Power** — under 30W typical - **Dimensions** — 7.7 in × 7.7 in × 1.4 in, rack-mountable ### Software - **DICOM Capacitor** — full-featured store-and-forward router - **Remote management** — Flux monitors and configures remotely - **Automatic updates** — software kept current by Flux engineering #right ![Flux Box Hardware](/images/products/flux-box-hardware.webp){width="500"} :: ## What It Does Flux Box runs DICOM Capacitor with all capabilities included: - **Store-and-forward** — cache studies locally, deliver when connectivity permits - **Intelligent routing** — send studies to multiple PACS destinations based on configurable rules - **Tag manipulation** — correct, standardize, and harmonize DICOM headers in transit - **Image compression** — JPEG 2000 lossless/lossy, reducing study sizes up to 35% - **Worklist caching** — serve modality worklists locally, sync when connected - **Format conversion** — [Hologic SCO and Siemens CTO to BTO conversion](/case-studies/medical/sco-bto-conversion) for mammography interoperability - **Prefetch** — [worklist-based prior study retrieval](/case-studies/medical/prefetch) with smart filtering - **Adaptive networking** — self-tuning timeouts, retries, and bandwidth management For full software details, see the [DICOM Capacitor product page](/medical/dicom-capacitor). ## Performance Benchmarked natively on an Apple M4 with full screening mammography studies (avg 1.5 GiB per study):
~9s
per study
~6s
per GiB
168
MiB/s
with JPEG 2000 lossless compression
~14s
per study
+5s
overhead
73%
smaller
*Dynamic multi-threading scales across available CPU cores. Performance varies with study size and hardware.* ## Common Deployments ::TwoColumn #left ### Mobile Imaging Vans Flux Box is purpose-built for mobile coaches: - **Fire-and-forget** — technologists send to Capacitor and move on - **Geolocation routing** — auto-detects which facility the van is at - **Flexible delivery** — send in real time or hold until docked, depending on policy - **Offline worklists** — cached locally, synced when connected [Mobile imaging overview →](/medical/mobile-imaging) #right ### Fixed-Site Departments Flux Box also deploys in hospital departments: - **Multi-destination routing** — distribute studies across PACS, CAD, VNA - **Prior study prefetch** — retrieve relevant priors before the patient arrives - **PACS migration** — managed data migration between systems - **Vendor integration** — Siemens, Hologic, GE, and others [Prefetch details →](/case-studies/medical/prefetch) :: ## Deployment Getting a Flux Box operational is straightforward: 1. **Connect** — plug into power and network 2. **Configure** — Flux engineers set up PACS destinations, routing rules, and worklist parameters remotely 3. **Validate** — send test studies, confirm delivery to all destinations 4. **Go live** — modalities point to Flux Box and start sending Ongoing management is handled by Flux: - **Remote monitoring** — Flux watches delivery queues, error rates, and connectivity - **Configuration changes** — new destinations, routing rules, or filter updates applied remotely - **Software updates** — Capacitor updates deployed with minimal disruption - **Support** — direct access to Flux DICOM engineers ::InfoBox For installation guides, network requirements, and configuration reference, see the [DICOM Capacitor documentation](https://docs.fluxinc.co/dicom-capacitor/). :: ::EmphasisBox ## Get Started Flux Box ships pre-configured for your environment. Tell us about your modalities, PACS destinations, and workflow requirements — we handle the rest. ::ProseButtonGroup ::ProseButton{to="/contact?product=FluxBox" variant="primary"} Request a Quote :: ::ProseButton{to="/medical/dicom-capacitor"} Capacitor Software Details :: ::ProseButton{to="/medical/dicom-capacitor/use-cases"} View All Use Cases :: :: :: --- URL: https://fluxinc.co/medical/mobile-imaging --- title: 'Mobile Imaging Fleet Operations — Flux Box' description: 'Flux Box helps enterprise mobile imaging operators manage site profiles, worklists, patient-release review, and safety checks across facility moves — for any modality.' keywords: 'mobile imaging fleet, mobile imaging, mobile mammography, mobile CT, mobile MRI, DICOM router, mobile PACS, mobile worklist, Flux Box, DICOM Capacitor, patient release portal, geofencing, fleet operations' sitemap: changefreq: monthly head: meta: - name: 'og:title' content: 'Mobile Imaging Fleet Operations — Flux Box' - name: 'og:description' content: 'Site-aware mobile imaging workflows with isolated profiles, worklist safeguards, and controlled patient release — across every modality in the fleet.' - name: 'og:type' content: 'product' - name: 'twitter:card' content: 'summary' - name: 'twitter:title' content: 'Mobile Imaging Fleet Operations — Flux Box' - name: 'twitter:description' content: 'Run mobile imaging units across facilities without scanner reconfiguration or cross-site release risk.' - name: 'canonical' content: 'https://fluxinc.co/medical/mobile-imaging' --- ::FullWidthSection{variant="custom" padding="xl" className="bg-transparent" backgroundImage="/images/mobile-truck.jpg" backgroundOverlayClass="bg-gradient-to-br from-zinc-950/90 via-primary-500/35 to-teal-950/90" backgroundImageFit="cover"} # Mobile Imaging Fleet Operations :RotatingText{items="Site profiles without scanner reconfiguration.|Patient-release safeguards for walk-ins and add-ons.|Location changes that fail closed before images can be stored." tag="p" rootClass="text-xl text-white md:text-2xl"} ::ProseButtonGroup ::ProseButton{to="/contact" variant="outlineInvert"} Schedule a Demo :: ::ProseButton{to="/medical/flux-box" variant="outline"} Learn About Flux Box :: :: :: ## Built for facility-based mobile programs Flux Box makes a mobile imaging unit easy to run across many facilities — owned sites, partner locations, renovation and overflow coverage, screening events, and semi-permanent installs. It works for any modality on the coach — mammography, CT, MR, ultrasound, or general radiography — and the imaging device is configured once and always sends to the same local destination, so installers set it up a single time instead of reconfiguring the scanner at every stop. Behind that single destination, Flux Box handles everything that changes between sites — PACS, worklist, routing, header rules, and delivery policy — and enforces each facility's safety rules automatically. The fleet is managed centrally, units move between facilities without truck rolls, and every study is protected before it leaves the box. ::TwoColumn #left - **Facilities change, scanner setup should not** — Technologists should not manage a different PACS, worklist, AE title, or IP address at each stop. - **Overflow work is high pressure** — Renovations, events, and capacity relief do not leave room for brittle network troubleshooting. - **Walk-ins and add-ons are real** — Patients may not always appear on the active worklist before the exam starts. #right - **The wrong release is the risk** — A study from one facility must never leak into another facility's PACS or reporting workflow. - **Local patient data follows the device** — The acquisition system must be clear before it is trusted at the next location. - **Fleet teams need leverage** — A single operator should be able to prepare profiles, push updates, and inspect delivery state across many units. :: ::MobileFeatureShowcase :: ## The mobile-ready feature set Flux Box runs [DICOM Capacitor](/medical/dicom-capacitor) as the routing and safety layer between the imaging device and the facility systems. The scanner keeps sending to the same local destination. Capacitor decides what is safe to receive, where each study belongs, and which profile is allowed to be active. ::TwoColumn #left ### Site profiles Each facility runs from its own profile — DICOM destinations, worklist source, routing rules, tag transformations, compression, and delivery policy. Profiles start cleanly when a unit arrives and stop when it leaves, so the technologist only ever sends to Flux Box. ### Patient-release safeguards Walk-ins and add-ons that aren't on the active worklist are held for deliberate review instead of being released automatically — and the review is scoped to the current facility, so an add-on at one site never mixes into another site's destinations. #right ### Location-change safety The highest-risk moment is a facility change. Flux Box can require a preflight check — confirming the acquisition system has been cleared — before it accepts any new-site storage. It fails closed by default. ### Central fleet operations Profiles are prepared, validated, and pushed from one place. Service teams bring the right profile online when a unit arrives and inspect queues, holds, and delivery state across the fleet without touching the scanner. :: ::InfoBox Profiles are managed centrally through **Configatorium**, the Flux portal where operators create and maintain each facility's profile and push it to the fleet. *(A step-by-step Configatorium walkthrough with screenshots is in preparation.)* :: ::FullWidthSection{variant="custom" padding="lg" className="border border-zinc-200 bg-zinc-100 dark:border-zinc-800 dark:bg-zinc-900" contentClass="dark:text-zinc-100"} ## How the fleet workflow feels ::TwoColumn #left ### For technologists - Send every study to the same local Flux Box destination. - Query the same local worklist endpoint. - Keep scanning even when delivery is deferred by bandwidth or policy. - Review unmatched patients only when the system asks for confirmation. ### For service teams - Prepare facility profiles centrally in Configatorium. - Bring the right profile online when the unit arrives. - Keep remote access and troubleshooting under a controlled service model. - Inspect queues, holds, errors, and active profile state without touching the scanner. #right ### For health-system operators - Use one coach across owned facilities and partner locations. - Support renovation capacity, event screening, overflow demand, and recurring installations. - Standardize mobile imaging behavior across a fleet instead of re-solving every site. - Keep patient-routing boundaries clear for each institution. ### For IT and security - Limit the scanner to a stable local endpoint. - Keep per-site routing rules off the modality. - Seal inactive profiles and caches. - Require explicit release when patient or site context is uncertain. :: :: ## Best-fit mobile imaging use cases ::TwoColumn #left ### Enterprise mobile fleets Operators that run units between multiple facilities — and teams that share trailers across institutions — can centralize profiles and support from one place while keeping each site isolated. ### Facility overflow and renovations When a truck is parked outside a facility to cover construction, equipment downtime, or a backlog, Flux Box lets the unit behave like an extension of that facility without reconfiguring the scanner every time. #right ### Screening events and recurring programs Health fairs, awareness-month events, and recurring partner-site programs can keep a stable workflow while still honoring facility-specific routing and worklist rules. ### Standby and spare trailers Spare coaches can be kept ready with the same profile model, then activated for the facility that needs coverage. :: ::EmphasisBox ## See the mobile fleet model in action Flux Box is a compact, pre-configured appliance for mobile imaging programs that need profile control, patient-release safeguards, and safe facility changes. ::ProseButtonGroup ::ProseButton{to="/contact" variant="primary"} Schedule a Demo :: ::ProseButton{to="/medical/mobile-imaging-technical" variant="outline"} Technical Details :: ::ProseButton{to="/medical/flux-box" variant="outline"} Flux Box Hardware :: :: :: --- URL: https://fluxinc.co/medical/mobile-imaging-technical --- title: 'Technical Bulletin: Flux Box for Mobile Imaging Fleets' description: 'A technical bulletin on how Flux Box and DICOM Capacitor support mobile imaging fleet management with site profiles, worklist caching, store-forward delivery, release review, cache isolation, and location-change safety controls.' keywords: 'Flux Box, DICOM Capacitor, mobile imaging fleet, mobile DICOM router, site profiles, worklist cache, store and forward, DICOM C-STORE, DICOM C-FIND, patient release portal, location gate, mobile imaging security' ogType: article schemaType: Article sitemap: changefreq: monthly head: meta: - name: 'og:title' content: 'Technical Bulletin: Flux Box for Mobile Imaging Fleets' - name: 'og:description' content: 'Architecture, safety controls, DICOM dataflow, security posture, and implementation guidance for Flux Box and DICOM Capacitor in mobile imaging fleet operations.' - name: 'og:type' content: 'article' - name: 'twitter:card' content: 'summary' - name: 'twitter:title' content: 'Technical Bulletin: Flux Box for Mobile Imaging Fleets' - name: 'twitter:description' content: 'The technical model behind Flux Box mobile imaging fleet operations.' - name: 'canonical' content: 'https://fluxinc.co/medical/mobile-imaging-technical' --- ::FullWidthSection{variant="custom" padding="lg" className="border border-zinc-200 bg-zinc-100 dark:border-zinc-800 dark:bg-zinc-900" contentClass="dark:text-zinc-100"} # Technical Bulletin: Flux Box for Mobile Imaging Fleets Flux Box is a compact edge appliance that runs [DICOM Capacitor](/medical/dicom-capacitor) between a mobile imaging unit and the facility systems it visits. This bulletin describes the technical model for using Flux Box as a fleet-management layer: fixed scanner configuration, site profiles, local worklist and storage services, store-forward delivery, patient-release review, cache isolation, and optional location-change preflight checks. :: ::ProseButtonGroup ::ProseButton{to="/medical/mobile-imaging" variant="primary"} Fleet Operations Overview :: ::ProseButton{to="/medical/flux-box" variant="outline"} Flux Box Hardware :: ::ProseButton{to="/contact?product=FluxBox" variant="outline"} Discuss a Fleet :: :: ## Abstract Mobile imaging programs usually have three competing requirements: the acquisition device must stay simple, every visited facility needs its own PACS and worklist behavior, and studies must not cross institutional boundaries when the unit moves. Flux Box addresses that by making the modality talk to one local DICOM endpoint while Capacitor activates the correct downstream profile for the current site. ::TwoColumn #left ### The scanner-side contract - The modality keeps one local storage destination. - The modality queries one local worklist endpoint. - The technologist workflow stays stable across facility moves. - Manual or ad-hoc sends target generic local destinations instead of memorized site-specific nodes. #right ### The fleet-side contract - Each facility has its own profile, destinations, routing rules, worklist source, and delivery policy. - Profiles can be prepared centrally, deployed to the box, activated at arrival, and stopped when the unit leaves. - Safety controls can hold unmatched patients, seal inactive caches, and block new-site storage until the local acquisition system is clear. :: ## Design Pressure in Mobile Fleets | Constraint | Technical impact | Flux control | | -------------------------------------------- | --------------------------------------------------------------------- | -------------------------------------------------------- | | The same unit visits multiple institutions | PACS, worklist, tags, AE titles, and delivery policies change by site | Per-site profiles | | Site moves happen under operational pressure | Scanner reconfiguration creates failure risk | Fixed local scanner endpoint | | Mobile links are variable | Direct sends can fail, duplicate, or strand partial studies | Persistent store-forward queue | | Walk-ins and add-ons occur | A study may not match the active worklist | Release review workflow | | Facility boundaries matter | Prior-site studies must not leak into a new profile | Cache and runtime isolation | | Scanner databases retain local patients | A site move can leave old patient records on the acquisition system | Optional C-FIND location gate | | Hospital security rules differ | Network probing and ad-hoc router rules may trigger review | Low-change edge architecture with explicit site profiles | ## Reference Architecture ```mermaid graph LR MOD["Imaging modality"] FB["Flux Box - DICOM Capacitor"] PACS["PACS / VNA / archive"] AI["AI / CAD / viewer"] CFG["Configatorium validated profiles"] MOD -->|"C-STORE and MWL"| FB FB --> PACS FB --> AI CFG -.-> FB ``` Flux Box can sit beside the existing coach router instead of replacing every network function. In that model, the router continues to provide facility connectivity or remote-support paths, while Flux Box owns the DICOM workflow boundary between the modality and facility systems. The edge can also span two nodes when a program wants delivery to continue after the coach leaves: a workstation on the vehicle captures and caches studies at LAN speed, paired with an in-building gateway that owns facility-side delivery while the unit is on site (modality → on-coach Flux Box → gateway → PACS). Single-node and paired-gateway deployments use the same profile and safety model. ::InfoBox The architecture is deliberately conservative: keep the scanner stable, keep facility-specific logic on the edge appliance, and make the active site profile the unit of trust. :: ## Site Profiles A site profile is the complete operating definition for one facility or program location. It can include: - Facility identity, expected network evidence, and activation policy - PACS, VNA, AI, CAD, viewer, archive, and secondary destinations - Modality Worklist source and query behavior - DICOM AE titles, IPs, ports, and destination aliases - Routing rules by modality, SOP Class, body part, procedure, series, institution, or downstream requirement - Tag normalization, institution-name mapping, station-name changes, accession handling, and vendor compatibility rules - Compression, conversion, batch size, retry, bandwidth, and delivery schedule - Release-review policy for patients missing from the active worklist - Cache retention, encryption, isolation, and replay policy - Monitoring, audit, support, and rollback metadata ### Profile Lifecycle 1. **Prepare** - Build or update the facility profile in Configatorium or Flux engineering tooling. 2. **Validate** - Confirm DICOM endpoints, worklist behavior, routing rules, and downstream acceptance with test studies. 3. **Package** - Create a deployable profile package for the unit. 4. **Deploy** - Push remotely when connectivity exists, or stage offline for locked-down environments. 5. **Detect** - Use geofence, network, service, schedule, or operator evidence to select the expected profile. 6. **Preflight** - Optionally run a location-change safety check before storage opens. 7. **Activate** - Bring the profile online and expose the correct local DICOM behavior. 8. **Seal** - Stop the profile and keep its cache isolated when the unit leaves. ### Site Detection and Activation Detection is endpoint-agnostic — the modality is never reconfigured between sites. When the facility-side link comes up, Flux Box confirms which site it is on by probing the endpoints that profile expects; a DICOM C-ECHO to a known node is treated as positive confirmation, which holds even where hospital networks block ICMP. Coarse geolocation can act as an optional pre-filter, and an unrecognized network fails closed: no profile is activated and no storage port is opened. ```mermaid sequenceDiagram participant U as Coach arrives on site participant FB as Flux Box (detector) participant N as Expected facility node(s) U->>FB: Facility-side network link comes up FB->>FB: Optional geofence pre-filter (coarse location) FB->>N: Probe expected endpoints (C-ECHO) N-->>FB: Response from a recognized node FB->>FB: Activate the matching profile, and only that one Note over FB: No recognized network: fail closed, storage port stays shut ``` ## Scanner Configuration Model The scanner should not need a new PACS node for every stop. In a Flux Box deployment, the modality can be configured with stable local targets: | Scanner target | Typical meaning | Behind the box | | ----------------- | ------------------------- | ----------------------------------------------------------------- | | `PACS` | Default send | Active profile routes by site policy | | `PACS2` / `PACS3` | Ad-hoc or secondary sends | Active profile maps to archive, viewer, AI, or other destinations | | `WORKLIST` | Local MWL endpoint | Capacitor serves cached or live facility worklist data | This is especially useful for coaches that rotate across many sites. A technologist can send to the same local destination everywhere, while the profile translates that action into the correct facility routing. ## DICOM Dataflow ### Acquisition and Local Ingest The modality sends studies to Flux Box using standard DICOM C-STORE. Because the first hop is local, acquisition can finish at LAN speed even if the upstream facility link is slow, offline, or scheduled for later delivery. Capacitor accepts and writes acknowledged DICOM objects locally, tracks SOP Instance identity for delivery, and places the study into a persistent queue. ### Worklist Proxy and Cache The modality can query Flux Box as its local Modality Worklist endpoint. Capacitor can serve the last known good worklist, refresh against the active facility when connectivity allows, and apply profile-specific cleanup for downstream compatibility. This keeps the modality workflow usable even when a mobile link is unavailable during patient intake. ### Store-Forward Delivery Capacitor delivers queued studies asynchronously according to profile policy: - Immediate delivery when wireless or wired connectivity is sufficient - Scheduled delivery after patient hours or during a known docked window - Manual release from a portal when an operator wants a deliberate send step - Scripted triggers, including power state, site network evidence, or fleet policy - Retry and resume behavior based on acknowledged DICOM instances A study should remain queued until the intended destination acknowledges the required SOP Instances. If an association drops, Capacitor can use destination acknowledgements and SOP Instance tracking to resume with undelivered objects instead of forcing the technologist to resend the exam from the scanner. ### Routing, Transformation, and Compression Mobile fleet profiles often need more than one destination. A single exam may need PACS storage, AI processing, viewer-specific header compatibility, archive delivery, and selective exclusion of dose reports, raw projections, or unsupported SOP Classes. Capacitor can apply those rules at the edge: - Fan-out to multiple destinations - SOP Class and series filtering - Institution, station, procedure, and description normalization - Viewer-specific compatibility rules - JPEG 2000 or other transfer-syntax policies where supported - Large-study compression for DBT, CT, MR, and similar workflows ## Safety Controls ### Per-Site Cache Isolation Each site profile can keep its own cache, queue, and routing state. When a unit leaves Facility A and activates Facility B, Facility A data should not remain visible to the active Facility B workflow. This model supports encrypted local storage, inactive-profile shutdown, and profile-scoped replay. ### Release Review for Unmatched Patients Mobile programs need a safe path for walk-ins, add-ons, and event-day patients who are not present on the active worklist. Flux Box can hold those studies for review instead of releasing them automatically. The review workflow is scoped to the active profile, so an add-on patient at one facility is not silently routed under another facility profile after a move. ::WarningBox Fail closed is the correct default for unmatched patients. The system should hold the study until a qualified operator confirms the release context. :: ### Optional Location-Change Gate The highest-risk transition is a facility change. Flux Box can be configured to run a DICOM C-FIND preflight against the local acquisition system before Capacitor opens the storage port for the new site. 1. A site change is detected. 2. The expected profile is selected but not fully opened. 3. Flux Box queries the local acquisition system. 4. If prior patients remain, storage for the new profile stays closed. 5. The operator clears the acquisition system. 6. Capacitor opens storage under the new profile after a clear result. ```mermaid sequenceDiagram participant FB as Flux Box participant MOD as Acquisition modality Note over FB: New site detected FB->>MOD: C-FIND for residual patient records MOD-->>FB: Records still present FB->>FB: Keep storage port closed for the new profile Note over FB,MOD: Operator clears the local database FB->>MOD: C-FIND re-check MOD-->>FB: Clean FB->>FB: Open storage under the new profile ``` This control does not clean the scanner database itself. It prevents new-site storage until the local patient list is clear enough for the configured safety policy. ### Manual Sends Without Manual Site Logic Manual transmission still matters for radiologist-requested resends or exception handling. The safer pattern is to keep manual targets generic on the modality and map those targets through the active profile. That preserves ad-hoc flexibility without asking technologists to remember site-specific DICOM nodes. ## Network and Security Posture ::TwoColumn #left ### Network model - Scanner communicates with a stable local Flux Box endpoint. - Facility uplink can be Ethernet, Wi-Fi, cellular, VPN, or a managed router path. - Site detection can use geofence, gateway, subnet, service reachability, schedule, or operator confirmation. - Fleet programs can avoid broad scanner-side node lists and reduce per-site modality changes. - Where hospitals require a stable network identity, Flux Box can be configured for predictable adapter behavior. #right ### Security model - No facility profile is active unless selected and started. - Inactive caches and routes remain outside the active workflow. - Remote support can be limited to approved channels and audited operational access. - The box can operate without domain membership in many deployments because DICOM is the integration boundary. - Security review artifacts should cover data at rest, support access, update process, logging, and profile deployment. :: ## Fleet Operations Model Flux Box is not only a DICOM router on a truck. In a fleet deployment, it becomes an operations surface for profile control. | Operations function | Technical behavior | | --------------------- | ------------------------------------------------------------------------------------------------------ | | Profile inventory | Maintain the set of approved facilities, destinations, worklist sources, and route rules | | Pre-arrival setup | Stage profiles before the unit reaches the site | | Controlled activation | Bring one expected profile online at a time | | Release oversight | Review held studies and unmatched patients from the correct facility context | | Queue visibility | Inspect pending, delivered, failed, and held studies | | Remote support | Troubleshoot routing, connectivity, worklist, and downstream acceptance without changing scanner setup | | Auditability | Track profile changes, active site state, release decisions, and delivery outcomes | | Rollback | Revert to a previously validated profile if a site change fails acceptance | Configatorium is the Flux profile-management portal for this model. It is where operators can create and maintain profiles, review the profile-management workflow, and prepare updates for the fleet. The public page can be paired with a customer-specific Configatorium walkthrough during implementation. ## Deployment Patterns ### Facility Overflow and Renovation Coverage A coach parked outside a hospital can behave like an extension of that facility while local construction, equipment replacement, backlog relief, or event coverage is underway. The modality still sends locally; the active profile makes the unit match the facility. ### Multi-Site Rotation A shared trailer can rotate across facilities with different PACS, worklists, institution names, and downstream routing requirements. Flux Box keeps those differences out of scanner setup. ### Screening Events and Walk-Ins Release review is useful when patients may arrive outside the scheduled worklist. The box can hold the study, show the review state, and require deliberate release. ### Standby and Spare Trailers Standby units can carry the same profile model as production units. When a spare replaces a failed coach, the fleet team activates the correct site profile instead of rebuilding scanner configuration. ### Multi-Vendor Downstream Workflows Mobile programs often feed PACS, AI, CAD, viewer, archive, and router systems at the same time. Capacitor can apply profile-specific fan-out, SOP filtering, compression, and header rules so each destination receives the format it expects. ### Non-Mammography Mobile Imaging The architecture is modality-agnostic. It can support mammography, MR, CT, ultrasound, radiography, ophthalmology imaging, and other DICOM-producing devices when the workflow benefits from local DICOM services, site-aware routing, and controlled delivery. ## Implementation Checklist ### 1. Site and Fleet Intake - List every facility, trailer, scanner, router, PACS, worklist source, and downstream destination. - Decide which destinations are default, secondary, ad-hoc, AI, archive, or viewer-specific. - Capture AE titles, IPs, ports, transfer syntax support, SOP Class requirements, and firewall constraints. - Define site detection evidence and the fallback manual selection process. - Define retention, encryption, remote-support, and audit requirements. ### 2. Profile Build - Create one profile per facility or operating mode. - Configure routing, tag normalization, worklist behavior, compression, and delivery policy. - Configure hold/release behavior for patients missing from worklist. - Configure optional location-change gate if scanner database clearance is part of the safety model. - Package the profile for remote or offline deployment. ### 3. Lab Validation - Send test studies through every profile. - Verify worklist query behavior. - Verify downstream acceptance for PACS, viewer, AI, archive, and router destinations. - Test link loss, retry, resume, duplicate handling, and scheduled delivery. - Test profile stop/start and cache isolation between sites. ### 4. Field Pilot - Install the box with stable scanner-side addressing. - Confirm the modality sends to the same local endpoint at every stop. - Validate one low-risk site move under supervision. - Confirm operator response to holds, unmatched patients, and location-gate stops. - Record the rollback path. ### 5. Fleet Rollout - Publish the approved profile set. - Train operators on profile state, release review, and support escalation. - Monitor queues, failed associations, held studies, and worklist sync health. - Add new facilities through the same profile lifecycle rather than scanner-side changes. ## Boundary Conditions Flux Box is intentionally narrow about ownership: - It is not the legal patient identity authority; RIS, EHR, and facility worklist systems remain authoritative. - It does not silently clear the acquisition system; a location gate can block storage until clearance happens. - It does not remove the need for facility firewall, VPN, or network approval. - It does not make every downstream system accept every transfer syntax or SOP Class; profiles encode those compatibility rules. - It should not be used to hide unresolved workflow ambiguity. If patient or facility context is uncertain, the safer behavior is to hold. ## Why This Matters Mobile imaging fleets fail operationally when site-specific logic leaks into the scanner, technologist memory, or one-off router scripts. Flux Box moves that logic into versioned profiles, keeps the modality endpoint stable, and adds safety controls around the moments that matter: patient release, site changes, cache boundaries, and delivery over unreliable networks. ::EmphasisBox ## Review the Fleet Model Start with the operations overview, then use this bulletin during technical review, security review, and implementation planning. :: ::ProseButtonGroup ::ProseButton{to="/medical/mobile-imaging" variant="primary"} Operations Overview :: ::ProseButton{to="/medical/dicom-capacitor" variant="outline"} Capacitor Product Details :: ::ProseButton{to="/contact?product=FluxBox" variant="outline"} Schedule a Technical Review :: :: --- URL: https://fluxinc.co/medical/model-governance-layer --- title: Model Governance Layer description: Deploy untrusted AI safely into trusted healthcare and enterprise environments. Our Model Governance Layer acts as a cllama sidecar proxy — enforcing behavioral contracts, mediating tool access, and maintaining a governed identity trust boundary between LLMs and your organization. head: meta: - name: 'og:title' content: 'Model Governance Layer - Governed AI Deployment by Flux Inc.' - name: 'og:description' content: 'Deploy untrusted AI safely into trusted healthcare and enterprise settings. Behavioral contracts, governed tool presentation, identity trust, and audit at the infrastructure layer.' - name: 'og:type' content: 'product' - name: 'twitter:card' content: 'summary_large_image' - name: 'twitter:title' content: 'Model Governance Layer - Governed AI Deployment by Flux Inc.' - name: 'twitter:description' content: 'Behavioral contracts, governed tool presentation, and identity trust for AI in regulated environments.' - name: 'canonical' content: 'https://fluxinc.co/medical/model-governance-layer' --- ::FullWidthSection{variant="gradient" padding="sm" className="bg-transparent" patternOverlay="true" gradientColor="sky-800"} # Model Governance Layer ::RotatingText{items="Govern Untrusted AI.|Enforce Behavioral Contracts.|Mediate Tool Access.|Maintain Identity Trust." tag="p" rootClass="text-xl text-white md:text-2xl"} :: ::ProseButtonGroup ::ProseButton{to="/contact?product=ModelGovernanceLayer&interest=early_access" variant="outlineInvert"} Request Early Access :: ::ProseButton{to="/contact?product=ModelGovernanceLayer&interest=schedule_demo" variant="outline"} Schedule Demo :: :: :: The fundamental challenge of enterprise AI isn't capability — it's trust. Large language models are powerful but untrusted workloads. The Model Governance Layer (MGL) is the boundary that lets you deploy them safely inside trusted healthcare and enterprise environments: enforcing policy at the infrastructure layer, not the application layer, so your AI stays compliant even when it misbehaves. ## The Problem: Untrusted Workloads in Trusted Settings A hospital system doesn't hand a new contractor unrestricted access to patient records on their first day. Yet most AI deployments do exactly that — granting LLMs broad access to organizational data and tools with governance enforced only at the prompt level, if at all. Prompt-level governance is fragile. It can be bypassed, forgotten, or simply wrong. The MGL takes a different approach: **governance at the infrastructure layer, independent of the model itself**. ::TwoColumn #left ### The Regulated Environment Problem Healthcare, finance, and government operate under strict compliance regimes — HIPAA, SOC 2, FedRAMP, ISO 27001. A generalist LLM knows none of this. It doesn't know which users can see which patient records. It doesn't know that your sales team isn't allowed to quote prices without legal review. It doesn't know that your radiology department uses different terminology than the rest of the hospital. Left unmediated, AI erodes these boundaries. #right ### The MGL Solution The MGL sits between your users and your LLMs as a transparent, governed proxy. It knows your organization — roles, policies, data access rules, and behavioral expectations. It intercepts every request, decorates it with the appropriate identity and policy context, and governs every response before it reaches the user. The model never touches credentials it shouldn't. Tools are presented only to agents that are authorized to use them. Every interaction is logged. :: ## How It Works: The cllama Sidecar The MGL is implemented as a **[cllama](/ai/cllama) sidecar** — a lightweight governance proxy that runs alongside your LLM deployment and intercepts all inference traffic. This is the same architecture used in the open-source [clawdapus](/ai/clawdapus) agent containment framework, adapted for enterprise and healthcare customer deployment.
01
Identify
Resolve user identity, role, and group memberships. Establish who is asking and what policy applies.
02
Govern
Apply behavioral contracts and mediate tool access. Only permitted tools and data reach the model.
03
Deliver
Validate the response against MUST-priority rules before it reaches the user. Log everything at the proxy boundary.
**The request lifecycle:** 1. **Identity Resolution** — The user's identity, role, and group memberships are resolved (Active Directory, LDAP, or custom IAM). The proxy establishes who is asking. 2. **Behavioral Contract Enforcement** — Per-role behavioral contracts define what the model *must* and *must not* do. These are bind-mounted read-only at the infrastructure layer — the model cannot override them. 3. **Governed Tool Presentation** — Only the tools and data sources appropriate for this identity are surfaced to the model. A radiologist sees imaging tools; a billing clerk does not. Tool scope is declared at the infrastructure layer, not in the prompt. 4. **LLM Interaction** — The decorated, governed request is forwarded to the model. Real API credentials are held by the proxy — the model runtime never has direct key access. 5. **Response Governance** — The response is evaluated against MUST-priority compliance rules before delivery. Non-compliant responses are retried automatically with corrective context (up to five attempts) before escalation. 6. **Audit Trail** — Every inference transaction is recorded as a structured, append-only log at the proxy boundary — independent of and inaccessible to the model itself. ## Key Capabilities ::TwoColumn #left ### Behavioral Contracts Define what your AI *must*, *must not*, and *should* do — encoded as organizational policy rather than prompt engineering. Contracts compose: organization-wide rules, department-level overlays, and role-specific refinements stack cleanly. They're read-only at runtime. The model inherits them. It cannot modify them. ### Identity Trust Every inference carries a verified identity context. The MGL resolves who is asking, what they're authorized to access, and what behavioral constraints apply to their role. This identity envelope travels through the governance layer — it's not something the user or the model can forge. ### Governed Tool Presentation Tools aren't just enabled or disabled — they're *scoped*. A data query tool might be available to all users, but its permitted datasets differ by role. The MGL compiles per-identity tool manifests at request time. The model sees only what it's allowed to reach. #right ### Credential Starvation The model never holds real API keys, database credentials, or service tokens. The proxy holds them. This is the **credential starvation** pattern from cllama: even if a model were to attempt unauthorized access, it lacks the credentials to succeed. Security at the infrastructure layer, not the trust layer. ### Ambient Memory Plane Context that persists across sessions — organizational knowledge, prior interaction summaries, user preferences — is managed by the governance layer, not the model. The model receives curated context injections. It cannot modify, exfiltrate, or selectively forget them. Memory is infrastructure-owned. ### Compliance Retry Loop When a response violates a MUST-priority rule, the MGL retries automatically with a targeted corrective prompt explaining the specific failure. This loop runs up to five times before escalating. The user sees a compliant response or a clear escalation — never a raw governance failure. :: ## Built on Open Standards The MGL is Flux Inc.'s production implementation of the [cllama governance proxy standard](/ai/cllama), developed in collaboration with the [clawdapus](/ai/clawdapus) open-source project. These are MIT-licensed frameworks built for exactly this problem: deploying AI as an untrusted workload inside environments that require trust. ::ContentBox{variant="dark"} ### Why Open Standards Matter in Regulated Environments Proprietary AI governance is a liability. When an auditor asks how your AI enforces HIPAA-covered data boundaries, "it's in the prompt" is not an acceptable answer. The MGL's governance architecture is based on open, auditable standards — behavioral contracts that can be reviewed, credential isolation that can be verified, and audit logs that can be independently inspected. Flux contributes to these open standards and implements them for organizations that need production-grade deployment expertise. :: ## Deployment Options ::TwoColumn #left ### On-Premises The MGL runs entirely within your infrastructure. No data leaves your environment. The governance proxy runs as a sidecar to your existing LLM deployment — whether that's a self-hosted model, a private Azure OpenAI endpoint, or an Ollama instance. Compatible with OpenAI and Ollama API formats. ### Healthcare-Specific Deployment Pre-configured behavioral contracts for HIPAA-adjacent contexts: patient data access controls, PHI boundary enforcement, role-based clinical tool scoping, and audit logging formatted for compliance review. Integrates with existing LDAP/Active Directory for identity resolution. #right ### Enterprise Deployment Role-based governance for finance, legal, HR, and operations contexts. Conversational rule management lets authorized administrators modify behavioral contracts through natural language — no developer required. Conflict detection prevents contradictory rules from reaching production. ### Hybrid / Cloud For organizations using cloud LLM providers, the MGL proxy sits at your perimeter — data is governed before it leaves, and responses are governed before they arrive. Real API keys stay in your infrastructure. :: ## Ideal For - **Radiology and clinical departments** needing AI assistants that understand patient data access boundaries - **Healthcare IT teams** deploying LLMs under HIPAA with audit and compliance requirements - **Legal and compliance teams** that need AI operating under firm behavioral constraints - **Financial institutions** with role-based information barriers - **Government and defense** with clearance-based access requirements - **Any organization** that wants AI capability without surrendering governance ::EmphasisBox ## Deploy AI You Can Actually Trust Ready to put governance at the infrastructure layer instead of hoping the prompt holds? ::ProseButtonGroup ::ProseButton{to="/contact?product=ModelGovernanceLayer&interest=learn_more" variant="primary"} Speak With Our AI Specialists :: ::ProseButton{to="/ai/clawdapus" variant="outline"} Explore Agent Containment :: ::ProseButton{to="/flux-mentor" variant="outline"} Secure On-Prem AI :: :: :: --- URL: https://fluxinc.co/medical/tupacs --- title: TuPACS description: Easily scan documents and send them directly to your PACS system keywords: document scanning, PACS integration, medical documents, healthcare scanning, DICOM conversion, document management sitemap: changefreq: monthly head: meta: - name: 'og:title' content: 'TuPACS - Document Scanning to PACS Solution' - name: 'og:description' content: 'Easily scan documents and send them directly to your PACS system' - name: 'og:type' content: 'product' - name: 'twitter:card' content: 'summary' - name: 'twitter:title' content: 'TuPACS - Document Scanning to PACS Solution' - name: 'twitter:description' content: 'Easily scan documents and send them directly to your PACS system' - name: 'product:price:amount' content: '600.00' - name: 'product:price:currency' content: 'USD' - name: 'canonical' content: 'https://fluxinc.co/medical/tupacs' --- ::FullWidthSection{variant="custom" padding="sm" className="bg-transparent" backgroundImage="/images/hero.webp" backgroundOverlayClass="bg-gradient-to-br from-emerald-700/80 via-emerald-700/100 to-emerald-700/60"} # TuPACS ::RotatingText{items="Scan to PACS.|Worklist matching.|Attach documents." tag="p" rootClass="text-xl text-white md:text-2xl"} :: ::ProseButtonGroup ::ProseButton{to="https://store.fluxinc.ca/files/TPX/latest" variant="outlineInvert"} Download :: ::ProseButton{to="https://store.fluxinc.ca/cart/product/TPX" variant="outline"} Buy Now :: :: :: [Explore detailed use cases →](/case-studies/medical) TuPACS, our scan-to-PACS solution integrates document scanning directly with your medical imaging archive. Send scanned documents, ID cards, and consent forms directly to PACS with the right patient information. ## Key Features - **Super simple user interface** for quick adoption and minimal training - **Document scanning integration** with most scanner brands using WIA - **Page manipulation** allows reordering and rotating pages before sending to PACS - **Flexible worklist matching** using Patient ID, Accession, or Patient Name - **Error reporting** saves exams to a temporary folder for later access - **Background processing** stores to PACS while you match the next set of pages ## Use Cases ::TwoColumn #left ### Clinical Documentation - Scan and attach paper documents to patient imaging studies - Digitize consent forms and patient questionnaires - Incorporate outside reports into the patient's imaging record ### Legacy Paper Conversion - Convert historical paper documents to digital format - Associate paper records with current patient imaging - Maintain comprehensive digital patient records #right ### Referral Integration - Digitize paper referrals and requisitions - Match referral documents to the appropriate study - Ensure complete documentation is available in PACS :: ## How It Works 1. **Scan** a document using your connected scanner 2. **TuPACS activates** automatically and displays the scanned pages 3. **Adjust pages** by reordering or rotating if needed 4. **Search the worklist** using patient identifiers 5. **Match** the document to the correct patient or study 6. **TuPACS stores** the document to your PACS in the background ::ContentBox{type="info"} **Testing Your Setup?** For development or testing purposes, you can use our [Public Test DICOM Modality Worklist](/posts/public-test-dicom-modality-worklist) to verify proper worklist query functionality before connecting to your production environment. :: ## System Requirements - Windows 7 or higher - A document scanner that supports Windows Image Acquisition (WIA) or scan-to-file function - Microsoft .NET 4.0 Client Profile (downloaded automatically during installation) - A DICOM 3.0 compliant PACS ::InfoBox **Need custom document workflow integration?** TuPACS can be configured for specialized document handling requirements. ::ProseButton{to="/contact" variant="primary"} Contact Us :: :: --- URL: https://fluxinc.co/posts/adding-a-logo-to-dicom-printer-2-output --- title: 'Adding a Logo to DICOM Printer 2 Output' description: 'Learn how to customize your DICOM documents with a logo and facility information using DICOM Printer 2' date: '2023-06-15' keywords: DICOM printing, logo customization, facility branding, DICOM Printer 2, configuration, medical imaging --- # Adding a Logo to DICOM Printer 2 Output ::InfoBox This article is intended for IT staff. It includes XML configuration examples that might be difficult to understand for the non-initiated. If you need help implementing these customizations, please [contact our support team](/contact). :: ## Recap: Basic Film Output In our [previous post](/posts/printing-to-film-using-dicom-printer-2), we covered the installation and configuration of basic film output with DICOM Printer 2. While this setup works for basic use cases, most medical facilities want to include their identity on their printed output. This guide will show you how to enhance your DICOM output by adding your facility's logo and name to every printed document. ::TwoColumn #left ### Before: Basic DICOM Output ![Basic DICOM output without customization](/images/posts/adding-a-logo-to-dicom-printer-2-output/8x10-Ceph-no-logo.jpg) *Basic DICOM output without customization* #right ### After: Customized DICOM Output ![Enhanced output with facility branding](/images/posts/adding-a-logo-to-dicom-printer-2-output/8x10-Ceph-logo-and-facility.jpg) *Enhanced output with facility branding* :: ## Adding Your Logo to DICOM Printer 2 ### Step 1: Prepare Your Logo Image First, we need to save the logo image to a location where DICOM Printer can find it. The best place for this is the DICOM Printer config folder: 1. Open the DICOM Printer Control Center 2. Click the shortcut to the configuration folder ![Configuration folder shortcut](/images/posts/adding-a-logo-to-dicom-printer-2-output/go_to_config.jpg) 3. Save your logo in this folder ![Logo in explorer window](/images/posts/adding-a-logo-to-dicom-printer-2-output/saving_logo.jpg) ::EmphasisBox ### Logo Image Tips - Use PNG format for best quality - Recommended size: 200 x 100 pixels - The full path will typically be: `C:\ProgramData\Flux Inc\DICOM Printer 2\config\logo.png` - On Windows, you can also use the environment variable path: `%ProgramData%\Flux Inc\DICOM Printer 2\config\logo.png` :: ### Step 2: Create the PrintImage Action The logo is placed onto each page using a **PrintImage** action in your DICOM Printer 2 configuration. Here's how to configure it: ```xml C:\ProgramData\Flux Inc\DICOM Printer 2\config\logo.png 1 1 16 16 keep ``` Important parameters explained: - `name="addLogo"` - This identifier will be used to call the action in the workflow - `1` and `1` - Position the logo 1% from the top and 1% from the left of the page - `16` and `16` - The logo will be placed in a box that is 16% of the page width and height - `keep` - Maintain the original aspect ratio of the logo image ### Step 3: Integrate into Your Configuration When included as part of your complete configuration, the XML would look like this: ```xml 1 1 30 320 x 320 Grayscale12 DICOM_PRINTER DS5302 192.168.1.100 5040 10 10 C:\ProgramData\Flux Inc\DICOM Printer 2\config\logo.png 1 1 16 16 keep ``` ### Step 4: Restart the DICOM Printer 2 Service After saving your configuration, you need to restart the DICOM Printer 2 service: 1. Stop the service ![Stop the service](/images/posts/adding-a-logo-to-dicom-printer-2-output/save_config.jpg) 2. Start the service again ![Start the service](/images/posts/adding-a-logo-to-dicom-printer-2-output/restart_after_save.jpg) ## Testing Your Configuration Now when you print to DICOM Printer 2 from your application, your logo should appear at the top left of each printed document. ::WarningBox If your logo doesn't appear, check that: 1. The file path in your configuration matches where you saved the logo 2. The logo file format is supported (PNG is recommended) 3. The DICOM Printer 2 service was successfully restarted :: ## Adding Facility Information (Text) You can also add facility name or other text to your output by using the `PrintText` action, which works similarly to the `PrintImage` action. Here's an example configuration: ```xml ACME Medical Imaging Center 50 98 Arial 9 Black Center ``` Add this to your `ActionsList` section and include `` in your workflow to display the facility name at the bottom of the page. ## Advanced Customizations DICOM Printer 2 allows for even more advanced customizations: - **Patient demographics**: Extract patient information using a `ParseJobTextFile` action and display it with `PrintText` - **Multiple logos**: Add different logos at different positions on the page - **Conditional display**: Only show certain elements based on document type or content ::ProseButtonGroup ::ProseButton{to="https://store.fluxinc.ca/files/DP2/latest" variant="primary"} Download DICOM Printer 2 Trial :: ::ProseButton{to="https://store.fluxinc.ca/cart/product/DP2"} Purchase DP2 ($750 USD) :: :: ::EmphasisBox At $750 USD, DICOM Printer 2 is an affordable solution for customizing your DICOM output. Our fully-functional 60-day evaluation allows you to test all features before purchasing. :: ## Related Resources - [DICOM Printer 2 Overview](/medical/dicom-printer-2) - [Printing to Film Using DICOM Printer 2](/posts/printing-to-film-using-dicom-printer-2) - [Automating DICOM Printer 2](/posts/automating-dicom-printer-2) - [Which DICOM Printer Do I Need?](/medical/dicom-printer) ::WarningBox Need help with your specific configuration? Our DICOM specialists can help customize DICOM Printer 2 for your unique requirements. [Contact us](/contact) for personalized assistance. :: ::ProseButtonGroup{class="justify-between"} ::ProseButton{to="/posts/printing-to-film-using-dicom-printer-2" class="hidden md:inline-flex"} ← Printing to Film Using DICOM Printer 2 :: ::ProseButton{to="/posts/printing-to-film-using-dicom-printer-2" class="md:hidden"} ← Previous :: ::ProseButton{to="/posts/automating-dicom-printer-2" variant="primary" class="hidden md:inline-flex"} Automating DICOM Printer 2 → :: ::ProseButton{to="/posts/automating-dicom-printer-2" variant="primary" class="md:hidden"} Next → :: :: ::ProseButtonGroup ::ProseButton{to="/medical/dicom-printer-2"} Product Overview :: ::ProseButton{to="/medical/dicom-printer"} See Also: Which DICOM Printer Do I Need? :: :: --- URL: https://fluxinc.co/posts/automating-dicom-printer-2 --- title: 'Automating DICOM Printer 2' description: 'Learn how to automate DICOM Printer 2 for paperless workflows and efficient PACS integration' date: '2023-06-12' keywords: DICOM automation, paperless workflow, PACS integration, document processing, XML configuration, DICOM Printer 2, worklist query --- # Automating DICOM Printer 2 ::InfoBox This article is intended for IT staff. It includes samples of XML files that might be difficult to understand for the non-initiated. If you would like to learn about automated DICOM storage without the technical jargon, please [contact our team](/contact). :: ::ProseButtonGroup ::ProseButton{to="https://store.fluxinc.ca/files/DP2/latest" variant="primary"} Download DICOM Printer 2 Trial :: ::ProseButton{to="https://store.fluxinc.ca/cart/product/DP2"} Purchase DP2 ($750 USD) :: :: ## The Paper Problem in Medical Imaging One of the consequences of implementing a PACS is that everything has to be sent there. This has produced a world of patchwork solutions that often involve generating paper records for the sole purpose of digitizing them back into electronic form. I truly can't think of a greater offense to the purpose of electronic health records than to make them complicit in the needless use of paper. Not to mention the tragedy of entire human working lives spent scanning things that have just come out of a printer. ## Attaching Documents to PACS Efficiently **DICOM Printer 2** was originally designed to address this problem. The XML-based configuration, regular expression matching, plug-in interfaces and capability to operate according to data-driven logic gives it a natural ability to fit into whatever part of patient workflows are most wasteful of human time. ::TwoColumn #left ### Traditional Workflow 1. A document is generated (fax, BMD, transcribed report, etc.) 2. The document is printed to paper 3. The document is prepared into a scanning batch 4. Staff manually upload and link to patient records 5. The document arrives in PACS for storage #right ### Automated Workflow with DP2 1. A document is generated 2. **DP2 automatically reads patient and study information** 3. **DP2 queries PACS/Worklist and associates records** 4. The document arrives in PACS *No paper, no manual handling, same result in PACS* :: ## Sample Configuration ```xml ... Accession: (.*)$ Modality: (.*)$ DICOMPRINTER2 DVT localhost 104 CONQUESTSRV1 192.168.0.41 5678 ``` ## Understanding the Configuration The configuration above might seem complex, but it's composed of just a few key components: ### 1. Parse Document Content ```xml twoslash Accession: (.*)$ Modality: (.*)$ ``` ```ts twoslash // @filename: config.xml // @highlight: 3-4 Accession: (.*)$ Modality: (.*)$ ``` This action reads the printed document's text content, looking for accession numbers and modality values using regular expressions. The matched values are stored in DICOM tags for later use. ### 2. Query PACS/Worklist The Query action searches PACS or modality worklist for patient studies matching the extracted values, allowing automatic association. ### 3. Store Document in PACS Once the matching study is found, the document is automatically converted to DICOM and stored in the PACS system. ## Benefits of Automation ::EmphasisBox - **Eliminate Paper Waste**: No more printing documents just to scan them - **Save Staff Time**: Remove manual handling and data entry - **Reduce Errors**: Automatic matching prevents incorrect associations - **Faster Processing**: Documents arrive in PACS immediately, improving clinical workflows :: ::WarningBox Need help with your specific workflow? Our DICOM specialists can help customize DICOM Printer 2 for your unique requirements. [Contact us](/contact) for personalized assistance. :: ::ProseButtonGroup{class="justify-between"} ::ProseButton{to="/posts/adding-a-logo-to-dicom-printer-2-output" class="hidden md:inline-flex"} ← Adding a Logo to DICOM Printer 2 Output :: ::ProseButton{to="/posts/adding-a-logo-to-dicom-printer-2-output" class="md:hidden"} ← Previous :: ::ProseButton{to="/posts/multiple-pacs-and-print-destinations-using-dicom-printer-2" variant="primary" class="hidden md:inline-flex"} Multiple PACS and Print Destinations → :: ::ProseButton{to="/posts/multiple-pacs-and-print-destinations-using-dicom-printer-2" variant="primary" class="md:hidden"} Next → :: :: ::ProseButtonGroup ::ProseButton{to="/medical/dicom-printer"} See Also: Which DICOM Printer Do I Need? :: ::ProseButton{to="/medical/dicom-printer-2"} Product Overview :: :: ## Related Resources - [DICOM Printer 2 Overview](/medical/dicom-printer-2) - [Adding a Logo to DICOM Printer 2 Output](/posts/adding-a-logo-to-dicom-printer-2-output) - [Which DICOM Printer Do I Need?](/medical/dicom-printer) --- URL: https://fluxinc.co/posts/dicom-routing-using-capacitor --- title: 'DICOM Routing using Capacitor' description: 'Conditional routing and compression to multiple PACS using Flux Capacitor' date: '2024-05-25' keywords: DICOM routing, DICOM Capacitor, SOP Class routing, JPEG2000 compression, PACS integration, DICOM SR, store and forward --- # DICOM Routing using Capacitor ::InfoBox DICOM Capacitor is a store-and-forward DICOM router, and conditional routing is among the simplest of its many features. This tutorial will show you how to set up Capacitor to receive studies from any modality, compress images for a primary PACS, and re-route DICOM SR instances to a secondary PACS. :: ::ProseButtonGroup ::ProseButton{to="https://store.fluxinc.ca/files/DCP/latest" variant="primary"} Download Capacitor Trial :: ::ProseButton{to="https://store.fluxinc.ca/cart/product/Capacitor"} Purchase Capacitor :: :: ## Getting Started To begin, collect information about our PACS systems. For this example, we have gathered the following: | **PACS System** | **AE Title** | **IP Address** | **Port** | **Preferred Transfer Syntax** | |:------------------ |:------------:|:--------------:|:--------:|:-----------------------------:| | **Primary PACS** | IMAGEPACS | 192.168.1.200 | 104 | JPEG 2000 Lossless | | **Secondary PACS** | REPORTPACS | 192.168.1.201 | 104 | Any | Now we're ready to install. ## Install Capacitor 1. Click this link to download the latest evaluation of DICOM Capacitor: [Download DICOM Capacitor](https://store.fluxinc.ca/files) 2. Run the installer and complete the installation process. 3. Once finished, open **DICOM Capacitor Control** using your start menu, and, if needed, follow the prompts to obtain an evaluation license. 4. Start, **and then stop**, the "DICOM Capacitor" service using either the Control applet, the Windows Services snap-in, or by running the following commands: ```bash $ net start DICOMCapacitorService $ net stop DICOMCapacitorService ``` Close DICOM Capacitor Control if it's still open because all further steps will be performed outside the user interface. ## Configure Capacitor ::EmphasisBox All Capacitor configuration files live in the `%ProgramData%\Flux Inc\DICOM Capacitor` folder. Here are the three files we will be editing: * **config.yml**, which defines Capacitor's operational settings * **nodes.yml**, which defines all destination (and source) nodes * **routings.yml**, which defines the routing rules :: ### Set Capacitor Defaults 1. Open `config.yml` in your YAML text editor — we recommend Atom, or Visual Studio Code. 2. Confirm the value of `scpPort`: ```yaml scpPort: 1040 ``` 3. Turn on the routing module by adding "`route`" to the `filters` setting: ```yaml filters: route ``` 4. Finally, save and close config.yml. ### Define the Two Nodes Next, we define our destination nodes. 1. First, open `nodes.yml` in your YAML text editor. 2. Replace the contents of `nodes.yml` with: ```yaml # Primary PACS - NodeRole: Storage AeTitle: IMAGEPACS HostName: 192.168.1.200 Impersonate: true Port: 104 TransferSyntax: JPEG2000Lossless MinimumLineSpeed: 500 # Secondary PACS - NodeRole: Storage AeTitle: REPORTPACS HostName: 192.168.1.201 Impersonate: true Port: 104 MinimumLineSpeed: 500 ``` ::WarningBox According to this node definition file, Capacitor will: * Listen for C-ECHO and C-STORE associations on port 1040. * Respond and automatically route to AE titles IMAGEPACS and REPORTPACS¹. * Compress all instances bound for IMAGEPACS to JPEG 2000 Lossless. * *Impersonate*, i.e., use the sending modality's own AE title, when forwarding to these destinations. ¹ *Capacitor will also respond to DCP_IMAGEPACS, and DCP_REPORTPACS in the same way.* :: All that remains is for us to configure our routing rules. ### Define DICOM Routing Rules All route definitions live in a file called `routings.yml`. 1. Create `routings.yml` if it does not already exist, and open it in your YAML editor. 2. Paste in the following content and save the file: ```yaml --- - AeTitles: - IMAGEPACS Conditions: - Tag: 0008,0016 MatchExpression: ^1\.2\.840\.10008\.5\.1\.4\.1\.1\.88\.[\d]{1,2}$ Actions: - Description: Re-route to REPORTPACS Type: add_destination Target: REPORTPACS RemoveOriginal: true ``` This definition tells Capacitor's routing module to: * Consider only instances bound for IMAGEPACS * Determine if the SOP Class UID (0008,0016) matches the regular expression `^1.2.840.10008.5.1.4.1.1.88.[\d]{1,2}$`, which matches all DICOM SR types * If so, then add the destination REPORTPACS, which is defined in our nodes.yml file, and * Remove the original route for this instance We're ready to test. ## Start Capacitor and Inspect the Logs 1. Start the **DICOM Capacitor** service using the Windows Services snap-in, or: ```bash $ net start DICOMCapacitorService ``` 2. Next, open and inspect `%ProgramData%\Flux Inc\DICOM Capacitor\logs\capacitor_service.log` The last few lines in this log should confirm that Capacitor is running and accepting connections on behalf of our two nodes.
CT Scanner
MRI Scanner
SR Producer
→
Flux DICOM Capacitor
→
IMAGEPACS images, JP2K compressed
REPORTPACS DICOM SR reports
::ContentBox{bgColor="primary" bgShade="900" borderColor="primary" borderShade="500" shadow=true} ## Need Help? Comment below with any questions, and don't hesitate to reach out for our help! ::ProseButton{to="/contact" variant="primary"} Contact Technical Support :: :: ::ProseButtonGroup{class="justify-between"} ::ProseButton{to="/posts/multiple-pacs-and-print-destinations-using-dicom-printer-2" class="hidden md:inline-flex"} ← Multiple PACS and Print Destinations :: ::ProseButton{to="/posts/multiple-pacs-and-print-destinations-using-dicom-printer-2" class="md:hidden"} ← Previous :: :: ::ProseButtonGroup ::ProseButton{to="/medical/dicom-capacitor"} Product Overview :: ::ProseButton{to="/medical/dicom-printer"} See Also: Which DICOM Printer Do I Need? :: :: --- URL: https://fluxinc.co/posts/multiple-pacs-and-print-destinations-using-dicom-printer-2 --- title: 'Multiple PACS and Print Destinations using DICOM Printer 2' description: 'Learn how to configure DICOM Printer 2 to send documents to multiple PACS systems and print destinations' date: '2023-06-15' keywords: multi-destination DICOM, multiple PACS, DICOM routing, DICOM Printer 2, document distribution, medical imaging workflow, XML configuration --- # Multiple PACS and Print Destinations using DICOM Printer 2 ::InfoBox Configure DICOM Printer 2 to handle multiple destination targets. Need help with your specific workflow? [Contact our team](/contact). :: ::ProseButtonGroup ::ProseButton{to="https://store.fluxinc.ca/files/DP2/latest" variant="primary"} Download DICOM Printer 2 Trial :: ::ProseButton{to="https://store.fluxinc.ca/cart/product/DP2"} Purchase DP2 ($750 USD) :: :: ## Introduction Healthcare facilities often need to send documents to multiple PACS systems and print destinations. This guide shows you how to configure DICOM Printer 2 to offer users destination choices at print time. When you finish this setup, you'll be able to: - Print a document to DICOM Printer 2 - Choose from multiple destinations (2 PACS systems and 1 Dry Imager) - Let DICOM Printer handle the document based on your selection ::WarningBox DICOM Printer is a print-to-PACS product. If you need a store-forward multi-destination PACS router, use [DICOM Capacitor](/medical/dicom-capacitor) instead. :: ## Getting Started If you're new to DP2 configuration, read our [guide on automating storage to PACS](/posts/automating-dicom-printer-2) first. It covers basic DP2 configuration, `` components, and the `` block. ## Configuration Overview We'll enhance the basic configuration by: 1. Adding multiple `` actions for different PACS destinations 2. Adding a `` action for printing to film 3. Creating a `` action to show destination options 4. Adding conditional logic to process user selections ## Step 1: Set Up Multiple PACS Destinations First, modify your configuration to include multiple PACS destinations: ```xml CONQUESTSRV1 192.168.0.41 5678 DICOM_PRINTER CONQUESTSRV2 192.168.0.42 104 ``` Changes made: - Renamed the original `Store` action to `StoreToPrimary` for clarity - Added a second `` action with different connection parameters - Added a `` element to specify the AE title for the second PACS ## Step 2: Add Print Destination Next, add a print destination for the dry imager: ```xml Grayscale12 254 x 254 DICOM_PRINTER DRIPIX 192.168.0.43 5040 ``` This connects to a printer at 192.168.0.43 on port 5040 using the AE title DRYPIX. Setting the resolution to 254 DPI helps ensure true-size image reproduction. ## Step 3: Set Up User Selection Since DP2 doesn't have variables, we'll use a private DICOM tag to store user choices: ```xml ``` Then add a `` action to show destination options: ```xml plugins/GeneralSelectPlugin.exe 60000 Select Report Destination|Primary PACS|Secondary PACS|Dry Imager ``` This configuration: - Uses GeneralSelectPlugin.exe to show a dialog box - Gives users 60 seconds to choose an option - Offers three choices: "Primary PACS," "Secondary PACS," and "Dry Imager" - Stores the selection in our private tag ## Step 4: Build the Workflow Logic Now assemble these actions into a workflow: ```xml ``` The workflow follows this sequence: 1. Initialize the destination tag 2. Show destination options to the user 3. Check if printing to film is requested 4. For PACS destinations, parse the file and query the worklist 5. Based on user selection, store to the Primary and/or Secondary PACS The `\*Primary\*` syntax uses wildcard matching to detect if "Primary" appears in the selection. ## Setting Up the Plug-In Launcher ::WarningBox DICOM Printer 2 runs as a system service and cannot display UI elements directly. You must run the Plug-In Launcher for the interactive features to work. :: To ensure proper operation: 1. Set Plug-In Launcher to start on user login 2. Confirm it's running by checking for its icon in the task tray 3. Find the Plug-In Launcher shortcut in your Start Menu ## Complete Configuration Here's the complete configuration ready to use: ```xml 1 1 20 plugins/GeneralSelectPlugin.exe 60000 Select Report Destination|Primary PACS|Secondary PACS|Dry Imager ^(.*)\-.*$ ^.*\-(.*)$ DICOMPRINTER2 DVT localhost 104 CONQUESTSRV1 192.168.0.41 5678 DICOM_PRINTER CONQUESTSRV2 192.168.0.42 104 Grayscale12 254 x 254 DICOM_PRINTER DRIPIX 192.168.0.43 5040 ``` ::EmphasisBox ### Benefits - **Flexible Workflow**: Route documents to different PACS systems as needed - **Hybrid Support**: Maintain both digital storage and film output - **User Control**: Let staff choose destinations at print time - **Simplified Process**: Handle multiple output types with a single print action :: ## Related Resources - [Automating DICOM Printer 2](/posts/automating-dicom-printer-2) - [DICOM Routing using Capacitor](/posts/dicom-routing-using-capacitor) - [Which DICOM Printer Do I Need?](/medical/dicom-printer) ::ProseButtonGroup{class="justify-between"} ::ProseButton{to="/posts/automating-dicom-printer-2" class="hidden md:inline-flex"} ← Automating DICOM Printer 2 :: ::ProseButton{to="/posts/automating-dicom-printer-2" class="md:hidden"} ← Previous :: ::ProseButton{to="/posts/dicom-routing-using-capacitor" variant="primary" class="hidden md:inline-flex"} DICOM Routing using Capacitor → :: ::ProseButton{to="/posts/dicom-routing-using-capacitor" variant="primary" class="md:hidden"} Next → :: :: ::ProseButtonGroup ::ProseButton{to="/medical/dicom-printer-2"} Product Overview :: ::ProseButton{to="/medical/dicom-printer"} See Also: Which DICOM Printer Do I Need? :: :: --- URL: https://fluxinc.co/posts/printing-to-film-using-dicom-printer-2 --- title: 'Printing to Film Using DICOM Printer 2' description: 'Learn how to print true-size dental X-rays to DICOM film printers using DICOM Printer 2' date: '2023-06-10' keywords: DICOM film printing, dental X-rays, true-size printing, DICOM Printer 2, AGFA DRYSTAR, medical imaging, radiology printing --- # Printing to Film Using DICOM Printer 2 ::InfoBox This is the first in a series of guides explaining how to use DICOM Printer 2. While it's a powerful and complex tool, some of its most popular applications are quite straightforward. This guide focuses on one of the most common use cases: printing to film. :: ## Goal > To print true-size images of dental X-rays, with a facility logo in the corner of the film. We're looking to create output like this: ::FullWidthSection{contentClass="text-center"} ![Ceph image printed with DICOM Printer 2](/images/posts/ceph-image-printed.jpg) :: Note that: 1. There is a logo at the top left 2. Patient information is displayed at the top right 3. Clinic information appears at the bottom This tutorial will walk you through the basic steps required to output the image. We'll cover adding logos and patient demographics in the [next article in this series](/posts/adding-a-logo-to-dicom-printer-2-output). ## Details **Source application:** Dental imaging software such as DBSWIN or SIDEXIS **Destination:** AGFA Drystar 5302 (or any other DICOM Print SCP device) ## Setup Process ### Step 1: Install DICOM Printer 2 First, download and install DICOM Printer 2 from our [downloads](https://store.fluxinc.ca/files). The installation process is straightforward: 1. Run the installer and follow the on-screen instructions 2. When prompted, enter your DICOM Print SCP device details: - IP Address - AE Title - Port (usually 104) ### Step 2: Configure Print Settings After installation, you'll need to configure the print settings: ::FullWidthSection{contentClass="text-center"} ![DICOM Printer 2 Configuration](/images/posts/dicom-printer-config.png) :: 1. Open the DICOM Printer 2 configuration utility 2. Navigate to the Print Settings tab 3. Select the appropriate film size for your printer (e.g., 8×10, 11×14) 4. Set the image layout and orientation based on your requirements ::WarningBox Always ensure you select the correct film size in the print dialog. Using the wrong size can result in distorted images or wasted film. :: ### Step 3: Print Your First Document You're now ready to print: ::FullWidthSection{contentClass="text-center"} ![Print Dialog with DICOM Printer 2 selected](/images/posts/print-dialog.png) :: 1. Launch your dental imaging application 2. Open the X-ray image you want to print 3. Select **Print** from your application's menu 4. In the print dialog, select **DICOM Printer 2** as your printer 5. Choose the appropriate film size ::FullWidthSection{contentClass="text-center"} ![Film Size Selection Dialog](/images/posts/film-size-selection.png) :: 6. Click Print ::EmphasisBox ### Need to add your logo and clinic information? Continue to our [next guide on adding logos and facility information](/posts/adding-a-logo-to-dicom-printer-2-output) to customize your film output. ::ProseButton{to="/posts/adding-a-logo-to-dicom-printer-2-output" variant="primary"} Continue to Part 2: Adding a Logo :: :: ## Troubleshooting If you encounter an "Association Request Failed" error, this typically indicates that your connection parameters are incorrect or your film printer is offline. Verify that: 1. The IP Address is correct 2. The AE Titles match exactly (they are case-sensitive) 3. The port number is correct (usually 104) 4. The film printer is powered on and connected to the network If you continue to experience issues, please [contact our support team](/contact) for assistance. ::ProseButtonGroup{class="justify-between"} ::ProseButton{to="/posts/adding-a-logo-to-dicom-printer-2-output" variant="primary" class="hidden md:inline-flex"} Adding a Logo to DICOM Printer 2 Output → :: ::ProseButton{to="/posts/adding-a-logo-to-dicom-printer-2-output" variant="primary" class="md:hidden"} Next → :: :: ::ProseButtonGroup ::ProseButton{to="/medical/dicom-printer-2"} Product Overview :: ::ProseButton{to="/posts/automating-dicom-printer-2"} See Also: Automating DICOM Printer 2 :: :: --- URL: https://fluxinc.co/posts/public-test-dicom-modality-worklist --- title: Public Test DICOM Modality Worklist description: Free public DICOM Modality Worklist (MWL) server for testing and development of DICOM applications and workflows keywords: DICOM worklist, modality worklist, MWL testing, DICOM development, test server, connectivity testing, DICOM integration date: '2023-04-10' --- # Public Test DICOM Modality Worklist ::FullWidthSection{background="light" padding="md"} # Free Test DICOM Modality Worklist Server Our public DMWL server lets you test your DICOM systems against a reliable modality worklist without complex setup. Perfect for testing, development, and troubleshooting worklist integrations. :: ## What is DICOM Modality Worklist? DICOM Modality Worklist (DMWL) is a critical component of medical imaging workflows that allows imaging modalities (CT, MRI, ultrasound, etc.) to query patient demographic and scheduling information from information systems like RIS (Radiology Information System) or HIS (Hospital Information System). Key benefits include: - Elimination of manual data entry errors - Improved workflow efficiency - Consistent patient identification across systems - Proper study attribution and linking ## Our Public Test Server Flux's public DICOM Modality Worklist server provides: ::TwoColumn #left ### Features - Always-on availability - Pre-populated with test patients - Standard DICOM query/retrieve support - Real-world workflow simulation - No registration or setup required - Regular updates with fresh test data #right ### Technical Details - AE Title: `FLUX_WORKLIST` - IP: `worklist.fluxinc.ca` - Port: `1070` - Connection: Unencrypted (for testing only) - Supported SOP Classes: Modality Worklist Information Model :: ## How to Use the Test Server 1. Configure your DICOM modality or testing application to query the worklist 2. Use the connection parameters listed above 3. Send a C-FIND request to retrieve worklist entries 4. Test your system's ability to process and display worklist data ::ContentBox{type="warning"} This server is for testing purposes only and contains fictional patient data. Do not use for clinical purposes or with real patient information. :: ## Example Query Results When querying our test worklist, you'll receive standardized responses containing: - Patient Name, ID, and demographics - Scheduled Procedure Step information - Accession numbers - Referring physician details - Requested procedure descriptions These test entries allow you to simulate various clinical scenarios and workflow situations. ## Integration Examples ::ProseList{type="success"} - Testing new modality installations before connecting to production systems - Developing DICOM applications that need worklist functionality - Troubleshooting connectivity issues with existing worklist clients - Training technologists on worklist interaction - Validating system updates or patches affecting worklist functionality :: ::FullWidthSection{class="bg-primary-500/10 py-8"} ### Related Resources Enhance your integration with these additional tools and resources: - [DICOM Capacitor for worklist caching and enhancement](/case-studies/medical/worklist) - [TuPACS for document integration with DICOM worklists](/medical/tupacs) - [DICOM Printer 2 for advanced worklist integration](/medical/dicom-printer-2) :: ::ProseButtonGroup ::ProseButton{to="/contact" variant="primary"} Contact Support :: ::ProseButton{to="https://fluxinc.co/public-test-dicom-modality-worklist/" variant="secondary" external="true"} Visit Worklist Server Page :: :: --- URL: https://fluxinc.co/secure-ai/phi-gateway --- title: Phi Gateway | The AI Gateway for Protected Health Data | Flux Inc description: Phi Gateway is the AI gateway for protected health data. One OpenAI-compatible API for every model — policy, routing, credential isolation, and audit enforced at the wire. keywords: Phi Gateway, PHI, healthcare AI, AI gateway, LLM gateway, protected health information, OpenAI-compatible API, MGL, cllama sitemap: changefreq: monthly head: meta: - name: 'og:title' content: 'Phi Gateway — The AI Gateway for Protected Health Data' - name: 'og:description' content: 'One OpenAI-compatible API. Every model. Policy, routing, credentials, and audit at the wire — before traffic leaves your boundary.' - name: 'og:type' content: 'product' - name: 'twitter:card' content: 'summary_large_image' - name: 'twitter:title' content: 'Phi Gateway — The AI Gateway for Protected Health Data' - name: 'twitter:description' content: 'The AI gateway for protected health data. Policy at the wire. Audit by default.' - name: 'canonical' content: 'https://fluxinc.co/secure-ai/phi-gateway' --- ::FullWidthSection{variant="gradient" padding="sm" className="bg-transparent" patternOverlay="true" gradientColor="sky-800" gradientColorTwo="teal-600"} # Phi Gateway ::RotatingText{items="Many models. One API.|Policy at the wire.|Audit by default.|Built for PHI." tag="p" rootClass="text-xl text-white md:text-2xl"} :: ::ProseButtonGroup ::ProseButton{to="/contact?product=PhiGateway&interest=early_access" variant="outlineInvert"} Request Early Access :: ::ProseButton{to="/contact?product=PhiGateway&interest=schedule_demo" variant="outline"} Schedule Demo :: :: :: The AI gateway for protected health data. For developers, one OpenAI-compatible base URL — no SDK rewrite, no provider keys in the application. For IT and compliance, a control point at the wire where every request is identified, policy-checked, credential-isolated, and recorded before it leaves your boundary. ## Drop in and route Phi Gateway speaks the OpenAI API. The application changes one line. The gateway handles identity, policy, provider keys, and audit. ```python from openai import OpenAI # Same SDK. New base URL. No provider keys in the app. client = OpenAI( base_url="https://phi.your-hospital.internal/v1", api_key="agent:abc123...", # identity token issued by Phi Gateway ) response = client.chat.completions.create( model="anthropic/claude-sonnet-4", # provider/model — any route policy allows messages=[ {"role": "user", "content": "Summarize the findings in this report."} ], ) ``` Address any model as `provider/model` — `openai/gpt-4o`, `anthropic/claude-sonnet-4`, `google/gemini-2.0-pro`, `local/llama-3-70b`. Phi Gateway resolves the route, swaps in the real provider credential, forwards the request, and records the transaction. The application never holds a provider key. ## How a request flows
01
Identify
Resolve caller identity from the bearer token. Establish which organization, role, and policy apply to this request.
02
Police
Apply per-role policy from Model Governance Layer: which prompts, tools, data classes, and routes are allowed.
03
Route
Swap the identity token for the real provider credential. Forward to the allowed upstream — BAA cloud, private cloud, or local LLM.
04
Record
Log the transaction at the boundary: caller, route, model, decision, latency, tokens, cost. Independent of the model. Suitable for compliance review.
The four mechanisms — policy, routing, credential isolation, audit — are not features layered on. They are the four phases of every request, enforced at the infrastructure boundary on the way out and on the way back. ## Cloud or on-prem Same API surface, same SDK, two deployment shapes. ::TwoColumn #left ### Phi Cloud Flux-hosted. One endpoint, BAA with Flux, customer or Flux-pooled provider keys. Built for evaluation, early deployments, and mid-size practices that want the control plane without operating it. #right ### Phi On-Prem Customer-deployed. Docker image, OVA, or Windows installer. Customer keys, customer perimeter, customer-chosen routes including local LLMs. Built for hospitals, IDNs, regulated enterprises, and air-gapped sites where the trust boundary cannot move outside the network. :: ::ProseButtonGroup ::ProseButton{to="/contact?product=PhiGateway&deployment=cloud" variant="primary"} Discuss Phi Cloud :: ::ProseButton{to="/contact?product=PhiGateway&deployment=on_prem" variant="outline"} Discuss Phi On-Prem :: :: ## Phi Vault The local store inside your perimeter — provider keys, identity tokens, the audit ledger, and optional de-identification mappings for workloads where reversible tokenization is sound. Ships with Phi On-Prem. ::WarningBox Not a magical PHI scrubber. Reversible tokenization works for structured extraction, classification, and controlled-schema report transforms where the model preserves tokens. Free-form chat that paraphrases or invents identifiers is out of scope. The vault is credible because its scope is explicit. :: ## For developers ::TwoColumn #left ### Drop-in compatibility The OpenAI SDK works unchanged. Existing clients, agent frameworks, and internal tools point at one new base URL. Model strings move from `gpt-4o` to `openai/gpt-4o` so the gateway can route. ### No provider keys in the application Phi Gateway issues identity tokens scoped to your agent or service. Real provider keys live at the gateway. A compromised client has nothing to leak — its token is useful only inside the boundary. #right ### Audit and cost for free Every request is logged with caller, model, tokens, latency, and cost. Operator dashboards surface spend per agent and per provider. The same JSON feeds external SIEMs, billing systems, and the MGL fleet view. ### Same shape as the open standard Phi Gateway is built on the [cllama](/ai/cllama) credential-starvation proxy. The wire protocol, identity model, and audit log shape are the public cllama specification — applications built against Phi Gateway run against any cllama-compatible proxy. :: ## For IT and compliance ::TwoColumn #left ### Policy at the infrastructure layer Per-organization and per-role rules authored in [Model Governance Layer](/medical/model-governance-layer). Policy is enforced by infrastructure, not prompt — a billing workflow and a radiology assistant do not share permissions. ### Audit-ready evidence Caller, route, model, decision, latency, tokens, and cost recorded for every request. Append-only, independent of the model, suitable for HIPAA, PHIPA, or GDPR special-category review. #right ### BAA path or your perimeter Phi Cloud carries a BAA with Flux. Phi On-Prem keeps Flux out of the data path entirely — the gateway, the keys, the ledger, and the de-identification mappings all live inside your network. ### Deployment forms you already operate Docker container, OVA appliance, or Windows installer — the same packaging pattern used by the rest of the Flux medical fleet. No bespoke runtime, no proprietary orchestrator. :: ::EmphasisBox ## Govern every LLM call before it leaves ::ProseButtonGroup ::ProseButton{to="/contact?product=PhiGateway&interest=early_access" variant="primary"} Request Early Access :: ::ProseButton{to="/contact?product=PhiGateway&interest=schedule_demo" variant="outline"} Schedule Demo :: ::ProseButton{to="/medical/model-governance-layer" variant="outline"} See the Governance Layer :: :: ::