"Request signature" on an uploaded document — asked on 2026-09-10, captured in no issue

Open
#585 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
2/5
Estimated time
1-3 hours
Newbie friendliness
48/100
Issue type
Documentation
Clarity
Mostly clear
Activity status
Active
Domain
documentation

Research direction

Start with related issue #565 and compare its upload and document write-path scope with the 2026-09-10 call note. Confirm with MIE whether WebChart's write API exposes signature requesting, then record the result in #565. Done means the signature requirement is documented or its ownership and API limitation are explicitly captured.

Written by the indexing model from the issue text.

Description

blocked-on-mie enhancement

On the 2026-09-10 call, alongside "upload the record and pick a doc type", the practice said they also need to request a signature on it. The doc-type half is captured (#565, and the honest answer that an upload cannot satisfy a measure under CQL-is-truth). The signature half is captured nowhere — not in #565, not in the roadmap, not in a transcript summary.

It is a small ask with a real workflow behind it: a document that needs a clinician's signature is not finished until it has one, and a quality workflow that hands someone a document without that step hands them an unfinished task.

Almost certainly not WorkWell's to build. Signature request and capture is chart functionality — it belongs to the document in WebChart, next to the doc type. The likely correct outcome of this issue is one line in #565's scope ("the document write path includes requesting signature") plus confirmation from MIE that the write API exposes it.

Filed so the ask is not lost in the gap between "the upload ask" and "the write path", which is exactly where it fell.

Found while re-auditing the four pilot source documents on 2026-09-18. Related: #565.

Dominant language
TypeScript
Stars
0
Forks
0
Avg merge
6h 6m
Merged PRs (30d)
69

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from Taleef7/workwell

All issues in Taleef7/workwell

Similar issues

More TypeScript issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.