Clinical notes serve as a core data stream that powers comprehensive patient engagement across the care journey. Our AI processes these notes in real-time to:
Provide real-time updates and visit progression
Generate patient-friendly timelines and daily schedules
Display current dietary restrictions and recommendations
Track and communicate patient goals and progress
Create personalized discharge checklists from complex instructions
Surface important follow-up care requirements and prescriptions
Deliver targeted education based on documented conditions
Our goal is to transform detailed clinical narratives into clear, actionable information for patients that is easy to read and understand. We want patients to be informed and part of their care journey towards better health.
Required Notes
Provider Notes
Nursing Notes
Discharge Notes/Instructions
Required Statuses
In Progress/Preliminary
Final/Authenticated
Amended/Corrected
Required Formats
Plain Text (preferred)
RTF
We support all event types and we support all segments (ORU or TXA) and fields. Below is our minimum required segment and field specification.
Segment | Field | Field / Expected Value | Comments |
MSH | 1 | Field Separator |
|
MSH | 2 | ^~& |
|
MSH | 3 | Sending Application |
|
MSH | 4 | Facility Identifier | Unique identifier per facility, e.g. ACME |
MSH | 5 | Receiving Application |
|
MSH | 6 | Interface Identifier | NOTES |
MSH | 7 | Date/Time of Message |
|
MSH | 9 | Message Type |
|
MSH | 10 | Message Control ID |
|
MSH | 11 | Processing ID | T for Test, P for Prod |
MSH | 12 | Version ID |
|
|
|
|
|
Segment | Field | Field / Expected Value | Comments |
EVN | 1 | Event Type Code |
|
EVN | 2 | Recorded Date/Time |
|
EVN | 4 | Event Reason Code |
|
|
|
|
|
Segment | Field | Field / Expected Value | Comments |
PID | 1 | Set ID |
|
PID | 2 | Patient ID | Enterprise MRN |
PID | 3 | Patient Identifier List | Facility MRN |
PID | 18 | Patient Account Number |
|
|
|
|
|
Segment | Field | Field / Expected Value | Comments |
PV1 | 1 | Set ID |
|
PV1 | 2 | Patient Class | Values table required |
PV1 | 10 | Hospital Service | Values table required |
PV1 | 18 | Patient Type |
|
PV1 | 19 | Visit Number |
|
|
|
|
|
Segment | Field | Field / Expected Value | Comments |
ORC | 1 | Order Control | Values table required |
ORC | 9 | Date/Time of Transaction |
|
ORC | 10 | Entered By |
|
|
|
|
|
Segment | Field | Field / Expected Value | Comments |
OBR | 1 | Set ID |
|
OBR | 3 | Filler Order Number |
|
OBR | 4 | Universal Service Identifier |
|
OBR | 7 | Observation Date/Time |
|
OBR | 22 | Result Date/Time |
|
OBR | 24 | Diagnostic Service ID |
|
OBR | 25 | Result Status |
|
|
|
|
|
Segment | Field | Field / Expected Value | Comments |
OBX | 1 | Set ID |
|
OBX | 2 | Value Type |
|
OBX | 3 | Observation Identifier |
|
OBX | 5 | Observation Value | Concatenated if possible |
OBX | 7 | Reference Range |
|
OBX | 11 | Observation Result Status |
|
OBX | 14 | Date/Time of Observation |
|
|
|
|
|
Segment | Field | Field / Expected Value | Comments |
NTE | 1 | Set ID |
|
NTE | 2 | Source of Comment |
|
NTE | 3 | Comment |
|
|
|
|
|
Segment | Field | Field / Expected Value | Comments |
TXA | 1 | Set ID |
|
TXA | 2 | Document Type |
|
TXA | 3 | Document Content Presentation |
|
TXA | 4 | Activity Date/Time |
|
TXA | 5 | Primary Activity Provider Code/Name |
|
TXA | 6 | Origination Date/Time |
|
TXA | 8 | Edit Date/Time |
|
TXA | 9 | Originator Code/Name |
|
TXA | 12 | Unique Document Number |
|
TXA | 17 | Document Completion Status |
|