01 · OUTPATIENT CLINICTherapist-led appointment
The PT launches a knee ROM or sit-to-stand protocol from an encounter. A tablet guides capture. After review, numerical measurements and a report are attached to the existing chart.
For EHR vendors · healthcare integrators · care networks
Built to work inside existing care.
MedMeters is designing a protocol-based measurement layer for clinical workflows. Let clinicians order a test from their familiar system, capture a measurement in clinic or at home, compare past visits when permitted, and return a reviewable result to the same patient record.
No new EHRClinic-to-home assessmentsPrivacy-first captureFHIR R4-oriented design
Product architecture proposal. The integrations, certifications, security controls and clinical validation described here are not yet deployed or confirmed.
Use cases
The assessment stays with the clinical encounter.
Three practical ways an existing healthcare provider or software vendor could offer MedMeters without replacing its practice-management or EHR system.
01 · OUTPATIENT CLINIC
02 · HOME FOLLOW-UPPrescribed remote retest
A clinician selects a safe home-capable protocol. The patient follows setup instructions, uploads only permitted data, and sees approved feedback after the professional reviews the comparison.
03 · PLATFORM PARTNEREmbedded white-label measurement
An EHR, telehealth platform or integrator could offer a branded capture component and receive machine-readable results, review status and audit metadata via a contracted interface.
Four integration levels
Start simple. Integrate deeper when the workflow is proven.
MedMeters can follow that principle while accounting for video capture, clinical safety and review.
| Level | How it works | Best initial customer | Proposed output |
|---|---|---|---|
| 1 · Report exportLowest integration effort | Standalone clinician portal; reviewed report exported or attached to EHR using an approved document workflow. | Small clinics, first pilots | PDF + summary CSV/JSON |
| 2 · Contextual launch | Launch app from the patient chart through SMART on FHIR where supported, avoiding duplicate patient selection. | Epic-connected clinics and hospitals | Context-linked draft measurement |
| 3 · Structured exchange | Authorized API or integration engine exchanges assessment status and measurements. FHIR support depends on each partner's implemented resources and permissions. | Enterprise EHR / integration hubs | FHIR R4 Observation; PDF DocumentReference where supported |
| 4 · Embedded SDK / OEM | White-label capture and protocol engine inside a partner product; hosting and data-residency options scoped contractually. | Digital health vendors and resellers | SDK + webhooks + governed data flow |
Important: EHR launch, reading past visits, writing observations and creating a clinical document are separate permissions and endpoints. “FHIR support” alone does not mean that an EHR will allow all four operations. A pilot must test the actual write-back route.
Clinical data flow
Standardized endpoints, not raw video by default.
MedMeters would keep protocol identity, equipment/setting, quality, review state and historical comparability alongside each result. The EHR remains the system of record.
01 / REQUEST
Assign a protocol
Encounter context; ServiceRequest or Task when supported; otherwise a local order reference.
02 / IDENTITY
Map the patient securely
Scoped identifiers and consent; no need to expose the patient's name to the CV measurement engine.
03 / CAPTURE
Check capture quality
Protocol angle, distance, light, body landmarks, safety and exception-specific masking.
04 / RESULT
Return reviewable values
Draft measurement with units, timestamps, model version, source and quality flags.
05 / APPROVAL
Write back after review
Clinician-approved numeric Observations, report document and optional patient explanation.
FHIR R4 resource mapping
- ServiceRequest / Task — selected assessment and work status, when the receiver supports this workflow.
- Observation — coded result, UCUM units, timing, patient/encounter and device/protocol references.
- DiagnosticReport — optional panel/report context where a diagnostic-report workflow is appropriate.
- DocumentReference — approved PDF and authorized supporting media references, if retained.
- Provenance — technical origin, version, identity of the approving professional and transformation history where supported.
Exact codes, patient references, consent, scopes and endpoint permissions are determined per customer and clinical protocol. This is an illustrative data contract, not a working FHIR integration.
Illustrative measurement — NOT A LIVE API
{
"resourceType": "Observation",
"status": "preliminary",
"code": { "text": "Five Times Sit-to-Stand" },
"subject": { "reference": "Patient/example" },
"effectiveDateTime": "2026-10-31T10:00:00Z",
"valueQuantity": {
"value": 13.8, "unit": "s",
"system": "http://unitsofmeasure.org",
"code": "s"
},
"note": [{
"text": "Draft: clinician review required; sample data."
}]
}Partner distribution
Where MedMeters could fit in healthcare software.
Buyer-specific routes, not a claim of an existing commercial relationship. Each vendor requires its own integration, security and partner approvals.
INTEROPERABILITY PARTNER
InterSystems IRIS for Health
FHIR / HL7 v2 translation and API orchestration across enterprise systems. Ideal for a measurement infrastructure component embedded by an integrator.
POST-ACUTE & SENIOR CARE
PointClickCare Marketplace
Care assessment workflows in SNF / long-term care. A candidate for measured mobility and clinician-reviewed Section GG support, not automatic GG coding.
OUTPATIENT REHAB
WebPT & therapy EMRs
Import approved measurement PDFs into the patient chart, then evaluate deeper integrations for ROM, 5xSTS, gait and clinical outcomes.
ENTERPRISE EHR
Epic Vendor Services
SMART on FHIR EHR launch and APIs provide a route to embedded workflows, subject to specific customer implementation and resource support.
AMBULATORY CARE
athenahealth Marketplace
Large outpatient distribution channel. The published partner application currently requires a U.S.-located partner, relevant to company setup.
REHAB · ORTHOPEDICS · NEURO
Other EHR & OEM partners
Potential partner-specific integrations with rehab and specialty systems. Validate each customer journey before building a generic connector.
Proposed sequence
From a clinical pilot to a partner-ready integration.
A phased route to a listing, not a promise of approval.
STEP 1
One protocol + demo
Build one reproducible test and a reproducible sample data package for a sandbox environment.
STEP 2
Integration adapter
Test FHIR R4 exchange through an InterSystems or customer-provided development environment.
STEP 3
Clinical pilot
Assess repeatability, workflow time, clinician acceptance, safety and data-quality failure rates.
STEP 4
Security & legal review
HIPAA BAA readiness, privacy documentation, FDA intended-use review, access controls and audit trails.
STEP 5
Partner submission
Apply through the relevant program, submit the solution and complete their review before claiming a listing.
InterSystems partner directory: Company registration and solution submission are separate steps; the vendor documentation describes draft, approval and published states. Listing is a discovery path, not an assured reseller contract.
Verification
Public documentation behind this integration plan.
Sources are linked so clinical IT teams can independently verify support. The integration proposal is our interpretation, not a vendor-endorsed implementation.
InterSystems — Health Innovation HubOfficial documentation ↗
InterSystems — Company listing and submissionOfficial documentation ↗
InterSystems — FHIR interoperabilityOfficial documentation ↗
Epic — Vendor Services FAQOfficial documentation ↗
WebPT — Integrations and interoperabilityOfficial documentation ↗
PointClickCare — Developer ProgramOfficial documentation ↗
athenahealth — Marketplace PartnersOfficial documentation ↗