If everyone would expose usable, complete, idiomatic, well-documented APIs with a openly-published specs, I would care a lot less about standards. Our current regulations do not require open specs outside of FHIR and non-API EHI export. So: in the current landscape it is still fine to have proprietary APIs whose definitions are trade secrets and for that to be the only actually-working way to access some data.

“If you are suggesting a shift in regulations to remove requirements for standards but introduce new, strong requirements for openness and completeness (something like: If you have an API that anyone can use, everyone can request authorization and use it once authorized) let’s draft some bullet points 🙂But… if the primary motivation for exposing an API is compliance, then it doesn’t really matter whether the API standards based or not, you’re going to get something unusable. (At least with standards, the general shape of the thing has had some thought go into it.)