-
Notifications
You must be signed in to change notification settings - Fork 0
Intake Processes
The Public Health Data Center of Practice offers several intake processes scenarios to help ensure that your request is aligned with our services and resources. Each intake process is tailored to different types of situation, and can help streamline the process of getting started with our services. Here are the different intake processes we offer:
The Directed intake process is for situations where there is a directive from leadership or management to undertake a specific action. This intake process is for situations where there is a clear mandate to execute a particular project or initiative, and the request needs to be actioned immediately. Directed requests are typically handled on a case-by-case basis, and may involve expedited processing and dedicated resources to ensure timely completion.
The Lead Conversion intake process is designed for our embedded staff who have identified potential new business opportunities that align with our services and resources. This intake process empowers our staff to bring new projects to our attention and follow a streamlined process for onboarding them. We trust our staff's good judgment and expertise to identify opportunities that are a good fit for our organization, and we value their input in identifying potential new projects or initiatives. Lead Conversion requests are typically handled by a member of our coaching and mentoring team, and may involve dedicated resources to ensure a smooth and efficient onboarding process. This intake process is primarily geared towards small initiatives and experiments that align with our organization's strategic objectives.
The Service Catalog (Small Request) intake process is for requests that require a small amount of resources or services, and are available through the service catalog. This intake process is for situations where the requestor has identified a specific service or resource they need from our catalog, and can provide a clear description of their requirements. Service Catalog (Small Request) requests are typically handled by an intake team.
The Service Catalog (Large Request) intake process is for requests that require a large amount of resources or services, and are available through our service catalog. This intake process is for situations where the requestor has identified a specific service or resource they need from the catalog, but the request requires a more detailed analysis or consultation before implementation. Service Catalog (Large Request) requests are typically handled by our intake team, with support from a solutions architect or technical lead.
The Organizationally Strategy intake process is designed for larger initiatives and projects that are identified by the organization or the CIO as planned activities for the yearly strategic plan. This intake process is intended for situations where strategic planning and consultation are necessary before implementation, and may involve a detailed analysis of business requirements, technical architecture, and project planning. Our solutions architecture or project management teams, with support from technical leads and business analysts, typically handle Organizationally Strategy requests. This intake process is focused on projects that have a significant impact on the organization's strategic objectives and may require dedicated resources and extended timelines to ensure successful implementation. By following this intake process, we ensure that projects are aligned with our organization's strategic objectives and are executed with careful planning and consideration.
We encourage you to review the different intake processes outlined above. Our intake processes are constantly evolving and improving, and we are committed to providing the best possible support to our stakeholders. If you have any questions please do not hesitate to contact the Public Health Data Center of Practice for guidance and support. Please note that the above list of intake processes is fo educational purposes, is not exhaustive, and we welcome feedback and suggestions for improving our processes.
🚧🚧🚧🚧🚧🚧🚧🚧🚧🚧🚧🚧🚧🚧🚧🚧🚧🚧🚧🚧🚧🚧🚧🚧
Under Development
- This wiki and the documents being developed under it are living documents.
- They are all pre-decisional.
- Some of these documents were generated using chatGPT or were developed by other organizations for reuse and adaptation.
- Some of the documents in this wiki are in early early drafts, they make reference to things that do no exist or to process not yet being used.
- The Center of practice(COP) is best effort and will be developed iteratively. This includes the technology supporting the COP
- At the early stages of the COP expect change; short life cycles and rapid changes. Plan accordingly.
- Stability in the COP will materialize over time.
- For immediate reference engage your COP support channel, use the documentation as a secondary source.
- There is reference to the COP and PDCP in the documentation, these are the same entity. We haven't picked a name yet :)
All of the pages in this wiki should be considered draft, underdevelopment and needing review. None of these pages are official documentation. All of the pages are a work in progress and discussion is encouraged via the GitHub issues mechanism.
🚧🚧🚧🚧🚧🚧🚧🚧🚧🚧🚧🚧🚧🚧🚧🚧🚧🚧🚧🚧🚧🚧🚧🚧