cfr
General Information
Solution name
cfr
Solution category
Open Software
Short description
R package to estimate disease severity and under-reporting in real-time, accounting for reporting delays in epidemic time-series
Website
https://github.com/epiverse-trace/cfr
Alternate Email Address
[email protected]
Where is your solution’s source hosted?
https://epiverse-trace.github.io/cfr/
cfr
Solution category
Open Software
Short description
R package to estimate disease severity and under-reporting in real-time, accounting for reporting delays in epidemic time-series
Website
https://github.com/epiverse-trace/cfr
Alternate Email Address
[email protected]
Where is your solution’s source hosted?
https://epiverse-trace.github.io/cfr/
1. SDG Relevance
Which SDG/s is your solution relevant to?
SDG3: Good Health and Well-Being,SDG17: Partnerships for the Goals
How is your solution relevant to each SDG you’ve selected above?
crf contributes to timely and accurate epidemiological insights, allowing decision-makers to respond to health crises more quickly and effectively, thus supporting the goal of achieving better health outcomes. As part of the Epiverse initiative, cfr underscores the importance of Partnerships for the Goals by relying on open-source collaborations and international partnerships to develop and maintain tools like crf. This collaborative approach enhances the accessibility and effectiveness of public health interventions, aligning with the SDGs' broader objective of fostering global cooperation for sustainable development.
SDG3: Good Health and Well-Being,SDG17: Partnerships for the Goals
How is your solution relevant to each SDG you’ve selected above?
crf contributes to timely and accurate epidemiological insights, allowing decision-makers to respond to health crises more quickly and effectively, thus supporting the goal of achieving better health outcomes. As part of the Epiverse initiative, cfr underscores the importance of Partnerships for the Goals by relying on open-source collaborations and international partnerships to develop and maintain tools like crf. This collaborative approach enhances the accessibility and effectiveness of public health interventions, aligning with the SDGs' broader objective of fostering global cooperation for sustainable development.
2. Open Licensing
Which open license(s) is/are used by your solution?
MIT
Provide evidence of use of the selected open license(s).
https://github.com/epiverse-trace/cfr/blob/main/LICENSE.md
MIT
Provide evidence of use of the selected open license(s).
https://github.com/epiverse-trace/cfr/blob/main/LICENSE.md
3. Clear Ownership
Who owns this digital solution?
Epiverse-TRACE; Pratik Gupte
Provide evidence(s) of ownership.
https://epiverse-trace.r-universe.dev/cfr, https://cran.r-project.org/web/packages/cfr/index.html
Epiverse-TRACE; Pratik Gupte
Provide evidence(s) of ownership.
https://epiverse-trace.r-universe.dev/cfr, https://cran.r-project.org/web/packages/cfr/index.html
4. Platform Independence
Does this solution use any closed components that create proprietary dependency?
No
No
5. Documentation
Where is your solution’s documentation?
Instructions for download, installation, and requirements - https://github.com/epiverse-trace/cfr, https://cran.r-project.org/web/packages/cfr/index.html
Instructions for download, installation, and requirements - https://github.com/epiverse-trace/cfr, https://cran.r-project.org/web/packages/cfr/index.html
6. Non-PII Data Extraction
Does your solution collects or uses non-PII data and/or content?
Yes
Describe the mechanism for extracting or importing non-PII data from or into the system in a non-proprietary format.
CSV
Yes
Describe the mechanism for extracting or importing non-PII data from or into the system in a non-proprietary format.
CSV
7. Privacy & Applicable Laws
Provide a list of relevant privacy, domestic and other applicable international laws your solution complies with.
cfr only uses non-personal, publicly available information and doesn't save or export any kind of user data or analytics.
Provide evidence(s) of adherence with the laws mentioned above.
https://epiverse-trace.github.io/cfr/articles/software-permissions.html
cfr only uses non-personal, publicly available information and doesn't save or export any kind of user data or analytics.
Provide evidence(s) of adherence with the laws mentioned above.
https://epiverse-trace.github.io/cfr/articles/software-permissions.html
8. Open Standards & Best Practices
Provide a list of the open standards your solution adheres to and demonstrate adhrence.
HTTPS, UTF-8 encoding
Provide a list of best practices & principles your solution adheres to and demonstrate adhrence.
Encoding of these are in the DESCRIPTION file of cfr https://github.com/epiverse-trace/cfr/blob/main/DESCRIPTION
HTTPS, UTF-8 encoding
Provide a list of best practices & principles your solution adheres to and demonstrate adhrence.
Encoding of these are in the DESCRIPTION file of cfr https://github.com/epiverse-trace/cfr/blob/main/DESCRIPTION
9A. Data Privacy & Security
Does your solution collect / store / distribute PII data?
PII data is NOT collected NOT stored and NOT distributed.
PII data is NOT collected NOT stored and NOT distributed.
9B. Inappropriate & Illegal Content
Does your solution collect / store / distribute content?
Content is NOT collected NOT stored and NOT distributed.
Content is NOT collected NOT stored and NOT distributed.
9C. Protection from Harassment
Does your solution facilitate interactions with or between users and/or contributors?
Yes
How does your solution enables users and contributors to protect themselves from harassment.
Epiverse software is open content, which anyone may contribute to. We enforce a Code of Conduct for each package: https://docs.google.com/document/u/1/d/e/2PACX-1vRcwl2uaKdEQT5iS-9MroDMKsd81oR8v1gdlY1kHTTjgGEbLKfcWxtdrkvVRhJJGQalsgC1A4K4YiDe/pub?pli=1
Yes
How does your solution enables users and contributors to protect themselves from harassment.
Epiverse software is open content, which anyone may contribute to. We enforce a Code of Conduct for each package: https://docs.google.com/document/u/1/d/e/2PACX-1vRcwl2uaKdEQT5iS-9MroDMKsd81oR8v1gdlY1kHTTjgGEbLKfcWxtdrkvVRhJJGQalsgC1A4K4YiDe/pub?pli=1
Scale of Solution
Where was this solution developed?
United Kingdom
Where is this solution actively deployed?
United Kingdom
Are there any governments departments and/or ministries using your solution?
No governments or ministries are currently using our solution, but Epiverse is running a country selection exercise over the next year to determine where to pilot this solution.
Who else is using your solution?
Epiverse is currently collaborating with the WHO Berlin to deploy its tools to the WHO's Pandemic and Epidemic Intelligence members. The partnership is still young, but is projected to reach a mature stage by 2025.
United Kingdom
Where is this solution actively deployed?
United Kingdom
Are there any governments departments and/or ministries using your solution?
No governments or ministries are currently using our solution, but Epiverse is running a country selection exercise over the next year to determine where to pilot this solution.
Who else is using your solution?
Epiverse is currently collaborating with the WHO Berlin to deploy its tools to the WHO's Pandemic and Epidemic Intelligence members. The partnership is still young, but is projected to reach a mature stage by 2025.
Application Details
| Application ID | 11092 |
| Parent Application ID | NA |
| Status | DPG |
| Date Created | 22-11-2023 03:11 PM UTC |
| Date Submitted | 22-11-2023 03:55 PM UTC |
| Date Reviewed | 04-03-2024 08:02 AM UTC |
| Date of Expiry | 04-03-2025 08:02 AM UTC |
Application Log Details
| Timestamp | Activity |
|---|---|
| 04-03-2024 08:02 AM UTC | Richard Kagaba (L2 Reviewer) submitted their review of cfr (1051) and found it to be a DPG |
| 04-03-2024 08:02 AM UTC | System unmarked cfr (11092) as a nominee |
| 04-03-2024 08:02 AM UTC | Richard Kagaba (L2 Reviewer) passed 7. Privacy & Applicable Laws for cfr (11092) |
| 04-03-2024 08:01 AM UTC | Richard Kagaba (L2 Reviewer) pulled cfr (11092) under review |
| 04-03-2024 01:36 AM UTC | L1 Reviewer (L1 Reviewer) submitted their review of cfr (11092) |
| 04-03-2024 01:36 AM UTC | L1 Reviewer (L1 Reviewer) passed 7. Privacy & Applicable Laws for cfr (11092) |
| 04-03-2024 01:36 AM UTC | L1 Reviewer (L1 Reviewer) edited 7. Privacy & Applicable Laws for cfr (11092) |
| 04-03-2024 01:34 AM UTC | L1 Reviewer (L1 Reviewer) pulled cfr (11092) under review |
| 19-02-2024 09:40 AM UTC | New tag (Clarifications) added to application |
| 19-02-2024 09:40 AM UTC | Application clarifications submitted, Application move to L1 for review again |
| 06-02-2024 01:08 PM UTC | Admin (Admin) modified owner from 837 (Claudine Lim) to 4120 (Hugo Gruson) for cfr (11092) |
| 25-01-2024 04:46 PM UTC | Richard Kagaba (L2 Reviewer) requested clarifications for cfr (11092) |
| 25-01-2024 04:46 PM UTC | System marked cfr (11092) as a nominee |
| 25-01-2024 04:45 PM UTC | Richard Kagaba (L2 Reviewer) require clarification on 7. Privacy & Applicable Laws for cfr (11092) |
| 25-01-2024 04:29 PM UTC | Richard Kagaba (L2 Reviewer) moved cfr (11092) to under review |
| 22-01-2024 11:23 AM UTC | Richard Kagaba (L2 Reviewer) moved cfr (11092) to under consultation |
| 22-01-2024 11:11 AM UTC | Richard Kagaba (L2 Reviewer) passed Scale of Solution for cfr (11092) |
| 22-01-2024 11:11 AM UTC | Richard Kagaba (L2 Reviewer) passed 9C. Protection from Harassment for cfr (11092) |
| 22-01-2024 11:10 AM UTC | Richard Kagaba (L2 Reviewer) passed 9B. Inappropriate & Illegal Content for cfr (11092) |
| 22-01-2024 11:10 AM UTC | Richard Kagaba (L2 Reviewer) passed 9A. Data Privacy & Security for cfr (11092) |
| 22-01-2024 11:05 AM UTC | Richard Kagaba (L2 Reviewer) passed 8. Open Standards & Best Practices for cfr (11092) |
| 22-01-2024 10:55 AM UTC | Richard Kagaba (L2 Reviewer) passed 6. Non-PII Data Extraction for cfr (11092) |
| 22-01-2024 10:54 AM UTC | Richard Kagaba (L2 Reviewer) passed 5. Documentation for cfr (11092) |
| 22-01-2024 10:52 AM UTC | Richard Kagaba (L2 Reviewer) passed 4. Platform Independence for cfr (11092) |
| 22-01-2024 10:51 AM UTC | Richard Kagaba (L2 Reviewer) passed 3. Clear Ownership for cfr (11092) |
| 22-01-2024 10:51 AM UTC | Richard Kagaba (L2 Reviewer) passed 2. Open Licensing for cfr (11092) |
| 22-01-2024 10:51 AM UTC | Richard Kagaba (L2 Reviewer) passed 1. SDG Relevance for cfr (11092) |
| 22-01-2024 10:38 AM UTC | Richard Kagaba (L2 Reviewer) passed General Information for cfr (11092) |
| 22-01-2024 10:36 AM UTC | Richard Kagaba (L2 Reviewer) pulled cfr (11092) under review |
| 20-01-2024 01:34 AM UTC | L1 Reviewer (L1 Reviewer) submitted their review of cfr (11092) |
| 20-01-2024 01:34 AM UTC | L1 Reviewer (L1 Reviewer) passed Scale of Solution for cfr (11092) |
| 20-01-2024 01:34 AM UTC | L1 Reviewer (L1 Reviewer) edited Scale of Solution for cfr (11092) |
| 20-01-2024 01:34 AM UTC | L1 Reviewer (L1 Reviewer) passed 9C. Protection from Harassment for cfr (11092) |
| 20-01-2024 01:34 AM UTC | L1 Reviewer (L1 Reviewer) passed 9B. Inappropriate & Illegal Content for cfr (11092) |
| 20-01-2024 01:34 AM UTC | L1 Reviewer (L1 Reviewer) passed 9A. Data Privacy & Security for cfr (11092) |
| 20-01-2024 01:34 AM UTC | L1 Reviewer (L1 Reviewer) passed 8. Open Standards & Best Practices for cfr (11092) |
| 20-01-2024 01:33 AM UTC | L1 Reviewer (L1 Reviewer) failed 7. Privacy & Applicable Laws for cfr (11092) |
| 20-01-2024 01:32 AM UTC | L1 Reviewer (L1 Reviewer) edited 7. Privacy & Applicable Laws for cfr (11092) |
| 20-01-2024 01:29 AM UTC | L1 Reviewer (L1 Reviewer) passed 6. Non-PII Data Extraction for cfr (11092) |
| 20-01-2024 01:29 AM UTC | L1 Reviewer (L1 Reviewer) edited 6. Non-PII Data Extraction for cfr (11092) |
| 20-01-2024 01:28 AM UTC | L1 Reviewer (L1 Reviewer) passed 5. Documentation for cfr (11092) |
| 20-01-2024 01:27 AM UTC | L1 Reviewer (L1 Reviewer) edited 5. Documentation for cfr (11092) |
| 20-01-2024 01:27 AM UTC | L1 Reviewer (L1 Reviewer) passed 4. Platform Independence for cfr (11092) |
| 20-01-2024 01:27 AM UTC | L1 Reviewer (L1 Reviewer) edited 3. Clear Ownership for cfr (11092) |
| 20-01-2024 01:27 AM UTC | L1 Reviewer (L1 Reviewer) passed 3. Clear Ownership for cfr (11092) |
| 20-01-2024 01:26 AM UTC | L1 Reviewer (L1 Reviewer) passed 2. Open Licensing for cfr (11092) |
| 20-01-2024 01:26 AM UTC | L1 Reviewer (L1 Reviewer) edited 2. Open Licensing for cfr (11092) |
| 20-01-2024 01:25 AM UTC | L1 Reviewer (L1 Reviewer) passed 1. SDG Relevance for cfr (11092) |
| 20-01-2024 01:25 AM UTC | L1 Reviewer (L1 Reviewer) edited 1. SDG Relevance for cfr (11092) |
| 20-01-2024 01:24 AM UTC | L1 Reviewer (L1 Reviewer) passed General Information for cfr (11092) |
| 19-01-2024 06:42 PM UTC | L1 Reviewer (L1 Reviewer) pulled cfr (11092) under review |
| 22-11-2023 03:55 PM UTC | Claudine Lim (Applicant) submitted application for cfr (11092) |