...
Remove all [bracketed] and/or red text before publishing! And also this info panel!
[Bracketed] text should be replaced with actual content.
Red text is instructional.
| Page Properties | ||
|---|---|---|
|
...
Field Name
...
[fieldName for Mark, Confluence API]
...
Segment
...
Edition
...
[for Mark, Confluence API]
[1, 2, 3]
[1, 2, 3, 4]
|
...
|
...
...
|
...
...
|
...
[Assignment: blank if IB status is “not started”; use '@' with name for on-going work; replace with initials and date initial build completed for work that is ready for staff review]
...
Staff Review
...
| Status | ||||
|---|---|---|---|---|
|
...
| Status | ||||
|---|---|---|---|---|
|
...
|
...
|
...
|
...
...
|
...
...
|
...
| Status | ||||
|---|---|---|---|---|
|
...
Description
...
|
Description
Date the event was initially submitted.
| Info |
|---|
This field only appears on-screen after the patient safety report is submitted. |
On-Screen Instructions
[Prompt text as it appears in the user interface. If none, put “n/a.” If field does not appear on-screen delete this header.]
Field Type
...
| Include Page |
|---|
...
|
...
|
Field Type
Date (mm/dd/yyyy)
...
Number (minimum value: x; maximum value: x)
...
Text (maximum length: x)
...
Time (hh:mm)
...
True/False
...
Yes/No
...
[OPTION ONE: Answer options with content]
[Table of contents should be limited to the answer options and displayed as a list. Add a dividing line macro below the table of contents.]
| Table of Contents | ||||||||||
|---|---|---|---|---|---|---|---|---|---|---|
|
...
[Each answer option gets an anchor and a heading 2.
...
[Add a page layout of two equal columns below the definition. Inclusions go in the left column, exclusions in the right. Example page: https://oregonpsc.atlassian.net/wiki/pages/resumedraft.action?draftId=2087354595 ]
Includes
Excludes
[If the answer option triggers additional question, add a content by label macro to display all pages that share the form_field label plus the relevant answer option label, possibly plus the relevant segment label, depending on the situation. The macro goes in a single cell table with a light gray fill. The title above the macro should just be table text, bold (no header level), that reads: Event Specific Questions Triggered by Selecting This Event Type]
...
Event Specific Questions Triggered by Selecting This Event Type
| Filter by label (Content by label) | ||||||||
|---|---|---|---|---|---|---|---|---|
|
...
Additional Support
| Filter by label (Content by label) | ||||||||
|---|---|---|---|---|---|---|---|---|
|
[If the answer option is associated with an “faq” item, add a second row to the table and paste in a content by label macro to display all pages that share the faq label plus the relevant answer option label, possibly plus the relevant segment label, depending on the situation. Macro should have title “Additional Support” in the table cell, above it, as with the “Event specific questions” macro.]
[Below the page layout or Content by Label macro(s) (if relevant), include a link to the “top” anchor to take the user back to the responses table of content. Below that, a dividing line before the next answer option, or the next section (probably “Additional Guidance”).]
[OPTION TWO: Answer options without content]
[Just list the available answer options without the answerID and answerCode. Example page: Was a briefing conducted prior to the induction of anesthesia?]
Answer option 1
Answer option 2
Answer option 3
Additional Guidance
...
[In Option 2, this is where one would put an “Event specific questions” Content by Label macro in a single-cell table with light gray fill.]
...
Additional Support
| Filter by label (Content by label) | ||||||||
|---|---|---|---|---|---|---|---|---|
|
History
...
Start Date
...
Guide for Use
| Include Page | ||||
|---|---|---|---|---|
|
History
Start Date | 2012 |
|---|---|
End Date | n/a |
Change History | n/a |
Field Name | datSdate |