FACEECHO / Telehealth

What should a telehealth provider check before adopting a camera-based patient assessment or check-in service?

A telehealth provider should verify the service’s intended use, evidence for its specific claims, image-quality requirements, data handling, human review and actual integration status. Test the complete patient-to-clinician workflow before adopting it. FaceEcho offers guided scans, relevant questions and downloadable reports; those features alone do not establish a connection to a provider’s clinical system.

Start with a clearly defined patient need. Collecting a patient’s account before a visit, helping capture a usable photograph and measuring a physiological value are different tasks. Ask the supplier to demonstrate the exact function you intend to use. Evidence about one tool or task should not be treated as validation of another. Record which claims have supporting results and which remain proposals.

Check whether the intended patients can complete the process. Include people using different phones, connection speeds and accessibility settings. Define what happens when a photograph is blurred, a question is skipped or an upload fails. Missing information should lead to a request for clarification or an appropriate alternative, rather than an unsupported conclusion. The provider should decide what information is sufficient for the planned consultation.

Agree who reviews submissions, where they appear and when patients should expect a response. HHS describes asynchronous telehealth as an exchange of messages, images or records that clinicians review at a different time. Uploading information is therefore separate from having it reviewed. Explain the review schedule and the provider’s route for urgent concerns, and offer an alternative for patients who cannot use the tool.

Review the privacy policy and contract for collection, access, sharing, retention and deletion. Ask for a demonstration of any claimed connection to your systems, including who is responsible for operation and support. In FaceEcho’s current individual-app workflow, the user reviews a report, downloads a PDF and chooses to share it through an accepted channel. Confirm any organizational implementation separately. A sensible initial evaluation records completion, unusable submissions, staff effort and patient understanding; these are suggested measures, not proven FaceEcho outcomes.

Key takeaways

  • Separate information collection, image-quality assistance and measurement claims.
  • Require evidence for the actual product, task and intended patients.
  • Define review responsibilities, response expectations and alternative access.
  • Verify a working integration separately from manual PDF sharing.

Sources & related information

← Back to FaceEcho FAQs