Medical Connections
- Company typePrivate
- Founded1998
- HeadquartersSwansea, United Kingdom
- Headcount1–10
- GTM typeB2B
- OfferingSoftware
Medical Connections firmographics
Firmographics- Name
- Medical Connections
- Legal name
- Medical Connections Ltd
- Website
- https://medicalconnections.co.uk
- Company type
- Private
- Founded year
- 1998
- Operating status
- Operating
- Headcount range
- 1–10 employees
- Ownership category
- akta.pro rank
Medical Connections industry classification
Industry- Product category
- Medical Imaging Software Development Toolkits
- NAICS
- Software Publishers (5132), Software Publishers (513210), Computer Systems Design and Related Services (54151)
- SIC
- Services-Computer Programming Services (7371), Services-Computer Programming, Data Processing, Etc. (7370)
- akta.pro primary industry
- Imaging & Diagnostic Interoperability (DICOM exchange, image sharing, VNA connectivity) (HLACABAM)
- akta.pro secondary industries
- Image Exchange, Sharing & Patient/Provider Portals (DICOM/Web) (HLACALAI), EHR/EMR Integration & Interoperability Middleware (HL7/FHIR) (HLALAKAD)
Keywords
Where Medical Connections is headquartered
LocationHeadquarters
- HQ city
- Swansea
- HQ country
- United Kingdom
- HQ region
- Europe
Markets served
Medical Connections business model
Business model- GTM type
- B2B
- Offering type
- Software
- Cost components
- Personnel, Technology or R&D, Operations, Marketing or Sales, Infrastructure
Revenue model
- Software Licenses: Medical Connections sells permanent and time-limited software licenses for DicomObjects SDKs. Licenses are machine-specific and activated online or offline using license keys in format like XYZ-1111-2222-3333. Concurrent licensing is available for scenarios requiring multiple simultaneous activations.
- Combined Package Discounts: Discounted packages are available for combined use of DicomObjects and XdsObjects toolkits when purchased together.
Go-to-market motion1 record
Distribution channels1 record
Marketing channels1 record
Medical Connections product offering
Product offeringCore offering
Medical Connections develops and sells software development toolkits (SDKs) for medical imaging interoperability. Its DicomObjects product family (COM, .NET, and .NET Core editions) enables developers to embed DICOM-compliant image display, network transmission, printing, query/retrieve, and storage commitment into healthcare applications. The company also offers XdsObjects for IHE XDS and XDS-I profile-based document and imaging sharing.
Product overview
Medical Connections offers a suite of DICOM software development toolkits under the DicomObjects brand, comprising three editions: DicomObjects.COM (COM/ActiveX), DicomObjects.NET (.NET Framework), and DicomObjects.Core (.NET Core/.NET 5+). These toolkits enable developers to embed DICOM image display, network transmission, printing, and data manipulation capabilities into medical imaging applications. Complementing DicomObjects is XdsObjects.NET, a separate toolkit for IHE XDS (Cross-Enterprise Document Sharing) and XDS-I (Imaging) profile implementations. Together, these products provide a complete development solution for DICOM-compliant medical imaging systems and document sharing infrastructure.
Differentiator
Problem solved
Functional benefit
Brands
- DicomObjects: DICOM software development toolkit supporting COM, .NET, and .NET Core platforms for adding DICOM functionality to software products
- XdsObjects
Products and services
- DicomObjects.COM COM/ActiveX-based DICOM toolkit enabling developers to add DICOM image display, manipulation, network transmission, printing, storage commitment, and normalised operations to their applications. Sold as a developer SDK with machine-specific license keys.
- DicomObjects.NET .NET Framework-based DICOM toolkit (version 8.48) offering comprehensive DICOM image processing, network communications, worklist handling, printing, and storage commitment for Windows .NET developers building medical imaging applications.
- DicomObjects.Core .NET Core/.NET 5+ compatible DICOM toolkit providing image read/write, parsing, and DICOM Web client and server implementations, including RESTful DICOM Web (DICOMweb) support for cross-platform and cloud-ready medical imaging development.
- XdsObjects.NET Toolkit for developing applications that implement IHE XDS (Cross-Enterprise Document Sharing) and XDS-I (Imaging) profiles, providing client and server support for document sharing, registry functionality, and imaging integration across healthcare enterprises.
Companies that use Medical Connections
Customer profileSegments1 record
Ideal customer profiles1 record
Medical Connections technology and API
TechnologyTechnology focussed Yes
API detail
- Has API
- No
- API docs
- API detail
Core technology
AI maturity
App detail
Feature11 records
Medical Connections partnerships and signals
Strategic signalPartnerships
One partnership is on record.
- DicomObjects and XdsObjects IntegrationcoreDicomObjects and XdsObjects are complementary products from Medical Connections. DicomObjects provides DICOM protocol implementation while XdsObjects handles IHE XDS and XDS-I profiles for document and imaging data sharing. Combined packages are available at discounted rates for developers needing both medical imaging (DICOM) and healthcare document interoperability capabilities.
Recent moves4 records
Expansion highlights3 records
Medical Connections competitors and assessment
Company assessmentDirect peers
- DCMTK (OFFIS): OFFIS Institute's DCMTK is the reference open-source C++ DICOM toolkit. It is the closest direct alternative to DicomObjects, providing DICOM protocol libraries for building medical imaging applications, and is the primary free substitute Medical Connections competes against.
- fo-dicom: fo-dicom is the leading open-source .NET DICOM library, mirroring exactly the developer audience and platform (.NET) that DicomObjects targets. It is a direct substitute for medical imaging developers evaluating commercial vs. open-source tooling on .NET.
- LEADTOOLS: LEAD Technologies' LEADTOOLS provides commercial DICOM and medical imaging SDKs across .NET, COM, and web platforms. It targets the same developer-tool buyer, offers overlapping protocol coverage, and is one of the most directly comparable commercial alternatives to DicomObjects.
- Laurel Bridge Software: Laurel Bridge provides DICOM and IHE integration components for imaging workflow, routing, and interoperability. It sells toolkit-style products to imaging application developers and healthcare IT vendors, overlapping the developer/embedder segment served by XdsObjects and DicomObjects.
- Dicom Systems: Dicom Systems builds DICOM routing, interoperability, and imaging workflow solutions. It operates in the same medical imaging interoperability space, with both standalone tools and enterprise offerings that overlap with Medical Connections' DICOM toolkit focus.
- pydicom: pydicom is the dominant open-source Python DICOM library, widely adopted by healthcare data science and imaging AI teams. While it targets a different language ecosystem, it competes for the same underlying DICOM-developer mind share and budget as Medical Connections' toolkits.
Broad incumbents
- Hyland (NilRead / Acuo): Hyland's enterprise imaging portfolio (NilRead viewer and acquired Acuo VNA) sits upstream of Medical Connections' developer-toolkit layer, providing DICOM/HL7/XDS interoperability as part of broader enterprise imaging suites that customers may purchase instead of building with an SDK.
Emerging players
- Google Cloud Healthcare API: Google Cloud's managed DICOM/HL7/FHIR API offers cloud-native interoperability that competes for the same healthcare imaging data sharing use case served by DicomObjects and XdsObjects, but as a hosted service rather than a developer toolkit.
- AWS HealthImaging: Amazon's HealthImaging service provides DICOM imaging storage and APIs in a managed cloud format. It targets healthcare application developers building imaging workflows, partially overlapping Medical Connections' developer-toolkit value proposition with a managed platform alternative.
- Microsoft Azure Health Data Services: Microsoft's DICOM and FHIR services provide managed cloud-based interoperability for medical imaging and health data. They target the same healthcare developer audience as DicomObjects but via cloud APIs, and are a likely long-term substitute for embedded SDK-based interoperability.
Market position
Strengths5 records
Weaknesses5 records
Competitive moat3 records
Key risks5 records
Key highlights6 records
Customer concentration
Medical Connections social profiles
Digital presenceMedical Connections financial estimates
Financial estimateRevenue estimate
Valuation estimate
Medical Connections leadership team
Management profileNumber of profiles
Profiles1 record
Medical Connections funding detail
Funding detailFunding overview
Funding rounds
Investors
Funding detail is available on the Subscription and Enterprise plan.Contact sales →
Medical Connections M&A and investment
M&A and investmentM&A
Investments
M&A and investment is available on the Subscription and Enterprise plan.Contact sales →
Frequently asked questions about Medical Connections
What does Medical Connections do?
Medical Connections develops and sells software development toolkits (SDKs) for medical imaging interoperability. Its DicomObjects product family (COM, .NET, and .NET Core editions) enables developers to embed DICOM-compliant image display, network transmission, printing, query/retrieve, and storage commitment into healthcare applications. The company also offers XdsObjects for IHE XDS and XDS-I profile-based document and imaging sharing.
Is Medical Connections a public or private company?
Medical Connections is a private company. It is classified as founder individual operated bootstrapped and is currently operating.
When was Medical Connections founded?
Medical Connections was founded in 1998. It employs 1 to 10 people.
Where is Medical Connections based?
Medical Connections is headquartered in Swansea, United Kingdom, in the Europe region.
How does Medical Connections make money?
Two revenue lines are on record. Software Licenses are the primary driver. The others are combined Package Discounts.
Who are Medical Connections's main competitors?
Direct peers on record are DCMTK (OFFIS), fo-dicom, LEADTOOLS, Laurel Bridge Software, Dicom Systems and pydicom. Hyland (NilRead / Acuo) is listed as a broad incumbent. Emerging players are Google Cloud Healthcare API, AWS HealthImaging and Microsoft Azure Health Data Services.
Does Medical Connections have an API?
No public API is recorded for Medical Connections.
What industry is Medical Connections in?
Medical Connections's product category is Medical Imaging Software Development Toolkits. Its primary akta.pro industry code is HLACABAM, Imaging & Diagnostic Interoperability (DICOM exchange, image sharing, VNA connectivity), with a secondary code of HLACALAI, Image Exchange, Sharing & Patient/Provider Portals (DICOM/Web). Its NAICS code is 5132 and its SIC code is 7371.