bdd1b6ec3e
Both pages were partial ports — HospitalCourse had a single "notes
textarea separated by blank lines" instead of the dynamic note cards
vanilla shipped, and ChartReview lacked per-visit type / specialist
/ specialty fields plus the Additional Labs block. These commits
close the gap.
HospitalCourse (ports public/components/hospital.html +
public/js/hospitalCourse.js @be14578):
client/src/pages/hospital/DictatableCard.tsx — reusable card
(title + date + meta children + content + per-card Recorder).
Each note gets its own recorder so dictating into one card
doesn't interrupt another in progress.
client/src/pages/hospital/LabsList.tsx — dynamic (date, values)
rows with add/remove.
client/src/pages/hospital/ClarifyButton.tsx — "What's Missing?"
→ POST /api/hospital-course-clarify, renders the returned
questions inline.
client/src/pages/HospitalCourse.tsx — rewritten: ED Note card
(date + ED labs + content + dictate), H&P card (date + content
+ dictate), Progress Notes as dynamic cards (date + type
select matching vanilla's 6 options + content + per-card
dictate + remove), separate Labs list, instructions,
EditableResult output, ClarifyButton. Save/Load round-trips the
entire structured note-set via JSON in the transcript column.
ChartReview (ports public/components/chart.html +
public/js/chartReview.js @be14578):
client/src/pages/ChartReview.tsx — rewritten: each visit now has
its own date + visit-type select (outpatient/subspecialty/ed),
and when subspecialty is selected the specialist-name +
specialty fields appear inline. Per-visit labs textarea.
New Additional Labs block (reuses hospital/LabsList) for labs
not tied to a visit. Submit splits visits by type into the
server's visits / subspecialty / edVisits arrays, matching
src/routes/chartReview.ts.
|
||
|---|---|---|
| .. | ||
| public | ||
| src | ||
| .gitignore | ||
| components.json | ||
| eslint.config.js | ||
| index.html | ||
| package-lock.json | ||
| package.json | ||
| README.md | ||
| tsconfig.app.json | ||
| tsconfig.json | ||
| tsconfig.node.json | ||
| vite.config.ts | ||
React + TypeScript + Vite
This template provides a minimal setup to get React working in Vite with HMR and some ESLint rules.
Currently, two official plugins are available:
- @vitejs/plugin-react uses Oxc
- @vitejs/plugin-react-swc uses SWC
React Compiler
The React Compiler is not enabled on this template because of its impact on dev & build performances. To add it, see this documentation.
Expanding the ESLint configuration
If you are developing a production application, we recommend updating the configuration to enable type-aware lint rules:
export default defineConfig([
globalIgnores(['dist']),
{
files: ['**/*.{ts,tsx}'],
extends: [
// Other configs...
// Remove tseslint.configs.recommended and replace with this
tseslint.configs.recommendedTypeChecked,
// Alternatively, use this for stricter rules
tseslint.configs.strictTypeChecked,
// Optionally, add this for stylistic rules
tseslint.configs.stylisticTypeChecked,
// Other configs...
],
languageOptions: {
parserOptions: {
project: ['./tsconfig.node.json', './tsconfig.app.json'],
tsconfigRootDir: import.meta.dirname,
},
// other options...
},
},
])
You can also install eslint-plugin-react-x and eslint-plugin-react-dom for React-specific lint rules:
// eslint.config.js
import reactX from 'eslint-plugin-react-x'
import reactDom from 'eslint-plugin-react-dom'
export default defineConfig([
globalIgnores(['dist']),
{
files: ['**/*.{ts,tsx}'],
extends: [
// Other configs...
// Enable lint rules for React
reactX.configs['recommended-typescript'],
// Enable lint rules for React DOM
reactDom.configs.recommended,
],
languageOptions: {
parserOptions: {
project: ['./tsconfig.node.json', './tsconfig.app.json'],
tsconfigRootDir: import.meta.dirname,
},
// other options...
},
},
])