temetro

gsadmin/temetro

Fork 0

mirror of https://github.com/temetro/temetro.git synced 2026-07-28 04:38:57 +00:00

Commit Graph

Author	SHA1	Message	Date
Khalid Abdi	0d2494d67a	feat: read-only FHIR R4 server (share records over /fhir) Expose temetro's own records as a read-only FHIR R4 server at /fhir, authenticated with per-clinic API keys (tmf_… bearer tokens, SHA-256 hashed, shown once). Serves Patient, Observation (labs + vitals), AllergyIntolerance, Condition, MedicationRequest, Encounter and Appointment as text-only CodeableConcepts (temetro stores free-text clinical values); CapabilityStatement at /fhir/metadata (unauth). Searchset Bundles with _count/_offset pagination and self/next/prev links; every request is org-scoped and written to the activity log. Keys are created/revoked under Settings → Integrations (owner/admin). Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>	2026-07-04 01:27:32 +03:00
Khalid Abdi	43eaccb97e	feat: HL7/FHIR, e-prescribing & insurance claims integrations Real, standards-compliant integration clients that the clinic points at its own (sandbox or production) endpoints — no mock data. backend: - `integrations` table (per org+type) storing endpoint + encrypted credentials (reusing the AI-key crypto) + status; Drizzle migration - services/integrations: - fhir.ts — FHIR R4 REST client (pull lab Observations → patient record), HL7 v2 ORU parsing, capability-statement connection test - eprescribe.ts — NCPDP SCRIPT NewRx message build + transmit - claims.ts — X12 837P claim generation + 835 remittance parsing - `/api/integrations` route: config GET/PUT (owner/admin), connection test, and the FHIR sync / HL7 ingest / e-Rx send / claim submit actions, RBAC-gated (lab/patient, prescription, invoice) frontend: - lib/integrations.ts client - Settings → Integrations tab to configure endpoints/credentials/enable + test each integration - on-page actions, shown only when the integration is enabled: Lab page → FHIR "Sync results" card; prescription sheet → "Send to pharmacy"; invoice sheet → "Submit claim" Production e-Rx/claims routing requires the clinic's own Surescripts / clearinghouse credentials; the code transmits real messages once supplied. Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>	2026-06-18 20:15:00 +03:00

Author

SHA1

Message

Date

Khalid Abdi

0d2494d67a

feat: read-only FHIR R4 server (share records over /fhir)

Expose temetro's own records as a read-only FHIR R4 server at /fhir,
authenticated with per-clinic API keys (tmf_… bearer tokens, SHA-256
hashed, shown once). Serves Patient, Observation (labs + vitals),
AllergyIntolerance, Condition, MedicationRequest, Encounter and
Appointment as text-only CodeableConcepts (temetro stores free-text
clinical values); CapabilityStatement at /fhir/metadata (unauth).
Searchset Bundles with _count/_offset pagination and self/next/prev
links; every request is org-scoped and written to the activity log.
Keys are created/revoked under Settings → Integrations (owner/admin).

Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>

2026-07-04 01:27:32 +03:00

Khalid Abdi

43eaccb97e

feat: HL7/FHIR, e-prescribing & insurance claims integrations

Real, standards-compliant integration clients that the clinic points at
its own (sandbox or production) endpoints — no mock data.

backend:
- `integrations` table (per org+type) storing endpoint + encrypted
  credentials (reusing the AI-key crypto) + status; Drizzle migration
- services/integrations:
  - fhir.ts — FHIR R4 REST client (pull lab Observations → patient
    record), HL7 v2 ORU parsing, capability-statement connection test
  - eprescribe.ts — NCPDP SCRIPT NewRx message build + transmit
  - claims.ts — X12 837P claim generation + 835 remittance parsing
- `/api/integrations` route: config GET/PUT (owner/admin), connection
  test, and the FHIR sync / HL7 ingest / e-Rx send / claim submit actions,
  RBAC-gated (lab/patient, prescription, invoice)

frontend:
- lib/integrations.ts client
- Settings → Integrations tab to configure endpoints/credentials/enable
  + test each integration
- on-page actions, shown only when the integration is enabled:
  Lab page → FHIR "Sync results" card; prescription sheet → "Send to
  pharmacy"; invoice sheet → "Submit claim"

Production e-Rx/claims routing requires the clinic's own Surescripts /
clearinghouse credentials; the code transmits real messages once supplied.

Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>

2026-06-18 20:15:00 +03:00

2 Commits