Remove all [bracketed] and/or red text before publishing! And also the purple note panels!
[Bracketed] text should be replaced with actual content.
Red text is instructional.
Header Case
Title of page and response option headers should be sentence case (to match how they display in the online system).
Other headers in page that aren’t response options should be title case (Description, On-Screen Instructions, etc.).
Page Properties | ||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|
| ||||||||||||
|
Labels
Use form_field and any relevant segment labels (asc, hospital, nursingfacility, pharmacy)
Use the relevant section label (e.g., surgical_event, event_information)
Note: event-specific fields should be tagged with the associated event type (e.g., surgical_event, fall_event) and NOT with overarching header “event_information”)
Use required if the field is required to submit for all reports.
For example, “it is required if it appears” should not be labeled “required.”
Use essential if the field is a top priority for transferring the data dictionary.
Note: if the field is required, it will already be considered “essential” and doesn’t need a second label.
All “essential” labels will need to be removed before the data dictionary goes live.
Description
[Brief description of what this field is collecting]
Description
Determination of whether or not cause or finding was a root cause.
|
On-Screen Instructions
[Prompt text as it appears in the user interface.]
Prompt Text
...
n/a
Field Type
Include Page | ||||
---|---|---|---|---|
|
Responses
Yes
No
Guide for Use
...
A “root cause” is a condition or circumstance that prompted an action that led to the event or near miss occurrence or harm. The most basic cause(s) are often several steps removed from the action (or inaction) that precipitated the event or near miss. Correction of a root cause within the system can prevent (or significantly reduce the likelihood of) the recurrence of the event or near miss.
History
Start Date | Spring 2012 |
---|---|
End Date | n/a |
Change History | n/a [Month yyyy: brief description of change] [Spring 2012: PSRP implementation] |