Senior GCP Backend Engineer - Phase 1 Healthcare RCM Infrastructure Setup (Fixed-Price)

Job Description

Overview We are launching a specialized, white-label Revenue Cycle Management (RCM) and automated billing utility tailored for the South Carolina primary care and rural Medicaid market. We are seeking an independent, senior-level Google Cloud Platform (GCP) engineer to execute Phase 1: Secure Infrastructure & BigQuery Schema Setup. This is a strictly defined, project-based milestone with clean specifications. We are a non-technical founder team utilizing professional architectural layouts—you will not have to guess requirements. If this milestone is executed cleanly and on schedule, you will be given priority consideration for Phase 2 (API Connectivity) and Phase 3 (Stripe Webhook Integrations). Technical Specification: Phase 1 Core Infrastructure & Data Schema Project Objective: Initialize a secure, scalable, HIPAA-compliant data container environment on Google Cloud Platform (GCP) to act as the foundational engine for a multi-tenant healthcare Revenue Cycle Management (RCM) utility. Engagement Model: Fixed-Price Milestone. Target Architecture: Google Cloud Platform (GCP), BigQuery, Cloud Storage (GCS), Cloud IAM. 🛠️ Section 1: Security, IAM, & Compliance Mandates To meet strict healthcare compliance standards and prevent data-blocking liabilities under federal information laws, the developer must implement the following access controls and lifecycle rules: 1.Principle of Least Privilege (IAM): Initialize a production project (rcm-grid-sc-production). Configure a dedicated Service Account utilizing SPIFFE-based identity protocols. The infrastructure must isolate data layers so app servers maintain read-only access to ingestion streams and write-only access to transaction ledgers. 2. Stateless Ingestion & Data-Purging Policy: Configure a Google Cloud Storage (GCS) landing bucket (incoming-clinic-payloads-raw) to receive incoming transaction text. 3. The 60-Second Auto-Purge Rule: The developer must explicitly configure an Object Lifecycle Management rule on this bucket. All files must automatically delete exactly 1 minute after creation. Data processing must happen entirely inside stateless memory (e.g., in-memory Cloud Functions) to guarantee that no un-redacted clinical narratives are permanently stored on physical disks. 🗄️ Section 2: BigQuery Database Schema Specifications The developer will initialize a single BigQuery dataset containing the following four relational flat tables. Field types and constraints must be strictly mapped exactly as detailed below: Table 1: Client_Tenants Manages active clinic accounts, software tiers, and user interface access variables.

• tenant_id (STRING, REQUIRED, PRIMARY KEY) — Unique system hash for each white-label medical clinic.
• practice_name (STRING, REQUIRED) — Legal name of the provider medical group.
• account_status (STRING, REQUIRED) — Enforced status enum restricted to: ["Active", "Delinquent_Grace", "Suspended"]
• user_role (STRING, REQUIRED) — Access state enum restricted to: ["Admin_Full", "Admin_Archive"]
• stripe_customer_id (STRING) — Secure mapping token pointing to the external payment profile.

Table 2: Optimization_Logs The compliance-safe, flat historical ledger tracking billing changes and performance tier fees.

• transaction_id (STRING, REQUIRED, PRIMARY KEY) — Unique random string tracking the individual chart encounter.
• tenant_id (STRING, REQUIRED, FOREIGN KEY) — Maps directly back to Client_Tenants.tenant_id.
• encounter_date (TIMESTAMP, REQUIRED) — Date and time stamp of when the chart note was scrubbed.
• verified_codes_billed (ARRAY) — Flat array recording final codes verified from the outbound stream (e.g., ["99214", "G2211"]).
• optimization_status (STRING, REQUIRED) — Evaluation state enum restricted to: ["Yield_Captured_Full", "Yield_Bypassed_By_User"]
• performance_fee_delta (NUMERIC, REQUIRED) — The actual calculated dollar amount for our 15% value fee calculation.

Table 3: Payer_Schedules_SC_Standard The primary baseline look-up table tracking standard regional reimbursement values.

• payer_id (STRING, REQUIRED, PRIMARY KEY) — Local structural payer identifiers, restricted to: ["PALMETTO_GBA_MEDICARE", "BCBSSC_COMMERCIAL", "BCBSSC_MED_ADVANTAGE", "UNITED_HEALTH_SC"]
• code_cpt_hcpcs (STRING, REQUIRED) — Individual 5-character procedure or complexity string (e.g., "99214", "G2211").
• allowed_amount (NUMERIC, REQUIRED) — Localized dollar value base payout.

Table 4: Payer_Schedules_SC_Medicaid A dedicated master lookup table for the South Carolina Healthy Connections (Medicaid) baseline. This functions as a single source of truth for regional rural MCOs (Molina, First Choice, Healthy Blue, Absolute, Humana).

• code_cpt_hcpcs (STRING, REQUIRED, PRIMARY KEY) — Individual procedure code string.
• sc_medicaid_allowed_amount (NUMERIC, REQUIRED) — State-mandated fee payout.

🏁 Section 3: Definition of Done & Milestone Payout Requirements Payment for this fixed-price milestone ($400 - $700 depending on experience) will be unlocked only upon the successful completion and delivery of the following verification artifacts: 1. GitHub Repository Delivery: All build scripts, infrastructure-as-code files, and schema creation statements must be pushed to a private GitHub Repository owned completely by the Founder. 2. The Live Console Walkthrough: A live screen-share demonstration proving that all four BigQuery tables exist with the exact schemas, datatypes, and constraints requested. 3. The Lifecycle Verification Test: Dropping a test document into the GCS bucket and showing live on screen that the bucket's Object Lifecycle rule successfully deletes it automatically within 60 seconds. 🚨 MANDATORY PROPOSAL REQUIREMENT (ATTENTION TO DETAIL) Because this project handles secure data environments, attention to detail is our highest priority. You must start the very first line of your proposal text with the word PALMETTO in all capital letters. If you do not include the word PALMETTO on the first line of your application, it will be automatically archived and rejected by our system without a manual review. Thank you, and we look forward to reviewing your engineering qualifications! Recommended Upwork Settings to Select:

• Project Type: One-time project
• Experience Level: Expert / Senior
• Budget Type: Fixed-Price ($400 - $700)
• Skills/Keywords Tags: Google Cloud Platform, Google BigQuery, Google Cloud Storage, Database Schema Design, IAM Security, Healthcare API, Backend Development.

Apply To This Job