I have long advocated healthcare platforms. I have also mentioned (in the past) about the economics and “micoservices” (if you will) around those platforms. You can then run the services in isolation or through the inter-dependability modules for a desired outcome. This also facilitates data retention and running AI algorithms at scale; providing the returns on investment to investigate specific healthcare outcomes.
In defence of standards:
Technical standards are awesome. Standards help teams save time and money by giving them a common language for how their products can interact with other products, eliminating the need to build each component within a market or re-define how systems communicate with each other. For example, a team building a new email client doesn’t need to reinvent the format for how email is transmitted between sender and recipient; instead they can just adopt SMTP (Simple Mail Transfer Protocol, the standard that defines how email transmission works) and focus on crafting a great experience for their users. This means the wheel doesn’t get reinvented when someone wants to do something that’s been done before — they can just adopt the standard and accelerate their product development, reaching their audience — and oftentimes, product market fit — much faster than by building completely proprietary products.
Benefits of standards with RSS as and example:
To understand the full scope of benefits that standards provide to product teams, it’s helpful to unpack an example, such as RSS (Really Simple Syndication) in podcasts. RSS has long been the backbone of podcasts, providing a powerful distribution mechanism that enables creators to publish their audio from a single endpoint and immediately syndicate their content to any consumption platform that wants to ingest it. RSS has enabled podcasts to flourish on the open internet over the past two decades by defining a language for how a vast network of podcasters and podcast listening apps communicate with each other. To publish audio via RSS, a creator (or podcasting platform, on the creator’s behalf) must publish the podcast in a specific format and include only the parameters defined within the standard, such as a URL pointing to the podcast’s cover art, a list of episodes, and so on.
Open source standards (in lieu of the proprietary standards) are a welcome approach to determine relevance and ensure data portability. Besides, they ensure anyone contributes and grows the services (in essence, grow ecosystems around it and open API’s).
RadOncNotes 