{
  "$type": "site.standard.document",
  "bskyPostRef": {
    "cid": "bafyreihwo4horr4s7iz22iie2vupasg5u4ylr22xuspaxu3iwja6solyma",
    "uri": "at://did:plc:wwyqal4cnqhuwyacdj7rqq3n/app.bsky.feed.post/3mhxfjrdydvt2"
  },
  "path": "/t/scoping-review-soci-to-assess-dhis2-applicability-for-ncd/28675#post_2",
  "publishedAt": "2026-03-26T05:57:15.000Z",
  "site": "https://discourse.datamethods.org",
  "tags": [
    "Software Features - DHIS2",
    "https://www.measureevaluation.org/resources/publications/ms-19-158/at_download/document#page=19",
    "Scoping reviews",
    "Digital public goods - Wikipedia",
    "Centor criteria - Wikipedia",
    "failed to achieve localization"
  ],
  "textContent": "Welcome, Oleg! As a new user, you probably aren’t permitted to add very many links to your first post. So I will just drop 3 here, which I have found interesting to look up:\n\n  * Software Features - DHIS2\n  * On HIS Stages Of Continuous Improvement (SOCI): https://www.measureevaluation.org/resources/publications/ms-19-158/at_download/document#page=19\n  * Scoping reviews\n\n\n\nI hadn’t heard of DHIS2 before; the Digital public goods - Wikipedia concept is appealing.\n\nAs for the formulas you present, they remind me very much of the arbitrary ‘scoring systems’ often appearing in primitive clinical assessment tools such as the Centor criteria - Wikipedia. My feeling is that your formulas don’t warrant criticism in and of themselves; rather, their arbitrary nature points to a bigger problem.\n\nThat problem is that this whole enterprise looks like piling abstraction upon abstraction, each one supporting a new layer of bureaucracy 1 further step removed from the real problems. I noticed that the HIS SOCI link above was funded by USAID, which famously has failed to achieve localization.\n\nOne hard question to ask yourself: even if you pursue this effort with all due diligence and sincerity, what would distinguish it from something generated by an LLM? My sense is that the only way to ensure such a distinction is to adopt an actively critical stance — starting with posing a **sharply-defined problem**. One way to do this would be to _contrast_ DHIS2 against one or more competing technologies. Perhaps you could consider a _specific_ non-communicable disease. Perhaps you could examine one _particular_ aspect of adoption, such as how difficult it is to develop a new mobile app or data dashboard in DHIS2 vs competitors.",
  "title": "Scoping review + SOCI: to assess DHIS2 applicability for NCD"
}