forked from uwcirg/ISACC-project
-
Notifications
You must be signed in to change notification settings - Fork 0
/
Copy pathCCguide.html
274 lines (248 loc) · 18.7 KB
/
CCguide.html
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
132
133
134
135
136
137
138
139
140
141
142
143
144
145
146
147
148
149
150
151
152
153
154
155
156
157
158
159
160
161
162
163
164
165
166
167
168
169
170
171
172
173
174
175
176
177
178
179
180
181
182
183
184
185
186
187
188
189
190
191
192
193
194
195
196
197
198
199
200
201
202
203
204
205
206
207
208
209
210
211
212
213
214
215
216
217
218
219
220
221
222
223
224
225
226
227
228
229
230
231
232
233
234
235
236
237
238
239
240
241
242
243
244
245
246
247
248
249
250
251
252
253
254
255
256
257
258
259
260
261
262
263
264
265
266
267
268
269
270
271
272
273
274
<!DOCTYPE HTML>
<html>
<head>
<title>ISACC CARING CONTACTS</title>
<meta charset="utf-8" />
<meta name="viewport" content="width=device-width, initial-scale=1, user-scalable=no" />
<link rel="shortcut icon" type="./image/x-icon" href="./images/Icon.png"/>
<link rel="stylesheet" href="assets/css/main.css" />
<link rel="stylesheet"
href="https://fonts.googleapis.com/css?family=MuseoModerno">
<script src="https://kit.fontawesome.com/0fbfe3d2f7.js" crossorigin="anonymous"></script>
<noscript><link rel="stylesheet" href="assets/css/noscript.css" /></noscript>
<style>
.resource {
color: #b292c8;
}
.faq {
color: #efc542;
}
.story {
color: #96cfcf;
}
.clip-spacer {
clip-path: polygon(100% 0%, 0% 0%, 0% 65%, 1% 64.95%, 2% 64.8%, 3% 64.59999999999999%, 4% 64.3%, 5% 63.9%, 6% 63.45%, 7% 62.9%, 8% 62.25%, 9% 61.55%, 10% 60.8%, 11% 59.95%, 12% 59.05%, 13% 58.1%, 14% 57.1%, 15% 56.05%, 16% 55%, 17% 53.9%, 18% 52.8%, 19% 51.65%, 20% 50.5%, 21% 49.35%, 22% 48.2%, 23% 47.05%, 24% 45.9%, 25% 44.8%, 26% 43.75%, 27% 42.75%, 28% 41.75%, 29% 40.8%, 30% 39.9%, 31% 39.1%, 32% 38.35%, 33% 37.65%, 34% 37.05%, 35% 36.5%, 36% 36.05%, 37% 35.65%, 38% 35.35%, 39% 35.15%, 40% 35.05%, 41% 35%, 42% 35.05%, 43% 35.2%, 44% 35.45%, 45% 35.75%, 46% 36.15%, 47% 36.65%, 48% 37.2%, 49% 37.85%, 50% 38.55%, 51% 39.35%, 52% 40.2%, 53% 41.1%, 54% 42.05%, 55% 43.05%, 56% 44.1%, 57% 45.15%, 58% 46.3%, 59% 47.4%, 60% 48.55%, 61% 49.7%, 62% 50.85%, 63% 52%, 64% 53.15%, 65% 54.25%, 66% 55.35%, 67% 56.4%, 68% 57.45%, 69% 58.4%, 70% 59.35%, 71% 60.2%, 72% 61.05%, 73% 61.8%, 74% 62.45%, 75% 63.05%, 76% 63.6%, 77% 64.05%, 78% 64.40000000000001%, 79% 64.7%, 80% 64.84999999999999%, 81% 65%, 82% 65%, 83% 64.90000000000001%, 84% 64.75%, 85% 64.5%, 86% 64.2%, 87% 63.75%, 88% 63.25%, 89% 62.7%, 90% 62.05%, 91% 61.3%, 92% 60.5%, 93% 59.65%, 94% 58.75%, 95% 57.8%, 96% 56.8%, 97% 55.75%, 98% 54.65%, 99% 53.55%, 100% 52.4%);
background: #f3eefa;
min-height: 48px;
margin-top: -48px;
transform: rotate(180deg);
position: relative;
top: 120px;
}
h1 {
font-weight: 900;
font-family: 'MuseoModerno', serif;
letter-spacing: 0.4rem;
font-size: 5em; }
h2 {
font-family: 'MuseoModerno', serif;
}
h3 {
font-weight: 100;
}
#mybutton {
position: fixed;
top: 4px;
right: 10px;
z-index: 1;
}
.interactive {
border: 1em;
}
</style>
<script type="text/javascript">
function toggle_visibility(id) {
var e = document.getElementById(id);
if(e.style.display == 'block')
e.style.display = 'none';
else
e.style.display = 'block';
}
/* When the user clicks on the button,
toggle between hiding and showing the dropdown content */
function myFunction() {
document.getElementById("myDropdown").classList.toggle("show");
}
// Close the dropdown if the user clicks outside of it
window.onclick = function(e) {
if (!e.target.matches('.dropbtn')) {
var myDropdown = document.getElementById("myDropdown");
if (myDropdown.classList.contains('show')) {
myDropdown.classList.remove('show');
}
}
}
</script>
</script>
</head>
<body class="is-preload">
<!--Menu-->
<section id="sidebar">
<div class="inner">
<nav>
<ul>
<li><a href="index.html" class="smooth-scroll-middle" style="text-decoration: none;">Home</a></li>
<li><a href="GDM1.html" class="smooth-scroll-middle" style="text-decoration: none;">Caring Contacts</a></li>
<li><a href="GDM2.html" class="smooth-scroll-middle" style="text-decoration: none;">Exploring Options</a></li>
<li><a href="CCguide.html" class="smooth-scroll-middle" style="text-decoration: none;">Getting Started</a></li>
<li><a href="other.html" class="smooth-scroll-middle" style="text-decoration: none;">More</a></li>
</ul>
</nav>
</div>
</section>
<section id="hambagaMenu" role="navigation">
<div id="menuToggle">
<!-- A fake / hidden checkbox is used as click reciever, so you can use the :checked selector on it. -->
<input type="checkbox" />
<!-- Some spans to act as a hamburger. They are acting like a real hamburger, not that McDonalds stuff. -->
<span></span>
<span></span>
<span></span>
<!-- Too bad the menu has to be inside of the button but hey, it's pure CSS magic. -->
<ul id="menu">
<li><a href="index.html" class="smooth-scroll-middle" style="text-decoration: none;">Home</a></li>
<li><a href="GDM1.html" class="smooth-scroll-middle" style="text-decoration: none;">Caring Contacts</a></li>
<li><a href="GDM2.html" class="smooth-scroll-middle" style="text-decoration: none;">Exploring Options</a></li>
<li><a href="CCguide.html" class="smooth-scroll-middle" style="text-decoration: none;">Getting Started</a></li>
<li><a href="other.html" class="smooth-scroll-middle" style="text-decoration: none;">More</a></li>
</ul>
</div>
</section>
<!-- Sidebar2 -->
<section id="sidebar2">
<div class="inner">
<nav>
<ul>
<!--<li><a href="#welcome">Welcome</a></li>-->
<li><a href="#number">CC Number and Timing</a></li>
<li><a href="#individual">Individualizing</a></li>
<li><a href="#Principles">Principles</a></li>
<li><a href="#Responses">Responses</a></li>
</ul>
</nav>
</div>
</section>
<!-- Wrapper -->
<div id="wrapper narrow" class="divided" style="width: 85%;">
<!-- One -->
<section class="banner onload-image-fade-in onload-content-fade-right style5 image-position-center content-align-left">
<div class="content">
<h1>Practical Guide </h1>
</div>
<div class="image">
<img src="images/Large header.png" alt="" />
</div>
</section>
<section class="wrapper style1 content-align-left">
<div class="inner">
<h2 id="number">Non-demanding Caring Contacts Number and Timing</h2>
<p>One of your first decisions is<mark style="background-color: Pink;"> how many messages do you want to send, how often do you want to send the messages, and for how long</mark>. These are your choices. You may want to review different approaches to messages and different message content at the VA/DoD Clinical Practice Guidelines for Caring Contacts website (https://mirecc.va.gov/MIRECC/visn19/cpg/recs/13/) In addition, we can provide you with sample lists of messages of different content, frequency, and duration to help you decide. To prevent messages from being perceived by recipients as automated or “spammy,” you may want to send the messages at varying times of day and at varying intervals between messages rather than a set day and time. </p>
<h2>Principles of Non-demanding Caring Contact Message Content</h2>
<p>You should develop your own messages to ensure that they appropriately reflect and respect your local culture(s) and context(s). Here are some thoughts to consider:</p>
<ul>
<li>The most important issue is that the messages follow Motto’s 4 key principles described in the background section to be true to the Caring Contacts model and avoid including things that have any demand to them. For example, advice like “be kind to yourself” or “exercise can be helpful” may be said with supportive intent but often are experienced by stressed or distressed individuals as demands – “if I could be kind to myself, I wouldn’t be suicidal” or “as if I’m not stressed enough - now I’m supposed to exercise?”).</li>
<li>Similarly, appointment reminders can often be a distraction from the Caring Contacts message and a reminder of something they don’t want to or have to do.</li>
<li>It can seem like another simple message conveying welcome, support, or care that doesn’t expect or demand anything from the recipient is not enough. We have found authors often feel compelled to make their messages longer or “more meaningful” in some way, but it is not clear that doing so makes for a better message.</li>
</ul>
<a onclick="toggle_visibility('setting');" href="#setting" class="button fit small"> See Message Examples
</a>
<p id="setting" style="padding: 1em; display: block; background-color: pink;">
Lorem ipsum dolor sit amet, consectetur adipisicing elit, sed do eiusmod
tempor incididunt ut labore et dolore magna aliqua. Ut enim ad minim veniam,
quis nostrud exercitation ullamco laboris nisi ut aliquip ex ea commodo
consequat. Duis aute irure dolor in reprehenderit in voluptate velit esse
cillum dolore eu fugiat nulla pariatur. Excepteur sint occaecat cupidatat non
proident, sunt in culpa qui officia deserunt mollit anim id est laborum.
</p>
<p>Here are some ideas that we have found helpful in crafting Caring Contacts</p>
<ul>
<li>The general approach in Caring contacts is to welcome and invite replies to messages but not to expect or demand this – so you may want to include comments such as, “if you would like to respond, I’d be happy to hear from you” or equivalent in your CarePlan.</li>
<li>Depending on the constraints of your chosen implementation platform, we encourage you to ask the recipient to respond just to their first message so you know they received it and that they can reply. Then you can, in turn, respond with an individualized response to demonstrate that you can receive and will respond personally to their messages.</li>
<li>We generally do not continue reminding recipients to reply to the first Caring Contact (beyond the original ask of them to confirm receipt of the first message) as it could be demanding.</li>
<li>Since messages will be coming from an unrecognized number rather than an individual or agency phone number, you may want to explain this to the recipient and even have them add the number from the initial contact to their Address Book with yours or your agency’s name so they recognize it in the future.</li>
</ul>
<h3 id="individual">Reminders for individualizing/starting the Care Plan</h3>
<p>Review all of the dates and times of the messages on the CarePlan to be sure that they fall on the days and time windows your Caring Contacts team wants them to be sent. </p>
<ul>
<li>Time and date CAN be edited for any message to individualize it for a recipient’s needs (e.g., they work nights and you know they never wake up before noon). Be sure to save the changes by clicking the “DONE” button at the bottom of the screen.</li>
<li><mark style="background-color: Pink;">IMPORTANT: Please make sure that all of the messages are delivered within the 3 months following the beginning of the recipient’s CarePlan. </mark></li>
</ul>
<p>Remember that we want the messages to appear as if they are sent by your team and come across as natural as possible. Avoid having all of your messages come on the same day or time each week as this can look like spam.</p>
<p>Important reminders:</p>
<ul>
<li>You might want to make sure that if the recipient’s birthday falls during the projected Caring Contacts period, one of the existing scheduled messages is replaced by their birthday message. If their birthday falls on a weekend, your team may decide to reset the date for the message a day or two early and adjust the text to say, “Happy early birthday!...” </li>
<li>If any relevant holidays or seasonal messages will occur during the recipient’s study period, those messages can also replace the nearest existing scheduled message. Again, this is to ensure that all recipients receive the same number of messages. Check to see if any of the messages written by your team will apply during the recipient’s study period and schedule them accordingly!</li>
</ul>
<h2 id="Principles">Principles of Responding to Caring Contact Replies</h2>
<p>Your agency is responsible for monitoring and responding to all incoming messages from your recipients (what we call “replies” to differentiate from what you send which we call “responses”). Here are some points to consider in planning your Caring Contacts program: </p>
<h3>Monitoring</h3>
<ul>
<li>How often will notifications be checked? Who will be responsible for checking them?</li>
<li>Will one person or multiple people be notified?</li>
<li>If a team member is sick or on vacation, who will cover for them?</li>
<li>If/how would you like to communicate among your Caring Contacts team about who is responding to the message?</li>
</ul>
<h2 id="Responses">Responses to the Recipients’ Replies</h2>
<ul>
<li>Replies to at least some of the pre-programmed Caring Contacts are expected. In our experience the vast majority of responses will reflect gratitude (“thanks so much”) or reciprocity (“I hope you have a good day too”) or something general like a thumb's up emoji.</li>
<li>In the minority of situations, the reply will indicate distress or request assistance. This may occur when they are getting Caring Contacts and no other services from your agency, so this offers an opportunity to support someone who is in distress that might otherwise be missed.</li>
<li><b>Not responding to a recipient’s reply may well be taken as either uncaring or that Caring Contacts are from a bot, spam, or otherwise disingenuous, so it is important to reply.</b></li>
<li>Responses do not have to be immediate. It is important to orient recipients at the beginning of the program about how long they can expect to wait for a response. It can also be strategic to let time pass before responding if the agency is less interested in getting into a text dialogue with the recipient. It is common in our programs to hold “by next business day” as a standard for a reply that does not indicate distress. Programs vary in how quickly a response is expected if the message indicates distress or risk. Agencies are advised to follow their existing crisis response protocols.</li>
<li>Caring Contacts is a behavioral health intervention but not intended to function as a crisis line . Recipients should be oriented up front about when to expect a response and when not to. It is important to communicate in advance what recipients should do if they need help at a time no one can respond. We have found that recipients are flexible and respectful of this, and it has not been an issue. </li>
</ul>
<h3 id="Crisis Intervention">Crisis Intervention</h3>
<ul>
<li>In the event of a reply indicating suicidality or another crisis, how will this be handled?</li>
<li>Are there specific protocols you expect to be followed or should Caring Contacts program staff follow general protocols for crisis intervention or high-risk circumstances?</li>
</ul>
<h3 id="Documentation">Documentation</h3>
<p>This is important to think through if you want to be consistent across your Caring Contacts team.</p>
<p>Do you want to document Caring Contacts anywhere other than the platform you're using?</p>
<ul>
<li>In a healthcare environment, it may be important to document in the medical or electronic health record. If so, do you want to document every Caring Contact interaction with a patient? Or a more limited set of information such as the patient’s start and end date of the Caring Contacts intervention. </li>
<li>It might also be important to document any distressed or high risk replies and how they were handled.</li>
</ul>
<h3>Culturally adapting CC content [taken from the CARE sop, need to expand upon, maybe link to the CARE papers]: </h3>
<p>Messages will incorporate heritage languages and customs. For example, greetings and some closings in messages will use words from American Indian and Alaska Native languages that are commonly used in the participating communities. In areas where multiple heritage languages are spoken, such as Anchorage, site partners will use the language preferred by the participant. If the researcher is AN/AI, they may use their own heritage language in message greetings. At baseline, participants will be asked if they prefer a specific language or greeting. For example, some Elders may prefer a formal greeting in their heritage language, or in some communities, participants may need a specific greeting based on age and/or gender. Site partners will do as the participant prefers. Messages will contain language that may be considered spiritual (e.g., “sending good energy”) but is not specific to any religious or spiritual tradition. These messages will refer instead to general pan-human values of care, support, and inclusion. </p>
</div>
</section>
<span class="clip-spacer"></span>
<!-- Seven -->
<section class="wrapper style1 align-center" style="background: #E3F1F1;">
<div class="inner medium">
<div class="items style3 medium">
<section>
<a href="https://www.washington.edu/" target="_blank"><img src="images/uwLogo-transparentbg.png" class="image fit" alt="UW logo" /></a>
</section>
<section>
<a href="https://www.cirg.washington.edu/" target="_blank"><img src="images/CIRG_logo.png" class="image fit" style="padding: 3em;" alt="CIRG logo" /></a>
</section>
<section>
<a href="https://www.uwcspar.org/" target="_blank"><img src="images/CSPAR-logo-4-10-20-for-light-background.png" class="image fit" alt="CSPAR foundation logo" /></a>
</section>
</div>
</div>
</section>
<!-- Footer -->
<footer class="wrapper style1 align-center" style="background-color: #34A9C7 !important; color: #ffffff !important;">
<div class="inner">
<h2 style="color: #ffffff;">Contact Us!</h2>
<hr/>
<ul class="icons">
<li>email: isaccsupport@uw.edu</li>
<!--<li>phone: ---</li>-->
</ul>
<p>© 2024 University of Washington All rights reserved</p>
</div>
</footer>
</div>
<!-- Scripts -->
<script src="assets/js/jquery.min.js"></script>
<script src="assets/js/jquery.scrollex.min.js"></script>
<script src="assets/js/jquery.scrolly.min.js"></script>
<script src="assets/js/browser.min.js"></script>
<script src="assets/js/breakpoints.min.js"></script>
<script src="assets/js/util.js"></script>
<script src="assets/js/main.js"></script>
</body>
</html>