GA4GH Connect session follow up - Path to normative: implementing a GA4GH maturity model
0 views
Skip to first unread message
Beatrice Amos
Oct 13, 2025, 4:10:34 PM10/13/25
to Wagner, Alex, Melissa Cline, Larry Babb, Andy Yates, Sasha Siegel, Mamana Mbiyavanga, Clinical and Phenotypic Data Capture, GA4GH Variation Representation, Product - Categorical Variation Representation Specification (Cat-VRS), GA4GH Variant Annotation, Discovery Technical Work Stream, TASC, GA4GH Tech Team, Work Stream - Genomic Knowledge Standards (GKS), Cloud Work Stream
Dear Colleagues,
Thank you all for contributing to the GA4GH Connect session: Path to normative: implementing a GA4GH maturity model - what a productive and engaging discussion! A big thank you to Alex Wagner, Larry Babb, Andy Yates, Sasha Siegel, and Mamana Mbiyavanga for an excellent session, and to all participants for their valuable contributions and engaging discussions. Your input made this a truly meaningful conversation.
‼️ Please take a moment to review the meeting notes and share any edits or additions to help keep the summary accurate and complete. If you notice any mistakes, have resources to add, or want to share more details, please feel free to jump in and update the notes - we welcome your input! A link to the recording is available in the linked meeting notes.
Thank you all for contributing to the GA4GH Connect session: Path to normative: implementing a GA4GH maturity model - what a productive and engaging discussion! A big thank you to Alex Wagner, Larry Babb, Andy Yates, Sasha Siegel, and Mamana Mbiyavanga for an excellent session, and to all participants for their valuable contributions and engaging discussions. Your input made this a truly meaningful conversation.
‼️ Please take a moment to review the meeting notes and share any edits or additions to help keep the summary accurate and complete. If you notice any mistakes, have resources to add, or want to share more details, please feel free to jump in and update the notes - we welcome your input! A link to the recording is available in the linked meeting notes.
________
Key Takeaways
🔶 The maturity model is comprehensive and adaptable, suitable for technical products like APIs and data models, but requires customisation for policies due to their unique nature.
🔶 Broad community feedback is essential to stress-test and refine the model, ensuring it aligns with diverse product needs and supports interoperability.
🔶 The model enables clear communication of feature readiness to adopters, from early innovators to those requiring stable, normative standards, enhancing trust and usability.
Key Takeaways
🔶 The maturity model is comprehensive and adaptable, suitable for technical products like APIs and data models, but requires customisation for policies due to their unique nature.
🔶 Broad community feedback is essential to stress-test and refine the model, ensuring it aligns with diverse product needs and supports interoperability.
🔶 The model enables clear communication of feature readiness to adopters, from early innovators to those requiring stable, normative standards, enhancing trust and usability.
________
Meeting Summary
The meeting focused on introducing and discussing the GA4GH Product Feature Maturity Model, a framework designed to communicate the readiness and stability of GA4GH products, such as APIs, data models, and policies, to facilitate interoperability and adoption.
The session included an in-depth exploration of applying the maturity model across various product types, with breakout discussions on APIs, data models, policies, and protocols.
Key points included defining product features, distinguishing between draft, trial use, and normative stages, and addressing challenges in applying the model to non-technical products like policies.
The meeting emphasised community feedback to refine the model and ensure its broad applicability.
________
Action Items
🔶 Product leads should maintain regular communication with implementers to track feedback and progress, ensuring features meet maturity criteria (e.g. moving from draft to trial use or normative).
🔶 Develop tailored guidelines or appendices for different product types, particularly policies, to address nuances in applying the maturity model.
🔶 Gradually introduce the maturity model by auditing existing GA4GH specifications and discussing implementation with Work Stream leads to prepare for broader adoption, potentially by the next Connect meeting.
🔶 Product leads should maintain regular communication with implementers to track feedback and progress, ensuring features meet maturity criteria (e.g. moving from draft to trial use or normative).
🔶 Develop tailored guidelines or appendices for different product types, particularly policies, to address nuances in applying the maturity model.
🔶 Gradually introduce the maturity model by auditing existing GA4GH specifications and discussing implementation with Work Stream leads to prepare for broader adoption, potentially by the next Connect meeting.
________
Your feedback is invaluable and helps us improve future GA4GH Plenary and Connect meetings, ensuring they continue to provide the best possible experience for our community.
If there's anything we missed or anything you'd like to add, feel free to reach out!
Thanks again for your engagement and contributions!
Best,
Beatrice
Thanks again for your engagement and contributions!
Best,
Beatrice
Beatrice Amos
Work Stream Manager
Reply all
Reply to author
Forward
0 new messages