clearPath exposes hand-hygiene compliance events and custom audit definitions as standard HL7 FHIR R4 resources under /api/v1/fhir/*. The surface conforms to the FHIR R4 resource model (fhirVersion 4.0.1) and is intended for server-to-server integrations with analytics platforms, EHRs, and reporting systems that speak FHIR natively.
All responses are served as application/fhir+json. Search results are returned as FHIR Bundle resources of type searchset, and errors are returned as FHIR OperationOutcome resources — exactly what your downstream systems already expect.
application/fhir+jsonQuestionnaireResponse/fhir/metadataclearPath publishes four FHIR resource types out of the box, each mapped to the closest semantic match in the clearPath data model. Hand-hygiene events become Observation resources, rolled-up compliance becomes MeasureReport, custom audits become Questionnaire definitions, and submitted responses become QuestionnaireResponse entries.
54564-0 ("Hand hygiene observation"). The valueCodeableConcept field carries the compliant / non-compliant result.FHIR endpoints are protected by a per-account API token sent in the X-API-Token header. Tokens are managed through the standard clearPath user editor, can be rotated at any time, and are scoped to a single corporation — so a partner system can read from one account without ever seeing data from another.
X-API-Token header/fhir/metadata for capability discoverysubject, date-from, date-to, _count, _offsetge / le / eq / gt / lt date prefixes acceptedHL7 FHIR R4 support is included with the Ultimate edition. Wire clearPath into your EHR, your analytics warehouse, or any FHIR-aware reporting system without writing a custom data extract.
Request a Quote Compare Editions