The idea was to create a single, simple place where patients can see all their visit history, and doctors can add details without dealing with clunky hospital systems.
Right now, it's very early, more of a proof of concept, so attachments and some features are still being built. The long-term goal is to give patients control and clarity over their health records, rather than having it locked away in a dozen separate systems.
I live in Germany, and here it’s even harder to get access to your own health data. You go in for a visit, they run a bunch of tests, and unless it’s really urgent, like “you have one month to live” urgent, you basically hear nothing.
There’s no easy way to check if you should be watching your cholesterol, blood sugar, or anything else. The information just sits there, locked away, and you’re left guessing.
That’s a big part of why I wanted to build Cloud Patient, to make this kind of information accessible and transparent so patients aren’t left in the dark about their own health.
iCeGaming•1h ago
The goal is to give patients a unified, accessible view of their health history without relying on fragmented clinic portals.
Why it matters
Patients often lack access to a full medical history, especially when they’ve seen multiple doctors or visited different hospitals.
Doctors and clinics use different systems, making it hard to share data seamlessly.
Having a single cloud-based place to store and review visits can:
Reduce duplicate tests and miscommunication.
Improve patient understanding of their health.
Enable smoother transfers of care between providers.
Current state (preview)
Working well:
Clean and intuitive UI.
Doctors can log visit details that instantly show up for patients.
Still in progress:
Attachments (lab results, scans, etc.) cannot be downloaded or viewed yet — this feature is coming soon.
Privacy, encryption, and compliance frameworks (GDPR/HIPAA) are still being finalized.
No external integrations yet (e.g., hospital systems, fitness apps).
Roadmap questions:
When will attachments be viewable and downloadable?
What encryption and security measures will protect sensitive health data?
Will there be multi-factor authentication for both patients and doctors?
How will integrations with existing hospital systems be handled (e.g., FHIR, HL7)?
What happens if a user wants to export all their data?
Bottom line Cloud Patient has the potential to simplify how people manage their medical history. If the team can deliver on privacy, compliance, and interoperability while making attachments fully functional, it could become a valuable tool for both patients and providers.
For now, it’s a solid preview with a promising vision.