@jjameswalk@GaryMcAllister For technical standards, if you consider HL7, openEHR, IHE, etc - how many people were/are actively engaged in creating the base standards. In my day it was ~1. Consider the US, Australia, New Zealand, Netherlands, etc - a completely different story.
@jjameswalk@GaryMcAllister If the NHS stopped creating its own standards and perhaps used existing standards then there would be less to deprecate and a greater incentive to follow them.
Time for a new PC.
Current, PC will not run Windows 11, does not support Android App emulator and now will not run Docker.
Any suggestions for a laptop for software development (must support multiple monitors).
@GaryMcAllister An environment to work in that was with other skilled resources. Putting skilled people in a pool where 50% are just plainly not performing is beyond demoralising
My son recently made the decision to become a software developer so we started a project together so I could share some knowledge.
Decided to make a simple web app for my running club.
Scaled out quickly :-)
#aws#flutter#serverless#api
@JohnMeredith It's about establishing consistent patterns both from modelling and implementation perspectives. Each has different methods to resolve to actual codes at runtime.
If you use a valueset then it allows multiple CodeSystems on the same binding. Maybe not an issue in your use case.
@GaryMcAllister I could not agree more - there sheer quantity of "legacy" standards that have been created and never used is just as disappointing as the new ones being created.
As long as standards are built in isolation without the understanding of the existing set, this will continue.