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.).
...
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.
...
| 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”)
Description
[Brief description of what this field is collecting]patient admitting primary diagnosis.
On-Screen Instructions
[Prompt text as it appears in the user interface.]
Prompt Text
If none or if field does not appear on-screen, put “n/a.” Use “include page” macro where possible (see examples below).
...
Only indicate primary diagnosis. ICD-9 not required.
Field Type
Text (maximum length: 128)
...
| Include Page | ||||
|---|---|---|---|---|
|
History
Start Date |
|---|
2006 | |
End Date | n/a |
|---|---|
Change History |
n/a [Month yyyy: brief description of change]
Spring 2012: PSRP implementation |