Spaces:
Sleeping
Sleeping
Commit ·
b7ea650
1
Parent(s): bcf7de3
Add Zorgfilter deployed app verification guide
Browse files
CARE_PROFILE_APP_VERIFICATION.md
ADDED
|
@@ -0,0 +1,81 @@
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| 1 |
+
# Zorgfilter v1 — deployed app verification
|
| 2 |
+
|
| 3 |
+
Status: technical deployment verified; visible app verification pending coordinator/user confirmation.
|
| 4 |
+
|
| 5 |
+
## Technical evidence
|
| 6 |
+
|
| 7 |
+
An independent GitHub Actions check compared the relevant GitHub `main` files with the files in Hugging Face Space `solidprivacy/scrub`.
|
| 8 |
+
|
| 9 |
+
```text
|
| 10 |
+
Files compared byte-for-byte: 12
|
| 11 |
+
Exact matches: 12/12
|
| 12 |
+
Correctly scoped markers: all passed
|
| 13 |
+
Space health: HTTP 200 / ok
|
| 14 |
+
Space root: HTTP 200
|
| 15 |
+
Technical deployment: verified
|
| 16 |
+
```
|
| 17 |
+
|
| 18 |
+
Evidence:
|
| 19 |
+
|
| 20 |
+
```text
|
| 21 |
+
output/validation/care_profile_hf_sync_verification.json
|
| 22 |
+
```
|
| 23 |
+
|
| 24 |
+
The first verification attempt produced a false negative because two marker checks looked for labels in the wrong modules. The byte hashes were already equal. The corrected check moved those markers to `recognition_profiles.py` and `review_status.py` and passed all exact-file, marker and health gates.
|
| 25 |
+
|
| 26 |
+
## Coordinator/user verification
|
| 27 |
+
|
| 28 |
+
Open:
|
| 29 |
+
|
| 30 |
+
```text
|
| 31 |
+
https://solidprivacy-scrub.hf.space/
|
| 32 |
+
```
|
| 33 |
+
|
| 34 |
+
Use only the built-in synthetic examples.
|
| 35 |
+
|
| 36 |
+
### A. Profile selector
|
| 37 |
+
|
| 38 |
+
Confirm:
|
| 39 |
+
|
| 40 |
+
- four profile choices are visible;
|
| 41 |
+
- their order is:
|
| 42 |
+
1. `Zorgcontrole — streng`;
|
| 43 |
+
2. `Juridische controle — streng`;
|
| 44 |
+
3. `Algemene Nederlandse controle`;
|
| 45 |
+
4. `Algemene internationale controle`;
|
| 46 |
+
- `Juridische controle — streng` is selected initially;
|
| 47 |
+
- switching profiles never happens silently.
|
| 48 |
+
|
| 49 |
+
### B. Care profile content
|
| 50 |
+
|
| 51 |
+
Select `Zorgcontrole — streng` and confirm:
|
| 52 |
+
|
| 53 |
+
- the description mentions patient/client identifiers, EPD/ECD or dossier references, care providers, organizations, locations and exact care dates;
|
| 54 |
+
- the description says diagnosis, medication, dosage, laboratory values and observations should remain readable;
|
| 55 |
+
- an expander for a synthetic care example is visible;
|
| 56 |
+
- the example selector contains eight care examples.
|
| 57 |
+
|
| 58 |
+
### C. Review policy
|
| 59 |
+
|
| 60 |
+
Load a synthetic care example containing both patient identity and review-selected context. Confirm:
|
| 61 |
+
|
| 62 |
+
- patient/client identifiers are included for replacement;
|
| 63 |
+
- care-provider, organization, location, room/bed or exact care-date detections remain selected but show `Controle nodig`;
|
| 64 |
+
- labels and professional roles remain readable;
|
| 65 |
+
- diagnosis, medication, dosages, laboratory values and observations are not blindly replaced;
|
| 66 |
+
- possible unresolved administrative care-reference candidates are unchecked.
|
| 67 |
+
|
| 68 |
+
### D. Existing profiles and workflow
|
| 69 |
+
|
| 70 |
+
Confirm:
|
| 71 |
+
|
| 72 |
+
- Legal, General Dutch and International profiles remain selectable;
|
| 73 |
+
- the side-by-side review and replacement table remain available;
|
| 74 |
+
- export/download remains available;
|
| 75 |
+
- the Scrub Key flow remains available;
|
| 76 |
+
- `Originele waarden terugzetten` remains available;
|
| 77 |
+
- no Script execution error is visible.
|
| 78 |
+
|
| 79 |
+
## Closeout rule
|
| 80 |
+
|
| 81 |
+
The package may be marked completed only after the coordinator/user confirms the visible behavior above. Technical deployment evidence alone does not establish functional or production readiness.
|