susin1

You are a senior healthcare project management consultant. I need you to perform a comprehensive Stakeholder X-Ray analysis for my project.

**Project Context:** [DESCRIBE YOUR PROJECT — e.g., EHR migration, new clinic build-out, telehealth expansion, revenue cycle overhaul]

For every stakeholder group you identify, provide:

1. **Stakeholder Name/Role** (be specific — not just "leadership" but "CMO," "Nurse Manager — Med/Surg," "Revenue Cycle Director")
2. **Influence Level** (High / Medium / Low) — their power to accelerate or kill the project
3. **Interest Level** (High / Medium / Low) — how much they care about the outcome
4. **Stance** (Champion / Supportive / Neutral / Resistant / Hostile)
5. **What They Care About Most** (1 sentence — their real motivation)
6. **Hidden Risk** (what could go wrong if you ignore them)
7. **Engagement Strategy** (1-2 sentences — how to win them over or neutralize resistance)

Organize into a table. Then provide:
- A **Power/Interest Grid** summary (who goes in each quadrant)
- **Top 3 Stakeholders to Engage First** with rationale
- **The One Stakeholder Everyone Forgets** (and why they matter)

Be specific to healthcare. Think about clinical staff, IT, compliance, finance, patients, unions, and vendors.

You are a healthcare compliance and project management expert. I need a comprehensive Regulatory Landscape Scan for my project.

**Project:** describe_your_project
**State(s):** list_states_where_project_operates
**Organization Type:** [Hospital system / FQHC / Health plan / Post-acute / Ambulatory]

Perform the following analysis:

**1. Federal Regulatory Scan**
For each applicable regulation (HIPAA, HITECH, CMS Conditions of Participation, 21st Century Cures Act, Information Blocking Rule, etc.):
- How it applies to this specific project
- Key requirements that affect scope or timeline
- Penalty for non-compliance
- Recent enforcement trends (last 12 months)

**2. State Regulatory Scan**
- State health department requirements
- Certificate of Need (CON) implications if applicable
- State privacy laws that exceed HIPAA
- Medicaid-specific requirements

**3. Accreditation Requirements**
- Joint Commission / DNV / AAAHC standards affected
- Survey readiness implications
- Documentation requirements

**4. Compliance Risk Matrix**
Create a table with columns: Regulation | Requirement | Project Impact | Risk Level | Mitigation Action | Owner

**5. Timeline Implications**
- Which regulatory requirements create hard deadlines?
- Which require lead time for approvals or notifications?
- What's the critical path through the regulatory landscape?

**6. The "Gotcha" List**
- 5 regulatory surprises that commonly derail healthcare projects like this one

Be specific and actionable. I need to build this into my project plan.

You are a healthcare data analyst and project management strategist. I'm going to give you project data, and I need you to be a Data Detective — don't just summarize, INVESTIGATE.

**Data I'm Providing:** [PASTE YOUR DATA — could be project metrics, utilization data, budget reports, quality scores, survey results, timeline tracking, etc.]

Perform this investigation:

**1. First Impressions (The Headlines)**
- What are the 3 most important things this data is screaming at you?
- What's the single most surprising finding?

**2. Pattern Recognition**
- What trends are emerging? (improving, declining, cyclical, flat)
- Are there correlations between variables that suggest cause-and-effect?
- What patterns would a non-analyst miss?

**3. Anomaly Detection**
- What numbers don't make sense or seem off?
- Where are the outliers, and what might explain them?
- What data is suspiciously perfect (possible data quality issue)?

**4. The Missing Data**
- What data SHOULD be here but isn't?
- What questions can't you answer with what's provided?
- What additional data would change the analysis?

**5. So What? (The Actionable Insights)**
- For each key finding, provide: Finding → Implication → Recommended Action
- Prioritize by impact and urgency

**6. The Story**
- Write a 3-sentence narrative summary suitable for an executive audience
- Write a 1-paragraph technical summary for the project team

Be direct. Be specific. Don't hedge — tell me what the data says.