FAQ

Questions procurement teams ask.

Consolidated answers to the questions Basal receives from procurement teams, CDIOs, and programme directors. Structured for procurement packs, vendor-assessment forms, and RFP appendices.

• What does Basal do?
  Basal is a specialist health integration consultancy delivering HL7 and FHIR integration, clinical messaging architecture, cross-agency data sharing, cloud migration of integration estates, and health IT governance (PIA, SRA, ATO) for government and health-sector clients in Australia, New Zealand, and the United States.
• Who delivers the work?
  All engagements are delivered directly by Flynn McLean, Principal of Basal. There is no junior team, no offshore practice, and no hand-off.
• What size engagements does Basal take on?
  Most engagements are a fixed-scope architecture or strategy deliverable (4–8 weeks), a principal-architect retainer on a programme of work (3–12 months), or an on-call advisory arrangement during a critical transition window.
• Which jurisdictions does Basal work in?
  Basal is active across Australia, New Zealand, and the United States, with familiarity across Commonwealth and state health programmes (AU), national health and public-health agencies (NZ), and HIE / TEFCA contexts (US).
• How does Basal handle client IP and confidentiality?
  Basal executes NDAs as a matter of course and operates under each client's standard confidentiality regime. Case notes and references on this site are anonymised by default; named references are available on request under appropriate engagement terms.
• Does Basal hold security clearances?
  Vetting is handled per-engagement. Basal has delivered work inside agencies requiring background checks, police-vetted access, and NZISM-aligned control regimes.
• How is pricing structured?
  Most engagements price on a fixed-scope basis for defined deliverables, or as a monthly retainer for principal-architect involvement in a programme. Rates are aligned to the senior end of government digital panels and declared transparently during scoping.
• How is data handled during an engagement?
  Basal works inside the client's own cloud tenancy, VPN, or bastion wherever possible. Where data must leave the client environment (e.g. for analysis in a sandbox), it is first de-identified or synthetically generated, and the transfer is documented in the engagement SRA.

Last updated: 13 May 2026