Generating clinical documentation

When you complete a workflow session, Quiver transforms the information you captured into structured clinical documentation. This page explains what happens during generation and what to expect in the output.

​

What happens when a session ends

​

For workflow sessions

When you complete a workflow:

1. Data compilation — All captured fields are gathered
2. Template application — Information is formatted according to the workflow’s documentation template
3. Calculation — Any computed fields or scores are calculated
4. Document assembly — A complete document is generated from the structured data
5. Availability — The documentation becomes available for review

This process is usually takes a few seconds to a few minutes

​

How information becomes documentation

​

From structured data to documentation

Workflow sessions compile captured data into formatted documentation. What Quiver does:

• Assembles all completed fields
• Applies the documentation template associated with the workflow
• Formats data according to section structure
• Includes all required elements
• Calculates any derived values or scores

What Quiver preserves:

• All entered data exactly as captured
• Selections from dropdowns and checklists
• Attached images, voice notes and documents

What Quiver formats:

• Field labels and section headings
• Data presentation and layout
• Required versus optional content

​

What to expect in generated output

​

Documentation structure

Generated documentation follows the document template you selected. Not all sections appear in every document. Sections are included based on what was discussed or captured.

​

Content completeness

Generated documentation reflects what was captured during the session. Complete sections:

• Topics that were thoroughly discussed or documented
• Required workflow fields that were completed
• Areas where you provided detailed information

Minimal sections:

• Topics mentioned briefly
• Optional workflow fields left blank
• Areas not covered during the encounter

Absent sections:

• Topics not discussed at all
• Workflow sections marked as not applicable
• Template sections irrelevant to this encounter

This variability is expected. Not every encounter covers every possible topic.

​

Accuracy expectations

Generated documentation is a summary that requires review. What is typically accurate:

• Facts that were clearly stated
• Measurements and values you verbalized or entered
• Selections you made from dropdowns or checklists
• Medications and dosages you specified

What requires verification:

• Complex medical terminology
• Medication names that sound similar
• Laterality (left versus right)
• Numerical values stated quickly
• Ambiguous statements

​

What affects generation quality

​

For transcription

Audio quality:

• Clear speech produces better results than mumbled speech
• Quiet environments work better than noisy ones
• Proximity to the device affects capture quality

Verbal clarity:

• Explicitly stated information is captured more reliably
• Ambiguous statements may be interpreted incorrectly
• Key details should be verbalized clearly

Template selection:

• Appropriate templates produce better-organized documentation
• Mismatched templates may result in awkward section placement

​

For forms of input

Field completion:

• Completed fields produce complete documentation
• Skipped optional fields result in minimal sections
• Required fields ensure essential content is present

Data accuracy:

• Accurate input produces accurate documentation
• Errors in data entry appear in the final document
• Validation during capture prevents some errors

Workflow design:

• Well-designed workflows produce clear documentation
• Poorly designed workflows may result in awkward formatting

​

Handling generation issues

​

If generation takes longer than expected

Possible causes:

• Long or complex sessions require more processing time
• System load may temporarily slow generation
• Network connectivity issues may delay processing

What to do:

• Wait a few minutes before checking again
• Verify your network connection
• Check your history to see if the draft appeared
• Contact support if generation fails completely

​

If generated documentation is incomplete

Possible causes:

• Information wasn’t captured during the session
• Audio quality prevented accurate transcription
• Workflow fields were left incomplete

What to do:

• Review what was captured during the session
• Add missing information during review
• Note any information that’s pending
• Complete the documentation based on your memory

​

If generated documentation is inaccurate

Possible causes:

• Ambiguous statements were misinterpreted
• Similar-sounding terms were confused
• Complex information was simplified incorrectly

What to do:

• Correct errors during review
• Verify all critical information
• Add clarifying details
• Finalize only when accurate