Code review
AuraScore 79/100

Clinical FHIR Integration Code Review and Hardening Plan

Develop an actionable code review and validation plan for healthcare integration services processing protected health information.

Use this template when planning code reviews for clinical trial data pipelines and FHIR API adapters. It establishes strict peer-review protocols for patient data sanitization, schema conformance, and endpoint security.

Template

Role: Lead Health Informatics Integration Architect specializing in HL7 FHIR interoperability, HIPAA security rule enforcement, and distributed clinical data pipelines.

Context

  • Clinical Trial Program: {{clinical_trial_identifier}}
  • Source EHR System: {{ehr_source_system}}
  • Target FHIR Resources: {{fhir_resource_scope}}
  • De-Identification / PHI Tooling: {{phi_sanitization_tool}}
  • Hosting Infrastructure: {{deployment_environment}}
  • Target Go-Live Window: {{target_go_live_window}}

Task

Deliver an end-to-end code review and interface hardening plan that establishes strict verification checkpoints for the {{ehr_source_system}} integration adapter, ensuring complete FHIR compliance and zero PHI leakage prior to {{target_go_live_window}}.

Method

  1. Map {{fhir_resource_scope}} schema definitions against the integration adapter codebase to identify validation gaps.
  2. Review serialization, logging, and exception handling routines to guarantee {{phi_sanitization_tool}} scrub execution.
  3. Formulate code review guidelines targeting token life-cycle management, TLS cipher suites, and mTLS handshakes for {{ehr_source_system}}.
  4. Define automated unit test review standards for JSON resource parsing, null-pointer handling, and malformed payload resilience.
  5. Design concurrency and rate-limiting code inspection criteria for endpoint services operating in {{deployment_environment}}.
  6. Structure a stage-gate code review matrix distributing reviewers across clinical data engineers, privacy officers, and backend leads.
  7. Establish post-review validation drills including synthetic FHIR bundle validation and mock penetration testing.

Constraints

  • MUST enforce strict automated masking checks for all logging statements before code sign-off.
  • MUST NOT approve any interface changes without automated conformance validation against {{fhir_resource_scope}} specifications.
  • Action items must detail exact code artifacts, review triggers, and escalation pathways.
  • Limit scope strictly to integration layers connecting {{ehr_source_system}} to the clinical trial pipeline.

Output format

  1. Architecture Scope & Threat Surface Overview (150-200 words)
  2. Phased Code Review & Hardening Roadmap (3 stages: Static Review, Dynamic Payload Audit, Pre-prod Gate)
  3. Reviewer Checklist for FHIR & PHI Safeguards (8 specific inspection checkpoints)
  4. Go-Live Verification Signoff Criteria (numbered list of mandatory pass/fail requirements)

Self-review

  • Ensure {{phi_sanitization_tool}} and {{deployment_environment}} are explicitly evaluated in the inspection steps.
  • Check that all FHIR resources listed in {{fhir_resource_scope}} are accounted for in the review gates.
  • Validate that review timelines align with the scheduled {{target_go_live_window}}.
AuraScore breakdown
79/100Provisional
Instruction clarity15/15 · Strong

Explicit role, a named task, and discrete steps the model can follow.

Context architecture12/12 · Strong

Background, inputs and variables the model needs before it starts.

Constraint engineering10/12 · Adequate

Hard boundaries — what the model must and must not do.

Output specification6/14 · Thin

A named, field-level shape for the response.

Reasoning structure10/10 · Strong

Ordered work items that force analysis before an answer.

Model compatibility10/10 · Strong

Length and structure that travel across frontier models.

Token efficiency5/10 · Thin

Signal density — instruction weight without padding.

Reusability7/7 · Strong

Documented variables so the scaffold adapts to new inputs.

Robustness3/5 · Adequate

Quality bar, assumptions and behaviour when inputs are thin.

Observed performance1/5 · Thin

How much real usage the template has behind it.

developers
developers-code-review
healthcare-life-sciences
fhir
health-informatics
ehr