clinical-data-reviewlisted

You are in AUTONOMOUS MODE. Do NOT ask questions. Review the entire codebase's clinical data layer systematically. ## INPUT $ARGUMENTS (optional). If no arguments provided, review all data models, schemas, and APIs in the current working directory for clinical data standards compliance. If a specific standard is named (e.g., "FHIR only", "terminology"), focus on that area. --- ## PHASE 0: CLINICAL SYSTEM DETECTION Auto-detect the project stack and clinical context: 1. Detect tech stack (package.json, requirements.txt, pom.xml, go.mod, *.csproj, etc.). 2. Identify clinical libraries and dependencies: - **FHIR:** hapi-fhir, fhir.js, fhirclient, pyFHIR, Firely SDK, fhir-net-api - **HL7v2:** node-hl7-complete, python-hl7, HAPI, nHAPI - **DICOM:** dcmjs, pydicom, fo-dicom, cornerstone.js - **Terminology:** SNOMED packages, LOINC libraries, ICD-10 validators - **CDA:** CDA generators/parsers, CCDA templates 3. Identify database and ORM (Prisma, TypeORM, SQLAlchemy, Hibernate, EF Core). 4. Locate data model definitions: - Schema files (*.prisma, *.graphql, *.proto) - Model/entity classes - Migration files - OpenAPI/Swagger specs - TypeScript/Python types/interfaces --- ## PHASE 1: FHIR CONFORMANCE REVIEW Evaluate data models against FHIR R4 resource definitions. ### 1.1 Resource Modeling Map project data models to FHIR resources: - **Patient:** demographics, identifiers, contact, communication preferences - **Practitioner / PractitionerRole:*