Versioned connector profile engineering

solia.connector-profile.v1 is an immutable descriptive configuration boundary. Bind tenant, laboratory, environment and installation identity; track request mapping, result mapping and compendium versions separately. A profile version or synthetic approval is not a deployed installation, credential grant or Production permission.

Keep secrets in approved custody and use references in configuration, not values in files, logs, screenshots or support exports. Public examples intentionally omit reference names and private endpoints.

• REST: approved endpoint/path, authentication lifecycle, JSON field mapping, bounded responses, correlation, explicit application ACK and result lifecycle policy. The shared declarative executor uses configuration, not a per-lab source fork.
• FHIR R4: ServiceRequest/DiagnosticReport mapping and target response semantics. Resource creation alone does not establish application acceptance.
• HL7 v2/MLLP: agreed message/profile version, code/segment dictionary, message control identity, CA versus AA semantics and transport custody.
• SFTP: file schema/version, naming, host-key verification, pickup/archive semantics and canonical commit evidence. File transfer alone does not establish lab acceptance.
• Edge: separately approved installation/issuer/agent/destination binding, durable replay custody and deployed telemetry. Source packaging is not installed authority.

Canonical order ID, kit barcode, native panel code, specimen and accession must retain distinct meaning. Preserve an original idempotency/transmission identity after uncertain delivery. A result callback translates only under explicit identity, signature, bounds and exact correlation; polling may recover only through the existing authorized installation-bound path.

1. Have lab IT confirm endpoint ownership, TLS/certificate, allowlist and credential rotation outside documentation.
2. Have security/ops confirm pinned network identity, bounded inputs, signed callback policy and durable replay fence. Missing authority refuses, never falls back to guessed credentials.
3. Use separate lab A and lab B profiles, endpoints, credentials, codes and specimen dictionaries over the same shared executor.
4. Change A through a new immutable revision; verify B is unchanged and cross-lab callback/price/Program/secret scope refuses.
5. Run protocol-specific qualification with independent peers and then separately approved hosted acceptance. No zero-code universal connectivity promise is made.