Cardio
Suite
For research use only
Seven modules · One integrated workflow
mqDiagnostic
Cardiovascular analysis combining deterministic rule-based detection with neural-network classification — delivering ECG and echocardiography analysis with transparent, explainable reasoning that researchers and professionals can inspect and validate.
- 01Hybrid inference
- 02Explainable
- 03Real-time
- 04Reviewed
mqTherapy
Guideline-based therapy models generated by combining cardiovascular domain rules with language-model reasoning — derived from a research subject's profile: analysis results, biomarkers, vitals, and echocardiography. Each model covers medication, nutrition, and exercise as a structured FHIR R4 Bundle for researcher review and system integration.
- 01Output
- 02Personalised
- 03Guideline-based
- 04Holistic
mqData
Secure, sovereign data storage. Retain patient records, biosignals, and diagnostic outputs with configurable retention periods, storage capacity, and data residency region — built for regulatory compliance from day one.
- 01Secure
- 02Retention
- 03Capacity
- 04Region
mqPrompt
A language-model assistant embedded directly in the mQ-up suite, grounded in the platform's domain rules and structured data. Ask about ECG findings, therapy models, research workflows, or cardiovascular physiology — in plain language.
- 01Contextual
- 02Multi-provider
- 03Configurable
- 04Private
mqConsult
A guided research workflow tool combining structured cardiovascular domain rules with language-model reasoning — carrying research subjects from data intake to therapy modelling, step by step.
- 01Guided
- 02Rules + model
- 03Adaptive
- 04Integrated
mqGenerator
Synthetic medical data generation for research, training, and system validation. Produce physiologically accurate ECG signals, echocardiography studies, and patient-specific 3D heart models at scale — without compromising patient privacy.
- 01Synthesis
- 02Parametric
- 03Scale
- 04Standards
mqHub
The integration layer that connects the entire suite. mqHub bridges cloud storage, databases, local filesystems, and LLM/SLM APIs — so every module can ingest data, route outputs, and integrate with existing eHealth ecosystems without custom connectors.
- 01Cloud & local
- 02LLM / SLM APIs
- 03In · Out · InOut
- 04FHIR & HL7