Information Object Templates - Documents
Manual and Blog Linked Information Objects
The following list includes standard information "objects" used in Connect Care communications, help, support, and training initiatives. Links are provided for generic and/or CMIO variants of Microsoft Word template documents that can be used when creating new instances of the objects.
Frequently Created:
FAQ - (1-10 pages) Series of common questions about a particular topic, providing an accessible way for prescribers to quickly home in on issues of particular interest.
Memo - Connect Care (HSS Memo - CMIO) - Simple template for memos.
Quick Start Guide (QSG) - When a resource longer than a tip sheet but not as comprehensive as a full guide is needed. Has a table of contents.
Tip - (1-3 pages) Illustrated explanation of how to perform a particular function, always practical and always about how to use the CIS.
Others:
Backgrounder - (1-10 pages) Exploration of the context, history, or other background to a process or issue.
Byte - (~1 page) Brief explanation of a topic, function, concept, or process, serving as a quick orientation for readers unfamiliar with the focus of a Manual section.
Note: This is not a template for a blog post to go on the Connect Care Bytes Blog.
Compact - (1 page) Simple statement of mutual expectations and accountabilities.
Crib-Sheet - (1-5 pages) Summary of technical properties of a tool, setting, or other configuration.
Guide - (1-10 pages) More detailed exploration of the features and controls for a particular function, activity, or information process.
Norm - (5-10 pages) Exploration of expectations of users of the Connect Care CIS respecting a particular functionality.
Principles - (1 page) Summary of key principles guiding the design, build, or use of a particular functionality.
Process - (1-5 pages) Specific steps taken to execute a particular workflow or task.
File Naming Conventions
Connect Care Norms for file naming should be followed when saving any of the above templates as a specific document. If a document's content is unique to the CMIO (prescriber) context and is to be recognizably distinct from similar documents applying to other user populations, then "_cmio" should be appended to the end of the document name (just as used in the templates above).