StetoRadr Tutorial — Android app + Web app

A practical workflow for collectors, device admins, web admins, and researchers — from bedside APTM capture to the public heart-sound catalog.

At a glance — end-to-end data flow

Heart sounds move from the stethoscope through the local-first Android app, then to the web app for review, and finally (when published) to the de-identified public catalog.

End-to-end StetoRadr data flow diagram
Bedside capture → Android (on-device) → upload → web app → publish → public heart sounds catalog

Screening output supports research and workflow only. It is not a standalone medical diagnosis.

Track A — Android app

Install, register, and roles

A1. Install + first launch

  1. Download the demo APK from stetoradr.com/demo (or your pilot build).
  2. On a fresh install, register a local device admin (username/password stay on the device).
  3. Wait for approval in the web app under Admin → Devices (ADMIN role).
  4. After approval, that local admin can add collectors and other admins as usual.

Existing installs that already have local users are treated as approved (compat). App updates can arrive in-app — see What’s New.

A2. Roles on the device

Built-in admin / collector accounts stay fixed; device admins add additional users.

Track A — Android app

A3. Collector workflow

Log in with a local collector account, then complete one session per patient.

Android collector workflow diagram
Intake → Consent → A-P-T-M → CHD label → Save (optional upload by device admin)
  1. Patient intake

    Name, sex, city, optional MRN, weights, gejala chips (or “None observed”), maternal/pregnancy history, vitals, and recording environment. Age is entered as years + months + weeks (each may be 0 for a newborn today).

  2. Consent

    Parent/guardian name, date of birth, Indonesian phone (08… or +62…), and signature pad.

  3. APTM recording

    Four guided 10-second clips: Aortic → Pulmonic → Tricuspid → Mitral. Follow the on-screen reference map for placement.

  4. CHD label

    Mark congenital heart disease as yes or no for the session.

  5. Save locally

    Data stays on-device first. Start the next patient or finish. Uploads are handled by a device admin when online.

Track A — Android app

A4. Device admin workflow

Track B — Web app

Open the web app and admin tasks

Open stetoradr.com/app and sign in with your role.

Web admin workflow diagram
Login → approve devices → users → recordings → CRF templates → publish → public catalog

B2. First-time access

Pilot teams receive signed-in access from StetoRadr. No local server setup is required for collectors or site admins.

B3. Admin

B4. Researcher

Review collections and set the device default CRF template. Researchers do not approve devices or manage all users.

B5. Shared pages

What’s New, Settings, Saved Collections, Files/Storage, and Legacy recordings are available from the app shell depending on your role.

APTM protocol primer

Every collection session uses a fixed listening order: Aortic → Pulmonic → Tricuspid → Mitral. That consistency makes multi-site datasets comparable.

APTM chest diagram showing aortic, pulmonic, tricuspid, and mitral listening positions
APTM reference map used in StetoRadr capture sessions.

Full protocol detail: APTM heart sound protocol.

Roles cheatsheet

Same role names appear on Android and the web app; capabilities differ slightly by surface.

Roles and capabilities matrix
Collector focuses on capture; researcher on review/CRF; admin on users, devices, and publish.
Capability Collector Researcher Admin
Patient collection (APTM)
Review collections
Set default CRF template
Manage users / devices
Publish to public catalog ✓ (web)

Next steps

Ready to try a session or join a pilot?