Skip to content

Cloud Intake Process(Deprecated)

Jump to bottom
John Bain edited this page Mar 29, 2023 · 1 revision

Cloud Intake Process for PDCP

The cloud intake process for the Public Health Data Center of Excellence (PDCP) is designed to ensure that all requests for cloud services are properly validated, reviewed, and approved, and that all necessary technical and administrative information is collected before deployment. The following process outlines the steps involved in the cloud intake process:

Standard Intake Process

  1. The cloud intake request form is supplied to the requestor.
    • Cloud Intake Request Form
  2. The request is received by the PDCP intake team and validated as cloud.
  3. The request is reviewed by the Architecture and Technical Advisory Committee (ATAC) and assigned to the cloud team (PDCP).
  4. The PDCP approves the request and enters an automated entry into the Pathfinder/PoC Tracker.
  5. The requestor is asked to fill out the Technical Intake Form.
    • Technical Intake Form
  6. An automated entry is entered into a Task Tracker (TBD – DevOps/Planner/Other).
graph LR
    A[Supply cloud intake request form to requestor] -- 2. Receive and validate request --> B[Review request and assign to cloud team PDCP]
    B -- 3. Approve request and enter automated entry --> C[Ask requestor to fill out Technical Intake Form]
    C -- 4. Enter automated entry into Task Tracker --> D[Complete Task Tracker]
Loading

Expedited Intake Process

  1. The requestor is in direct contact with the PDCP for intake.
  2. The PDCP may require documentation, if so they will send the requestor through the regular intake and expedite the form processing. If not, proceed to step 3.
  3. The requestor is asked to fill out the Technical Intake Form.
  4. The request is validated and the environment is provided.
  5. The required information is manually added into the Pathfinder/PoC Tracker by the SME.
graph LR
    A[Requestor contacts PDCP for intake] -- 2. Review request --> B[Fill out Technical Intake Form]
    B -- 3. Validate request and provide environment --> C[Manually add required information into the Pathfinder/PoC Tracker by the SME]
Loading

Note: In order to use the Technical Intake Form, the requestor must have access to the PDCP's cloud services and be a member of the PDCP Team Site. In order to do this, a Team Owner must add them and they will receive a link through e-mail for the request. They will then be prompted to set up their Multi-Factor Authentication. Once this is complete and they have access to the site, they will be able to use the Technical Intake Form.

Conclusion

The cloud intake process outlined in this document is designed to ensure that all requests for cloud services are properly validated, reviewed, and approved, and that all necessary technical and administrative information is collected before deployment. By following this cloud intake process, the PDCP can ensure that all cloud services are deployed securely and effectively, and that they comply with relevant laws, regulations, and guidelines.

🚧🚧🚧🚧🚧🚧🚧🚧🚧🚧🚧🚧🚧🚧🚧🚧🚧🚧🚧🚧🚧🚧🚧🚧

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.

🚧🚧🚧🚧🚧🚧🚧🚧🚧🚧🚧🚧🚧🚧🚧🚧🚧🚧🚧🚧🚧🚧🚧🚧

Clone this wiki locally