Product overview
What forms do
Explains how Glyph lets a hospital design its own clinical and operational forms, run them, and keep each completed form as a fixed, versioned record.
Glyph is the forms tool. A hospital designs its own clinical and operational forms, runs the fill experience, and keeps every completed form as a fixed, versioned record. A form is a structured document a hospital defines to capture a set of entries in one place, such as a triage assessment, an operational checklist, a consent, or a set of results.
What Glyph carries
An administrator designs a form without a developer. Fields, layout, validation and calculation are arranged in the builder, and the form is published for staff to fill across the hospital.
Glyph runs the fill experience end to end. It prefills known details so staff retype less, and it checks entries as they are filled, so a completed form is consistent before it is saved.
Assisted fill prepares a draft entry, and the person filling confirms it. The record names the person who confirmed, so a filled form stays attributable.
The moment a form is finished it locks. Glyph keeps a version history against the design, so an old filled form always matches the form design that was in force when it was filled.
Forms it carries
Glyph carries clinical and operational forms with the same design and fill machinery. A consent form adds a formal sign-off step. A result form attaches to an order, so the response returns against the test that prompted it.
| Kind | What it captures | Where it lands |
|---|---|---|
| Clinical form | An assessment, a triage record, an observation set. | The patient record, against the encounter. |
| Operational form | A checklist or a step inside a larger process. | The process that requested it. |
| Consent form | A directive the patient gives, with a formal sign-off. | The patient record, as a consent entry. |
| Result form | The result of an ordered test or study. | The order that requested it. |
From design to record
A form travels the same path every time: an administrator designs it, publishes it, staff fill it, the built-in checks run, and the completed form locks into the record with a version behind it.
Built-in checks
A form checks its own entries and computes values as it is filled. Required fields, ranges and formats are set once in the design and applied to every filled copy. Calculated fields derive their value from other entries, so a total or a score stays consistent with what was recorded.
Read how validation and calculation run inside a form.
A completed form stays fixed
A filled form locks
When a form is finished it locks and stays as filled. A correction is added as a new version, with the prior version kept and marked superseded. The version history ties each filled copy to the design that was in force at the time, so a form read months later reads exactly as it stood.
Read how filling and locking hold a completed form fixed.
Where forms appear
A form reaches staff wherever the work is. A clinician orders a form to be filled through Forge, the same way they order a test. A consent form and a completed clinical form land in the patient record in Atlas, against the encounter. A form can also stand as a step inside a repeatable process in Cadence.
Common questions
Does designing a form need a developer?
An administrator designs a form in the builder by arranging fields, validation and layout. The form is published from the same place, with the version recorded.
What holds a filled form to its design?
Glyph keeps a version history. A filled form is bound to the form design that was in force when it was filled, so a later change to the design leaves earlier filled forms as they stood.
How does a result get back to the right test?
A result form attaches to the order that requested it, so the completed form returns against that test in the patient record.
Read how an administrator builds a form.