quadevs

Editorial policy

How we write the insights, case studies and service pages on this site, and what happens when one of them is wrong.

What we publish

Three kinds of pages. Insights explain the standards and systems we work with: FHIR, TEFCA, USCDI, HEDIS, clinical data platforms, medical document OCR and schema markup for healthcare sites. Case studies describe systems we built. Service pages say what we build and how a project starts.

Everything here is written by the studio. We publish no guest posts.

Where the facts come from

A statement about a standard or a regulation is checked against its official text before the page goes live: the HL7 specification for FHIR, the published framework for TEFCA, the NCQA measure specifications for HEDIS, the regulation itself for GDPR or the EHDS. Where the source and our experience differ, the page says which is which.

Case studies come from our own projects. Client names stay out unless the client agreed to be named, and the systems are described as they were delivered.

AI tools in our writing

We use AI tools for research and drafting, as the principles page says for code. A draft is published only after the facts in it have been checked against their sources, and every page is scanned for the patterns of machine-written text before it goes live.

Updates and corrections

Each article shows the date it was last updated, and the date changes when its content does. Standards move: when a new version changes what an article says, we revise the article.

Found an error? Write to hello@quadevs.com with the page address and what is wrong. We check it, correct the page if you're right and reply either way.

Independence of what we write

No page on this site is sponsored, and we use no affiliate links. When we name a product or a vendor, it is because a project used it. Our own services are described on their service pages; the contact form is the way to ask about them.