FHIR/HL7 Interoperability & Compliance

Lambent Synapse - Healthcare Data Standards Readiness

FHIR R4 Capability Statement

Lambent provides a FHIR R4 capability statement endpoint that describes the platform's readiness for healthcare data interoperability. This is currently a stub implementation with documented data mappings.

Endpoint:

GET https://api.example.com/api/integrations/fhir

Response (HTTP 200):

{
  "resourceType": "CapabilityStatement",
  "status": "draft",
  "kind": "capability",
  "fhirVersion": "4.0.1",
  "format": ["json"],
  "rest": [{
    "mode": "server",
    "resource": [
      { "type": "Patient", "interaction": [{"code":"read"},{"code":"search-type"}] },
      { "type": "Observation", "interaction": [{"code":"read"},{"code":"search-type"}] }
    ]
  }]
}

Data Mapping: Lambent -> FHIR

Lambent Field	FHIR Resource.Path	Notes
`patients.pseudonym`	`Patient.name[0].text`	Pseudonym only - no real name stored
`patients.age_range`	`Patient.extension(age-range)`	Range, not exact date of birth
`patients.gender`	`Patient.gender`	FHIR gender valueset
`patients.diagnosis`	`Condition.code.text`	ICD-10 coding planned for v2
`patients.consent_given`	`Consent.status`	Boolean mapped to active/inactive
`therapy_sessions.fluency_score`	`Observation.component[0].valueQuantity`	Code: fluency-score
`therapy_sessions.syntax_score`	`Observation.component[1].valueQuantity`	Code: syntax-score
`therapy_sessions.semantic_score`	`Observation.component[2].valueQuantity`	Code: semantic-score
`therapy_sessions.created_at`	`Observation.effectiveDateTime`	ISO 8601
`therapy_sessions.difficulty_level`	`Observation.extension(difficulty)`	Custom extension, 1-10 scale

HL7 v2.x Readiness

HL7 v2 ADT (Admit/Discharge/Transfer) message mapping is planned for a future release. Current data structures are designed to be compatible with ADT message segments:

PID: patients table
OBX: therapy_sessions
EVN: audit_logs

Synapse Approval Workflow

For safety and professional accountability, Synapse enforces a draft -> governance -> therapist approval -> session completion chain. No unapproved pack can be executed.

POST https://api.example.com/api/synapse/cases
POST https://api.example.com/api/synapse/cases/:caseId/session-packs/draft
POST https://api.example.com/api/synapse/session-packs/:packId/approve
POST https://api.example.com/api/synapse/session-packs/:packId/complete
GET  https://api.example.com/api/synapse/cases/:caseId/timeline
GET  https://api.example.com/api/synapse/cases/:caseId/report

Audit Trail Specification

All critical clinical actions are logged in the audit_logs table. Synapse approval events are mandatory before session execution. Audit payloads are PII-free: raw patient text is never stored in audit records.

Event Type	Payload Fields
`user.login`	user_id
`user.register`	user_id, role
`patient.create`	pseudonym (no real name)
`patient.upload`	patientId, input_type, word_count, text_hash_prefix
`patient.export`	patientId
`eval.run`	word_count, text_hash_prefix
`synapse.case.upsert`	patient_id, goals_count, language
`synapse.pack.draft`	pack_id, blocked, issues
`synapse.pack.review`	decision, edited_task_count
`synapse.pack.complete`	task_result_count, has_notes
`synapse.case.report`	case_id
`api_key.create`	key_id
`api_key.revoke`	key_id