HL7 FHIR Interoperability Code Review Report
Evaluate clinical integration code against HL7 FHIR R4 specifications, sanitization rules, and EHR integration safety constraints.
Use this template when preparing a technical peer review of API endpoints or data ingestion pipelines mapping clinical records to FHIR resources. It ensures strict schema validation, defensive error handling, and robust PHI handling across EHR adapters.
Role: Senior Healthcare Integration Architect specializing in HL7 FHIR standard compliance and HIPAA data handling.
Context
- Service under review: {{clinical_service_name}}
- Targeted FHIR resource types: {{fhir_resource_types}}
- Integration codebase snippet: {{source_code_snippet}}
- Destination EHR platform: {{target_ehr_platform}}
- Authentication and authorization model: {{auth_mechanism}}
- Known integration risks: {{known_data_risks}}
Task
Produce an evaluation report assessing the provided healthcare integration code for standard conformance, schema integrity, error resilience, and secure handling of protected health information.
Method
- Inspect the incoming data parsing logic in {{source_code_snippet}} for FHIR schema conformance against {{fhir_resource_types}}.
- Review serialization and deserialization routines to detect unvalidated null fields or unsupported custom extensions.
- Verify that {{auth_mechanism}} correctly enforces least-privilege scoping across all EHR endpoints.
- Audit the error-handling logic to ensure failed remote calls to {{target_ehr_platform}} do not leak raw payload traces into application logs.
- Evaluate data transformation routines for boundary conditions, invalid date/time offsets, and missing mandatory coding systems.
- Cross-reference the implementation against documented risks in {{known_data_risks}} to flag unmitigated pipeline failures.
- Formulate prioritized remediation recommendations with code-level correction examples.
Constraints
- MUST evaluate compliance specifically against HL7 FHIR Release 4 standard requirements.
- MUST NOT suggest external libraries not already compatible with {{target_ehr_platform}} connectivity profiles.
- All identified vulnerabilities MUST include an explicit severity rating (Critical, Major, Minor).
- Findings must isolate schema conformance separate from transport security.
Output format
- Section 1: Executive Findings Summary (max 150 words)
- Section 2: Conformance & PHI Safety Matrix (table with Resource, Finding, Severity, Code Location)
- Section 3: Technical Remediation Directives (numbered recommendations with diff-style fixes, max 400 words)
- Section 4: Operational Verification Checklist (exactly 4 bulleted validation criteria)
Self-review
- Did I verify all referenced {{fhir_resource_types}} against standard FHIR R4 schema invariants?
- Are all identified code snippets free of real PHI and syntactically actionable?
- Does the report avoid generic API advice in favor of healthcare-specific integration patterns?
Explicit role, a named task, and discrete steps the model can follow.
Background, inputs and variables the model needs before it starts.
Hard boundaries — what the model must and must not do.
A named, field-level shape for the response.
Ordered work items that force analysis before an answer.
Length and structure that travel across frontier models.
Signal density — instruction weight without padding.
Documented variables so the scaffold adapts to new inputs.
Quality bar, assumptions and behaviour when inputs are thin.
How much real usage the template has behind it.