docs: add architecture and intake intent documentation
- Add architecture overview, implementation plan, and intent overview - Add intake intent process specs (gap analyse, bouwplan, testplan) - Add swift architecture specs and visualization prompts - Remove obsolete aispeedrun-manifesto template Co-Authored-By: Claude Opus 4.5 <noreply@anthropic.com>
This commit is contained in:
colinislit
@@ -0,0 +1,221 @@
|
||||
# Text-to-Image Prompt: Intake Procesflow met Intents
|
||||
|
||||
**Doel:** Visualisatie van het complete intake proces met spraak-intents en EPD schermen
|
||||
|
||||
---
|
||||
|
||||
## Prompt (DALL-E 3 / Ideogram)
|
||||
|
||||
```
|
||||
A detailed horizontal process flow diagram for a Dutch healthcare EPD (Electronic Patient Dossier) system showing voice intents triggering UI screens.
|
||||
|
||||
The diagram flows LEFT to RIGHT through 4 main phases, each in a distinct colored zone:
|
||||
|
||||
PHASE 1 - "SCREENING" (light blue zone):
|
||||
┌─────────────────────────────────────────┐
|
||||
│ Voice intents (speech bubbles): │
|
||||
│ • "Wat is de hulpvraag?" │
|
||||
│ • "Jan is geschikt voor behandeling" │
|
||||
│ ↓ │
|
||||
│ EPD Screens (UI cards): │
|
||||
│ [HelpRequestCard] [DecisionCard] │
|
||||
│ [DocumentCard] [ActivityLog] │
|
||||
└─────────────────────────────────────────┘
|
||||
|
||||
Arrow → to next phase
|
||||
|
||||
PHASE 2 - "INTAKE START" (light green zone):
|
||||
┌─────────────────────────────────────────┐
|
||||
│ Voice intents: │
|
||||
│ • "Start intake voor Jan" │
|
||||
│ • "Nieuwe intake Volwassenen" │
|
||||
│ ↓ │
|
||||
│ EPD Screens: │
|
||||
│ [NewIntakeForm] │
|
||||
│ - Titel │
|
||||
│ - Afdeling │
|
||||
│ - Startdatum │
|
||||
└─────────────────────────────────────────┘
|
||||
|
||||
Arrow → to next phase
|
||||
|
||||
PHASE 3 - "INTAKE UITVOERING" (light teal zone, largest section):
|
||||
┌─────────────────────────────────────────────────────────────┐
|
||||
│ 9 TABS displayed as a horizontal tab bar: │
|
||||
│ [Algemeen|Contact|Kindcheck|Risico|Anamnese|Onderzoek|ROM|Diagnose|Advies] │
|
||||
│ │
|
||||
│ Below: 3 columns of intent→screen mappings: │
|
||||
│ │
|
||||
│ Column 1: Column 2: Column 3: │
|
||||
│ "Ga naar risico" "Wat zijn de risico's?" "Diagnose: depressie" │
|
||||
│ ↓ ↓ ↓ │
|
||||
│ [RiskManager] [RisicoBlock] [DiagnosisManager] │
|
||||
│ │
|
||||
│ "Kindcheck: geen kinderen" "Is intake compleet?" "Behandeladvies CGT" │
|
||||
│ ↓ ↓ ↓ │
|
||||
│ [KindcheckForm] [IntakeStatusBlock] [TreatmentAdviceForm] │
|
||||
└─────────────────────────────────────────────────────────────┘
|
||||
|
||||
Arrow → to next phase
|
||||
|
||||
PHASE 4 - "AFSLUITEN" (light purple zone):
|
||||
┌─────────────────────────────────────────┐
|
||||
│ Voice intents: │
|
||||
│ • "Sluit intake af" │
|
||||
│ • "Samenvatting intake" │
|
||||
│ ↓ │
|
||||
│ EPD Screens: │
|
||||
│ [IntakeSummaryBlock] │
|
||||
│ [Status: Afgerond ✓] │
|
||||
│ ↓ │
|
||||
│ "Start behandelplan" → │
|
||||
└─────────────────────────────────────────┘
|
||||
|
||||
LEGEND at bottom:
|
||||
🎤 = Voice Intent (input)
|
||||
📱 = EPD Screen/Component (output)
|
||||
→ = Process flow
|
||||
↓ = Intent triggers screen
|
||||
|
||||
Design style: Clean technical flowchart, software architecture diagram, white background with subtle colored zones for each phase. Speech bubbles for intents, rounded rectangles for UI components. Arrows showing relationships. Professional documentation style.
|
||||
|
||||
Typography: Sans-serif, clear hierarchy, Dutch language labels.
|
||||
Colors: Screening=#e0f2fe, Start=#dcfce7, Uitvoering=#ccfbf1, Afsluiten=#f3e8ff, Arrows=#0d9488
|
||||
Aspect ratio: 21:9 (ultrawide) or 3:1
|
||||
```
|
||||
|
||||
---
|
||||
|
||||
## Alternatief: Verticale Flow (voor A4/portrait)
|
||||
|
||||
```
|
||||
A vertical process flow diagram for a Dutch healthcare intake system showing voice commands and their corresponding EPD screens.
|
||||
|
||||
TOP TO BOTTOM layout with 4 stacked sections:
|
||||
|
||||
SECTION 1 - SCREENING
|
||||
├── Intent bubble: "Wat is de hulpvraag van Jan?"
|
||||
├── Arrow down
|
||||
└── Screen cards: [HelpRequestCard] [DecisionCard]
|
||||
|
||||
SECTION 2 - INTAKE START
|
||||
├── Intent bubble: "Start intake voor Jan"
|
||||
├── Arrow down
|
||||
└── Screen card: [NewIntakeForm]
|
||||
|
||||
SECTION 3 - INTAKE TABS (expanded section)
|
||||
├── Tab bar showing 9 tabs
|
||||
├── Three example flows side by side:
|
||||
│ ├── "Ga naar risico" → [RiskManager]
|
||||
│ ├── "Wat zijn diagnoses?" → [DiagnoseBlock]
|
||||
│ └── "Kindcheck geen kinderen" → [KindcheckForm]
|
||||
|
||||
SECTION 4 - AFSLUITEN
|
||||
├── Intent bubble: "Sluit intake af"
|
||||
├── Arrow down
|
||||
└── Screen cards: [IntakeSummaryBlock] → Behandelplan
|
||||
|
||||
Visual style: Technical documentation, swim lane diagram, clear sections with subtle background colors, speech bubbles for voice input, device frames for screens.
|
||||
|
||||
Aspect ratio: 9:16 or A4 portrait
|
||||
```
|
||||
|
||||
---
|
||||
|
||||
## Simpele Versie (voor snelle generatie)
|
||||
|
||||
```
|
||||
A software flowchart showing voice commands triggering healthcare screens.
|
||||
|
||||
Four colored columns left to right:
|
||||
1. SCREENING (blue): "Hulpvraag?" → HelpRequestCard
|
||||
2. INTAKE START (green): "Start intake" → NewIntakeForm
|
||||
3. UITVOERING (teal): "Risico's?" → RiskManager, "Diagnose?" → DiagnosisManager
|
||||
4. AFSLUITEN (purple): "Samenvatting" → IntakeSummaryBlock
|
||||
|
||||
Speech bubbles connect to UI component boxes with arrows.
|
||||
Clean, minimal, technical diagram style.
|
||||
White background, colored section headers.
|
||||
|
||||
Aspect ratio: 16:9
|
||||
```
|
||||
|
||||
---
|
||||
|
||||
## Mermaid Diagram (voor technische docs)
|
||||
|
||||
Als je liever een exacte diagram wilt die je zelf kunt renderen:
|
||||
|
||||
```mermaid
|
||||
flowchart LR
|
||||
subgraph SCREENING["🔵 SCREENING"]
|
||||
I1["🎤 Wat is de hulpvraag?"]
|
||||
I2["🎤 Jan is geschikt"]
|
||||
S1["📱 HelpRequestCard"]
|
||||
S2["📱 DecisionCard"]
|
||||
I1 --> S1
|
||||
I2 --> S2
|
||||
end
|
||||
|
||||
subgraph START["🟢 INTAKE START"]
|
||||
I3["🎤 Start intake voor Jan"]
|
||||
S3["📱 NewIntakeForm"]
|
||||
I3 --> S3
|
||||
end
|
||||
|
||||
subgraph UITVOERING["🔷 INTAKE UITVOERING"]
|
||||
direction TB
|
||||
TABS["9 Tabs: Algemeen | Contact | Kindcheck | Risico | Anamnese | Onderzoek | ROM | Diagnose | Advies"]
|
||||
|
||||
I4["🎤 Ga naar risico"]
|
||||
I5["🎤 Wat zijn de risico's?"]
|
||||
I6["🎤 Diagnose: depressie"]
|
||||
I7["🎤 Kindcheck: geen kinderen"]
|
||||
|
||||
S4["📱 RiskManager"]
|
||||
S5["📱 RisicoBlock"]
|
||||
S6["📱 DiagnosisManager"]
|
||||
S7["📱 KindcheckForm"]
|
||||
|
||||
I4 --> S4
|
||||
I5 --> S5
|
||||
I6 --> S6
|
||||
I7 --> S7
|
||||
end
|
||||
|
||||
subgraph AFSLUITEN["🟣 AFSLUITEN"]
|
||||
I8["🎤 Sluit intake af"]
|
||||
I9["🎤 Samenvatting intake"]
|
||||
S8["📱 IntakeSummaryBlock"]
|
||||
S9["📱 Status: Afgerond ✓"]
|
||||
I8 --> S9
|
||||
I9 --> S8
|
||||
end
|
||||
|
||||
SCREENING --> START
|
||||
START --> UITVOERING
|
||||
UITVOERING --> AFSLUITEN
|
||||
AFSLUITEN -->|"Start behandelplan"| BP["📱 BehandelplanView"]
|
||||
```
|
||||
|
||||
---
|
||||
|
||||
## Prompt Parameters
|
||||
|
||||
| Parameter | Waarde |
|
||||
|-----------|--------|
|
||||
| **Model** | DALL-E 3, Ideogram, of Midjourney |
|
||||
| **Style** | Technical diagram / Software flowchart |
|
||||
| **Aspect** | 21:9 (ultrawide) voor horizontaal, 9:16 voor verticaal |
|
||||
| **Kleuren** | Fase-gebonden: blauw→groen→teal→paars |
|
||||
| **Taal** | Nederlands (intent teksten) |
|
||||
|
||||
---
|
||||
|
||||
## Tips voor beste resultaat
|
||||
|
||||
1. **DALL-E 3**: Beste voor tekst in afbeeldingen, maar kan moeite hebben met complexe diagrammen
|
||||
2. **Ideogram**: Zeer sterk in diagrammen en flowcharts met tekst
|
||||
3. **Midjourney**: Mooi visueel maar minder nauwkeurig met tekst
|
||||
|
||||
**Aanbeveling**: Gebruik Ideogram voor dit type technische procesflow, of maak het diagram in Figma/Miro en gebruik AI alleen voor styling.
|
||||
Reference in New Issue
Block a user