Discussed inquiries w/one OHA AOR last week re: implications of 579. Agreed it would be prudent to provide OHA with refresher training and the opportunity for Q&A.
Considering a phased, multi-prong approach:
[x] reach out to GH's lead data steward to see if there are any upcoming meetings for the bureau's data stewards to get updates/share information/discuss issues; understood these meetings should be happening regularly
[x] provide targeted support to AORs and activity managers at next OHA monthly project management meeting (3/7). The 3/7 meeting would consist of a facilitated discussion to elicit questions, considerations, and scenarios which require guidance and support.
[ ] create document detailing the 3/7 meeting discussion & related questions; draft answers, and liaise with GH lead data stewards and/or 579 agency poc to validate
[ ] Use the question & answer doc generated from the OHA proj. mgmt meeting to provide refresher training to all OHA using examples and scenarios that are directly applicable to our mechs
*COP mtgs may impact attendance of 3/7 project mgmt meeting so will need to determine if we should push to April.
OHA monthly mgmt meeting is also a strategic venue for data governance conversations w/AORs.
Discussed inquiries w/one OHA AOR last week re: implications of 579. Agreed it would be prudent to provide OHA with refresher training and the opportunity for Q&A.
Considering a phased, multi-prong approach:
*COP mtgs may impact attendance of 3/7 project mgmt meeting so will need to determine if we should push to April.
OHA monthly mgmt meeting is also a strategic venue for data governance conversations w/AORs.