Saga IT

0 reviews

Saga IT is a US-based healthcare IT consulting and software development firm headquartered in West Palm Beach, FL, serving hospitals, medical device manufacturers, payers, and digital health companies since 2016. We specialize in healthcare interoperability and HIPAA-compliant software engineering: • Healthcare integration — HL7 v2 interfaces, FHIR R4 APIs, SMART on FHIR apps, CDS Hooks, FHIRcast, DICOM medical imaging, and X12 EDI • EHR integration — Epic (App Orchard / Showroom), Oracle Health (Cerner), athenahealth, MEDITECH, Veradigm (Allscripts), and eClinicalWorks • Integration engine work — Mirth Connect, Open Integration Engine (OIE), and Rhapsody implementation, migration, and managed services • Custom healthcare software — SaMD development under IEC 62304 and ISO 14971, HIPAA-compliant cloud builds on AWS and Azure, and patient-facing apps and platforms • Compliance — HIPAA programs, HITRUST CSF, SOC 2 Type II, and FDA pathway support for medical device software Saga also builds and contributes open-source tools for the healthcare integration community, including MirthSync (Git-based version control for Mirth Connect channels), the HL7 Workbench browser parser, and a free in-browser DICOM Viewer. We are an independent commercial support vendor in the Open Integration Engine (OIE) ecosystem. Our team operates as a flexible, expert-led extension of in-house engineering, regulatory, and IT teams — US-based, integration-first, with deep healthcare domain knowledge.

MirthSync

0 reviews

Interface configuration usually lives in one place: inside the engine's own database. That makes it hard to review, hard to promote between environments and hard to recover. MirthSync is an open-source command-line tool that pulls channels, code templates, the configuration map and global scripts out of a Mirth Connect or Open Integration Engine instance as plain files, and pushes them back. Once interfaces are files, they go in Git: changes show up in pull requests, a promotion from dev to test to prod is a deploy rather than a manual re-import, and a broken channel can be rolled back to a known-good commit. It runs anywhere Java runs, works against open-source Mirth Connect, Eclipse Open Integration Engine and BridgeLink, and is licensed under EPL-1.0. Built and maintained by Saga IT, a healthcare integration consultancy.

Clinical Extract

0 reviews

Clinical Extract pulls research data from any EHR with a certified bulk FHIR API: Epic, Oracle Health (Cerner), athenahealth, eClinicalWorks, MEDITECH, NextGen and Veradigm. It runs inside your environment as a SMART Backend Services client with read-only scopes, exports only the study cohort through a Group $export, and turns the NDJSON into one analysis-ready CSV with a data dictionary that names the FHIR element behind every column. Patient data never leaves your environment. It is built for cancer and clinical registries (coded case and abstraction fields in the NAACCR layout), research informatics teams and honest brokers (study-scoped pulls with an IRB-ready data dictionary), and research sites (clinical trial feasibility counts from coded criteria). Features include a cohort builder, roster pull with FHIR $match, the CSV and data dictionary, and an oncology lens that delivers biomarkers and TNM stage as named columns.

Kymolog

0 reviews

Kymolog™ is medical device integration and research analytics on the same data. An edge agent beside the devices picks up each reading as the device reports it and writes it as an HL7 FHIR R4 Observation with a LOINC code, a UCUM unit, the device (down to its serial number and UDI) and the time of measurement. Kymolog matches the reading to the patient and encounter by bed and files it in the EHR the hospital already runs: Epic, Oracle Health (Cerner), MEDITECH, athenahealth, eClinicalWorks, NextGen or Veradigm, over FHIR R4 or HL7 v2. The same coded record is kept for research with its device, time, patient and encounter, so a study dataset traces every value to its source. Kymolog reads continuous glucose monitors, ECG monitors, blood pressure cuffs, thermometers and pulse oximeters, and any other device class joins by configuration. The install runs on premises or in its operator's own cloud: a hospital's, or a device maker's when the maker runs it for its hospital customers. The research store runs beside the install or in our cloud, which only receives de-identified readings. An optional data network adds consent, de-identification, dataset licensing and royalties to contributing sites. Kymolog is built for hospitals that want device readings in the chart, device makers who need real-world evidence for post-market surveillance and PMCF, hospital and academic researchers, and trial sponsors running wearables in studies. Request a demo at https://kymolog.com/demo