03
Oct
Yoctobe Featured in Liverpool’s ‘Ones to Watch’ Business Roundtable
We're proud to share that Yoctobe was recently featured in a high-profile business roundtable hosted by CG Pro...
Articles
31
Mar
SaMD Classification Explained: Navigating EU & UK Regulatory Requirements
Are you developing software for healthcare applications? Understanding SaMD classification is crucial to your ...
14
Sep
Offline-First Hospital Systems for Constrained Networks
In many hospitals the network is not a utility you assume; it is a weather pattern. Clinics lose the uplink during storms, shared microwave links saturate at noon, and power events take the data centre offline while wards keep treating patients. Offline-first design is how custo…
11
Sep
MDR Evidence Packs for SaMD Software Updates
A SaMD release is not finished when the build is green. Under the EU Medical Device Regulation, a software update is either a controlled change with evidence or an uncontrolled drift of the device on the market. Teams that treat patches as “just IT” discover the gap when a notif…
08
Sep
Audit Trails That Survive Scrutiny in Custom Healthcare Software
When a hospital auditor asks who changed a medication order, when they changed it, and why, the answer cannot be a reconstructed story from chat logs. Custom healthcare software either produces an immutable audit trail or it produces theatre. The difference shows up the moment s…
05
Sep
Middleware vs Point-to-Point Device Interfaces
Connecting each analyser or medical device straight to the clinical system feels fastest on the first interface. By the tenth, every firmware upgrade is a mini-project, mappings drift, and nobody can say which message produced a wrong result. Middleware versus point-to-point is …
02
Sep
AIaMD: When Clinical AI Becomes a Medical Device
Not every clinical algorithm is a medical device, and not every “AI feature” in a health app is harmless productivity software. The line is intended use: what the software claims for diagnosis, treatment, prevention, or clinical decisions, and how far users are expected to rely …
30
Aug
Treat FHIR as an Integration Contract, Not a Buzzword
Calling an interface “FHIR” does not make it interoperable. FHIR becomes valuable when it is treated as a deployable contract: agreed profiles, identity rules, terminology bindings, and acknowledgement behaviour that both sides can test before go-live. Without that contract, you…
27
Aug
Custom Healthcare Software: When to Build vs Buy
Build versus buy in healthcare is rarely binary. The real question is which parts of the stack you will own for a decade: roadmap, integrations, regulatory evidence, and the cost of changing course when policy or care models move. Packaged platforms look cheaper on day one. Cust…
24
Aug
IEC 62304 and the SaMD Software Lifecycle
IEC 62304 still tells medical device software teams how to classify safety, control SOUP, and govern change. Early 2026 raised the stakes: FDA’s Quality Management System Regulation (QMSR) is live, and eSTAR filings expect a software story that maps cleanly to design control and…
14
Jul
Promed Health Suite Desktop v5: Offline HIS & LIS from Yoctobe
/* Palette: colors.md — Primary #475569 only */
.ph-wrap {
--ph-primary: #475569;
--ph-secondary: ...
11
Jun
Decoding Healthcare IT: The Real Difference Between EMR and HIS
/* Palette: colors.md — Primary #475569 only */
.ph-wrap {
--ph-primary: #475569;
--ph-secondary: ...
