FACEECHO / Diagnostic labs
What should a lab verify before piloting a smartphone-photo check-in service?
Before piloting a smartphone-photo check-in service, a lab should verify the named product, intended use, evidence for that use, available functions, data handling and review responsibilities. Establish whether the proposal is a concept, a working demonstration or an operational service. A facial photograph or app report does not determine which laboratory tests a person needs.
Ask the supplier to demonstrate the entire proposed sequence with representative sample information. Identify what the patient submits, what the tool produces and who receives the result. Keep patient-reported symptoms, visible observations and laboratory results clearly distinguished. Record which steps work now, which require configuration and which depend on development. A camera demonstration is not evidence of an implemented lab workflow.
Examine evidence against the specific claim being made. A study about image quality does not validate disease identification, and research on a different product does not establish the performance of the service under consideration. Ask about the study population, capture conditions, limitations and handling of incomplete input. If the supplier cannot support a proposed function, narrow the pilot to what can actually be evaluated.
Define an appropriate patient group, voluntary participation and an understandable explanation of the pilot. Agree how questions or concerns reach a qualified professional, what the lab’s staff are expected to do and what happens outside the review period. Check consent, access, retention, deletion, service providers and the accepted submission channel. Do not invite people to upload information until the participating organizations understand their responsibilities.
For FaceEcho, verify the current guided-scan, question and report workflow directly with the team. A user can download a PDF and choose to share it; that does not itself create lab booking, test routing or a lab-system connection. A proposed pilot should document any additional configuration separately. This verification page covers readiness to begin. Use the separate lab patient-engagement evaluation answer when deciding how to measure operating cost, usefulness and value after the pilot has been defined.
Key takeaways
- Verify the exact product and distinguish a proposal from an operational service.
- Match evidence to the intended task and patient group.
- Agree consent, data handling, review and patient-support arrangements before launch.
- Keep test selection with clinicians and confirm lab integrations separately.