The Data-Origin Policy
The operator’s EHR and eMAR remain the sole legal clinical record. Every value inside the operating record carries one of four origin labels, so nobody has to guess whether a number is clinical documentation, management context, a narrow direct entry, or something on its way back to a source system.
1 · The system-of-record default
For a pilot and for production, the operator’s EHR and eMAR are the authoritative sources for the legal clinical record across these categories, unless a specific alternative has been agreed in writing:
2 · The four labels
Every clinical value in the operating record is exactly one of these. The label travels with the value: on screen, in exports, and in the metrics the value feeds.
4 · Status
This policy is adopted. The enforcement mechanics — origin labels as a non-nullable attribute on clinical rows, the per-category system-of-record register, source-to-target reconciliation, the exception queue and the write-back gate — are registered engineering work and are not enabled in operator production. No third-party clinical integration is in operator production today. Data crossover will not be described as complete until source-to-target reconciliation and clinical acceptance testing are documented.
https://seniorcre.com/data-origin-policy