Moyae Ophthalmology FHIR Implementation Guide
0.1.0 - ci-build
Moyae Ophthalmology FHIR Implementation Guide - Local Development build (v0.1.0) built by the FHIR (HL7® FHIR® Standard) Build Tools. See the Directory of published versions
| Official URL: https://fhir.moyae.com/ImplementationGuide/moyae.fhir.ophthalmology | Version: 0.1.0 | |||
| Draft as of 2026-06-02 | Computable Name: MoyaeFhirOphthalmology | |||
Version 0.1.0 — first cut of profiles for the four resources Moyae emits today.
| Profile | Source file in Moyae | Purpose |
|---|---|---|
| MoyaeIntraocularPressure | packages/api/services/fhirObservations/iop.ts |
One Observation per eye for IOP measurements. |
| MoyaeVisualAcuity | packages/api/services/fhirObservations/visualAcuityHelpers/formatObservation.ts |
Distance / intermediate / near VA per eye, with pinhole and binocular variants. |
| MoyaeRefraction | Same file, typeOfExam = "refraction" path |
A refraction event. Shares structure with MoyaeVisualAcuity but code is SNOMED Refraction; focus always references the companion VisionPrescription. |
| MoyaeVisionPrescription | packages/api/services/fhirObservations/visualAcuityHelpers/formatVisionPrescription.ts |
Used twice in the lifecycle: status="draft" as the in-exam measurement carrier, status="active" as the signed Rx. |
These are the items partners and validators most often ask about. Each is documented honestly here, and where Moyae's current emission deviates from "ideal FHIR" or from peer IGs (e.g. the HL7 Eye Care IG), the Relationships and caveats page calls out the rationale and the v0.1.x migration plan.
laterality extension and (redundantly) via a component entry.Observation.code (corrected vs. uncorrected vs. refraction vs. retina VA) and by component method flags.Observation.focus. See the caveat below.status="draft" carries measurements during the exam; status="active" is the signed Rx.valueString today. This includes IOP pressure and VA notation. v0.1.x migrates to valueQuantity with UCUM where the unit is well-defined (mm[Hg] for IOP, LogMAR / decimal for VA).Moyae operates a translation layer between the canonical shapes documented here and partner-specific profiles. Customized endpoints, mappings, and per-partner derivations can be requested via the partnership program at moyae.com/build-with-moyae. The translation layer is permanent infrastructure; we don't expect every partner to consume the canonical shape directly.
Authored in FHIR Shorthand and built with SUSHI + the HL7 IG Publisher. Source repo: github.com/MOYAE/FHIR.
Thanks to David Flade and Tero Lipponen for reviewing early drafts of this Implementation Guide. Their review is ongoing, and not all of their suggestions are reflected in the current version — revisions are being incorporated across upcoming releases.
Implementation feedback, partner inquiries: partnerships@moyae.com or book at calendar.app.google/joEV8YqqYastTaNf6.