<div class="getting-started-hero" markdown="1">

Rules of the Road

Essential Guidelines for Epic on Azure Excellence

</div> <div class="rules-overview" markdown="1"> <div class="rules-card" markdown="1">

🚀 Development Standards

Essential coding practices, testing requirements, and technical excellence guidelines for healthcare software development.

<a href="rules-development/" class="card-link">Explore Development Rules →</a>

</div> <div class="rules-card" markdown="1">

🏗️ Infrastructure Practices

Best practices for cloud infrastructure, automation, and platform management in Azure healthcare environments.

<a href="rules-infrastructure/" class="card-link">Learn Infrastructure Rules →</a>

</div> <div class="rules-card" markdown="1">

🔒 Security & Compliance

Critical security requirements, HIPAA compliance, and data protection standards for healthcare applications.

<a href="rules-security/" class="card-link">Review Security Rules →</a>

</div> </div>

Essential Team Guidelines for Epic on Azure Success

---

🗺️ Complete Team Guidelines

Development Standards - View Details →

Essential development practices and workflows.

Key Topics: GitHub Flow, Branch Protection, Quality Gates, Pull Request Standards

Infrastructure Practices - View Details →

Infrastructure as Code and operational excellence.

Key Topics: IaC Excellence, Automation Standards, Issue Resolution, Advanced Practices

Security & Compliance - View Details →

Healthcare security requirements and compliance standards.

Key Topics: Healthcare Security, Secret Management, Security Tooling, Compliance

---

📋 Core Development Principles

These fundamental principles guide all our technical decisions and daily work.

🔄 Continuous Integration Excellence

🔒 Security First Approach

💬 Communication Excellence

✅ Quality Standards

---

🤝 Team Communication Standards

Daily Collaboration

• Daily Standups: 9:00 AM CT (Optional but encouraged)
• Team Channels: Use #epic-azure-engineering for technical discussions
• Status Updates: Communicate blockers and progress transparently
• Knowledge Sharing: Contribute to team learning through documentation and demos

Meeting Cadence

• Weekly Planning: Fridays 2:00 PM CT
• Monthly Architecture Review: First Thursday of each month
• Quarterly Retrospectives: Process improvement and team feedback
• Ad-hoc Technical Reviews: As needed for complex changes

Documentation Standards

• README Requirements: Every repository must have comprehensive README
• Decision Records: Document architectural decisions and rationale
• Runbooks: Operational procedures for common tasks
• Troubleshooting Guides: Solutions for known issues and problems

---

🎯 Quality Gates & Success Metrics

Individual Excellence Indicators

Team Performance Targets

!!! example "Reliability Targets" - System Uptime: 99.95% availability for Epic production systems - Incident Resolution: <4 hour mean time to resolution - Data Protection: Zero data loss incidents - Security Response: <15 minute response to security incidents

!!! example "Efficiency Targets" - Deployment Speed: <2 hour end-to-end deployment pipeline - Automation Coverage: 80% of routine tasks automated - Feature Delivery: <24 hour delivery for small changes - Infrastructure as Code: 90% of infrastructure managed as code

---

🆘 Getting Help & Escalation

Support Channels by Issue Type

!!! question "Technical Questions" - 💬 Teams Channel: #epic-azure-engineering for technical discussions - 🐙 GitHub Discussions: Create discussion in relevant repository - 📚 Documentation: Check MEGADOC first - 🎓 Learning: Bi-weekly lunch & learn sessions

!!! question "Operational Issues" - 🚨 Critical Issues: Contact on-call engineer immediately - 📊 Monitoring Alerts: Check Dynatrace/Splunk dashboards first - 🎫 Service Requests: Create ServiceNow ticket for formal requests - 🔒 Security Incidents: Follow security escalation procedure immediately

!!! question "Process Questions" - 👥 Team Lead: Your direct manager for role-specific guidance - 🏗️ Architecture Team: Technical design and architecture questions - 📋 Project Management: Timeline, priority, and resource questions - 🎯 Product Owner: Feature requirements and business logic

Escalation Matrix

Emergency Contacts

• Security Incidents: +1-800-SOC-HELP
• Platform Issues: Epic on Azure Teams Channel
• Access Issues: IT Help Desk
• Critical System Outage: On-call rotation (see team calendar)

---

🌟 Welcome to Excellence

**Remember:** Every line of code, every infrastructure change, and every security decision you make has the potential to improve healthcare delivery for millions of patients worldwide.

Your Next Steps

1. 📖 Review Detailed Guidelines:

   • Development Standards - Git workflows and code quality
   • Infrastructure Practices - IaC and operational excellence
   • Security & Compliance - Healthcare security requirements

2. 🛠️ Set Up Your Environment:

   • Developer Workstation Setup
   • Contributing Guidelines

3. 🔄 Practice the Workflow:

   • GitHub Workflow Guide
   • Make your first contribution!

4. 🤝 Join the Team:

   • Participate in daily standups
   • Engage in code reviews
   • Share knowledge and mentor others

---

📚 Quick Reference

Essential Links

Team Resources

• Epic Megadoc: https://epic.optum.com
• GitHub Organization: optum-tech-compute
• Team Teams space: Epic on Azure Engineering (your team's Teams channel)
• Support Channel: Epic on Azure Support Teams channel

---

These team guidelines are living documents that evolve with our practices and learnings. If you have suggestions for improvement, please create an issue or submit a pull request. Together, we build better healthcare technology.

Last updated: September 2025 | Team Impact: Serving millions of patients worldwide