OrthoRay – A native, lightweight DICOM viewer written in Rust/wgpu by a surgeon
3 pointsby DrMeric4 hours ago2 comments
  • DrMeric4 hours ago
    Documentation: For those interested in the technical details and usage, I wrote extensive documentation here: https://orthoarchives.com/en/orthoray/docs/getting-started/w...
  • verdverm3 hours ago
    How are you using this in your practice? What liabilities might arise?

    disclaimer, I work with a company that builds one of those expensive offerings

    • DrMerican hour ago
      Fair questions.

      I use OrthoRay as a secondary tool — preoperative planning, teaching, research. Clinical reads go through certified PACS, as they should. The app requires explicit consent at launch acknowledging it's not certified for clinical use.

      Since you work in this space, I'm curious: is there a realistic FDA/CE pathway for an independent developer, or is certification fundamentally an enterprise-level investment? How do open-source tools like 3D Slicer or OHIF handle this same liability question?

      Would appreciate your perspective.