Nursing Requirements
v.1 May 16, 2011
Prioritization of Requirements
The following priority codes described in the table below are used in this document to indicate the relative importance of a requirement to the final product to be produced.
Priority / Meaning /A / Essential
B / Important
C / Nice to have
8.2 Other Requirements
In addition to the priority field in the requirement tables, three other fields are present in both the requirements tables. They are: “Avail Today”, “Status”, and “Phase”. The meanings of these fields are as follows:
Process / Meaning /IT / Requirement requires engaging IT resources (people and software)
Role / The requirement requires it to be a role or responsibility that can be fulfilled by Nursing staff or any other role
Values/Policy/ Norm / These requirements/rules guide your behavior or business
Organizations / Does the requirements affect the organization
Status / Meaning /
√ / The requirement or rule has been reviewed and accepted in a group review session
X / The requirement or rule has been reviewed and accepted via individual review
? / Further definition is required to make the requirement or rule unambiguous
Requirement or rule has yet to be reviewed
Phase / Meaning /
1 / This requirement will be met in the first phase
N / This requirement will be met in phase n
none / This requirement will not be met
Requirement has not been dispositioned yet
/ Specific Requirements /
ID / Description / Priority / Process / Bus. Case / Req Areas / Status / Phase /
8.3.1 / Flexibility / Customization
Ability to restrict changes to global User Interface
(To maintain standards of template and interface through security) / a / IT, Role, Org, Norm
Ability to access content from outside the firewall
(Staff desire to view schedules from home.) / c / IT, Role, Norm
Ability to comment/provide feedback
(For ongoing improvement) / a / IT, Role
Ability to integrate code to add widgets and code reuse)
(To avoid duplication of content in various sections) / a / IT
Ability to measure traffic and usage statistics (built-in for users)
(Ongoing improvement – take down content not being utilized) / a / IT, Role
Ability to share components (nav., etc) across sites
(Consistent One Mayo look and feel) / a / IT, Role, Org
Ability to show logged-in state clearly
(In case of web portal capability – who is logged on would be important) / b / IT, Org,
Access control
(Editor access (editing) and end-user access (viewing) levels of editing depending on access type) / a / IT, Org, Role, Norm
Archive histories; edit and content change tracking
(required for legal purposes for certain content; have defined content types with archival requirements) / a / IT, Role, Norm
Can integrate with other publishing tools
(examples: quarterly widget, calendar widget, committee widget) / a / IT, Org, Role,
Norm
Content accountability
(author is identified and required to regularly review content by system notification and alerts) / A+ / IT, Org, Role
Current content key/FTP/access maintenance
(need to be able to manage user access at the local level) / a / IT
Custom forms integration
(this will be taken care of through the Eforms program) / c / Role
Develop and implement dynamic widgets
(we need dynamic update of content that may exist elsewhere – example, people information; in addition, the ability to add dynamic widgets in the future would be required based on role-based tasks) / b / IT, Org, Role
Develop flexible alert box system
(Nursing alerts such as Joint Commission or Medication/Practice alerts specific to nursing requires this) / a / IT, Org, Role,
Norm
Ease of transfer from one user / maintainer to another (switching usernames, permissions granularity)
(ex: If a CNS transfers to an NAS position, that content must be managed by the new CNS replacement. Each piece of content must have an owner.) / a / IT, Org, Role, Norm
Educational personal portfolio – interface to educational personal portfolio (portal to hold existing reports in one location unless institutional educational initiative will address this)
(Nurse needs to be able to keep track of her/his own requirement for licensing – competencies, annual training, required training) / a / IT, Org, Role, Norm
Enable RSS feeds
(Allow for Nursing newsletter(s) to have RSS for communication to personal devices) / c / IT, Org, Role
Existing templates or front-end package
(If a request for new content (patient education) is submitted, there is a template existing for it to go into) / a / IT, Role
Future expandability (designed for CMS with inheritance)
(Allows for site to expand and still work with the CMS) / a / IT
Group hierarchy for permissions, access, ease of setup and maintenance
(Identify different groups and have the security managed by groups rather than individual users, including selection of templates) / a / IT
Grouping of users into content management roles and the ability to assign publishing permissions to content / content categories are user roles / group roles
(Will need to identify the groups and describe what security is assigned to each) / a / IT, Role
LDAP integration (role management) or active directory
(This is important for personal portal which reduces the duplication of already existing data instead of manually storing user information.) / b / IT, Org, Role
Maintenance and ease of global content changes
(When JCAHO changed to Joint Commission, we should be able to update the content in all of Nursing) / a / IT, Org, Role
Allow dynamic leader information to display for each work unit
(provide summary directory information based on role and work area; Clint is working on this – interface with Quarterly directory) / b / IT, Org, Role
Page components (blocks) can be pushed from central
(If new section is required on each work unit page, have that pushed centrally rather than each work unit page (128 areas)) / a / IT, Org, Role
Personalization (my nursing page)
(Allow personalization because bookmarks/favorites and other content related to their role does not current follow them from computer to computer) / b / IT, Org, Role
Support technical and editorial process around tool
(Require central support in case someone leaves – can’t be a rogue system that is not institutionally supported) / a / IT, Org, Role, Norm
Syndicated content (one to many)
(Example: content related to IV Administration should be able to be syndicated to both the medication page and guidelines page) / a / IT
Workflow for content approval
(Example: work unit routines must be reviewed and approved annually) / a / IT, Norm
Workflows resulting in content creation in a process of supervised publishing, for example a content creator submits a story which is published only after the copy editor reviews it and editor-in-chief approves it
(Content related to Practice must be approved by an appointed committee – one cannot just publish information about patient care without proper content approval.) / a / IT, Norm
8.3.2 / Technical
Audit logging
(Due to legal reasons, we need to able to run reports on who edited specific content and when to assure proper approval) / a / IT, Norm
Simple navigation, e.g. auto created breadcrumb links
(Users understand where they are and where they came from to assist with navigation)
Easy access or one click access to unit pages/work areas / b(test) / IT
Collaborative work spaces
(all sites nursing staff should be able to share documents and work collaboratively on projects) – Interface to collaboration tool)
Create a comment engine (allow users to post comments on posted content)
“Our neighborhood” (examples of possible content could include staff profiles, social) – allows Nursing staff to create a sense of community – share pictures from work unit social events without having it be searchable outside of that area) / b / IT , Norm, Org
Content Management Tool
(to assure content accuracy, currency, search ability, and accountability for extremely high volume nursing specific content) / A+++ / IT, Org, Role, Norm
Create backups of system
(In case of accidental deletions or errors)
Rollback – ability to revert back pages to previous pages / a / IT
Identity Management
(See LDAP info in previous section: This is important for personal portal which reduces the duplication of already existing data instead of manually storing user information.) / a / IT, Org
Index nursing-related sites outside of nursing directories in nursing search (moderate sedation)
(Nurses need to have access to information which isn’t part nursing content and not able to search and find) / a / IT, Org, Norm
Search engine optimization/Mandatory key words
(Able to search and find relevant information; Advance search, like quarterly) / A++ / IT, Org, Norm
Meets Mayo Clinic’s Information security Policy
(To meet legal requirements) / a / IT, Org, Role, Norm
Must function under supported platforms supported by Mayo Clinic
(Is an understanding if the job is contracted outside of Mayo) / a / IT
Must support Mayo supported database platforms on the back-end / a / IT
Open APIs[1]
1Open API (often referred to as OpenAPI) is a word used to describe sets of technologies that enable websites to interact with each other by using SOAP, Javascript and other web technologies. While its possibilities aren't limited to web-based applications, it's becoming an increasing trend in so-called Web 2.0 applications. The term API stands for Application programming interface.
Example: community page (social) / b+ / IT
Product generates Web sites/content that is compliant with Mayo Clinic’s accessibility standards
(To protect us for usability and legal concerns) / a / IT, Norm
Product generates Web sites/content that is compliant with W3C standards for CSS and XHTML
(Follows Mayo technical standards) / a / IT
Scalable to meet enterprise requirements
(In the future, if we combine all Mayo Nursing sites, it must be able to bring those sites together) / a / IT, Org, Norm
Spell check
(Content editor – but assure both regular and medical spell check if possible) / a / IT
Support development/staging environments
(possibly using socrates for the code shop?) / a / IT
Supports multiple character sets on web pages
(Due to many manufacturing labels and trademarks, may be legally necessary) / a / IT
WYS/WYG content editor
(Allow end user to edit content based on access control but not requiring author to use html) / a / IT
8.3.3 / Functionality
Auto log into system (e.g. SharePoint)
(user frustration of multiple log ins; staff nurses have very little time to find what they need) / b / IT
Content editor (according to security level):
Submit content for approval
Request editorial review (reference editorial guidelines)
Format content (Meeting user Interface and brand guidelines)
Save content
Create new pages
Delete pages
Create web links
Integrate “rich content” (multimedia and flash…etc) into pages
Publish/Unpublish content
View unpublished content
Contact/Communicate with members of creation chain/workflow
Ability to set/enforce content and scripting policies (not sure this is possible) / a / IT
Ability to define and manage metadata
Set embargo, next review and expiration dates / A+ / IT
Export/Import data/content / a / IT
Generate traffic report/stats / a / IT
Support standalone web tools (calculators, calendar, newsletter, etc.) / A+ / IT
Maintain workflows
(Allows for multiple approvals of content; system generated notices) / A+ / IT
Create/Manage user friendly URLS (just like the UCM) / b / IT
Allow site visitors to rate content (not visible on site) / b / IT
Auto link-check integrity / a / IT
Develop online events system (really cool calendar – user friendly – like Google) / b+ / IT
CMS sends bounced emails to Deb Lafferty.
8.3.4 / Implementation
Change default to DON for EEDs (at least provide portion of main page for nursing) – allow more personalization in patient care mode (favorites) / b / IT
My bookmarks and profile follows me / a / IT
Create C-Name for Nursing / a / IT
8.3.5 / Usability (Tom)
Incorporate Mayo Usability Principles (see attached) / a
Mitigate problems/Issues document from usability study (see attached) / a
Use web style guide and other user guidelines as appropriate / a
User terminology/language / a
Ease of use for non-technical / a
Understand difference between ambulatory and inpatient / a
8.3.6 / Intranet components / widgets
Search / A++ / IT
Newsletter (eventually use the UCM newsletter tool) / a / IT, Org, Norm, Role
Weather / c / IT
Social Media – Face book, Yammer, Blog – specify need/audience; NO PRACTICE INFO RELATED TO PATIENTS OR WORK AREA EXAMPLES / b / IT
Develop poll functionality / b / IT
Calendars, ease of setup, use, and maintenance / a / IT, Org, Norm, Role
Employee Directory – to unit level, specific needs (quarterly beta results page) / a / IT, Org, Norm, Role
Organizational chart / a / IT, Org, Norm, Role
Committee agenda and minutes – committee app / a / IT, Org, Norm, Role
Forms (eForms program) / a / IT, Org, Norm, Role
Scheduling tool/Absence management / b / IT, Org, Norm, Role / 3
Work unit specific frequently used telephone numbers (role based, not person-based) (including
Service paging (maintenance, housekeeping, on-call, VAD, Hem1 service, etc.)) / a / IT, Org, Norm, Role
Feedback widget / a / IT
Patient event dashboard (work unit pages) / a / IT
Status Panel (home page only) / a / IT
8.3.7 / Layout / Design (Gianna, John)
Separation of contents semantic layer from its layout (for example, CMS may automatically set the color, fonts, etc. / A+
Design and layout of the intranet consistent across different sections / a
Professional overall appearance / a
Consistent navigation and content layout / a
Presentation of multimedia consistent with overall look and feel / a
Simple yet pretty / a
Standard format for policies, procedures, “official” content / a
Ability to create different page templates / a
8.3.8 / Maintenance
User friendly content management system
(administrative assistants will likely be high users of system, not programmers or coders) / A+ / IT
Consider a daily section to keep things fresh for employees/Rotating Content (moving picture) Top Ten accessed info or links (auto generated). / a / IT
Searchable Archive and Change tracking
(ability to search the archive; sometimes archives are not searchable) / a / IT, Norm
Assessment
Evaluation
Reporting
Communication/Notification
[1] Open API (often referred to as OpenAPI) is a word used to describe sets of technologies that enable websites to interact with each other by using SOAP, Javascript and other web technologies. While its possibilities aren't limited to web-based applications, it's becoming an increasing trend in so-called Web 2.0 applications. The term API stands for Application programming interface.