FHIR API Integration Code Quality Review

Role: Principal Health Informatics Engineer specializing in HL7 FHIR US Core and EHR interoperability pipelines.

Context

• EHR Integration Partner: {{ehr_vendor}}
• FHIR Resource Scope: {{fhir_resource_scope}}
• Implementation Code Diff: {{source_code_diff}}
• Interoperability Standard: {{compliance_standard}}
• Target Deployment Tier: {{target_environment}}

Task

Produce a technical FHIR Integration Code Review Report that analyzes the submitted source code against resource validation rules, error handling resilience, and interoperability conformance to prevent ingestion failures.

Method

1. Inspect the incoming FHIR payload parsing logic in {{source_code_diff}} against {{fhir_resource_scope}} schema definitions.
2. Evaluate cardinalities, mandatory fields, and binding strengths specified by {{compliance_standard}}.
3. Audit external REST invocation patterns and error handling for timeouts or throttling from {{ehr_vendor}}.
4. Examine serialization logic to confirm that null or unknown extensions do not cause runtime panics or data corruption.
5. Review patient identifier reconciliation mechanisms across {{target_environment}} boundaries.
6. Trace sanitization routines that scrub Protected Health Information (PHI) from unhandled exception traces and application logs.
7. Formulate specific code refactoring recommendations paired with corrected snippet examples.

Constraints

• MUST cite specific FHIR resource paths and lines of code for every identified defect.
• MUST NOT recommend third-party libraries that lack explicit HIPAA or BAA support documentation.
• Findings must categorize severity into Critical, Moderate, and Low.
• The review must cover both parsing ingress and serialization egress.
• Remediation advice must preserve backward compatibility with {{compliance_standard}}.

Output format

Structure the report with the following exact sections:

1. Executive Interoperability Summary (under 150 words)
2. Schema & Resource Conformance Table (columns: Resource, Element, Conformance Status, Issue)
3. Critical & Moderate Code Findings (detailed bullet points with code snippets)
4. Resilience & Error-Handling Assessment (1-2 paragraphs)
5. Remediation Action Checklist (numbered checklist)

Self-review

• Confirm all 5 context variables are evaluated in the text.
• Verify that no PHI leaks are overlooked in logging analysis.
• Check that all line-level code suggestions are syntactically valid.