maturity model clarification - who approves pull requests?

[isaacvetter]

The CDS Hooks Maturity Model level of 'Tested - 2' has these requirements:

Maturity Level	Maturity title	Requirements
2	Tested	The above, and … The hook has been tested and successfully supports interoperability among at least one CDS client and two independent CDS services using semi-realistic data and scenarios (e.g. at a FHIR Connectathon). The github pull request defining the hook is approved and published.

The CDS Hooks project's governance model includes a formal Project Management Committee comprised of the individuals technically enabled to commit directly to the source of the specification as it's published on https://cds-hooks.org. Of course, any modification of content on the https://cds-hooks.hl7.org site requires a more formal and ANSI-compatible process as implemented by HL7. The cds-hooks.org site (and associated github.com/cds-hooks) are intended to serve as a breeding ground for new ideas and contributed implementer artifacts. As reflected in the Maturity Model, the barriers for adding new content to cds-hooks.org are lower than those required to change the HL7 published specification. This two-stage maturation is intended to be a feature to the implementer community such that eventually successful ideas are to be incorporated into the HL7 specification as they are proven.

The published Maturity model should be updated to clearly indicate that it's the CDS Hooks PMC which approves and publishes these low-level hooks.

Maturity Level	Maturity title	Requirements
2	Tested	The above, and … The hook has been tested and successfully supports interoperability among at least one CDS client and two independent CDS services using semi-realistic data and scenarios (e.g. at a FHIR Connectathon). The github pull request defining the hook is approved and published by the CDS Hooks Project Management Committee .