Question 1

What standards does ClinicalSpan support?

Accepted Answer

ClinicalSpan supports HL7 v2.1 through v2.8, FHIR R4 output, REST APIs, TCP/MLLP, SFTP, file-based workflows, and database connections. Mapping profiles support HL7-to-HL7 and bidirectional HL7/JSON transformations.

Question 2

Can we keep processing in our own environment?

Accepted Answer

Yes. On-premises deployment runs in your datacenter or private cloud. A hybrid option combines a SaaS control plane with on-premises processing. Review data flows and infrastructure requirements with the team before choosing a deployment.

Question 3

How does ClinicalSpan handle security and PHI?

Accepted Answer

The platform provides encrypted archives, TLS connections, role-based access, audit trails, and configurable PHI retention and scrubbing. Its architecture is described as HIPAA-aligned, with an Enterprise BAA available on request. Discuss your organization's requirements during the security review.

Question 4

Is ClinicalSpan an alternative to Mirth Connect?

Accepted Answer

ClinicalSpan is an option for teams evaluating a different healthcare integration engine. Review your existing channels, transformations, scripts, and deployment requirements with our team to assess migration scope and compatibility.

Question 5

How is ClinicalSpan priced?

Accepted Answer

Contact the team for a quote for your integration scope. Share your interface count, expected message volume, deployment requirements, and support needs. These details help frame the pricing conversation.

Question 6

How long does implementation take?

Accepted Answer

Timing depends on interface complexity, mapping requirements, access to source and destination systems, and testing. A personalized demo is the starting point for discussing your use case and an implementation plan.

HL7 & FHIR integration. Move care forward.