06Jul
Why are SNOMED CT codes (Identifiers) meaningless numbers? — SNOMED CT Intro Part 3
As a team of terminology and informatics experts supporting legacy systems (and their migration), we often come [...]
Countries
4+
Products created
10+
Consultancy projects
25+
Combined experience
70+As a team of former-clinicians (doctors, nurses, etc) and software engineers, we are passionate about the role of informatics in successful adoption of technology in healthcare. We have decades of experience of working in various commercial organisations and national programmes across the globe.
We have decades of involvement in interoperability standards - covering terminologies (SNOMED CT), messaging (FHIR) and openEHR. We bring experience supporting of healthcare standards, enabling our clients to derive their benefits.
We have expertise in managing national reference terminologies, refsets/subsets and associated mappings. We support their implementation, having been involved in various national healthcare IT programs.
We have successfully delivered Agile projects, working closely with clients in integrated teams of clinicians, analysts, architects and software developers. We ensure that your standards requirements are incorporated in your products.
You can contact us by clicking on the contact us button below and filling in your details and we'll get in touch soon!
Keep scrolling to learn more about our Software Engineering team, some of past projects and more…
We design and create healthcare software that is used in live systems. We can build your next-gen system based on healthcare standards from scalable enterprise software to mobile apps. We work with clients in the NHS and across the UK to create software that solves clinical problems.
We support the use of SNOMED CT terminology server APIs, consuming FHIR based data, dynamic mapping, generating dashboards and other analytics functionality in your applications.
As a team of terminology and informatics experts supporting legacy systems (and their migration), we often come [...]
So earlier today I was migrating some of our older projects to a newer version and I encountered this [...]
Continuing from the SNOMED CT: An Introduction — Part 1 article, let’s now talk about how SNOMED [...]