In general, we can think of a spaced repetition system as being (i) Content-aware vs. Content-agnostic and (ii) Deck-aware vs. Deck-agnostic
Content-aware systems care about what you're studying (language, medecine, etc) while Content-agnostic systems don't care about what you're studying.
Deck-aware systems consider each card in the context of the rest of the cards (the "deck") while Deck-agnostic systems consider each card in pure isolation.
Currently, FSRS is both Content-agnostic as well as Deck-agnostic. This makes it extremely easy to integrate into a spaced repetition system, but this also means the model will underfit a bit.
It it interesting to note that you could in practice optimize seperate FSRS models for each deck covering different topics, which would make it Content-aware in a sense. Additionally, "fuzz" is a somewhat Deck-aware feature of the model in that it exists specifically to reduce interactions between other cards in the deck.
I was working in a detail rich context, where there were a lot of items, about which there were a lot of facts that mostly didn't change but only mostly. Getting a snapshot of these details into approximately everyone's head seemed like a job for spaced repetition, and I considered making a shared Anki deck for the company.
What wasn't clear was how to handle those updates. Just changing the deck in place feels wrong, for those who have been using it - they're remembering right, the cards have changed.
Deprecating cards that are no longer accurate but which don't have replacement information was a related question. It might be worth informing people who have been studying that card that it's wrong now, but there's no reason to surface the deprecation to a person who has never seen the card.
Is there an obvious way to use standard SRS features for this? A less obvious way? A system that provides less standard features? Is this an opportunity for a useful feature for a new or existing system? Or is this actually not an issue for some reason I've missed?
When any country mentioned hits the population of a small or medium US state, let us know how it goes.
> Canada, China, India, and Japan also have EHR system initiatives in place at varying levels of maturity.
Apparently the author could not care less. Apparently even the WHO could not care less, given the linked document tells us nothing.
As always, it's the US versus the world, and the world is a giant nothingburger, save some flyover countries in Europe that could be part of Greater Germany or Greater Russia for all anyone cares. How is the UK, Germany, France, Russia, or China doing? Oh...
> The United Kingdom was hoping to be a global leader in adopting interoperable health information systems, but a disastrous implementation of its National Programme for IT ended in 2011 after nine years and more than £10 billion.
No doubt when the US gets the standards and apps done, the rest of the world will magically start working too. All the billions spent and the world piggybacks and gives nothing back, save, quite amusingly, China. As always.
I don't know "how it goes" but Poland has the population of a large US state.
It isn't actually possible for fixing a bug to break a workaround. The point of a workaround is that you're not doing the thing that's broken; when that thing is fixed, your flow won't be affected, because you weren't doing it anyway.
That's not true. For instance, if there's a bug in formatting, that might be worked around by handing the unintended formatting. But now you're (maybe) not handling the intended formatting, and a fix would break you.