HALE INTEGRATIVE WELLNESS
DOC-STD-001Â
HIW Enterprise Records & Information Governance StandardÂ
Document ID: DOC-STD-001Â
Title: Enterprise Records Management & Information Governance StandardÂ
Version: 1.0Â
Classification: Enterprise Controlled StandardÂ
Owner: Executive Governance CouncilÂ
System Owner: HIW Governance OfficeÂ
Applies To: All HIW Business UnitsÂ
1. PurposeÂ
This standard establishes a single enterprise framework governing:Â
-
Document CreationÂ
-
Records ManagementÂ
-
Metadata StandardsÂ
-
SharePoint ArchitectureÂ
-
Document ControlÂ
-
Approval WorkflowsÂ
-
Retention & DispositionÂ
-
Information SecurityÂ
-
Audit RequirementsÂ
-
Exception ManagementÂ
-
Escalation ProceduresÂ
This standard serves as the parent authority for:Â
HIW ConstitutionÂ
CSS FrameworkÂ
LACS FrameworkÂ
Brand Governance FrameworkÂ
Operations Governance FrameworkÂ
Technology Governance FrameworkÂ
2. Governance HierarchyÂ
HIW ConstitutionÂ
↓Â
Enterprise Governance StandardsÂ
↓Â
Enterprise Records Standard (DOC-STD-001)Â
↓Â
PoliciesÂ
↓Â
SOPsÂ
↓Â
ProtocolsÂ
↓Â
ProceduresÂ
↓Â
FormsÂ
↓Â
TemplatesÂ
3. Information Classification ModelÂ
Level 1 - PublicÂ
Examples:Â
-
Marketing brochuresÂ
-
Published contentÂ
-
Public educational resourcesÂ
Retention: According to business needÂ
Â
Level 2 - InternalÂ
Examples:Â
-
Team proceduresÂ
-
Department documentationÂ
-
Training resourcesÂ
Retention: 7 YearsÂ
Â
Level 3 - ConfidentialÂ
Examples:Â
-
Strategic plansÂ
-
Financial planningÂ
-
Executive recordsÂ
Retention: Permanent unless supersededÂ
Â
Level 4 - RestrictedÂ
Examples:Â
-
Clinical informationÂ
-
Client recordsÂ
-
Legal investigationsÂ
-
Performance reviewsÂ
Retention: Governed by applicable policies and legal requirementsÂ
4. Enterprise Metadata ArchitectureÂ
All controlled documents shall inherit metadata from enterprise content types.Â
Â
GLOBAL METADATAÂ
Required for ALL Content TypesÂ
Metadata FieldÂ
TypeÂ
RequiredÂ
Document IDÂ
TextÂ
YesÂ
Document TitleÂ
TextÂ
YesÂ
VersionÂ
TextÂ
YesÂ
StatusÂ
ChoiceÂ
YesÂ
Document OwnerÂ
PersonÂ
YesÂ
Document AuthorÂ
PersonÂ
YesÂ
DepartmentÂ
ChoiceÂ
YesÂ
ClassificationÂ
ChoiceÂ
YesÂ
Effective DateÂ
DateÂ
YesÂ
Review DateÂ
DateÂ
YesÂ
Next Review DateÂ
DateÂ
YesÂ
Retention CategoryÂ
ChoiceÂ
YesÂ
Legal HoldÂ
Yes/NoÂ
YesÂ
Approval StatusÂ
ChoiceÂ
YesÂ
​
3. Information Classification ModelÂ
Level 1 - PublicÂ
Examples:Â
-
Marketing brochuresÂ
-
Published contentÂ
-
Public educational resourcesÂ
Retention: According to business needÂ
Â
Level 2 - InternalÂ
Examples:Â
-
Team proceduresÂ
-
Department documentationÂ
-
Training resourcesÂ
Retention: 7 YearsÂ
Â
Level 3 - ConfidentialÂ
Examples:Â
-
Strategic plansÂ
-
Financial planningÂ
-
Executive recordsÂ
Retention: Permanent unless supersededÂ
Â
Level 4 - RestrictedÂ
Examples:Â
-
Clinical informationÂ
-
Client recordsÂ
-
Legal investigationsÂ
-
Performance reviewsÂ
Retention: Governed by applicable policies and legal requirementsÂ
Â
4. Enterprise Metadata ArchitectureÂ
All controlled documents shall inherit metadata from enterprise content types.Â
Â
GLOBAL METADATAÂ
Required for ALL Content TypesÂ
Metadata FieldÂ
TypeÂ
RequiredÂ
Document IDÂ
TextÂ
YesÂ
Document TitleÂ
TextÂ
YesÂ
VersionÂ
TextÂ
YesÂ
StatusÂ
ChoiceÂ
YesÂ
Document OwnerÂ
PersonÂ
YesÂ
Document AuthorÂ
PersonÂ
YesÂ
DepartmentÂ
ChoiceÂ
YesÂ
ClassificationÂ
ChoiceÂ
YesÂ
Effective DateÂ
DateÂ
YesÂ
Review DateÂ
DateÂ
YesÂ
Next Review DateÂ
DateÂ
YesÂ
Retention CategoryÂ
ChoiceÂ
YesÂ
Legal HoldÂ
Yes/NoÂ
YesÂ
Approval StatusÂ
ChoiceÂ
YesÂ
Â
5. SharePoint Content Type MappingÂ
Enterprise Content Type HierarchyÂ
Plain TextÂ
HIW Controlled DocumentÂ
│Â
├── HIW Governance DocumentÂ
│ ├── PolicyÂ
│ ├── SOPÂ
│ ├── StandardÂ
│ ├── CharterÂ
│Â
├── HIW Operational DocumentÂ
│ ├── ProcedureÂ
│ ├── WorkflowÂ
│ ├── ChecklistÂ
│ ├── FormÂ
│ ├── TemplateÂ
│Â
├── HIW Clinical DocumentÂ
│ ├── AssessmentÂ
│ ├── ProtocolÂ
│ ├── GuidelineÂ
│ ├── Care PlanÂ
│Â
├── HIW Communications DocumentÂ
│ ├── CampaignÂ
│ ├── NewsletterÂ
│ ├── Website ContentÂ
│ ├── Social ContentÂ
│Â
└── HIW Records DocumentÂ
├── AuditÂ
├── ReportÂ
├── Meeting RecordÂ
├── Executive RecordÂ
Â
6. Metadata Mapping MatrixÂ
SOP Content TypeÂ
Required MetadataÂ
Plain TextÂ
Document IDÂ
DepartmentÂ
OwnerÂ
ApproverÂ
VersionÂ
Effective DateÂ
Review DateÂ
Retention CategoryÂ
ClassificationÂ
OptionalÂ
Plain TextÂ
Related PolicyÂ
Process AreaÂ
Framework AlignmentÂ
Â
Assessment Content TypeÂ
Required MetadataÂ
Plain TextÂ
Assessment TypeÂ
Clinical AreaÂ
LACS ArchetypeÂ
Journey StageÂ
OwnerÂ
Retention CategoryÂ
Â
Campaign Content TypeÂ
Required MetadataÂ
Plain TextÂ
Campaign NameÂ
Audience TypeÂ
ChannelÂ
Campaign Start DateÂ
Campaign End DateÂ
KPI CategoryÂ
Â
Protocol Content TypeÂ
Required MetadataÂ
Plain TextÂ
Protocol CategoryÂ
Clinical DisciplineÂ
LACS AlignmentÂ
Review FrequencyÂ
Â
7. Enterprise Approval ModelÂ
Approval Tier StructureÂ
Tier 1Â
Low Risk DocumentsÂ
Examples:Â
-
TemplatesÂ
-
ChecklistsÂ
-
Internal ProceduresÂ
Approval Required:Â
Plain TextÂ
Department ManagerÂ
Â
Tier 2Â
Medium Risk DocumentsÂ
Examples:Â
-
SOPsÂ
-
AssessmentsÂ
-
Training MaterialsÂ
Approval Required:Â
Plain TextÂ
ManagerÂ
+Â
DirectorÂ
Â
Tier 3Â
High Risk DocumentsÂ
Examples:Â
-
Clinical ProtocolsÂ
-
Organizational PoliciesÂ
-
Governance StandardsÂ
Approval Required:Â
Plain TextÂ
DirectorÂ
+Â
Executive SponsorÂ
Â
Tier 4Â
Enterprise Risk DocumentsÂ
Examples:Â
-
ConstitutionÂ
-
Strategic PlansÂ
-
Enterprise StandardsÂ
Approval Required:Â
Plain TextÂ
Executive CouncilÂ
Â
8. Enterprise Exceptions ProcessÂ
DefinitionÂ
An exception exists whenever a document cannot comply with one or more requirements established in this standard.Â
Examples:Â
-
Missing metadataÂ
-
Emergency publicationÂ
-
Delayed reviewÂ
-
Temporary policy varianceÂ
-
Compliance conflictÂ
-
Technology limitationsÂ
Â
Exception Request FormÂ
Required Fields:Â
Plain TextÂ
Exception IDÂ
RequestorÂ
Document IDÂ
ReasonÂ
Business ImpactÂ
Risk AssessmentÂ
Requested DurationÂ
Corrective Action PlanÂ
Executive SponsorÂ
Â
Exception Approval AuthorityÂ
Exception TypeÂ
ApproverÂ
DepartmentalÂ
Department DirectorÂ
ClinicalÂ
CCCOÂ
GovernanceÂ
Governance CommitteeÂ
EnterpriseÂ
Executive CouncilÂ
Â
Exception Status ValuesÂ
Plain TextÂ
ProposedÂ
Under ReviewÂ
ApprovedÂ
DeniedÂ
ExpiredÂ
ClosedÂ
Â
9. Escalation FrameworkÂ
Level 1 EscalationÂ
Trigger:Â
Plain TextÂ
Approval overdue > 5 daysÂ
Escalate To:Â
Plain TextÂ
Department ManagerÂ
Â
Level 2 EscalationÂ
Trigger:Â
Plain TextÂ
Approval overdue > 10 daysÂ
Escalate To:Â
Plain TextÂ
Department DirectorÂ
Â
Level 3 EscalationÂ
Trigger:Â
Plain TextÂ
Approval overdue > 15 daysÂ
Escalate To:Â
Plain TextÂ
CCCO / Executive SponsorÂ
Â
Level 4 EscalationÂ
Trigger:Â
Plain TextÂ
Approval overdue > 30 daysÂ
Escalate To:Â
Plain TextÂ
Executive Governance CouncilÂ
Â
10. Clinical Escalation PathÂ
Plain TextÂ
Clinical ReviewerÂ
↓Â
Patient Education ManagerÂ
↓Â
Clinical Marketing DirectorÂ
↓Â
Chief Clinical Communications OfficerÂ
↓Â
Executive Leadership CouncilÂ
Used for:Â
-
Clinical disputesÂ
-
Educational inaccuraciesÂ
-
LACS conflictsÂ
-
Safety concernsÂ
Â
11. Governance Escalation PathÂ
Plain TextÂ
Document OwnerÂ
↓Â
Department ManagerÂ
↓Â
Department DirectorÂ
↓Â
Governance OfficeÂ
↓Â
Executive Governance CouncilÂ
Used for:Â
-
Policy conflictsÂ
-
Standards interpretationÂ
-
Compliance violationsÂ
-
Audit findingsÂ
Â
12. Automated SharePoint Escalation WorkflowÂ
Day 0Â
Plain TextÂ
Approval Request SentÂ
Day 5Â
Plain TextÂ
Reminder EmailÂ
Day 10Â
Plain TextÂ
Manager NotificationÂ
Day 15Â
Plain TextÂ
Director NotificationÂ
Day 30Â
Plain TextÂ
Executive EscalationÂ
Day 45Â
Plain TextÂ
Document Automatically Flagged as Governance RiskÂ
Â
13. Enterprise Records Retention AuthorityÂ
Permanent RetentionÂ
Plain TextÂ
ConstitutionÂ
Strategic PlansÂ
PoliciesÂ
StandardsÂ
Executive RecordsÂ
Master RegistersÂ
Audit LogsÂ
Change HistoriesÂ
Â
10-Year RetentionÂ
Plain TextÂ
AssessmentsÂ
ProtocolsÂ
Approval RecordsÂ
Clinical Governance DocumentsÂ
Quality ReviewsÂ
Â
7-Year RetentionÂ
Plain TextÂ
TrainingÂ
ReportsÂ
Operational ProceduresÂ
Campaign Performance ReportsÂ
Â
5-Year RetentionÂ
Plain TextÂ
Marketing CampaignsÂ
Published CommunicationsÂ
Archived ContentÂ
Â
14. Enterprise SharePoint Hub ArchitectureÂ
Plain TextÂ
HIW Governance HubÂ
│Â
├── Executive GovernanceÂ
├── Enterprise StandardsÂ
├── PoliciesÂ
├── SOPsÂ
├── Clinical Support SystemÂ
├── LACS FrameworkÂ
├── Brand ManagementÂ
├── OperationsÂ
├── Human ResourcesÂ
├── FinanceÂ
├── Information TechnologyÂ
├── Records CenterÂ
├── Audit CenterÂ
├── Archive CenterÂ
└── Knowledge CenterÂ
Â
Enterprise Design RecommendationÂ
For HIW's long-term growth, create one centralized Content Type Gallery and one centralized Term Store at the SharePoint tenant level. Every future library, whether HIW, CSS, LACS, Brand, Operations, HR, Finance, or Clinical Services, should inherit its metadata from these master definitions. This creates a true enterprise governance model where documents, workflows, records retention, reporting, and Power Automate approvals all operate from a single source of truth.Â
TERM-STD-001Â
HIW Enterprise Term Store ArchitectureÂ
Purpose: Create a single managed metadata taxonomy for all SharePoint sites, document libraries, Power Automate workflows, Power BI reports, and governance systems.Â
Â
Term Group StructureÂ
Plain TextÂ
HIW Enterprise MetadataÂ
│Â
├── GovernanceÂ
├── DepartmentsÂ
├── Document ControlÂ
├── Clinical ServicesÂ
├── LACSÂ
├── Marketing & CommunicationsÂ
├── Human ResourcesÂ
├── OperationsÂ
├── FinanceÂ
├── TechnologyÂ
├── Quality & AuditÂ
├── Retention & RecordsÂ
└── Security & ComplianceÂ
Â
1. Governance Term SetÂ
Plain TextÂ
GovernanceÂ
│Â
├── ConstitutionÂ
├── PolicyÂ
├── StandardÂ
├── SOPÂ
├── ProcedureÂ
├── ProtocolÂ
├── CharterÂ
├── FrameworkÂ
├── GuidelineÂ
├── RegisterÂ
├── FormÂ
├── TemplateÂ
├── ChecklistÂ
└── WorkflowÂ
Used By:Â
-
Document TypeÂ
-
Governance ReportingÂ
-
Records ManagementÂ
Â
2. Department Term SetÂ
Plain TextÂ
DepartmentsÂ
│Â
├── ExecutiveÂ
├── Clinical ServicesÂ
├── CSSÂ
├── LACSÂ
├── MarketingÂ
├── OperationsÂ
├── Human ResourcesÂ
├── FinanceÂ
├── Information TechnologyÂ
├── ComplianceÂ
├── Quality AssuranceÂ
└── Research & DevelopmentÂ
Used By:Â
-
Department MetadataÂ
-
Security GroupsÂ
-
ReportingÂ
Â
3. LACS Term SetÂ
Plain TextÂ
LACSÂ
│Â
├── ArchetypesÂ
│ ├── Exhausted AchieverÂ
│ ├── Overwhelmed CaregiverÂ
│ ├── Stalled PerformerÂ
│ ├── Health RebuilderÂ
│ ├── Balanced OptimizerÂ
│ ├── Lifestyle NavigatorÂ
│ ├── Purpose SeekerÂ
│ └── Resilient TransformerÂ
│Â
├── StagesÂ
│ ├── Stage 0 IdentificationÂ
│ ├── Stage 1 AwarenessÂ
│ ├── Stage 2 AssessmentÂ
│ ├── Stage 3 DiscoveryÂ
│ ├── Stage 4 PreparationÂ
│ ├── Stage 5 ActivationÂ
│ ├── Stage 6 ImplementationÂ
│ ├── Stage 7 AdherenceÂ
│ ├── Stage 8 OptimizationÂ
│ ├── Stage 9 SustainabilityÂ
│ └── Stage 10 AdvocacyÂ
Â
4. Clinical Services Term SetÂ
Plain TextÂ
Clinical ServicesÂ
│Â
├── NutritionÂ
├── Weight OptimizationÂ
├── Lifestyle CoachingÂ
├── Sleep OptimizationÂ
├── Stress RecoveryÂ
├── Exercise PrescriptionÂ
├── Corporate WellnessÂ
├── Preventive HealthÂ
├── Chronic Disease SupportÂ
└── Future ProgramsÂ
Â
5. Communication ChannelsÂ
Plain TextÂ
Marketing ChannelsÂ
│Â
├── WebsiteÂ
├── EmailÂ
├── SMSÂ
├── FacebookÂ
├── InstagramÂ
├── LinkedInÂ
├── YouTubeÂ
├── WebinarÂ
├── PrintÂ
└── EventsÂ
Â
6. Retention CategoriesÂ
Plain TextÂ
Retention CategoriesÂ
│Â
├── PermanentÂ
├── 10 YearÂ
├── 7 YearÂ
├── 5 YearÂ
├── 3 YearÂ
├── ArchiveÂ
├── Legal HoldÂ
└── Disposal PendingÂ
Â
7. Risk CategoriesÂ
Plain TextÂ
Risk CategoriesÂ
│Â
├── LowÂ
├── ModerateÂ
├── HighÂ
└── Enterprise CriticalÂ
Â
SharePoint Enterprise Content Type GalleryÂ
Plain TextÂ
HIW Controlled DocumentÂ
│Â
├── HIW Governance DocumentÂ
│ ├── PolicyÂ
│ ├── StandardÂ
│ ├── SOPÂ
│ ├── CharterÂ
│Â
├── HIW Clinical DocumentÂ
│ ├── AssessmentÂ
│ ├── ProtocolÂ
│ ├── Care PlanÂ
│ ├── Clinical GuidelineÂ
│Â
├── HIW Operational DocumentÂ
│ ├── ProcedureÂ
│ ├── WorkflowÂ
│ ├── FormÂ
│ ├── TemplateÂ
│ ├── ChecklistÂ
│Â
├── HIW CommunicationsÂ
│ ├── CampaignÂ
│ ├── NewsletterÂ
│ ├── Email AssetÂ
│ ├── Web ContentÂ
│Â
└── HIW RecordsÂ
├── Audit RecordÂ
├── Executive RecordÂ
├── Meeting RecordÂ
└── ReportÂ
Â
Metadata Mapping MatrixÂ
Parent Content TypeÂ
HIW Controlled DocumentÂ
Inherited by all content types.Â
Required Fields:Â
Plain TextÂ
Document IDÂ
Document TitleÂ
OwnerÂ
AuthorÂ
DepartmentÂ
Document StatusÂ
Document ClassificationÂ
VersionÂ
Review DateÂ
Next Review DateÂ
Retention CategoryÂ
Approval StatusÂ
Risk CategoryÂ
Â
SOP Content TypeÂ
Additional MetadataÂ
Plain TextÂ
Process NameÂ
Process OwnerÂ
Framework AlignmentÂ
Supersedes DocumentÂ
Review FrequencyÂ
Â
Assessment Content TypeÂ
Additional MetadataÂ
Plain TextÂ
Assessment TypeÂ
LACS ArchetypeÂ
Journey StageÂ
Clinical ServiceÂ
Assessment VersionÂ
Â
Campaign Content TypeÂ
Additional MetadataÂ
Plain TextÂ
Campaign NameÂ
Target AudienceÂ
Communication ChannelÂ
Start DateÂ
End DateÂ
Budget CategoryÂ
Primary KPIÂ
Â
Audit Content TypeÂ
Additional MetadataÂ
Plain TextÂ
Audit TypeÂ
Audit PeriodÂ
Finding ClassificationÂ
Corrective Action RequiredÂ
Close DateÂ
Â
IMP-001Â
SharePoint Enterprise Implementation PlanÂ
Phase 1: Governance Foundation (Week 1)Â
DeliverablesÂ
✅ Governance HubÂ
✅ Content Type GalleryÂ
✅ Term StoreÂ
✅ Records CenterÂ
✅ Archive CenterÂ
✅ Audit CenterÂ
Success Criteria:Â
Plain TextÂ
Enterprise metadata operationalÂ
Â
Phase 2: Document Control (Week 2)Â
Create LibrariesÂ
Plain TextÂ
PoliciesÂ
StandardsÂ
SOPsÂ
ProtocolsÂ
FormsÂ
TemplatesÂ
AssessmentsÂ
ReportsÂ
CommunicationsÂ
ConfigureÂ
Plain TextÂ
Version ControlÂ
Check-In/OutÂ
Approval SettingsÂ
Power AutomateÂ
Retention LabelsÂ
Success Criteria:Â
Plain TextÂ
Controlled document management activeÂ
Â
Phase 3: Workflow Automation (Week 3)Â
Build FlowsÂ
Plain TextÂ
Document ApprovalÂ
Review ReminderÂ
Retention ReviewÂ
Archive WorkflowÂ
Exception ManagementÂ
Corrective Action WorkflowÂ
Success Criteria:Â
Plain TextÂ
Manual approval process eliminatedÂ
Â
Phase 4: Power BI Dashboarding (Week 4)Â
Build Executive DashboardÂ
Connect:Â
Plain TextÂ
SharePointÂ
Power AutomateÂ
Microsoft ListsÂ
FormsÂ
Success Criteria:Â
Plain TextÂ
Enterprise reporting activeÂ
Â
Phase 5: Quality & Audit Program (Week 5)Â
Audit LibrariesÂ
Plain TextÂ
Open FindingsÂ
Corrective ActionsÂ
Annual ReviewsÂ
Compliance MonitoringÂ
Success Criteria:Â
Plain TextÂ
Continuous governance monitoring activeÂ
Â
AUD-STD-001Â
Audit Metrics FrameworkÂ
Governance MetricsÂ
Measure document control performance.Â
KPI GroupÂ
Plain TextÂ
Total Controlled DocumentsÂ
Active DocumentsÂ
Archived DocumentsÂ
Overdue ReviewsÂ
Documents Missing MetadataÂ
Documents Missing ApprovalÂ
Target:Â
Plain TextÂ
95% ComplianceÂ
Â
Approval Workflow MetricsÂ
Plain TextÂ
Average Approval TimeÂ
Approvals PendingÂ
Approvals OverdueÂ
Rejected DocumentsÂ
Revision RequestsÂ
Target:Â
Plain TextÂ
<10 Business DaysÂ
Â
Quality MetricsÂ
Plain TextÂ
Audit FindingsÂ
Repeat FindingsÂ
Corrective Actions OpenÂ
Corrective Actions ClosedÂ
Target:Â
Plain TextÂ
>90% Closure RateÂ
Â
Clinical Governance MetricsÂ
Plain TextÂ
Protocol Reviews CurrentÂ
Assessments ReviewedÂ
Educational Content CurrentÂ
Clinical Review ComplianceÂ
Target:Â
Plain TextÂ
100%Â
Â
SharePoint Health MetricsÂ
Plain TextÂ
Libraries ConfiguredÂ
Content Types AppliedÂ
Retention Labels AppliedÂ
Metadata Completion RateÂ
Power Automate FailuresÂ
Target:Â
Plain TextÂ
98%+Â
Â
Executive Governance DashboardÂ
Page 1Â
Executive ScorecardÂ
Display:Â
-
Governance Compliance %Â
-
Audit Compliance %Â
-
Open RisksÂ
-
Overdue ReviewsÂ
-
Document InventoryÂ
Traffic Light StatusÂ
Plain TextÂ
Green = CompliantÂ
Yellow = MonitorÂ
Red = Immediate ActionÂ
Â
Page 2Â
Document Control DashboardÂ
Charts:Â
-
Documents by DepartmentÂ
-
Documents by StatusÂ
-
Review Status TrendÂ
-
Approval Cycle TimeÂ
Â
Page 3Â
Clinical Governance DashboardÂ
Charts:Â
-
Protocol CurrencyÂ
-
Assessment CurrencyÂ
-
Educational Content StatusÂ
-
LACS Documentation StatusÂ
Â
Page 4Â
Audit DashboardÂ
Charts:Â
-
Findings by SeverityÂ
-
Findings by DepartmentÂ
-
Corrective Action AgingÂ
-
Audit Trend AnalysisÂ
Â
Page 5Â
Executive Risk DashboardÂ
Metrics:Â
Plain TextÂ
High Risk DocumentsÂ
Expired DocumentsÂ
Compliance ExceptionsÂ
Open EscalationsÂ
Legal HoldsÂ
Â
HIW Enterprise Governance End-StateÂ
Once implemented, your Microsoft 365 environment will contain:Â
Plain TextÂ
HIW Governance HubÂ
│Â
├── ConstitutionÂ
├── Enterprise StandardsÂ
├── Records CenterÂ
├── Content Type GalleryÂ
├── Centralized Term StoreÂ
├── Power Automate Approval EngineÂ
├── Audit CenterÂ
├── Risk RegisterÂ
├── Power BI Governance DashboardsÂ
├── CSSÂ
├── LACSÂ
├── Brand ArchitectureÂ
├── OperationsÂ
├── HRÂ
├── FinanceÂ
└── TechnologyÂ
This becomes a true enterprise governance platform where every document, assessment, protocol, campaign, workflow, KPI, audit, and retention action is traceable from creation through disposition, providing a single source of truth for the entire HIW ecosystem.Â
Provide your feedback on BizChatÂ
You said:Â Â
Create the Power Automate flows. Draft the Power BI data model. Define content owner responsibilities. Â
Copilot said:Â Â
DOC-STD-002Â
Power Automate Workflow Architecture StandardÂ
Document ID: DOC-STD-002Â
Title: HIW Enterprise Workflow Automation StandardÂ
Owner: Governance OfficeÂ
System Owner: Information TechnologyÂ
Â
Workflow PortfolioÂ
The HIW Governance Platform should initially contain 8 enterprise-level Power Automate flows.Â
Â
FLOW-001Â
Controlled Document Approval WorkflowÂ
PurposeÂ
Manage document approval lifecycle.Â
TriggerÂ
Plain TextÂ
When file created or modifiedÂ
Source LibraryÂ
Plain TextÂ
Controlled DocumentsÂ
Workflow LogicÂ
Plain TextÂ
DraftÂ
↓Â
Metadata ValidationÂ
↓Â
Strategic ReviewÂ
↓Â
Clinical ReviewÂ
↓Â
LACS ReviewÂ
↓Â
Compliance ReviewÂ
↓Â
Brand ReviewÂ
↓Â
Executive ApprovalÂ
↓Â
PublishedÂ
OutputsÂ
Plain TextÂ
Status UpdatedÂ
Review Record CreatedÂ
Audit Trail GeneratedÂ
Version PublishedÂ
Â
FLOW-002Â
Metadata Compliance WorkflowÂ
PurposeÂ
Prevent uncontrolled documents.Â
TriggerÂ
Plain TextÂ
Document CreatedÂ
ValidationÂ
Plain TextÂ
Document IDÂ
OwnerÂ
DepartmentÂ
ClassificationÂ
Review DateÂ
Retention CategoryÂ
Failure ActionÂ
Plain TextÂ
Status = Metadata IncompleteÂ
NotificationsÂ
Plain TextÂ
AuthorÂ
Content OwnerÂ
Department ManagerÂ
Â
FLOW-003Â
Review Reminder WorkflowÂ
ScheduleÂ
Plain TextÂ
DailyÂ
LogicÂ
Plain TextÂ
Next Review DateÂ
Notifications:Â
Plain TextÂ
90 Days PriorÂ
60 Days PriorÂ
30 Days PriorÂ
7 Days PriorÂ
Â
FLOW-004Â
Escalation WorkflowÂ
TriggerÂ
Plain TextÂ
Review OverdueÂ
Escalation PathÂ
Plain TextÂ
Day 1Â
OwnerÂ
 Â
Day 7Â
ManagerÂ
 Â
Day 14Â
DirectorÂ
 Â
Day 30Â
Executive SponsorÂ
 Â
Day 45Â
Governance CommitteeÂ
Â
FLOW-005Â
Exception Request WorkflowÂ
TriggerÂ
Plain TextÂ
Exception Form SubmittedÂ
RoutingÂ
Plain TextÂ
Department ExceptionÂ
 Â
→ DirectorÂ
 Â
Clinical ExceptionÂ
 Â
→ CCCOÂ
 Â
Governance ExceptionÂ
 Â
→ Governance CommitteeÂ
 Â
Enterprise ExceptionÂ
 Â
→ Executive CouncilÂ
OutputsÂ
Plain TextÂ
Exception Register UpdateÂ
Decision RecordÂ
Review DateÂ
Â
FLOW-006Â
Retention & Archive WorkflowÂ
ScheduleÂ
Plain TextÂ
MonthlyÂ
CheckÂ
Plain TextÂ
Retention EligibilityÂ
ActionÂ
Plain TextÂ
Move to ArchiveÂ
Apply Record LabelÂ
Create Archive LogÂ
Â
FLOW-007Â
Audit Finding WorkflowÂ
TriggerÂ
Plain TextÂ
Audit Finding CreatedÂ
ActionsÂ
Plain TextÂ
Assign OwnerÂ
Set Due DateÂ
Generate Corrective ActionÂ
Track ClosureÂ
KPIÂ
Plain TextÂ
Days To CloseÂ
Â
FLOW-008Â
Governance Risk WorkflowÂ
Trigger ConditionsÂ
Plain TextÂ
Expired DocumentÂ
 Â
Missing ApprovalÂ
 Â
Review OverdueÂ
 Â
Audit Finding OverdueÂ
 Â
Exception ExpiredÂ
ActionÂ
Plain TextÂ
Create Governance RiskÂ
Notify Governance OfficeÂ
Assign Risk RatingÂ
Â
BI-STD-001Â
HIW Enterprise Power BI Data ModelÂ
The Power BI environment should be built using a simple star schema.Â
Â
Fact TablesÂ
FactDocumentsÂ
Stores all document activity.Â
FieldsÂ
Plain TextÂ
Document KeyÂ
Document IDÂ
Department KeyÂ
Owner KeyÂ
Status KeyÂ
Content Type KeyÂ
Review DateÂ
Approval DateÂ
VersionÂ
Measures:Â
DAXÂ
Total Documents =Â
COUNTROWS(FactDocuments)Â
DAXÂ
Published Documents =Â
CALCULATE(Â
COUNTROWS(FactDocuments),Â
FactDocuments[Status]="Published"Â
)Â
Â
FactApprovalsÂ
Tracks approvals.Â
FieldsÂ
Plain TextÂ
Approval KeyÂ
Document KeyÂ
Approver KeyÂ
Approval StageÂ
Start DateÂ
End DateÂ
OutcomeÂ
MeasuresÂ
DAXÂ
Average Approval Days =Â
AVERAGE(FactApprovals[Duration])Â
Â
FactAuditsÂ
Tracks audit activity.Â
FieldsÂ
Plain TextÂ
Audit KeyÂ
Finding KeyÂ
SeverityÂ
StatusÂ
DepartmentÂ
Open DateÂ
Close DateÂ
MeasuresÂ
DAXÂ
Open Findings =Â
COUNTROWS(Â
FILTER(FactAudits,Â
FactAudits[Status]="Open"Â
))Â
Â
FactExceptionsÂ
Tracks approved exceptions.Â
FieldsÂ
Plain TextÂ
Exception IDÂ
DepartmentÂ
CategoryÂ
Approval DateÂ
Expiry DateÂ
StatusÂ
Â
FactRetentionÂ
Tracks retention lifecycle.Â
FieldsÂ
Plain TextÂ
Document IDÂ
Retention ClassÂ
Archive DateÂ
Disposal DateÂ
Legal HoldÂ
Â
Dimension TablesÂ
DimDepartmentÂ
Plain TextÂ
Department KeyÂ
Department NameÂ
DirectorÂ
Â
DimOwnerÂ
Plain TextÂ
Owner KeyÂ
NameÂ
RoleÂ
DepartmentÂ
Â
DimStatusÂ
Plain TextÂ
DraftÂ
Under ReviewÂ
ApprovedÂ
PublishedÂ
ArchivedÂ
ExpiredÂ
Â
DimContentTypeÂ
Plain TextÂ
PolicyÂ
StandardÂ
SOPÂ
ProtocolÂ
AssessmentÂ
CampaignÂ
AuditÂ
FormÂ
TemplateÂ
Â
DimDateÂ
Standard calendar table.Â
Plain TextÂ
DateÂ
MonthÂ
QuarterÂ
YearÂ
Fiscal YearÂ
Â
Dashboard PortfolioÂ
Â
Dashboard 1Â
Executive Governance ScorecardÂ
KPIsÂ
Plain TextÂ
Total DocumentsÂ
 Â
Compliance %Â
 Â
Open FindingsÂ
 Â
Open RisksÂ
 Â
Overdue ReviewsÂ
 Â
Active ExceptionsÂ
Â
Dashboard 2Â
Document Control DashboardÂ
VisualsÂ
Plain TextÂ
Documents by DepartmentÂ
 Â
Documents by StatusÂ
 Â
Document Growth TrendÂ
 Â
Review Due CalendarÂ
 Â
Approval VolumeÂ
Â
Dashboard 3Â
Compliance DashboardÂ
VisualsÂ
Plain TextÂ
Metadata ComplianceÂ
 Â
Review ComplianceÂ
 Â
Retention ComplianceÂ
 Â
Exception VolumeÂ
 Â
Escalation TrendsÂ
Â
Dashboard 4Â
Clinical Governance DashboardÂ
VisualsÂ
Plain TextÂ
Protocols CurrentÂ
 Â
Assessments ApprovedÂ
 Â
Content Reviews CompleteÂ
 Â
LACS Documentation StatusÂ
 Â
Clinical Audit FindingsÂ
Â
Dashboard 5Â
Records Management DashboardÂ
VisualsÂ
Plain TextÂ
Records by Retention ClassÂ
 Â
Archive GrowthÂ
 Â
Items Pending DisposalÂ
 Â
Legal Hold ItemsÂ
 Â
Retention Compliance RateÂ
Â
ROLE-STD-001Â
Content Owner Responsibility StandardÂ
Â
PurposeÂ
Content Owners are accountable for the lifecycle, quality, compliance, and governance of assigned documents.Â
They do not merely create documents.Â
They own them.Â
Â
Core ResponsibilitiesÂ
Every Content Owner must:Â
1. Document StewardshipÂ
Ensure:Â
Plain TextÂ
AccuracyÂ
CompletenessÂ
CurrencyÂ
Version ControlÂ
Â
2. Metadata ManagementÂ
Responsible for:Â
Plain TextÂ
Document IDÂ
 Â
TitleÂ
 Â
Content TypeÂ
 Â
ClassificationÂ
 Â
Review DateÂ
 Â
Retention CategoryÂ
 Â
Owner AssignmentÂ
Target:Â
Plain TextÂ
100% Metadata CompletionÂ
Â
3. Review ManagementÂ
Ensure reviews occur before:Â
Plain TextÂ
Review DateÂ
Required actions:Â
Plain TextÂ
ReviewÂ
ReviseÂ
ReapproveÂ
RetireÂ
ArchiveÂ
Â
4. Audit SupportÂ
Provide:Â
Plain TextÂ
EvidenceÂ
  Â
Review RecordsÂ
 Â
Approval HistoryÂ
 Â
Supporting DocumentationÂ
During audits.Â
Â
5. Risk ManagementÂ
Identify:Â
Plain TextÂ
Expired ContentÂ
 Â
Conflicting DocumentsÂ
 Â
Compliance RisksÂ
 Â
Clinical RisksÂ
Escalate immediately.Â
Â
Content Owner RACIÂ
ActivityÂ
OwnerÂ
ManagerÂ
GovernanceÂ
ExecutiveÂ
Create DocumentÂ
RÂ
AÂ
CÂ
IÂ
Update MetadataÂ
RÂ
AÂ
CÂ
IÂ
Review DocumentÂ
RÂ
AÂ
CÂ
IÂ
Approve DocumentÂ
CÂ
AÂ
CÂ
IÂ
Archive DocumentÂ
RÂ
AÂ
CÂ
IÂ
Audit EvidenceÂ
RÂ
CÂ
AÂ
IÂ
Exception RequestÂ
RÂ
AÂ
CÂ
IÂ
EscalationÂ
RÂ
AÂ
CÂ
IÂ
R = ResponsibleÂ
A = AccountableÂ
C = ConsultedÂ
I = InformedÂ
Â
Content Owner Performance MetricsÂ
Compliance KPIsÂ
Plain TextÂ
Metadata Completion %Â
Target: 100%Â
Plain TextÂ
Review Completion %Â
Target: ≥95%Â
Plain TextÂ
Overdue ReviewsÂ
Target: 0Â
Plain TextÂ
Approval Cycle ComplianceÂ
Target: ≥90%Â
Plain TextÂ
Audit Finding RateÂ
Target: <5%Â
Â
Escalation AccountabilityÂ
If a document becomes:Â
Plain TextÂ
ExpiredÂ
UnreviewedÂ
Non-CompliantÂ
Missing MetadataÂ
the assigned Content Owner remains accountable until the issue is resolved or formally reassigned using the governance workflow.Â
Â
Recommended Next Governance ArtifactÂ
The next document to create should be:Â
GOV-CHR-001 Enterprise Governance CharterÂ
This would formally establish the Executive Governance Council, Governance Office, Clinical Governance Committee, Change Advisory Board, authority levels, voting rules, quorum requirements, and governance review cycles that oversee the entire HIW ecosystem.Â