HK Audiology Group
Research operations

Study Workflow Guide

A practical guide for deciding how a NeuraHear assessment tool should be configured, calibrated, collected, exported, and protected in a study.

Use this before recruitment

The goal is to make versioning, data mode, calibration, and export assumptions explicit before participant data collection starts.

Check version log

Workflow

From setup to export

01
Plan

Define the study mode

Decide whether the workflow is a public demonstration, a browser-only pilot, a restricted study link, or a server-backed data collection route.

Participant group and languageStudy protocol and consent contextTarget tool and expected outputs

Expected output

Documented study mode

02
Configure

Freeze the tool baseline

Record the tool version, audio set, calibration behavior, scoring logic, export fields, and any restricted access assumptions before recruitment starts.

Tool version noteStimulus and language versionExport schema and backup path

Expected output

Versioned study setup

03
Calibrate

Confirm playback and listening setup

Run the intended device and sound-level checks before testing so participants use a consistent listening setup and the noise or speech level is documented.

Headphone or speaker planNoise calibration procedureParticipant instruction wording

Expected output

Ready-to-test setup

04
Collect

Monitor records while data collection is live

For server-backed tools, check that new records are appended rather than replacing existing files. For browser-only tools, confirm local exports are saved after each session.

Record count monitoringFailed-submission handlingSession export confirmation

Expected output

Traceable raw data

05
Export

Archive raw and analysis-ready outputs

Keep raw records, exported CSV or JSON files, and analysis summaries separate so later scoring updates do not obscure the original participant data.

Raw data archiveAnalysis-ready exportVersion note included with files

Expected output

Reproducible study package

Browser-only

Best for

Pilots, demonstrations, questionnaires, and workflows where the researcher saves the export manually.

Data handling

No server submission by default. Results are exported from the browser as JSON, CSV, or summary text.

  • Explain export responsibility
  • Avoid collecting identifiable data unless approved
  • Keep version notes with exported files

Server-backed

Best for

Live study tools where participant records need to be appended to a server-side data file or database.

Data handling

Responses are submitted to a backend route and stored outside the static website release directory.

  • Back up before deployment
  • Monitor record counts
  • Keep static releases separate from study data

Restricted link

Best for

Study-specific experiments, review consoles, or tools that should not be listed until protocols are finalized.

Data handling

The tool may be deployed but kept out of public tool lists and navigation until the study is ready.

  • Avoid public listing
  • Confirm consent language
  • Log activation and deactivation dates

Release checklist

Before a study-facing update goes live

Tool URL and version log entry are confirmed
Language, audio stimuli, and calibration flow are frozen
Participant instructions match the actual page flow
Consent and study protocol language are finalized where required
Data mode is clear: browser-only, server-backed, or restricted link
Export fields and file formats are documented
Backup and rollback plan are checked before deployment
A small pilot run is inspected before recruiting more participants

Ready to configure a study?

Start with the tool baseline, then confirm the data mode.

View toolsContact