Inside Cross-Device Sync: How One Wound Chart Follows You From Phone to iPad to Web
product
A look at how WoundScribe keeps a single wound visit record in sync across iPhone, iPad, and browser — in real time, with no re-entry.
Most wound care EMRs treat the phone as a second-class citizen — a thin shell that uploads to the real system later. WoundScribe treats every device as a first-class view of the same live record. Here's how the sync layer actually works.
A single visit object, not three copies
When you start a visit on your iPhone, the app creates one visit record on the server. Your iPad and browser session subscribe to that record. Edits propagate in seconds, not at the end of the day.
Real-time draft, real-time sync
As the scribe drafts the SOAP note at the bedside, every token streams to the same record. Walk out, open your iPad, and the note is already there — not a copy, the same one. The underlying AI scribe for wound care runs server-side so the draft doesn't depend on which device you captured on.
Images and measurements live with the visit
Point-n-Capture images, computed length/width/depth, and the healing trend all attach to the same visit object. Switching to the browser doesn't require re-uploading — the image is already associated.
Conflict handling
Two devices editing the same field? Last write wins per field, not per note, so a biller touching the CPT code on web doesn't clobber a clinician's assessment edit on iPad.
Offline-first on mobile
Phone captures work without signal. The sync layer queues changes and reconciles them when the device reconnects — the browser view updates automatically once reconciliation finishes.
What this unlocks
- Start a visit at the bedside, finish it from the car.
- Hand off review to a colleague on the web without exporting anything.
- Keep the healing timeline on the healing dashboard accurate the moment a visit is signed — not the next morning.