Models and Patterns: getting tech and clinical people together
Tech review of clinical models
- technical patterns approach for tools
- patterns workshop for clin community?
- how do tech people get involved in reviews
- Ian; join existing reviews (adopt an archetype...)
- Patterns
- Questionnaires - new Entry type? (Samuel Frade)
- Timing in Rx archetype / TP model
- Labs - TB
- Cambio - 22 examples in Psych; collection of Archetypes, GDLs, etc; 100s overall - Rong
Ian: avoid another long tech review round; better to have tech people inside the same review.
Dissemination
Sharing - should be using Github for CKM; how to synchronise e.g. DIPS own Git repos v CKM
Rong: should always use Github as the sharing mechanism and allow e.g. pull requests etc
Package Management
Dependency management - not handled properly; need equivalent of NPM, Maven etc;
Also need better designed packages and release concept.
Problem of channels from Vendor / customer environments to openEHR
Opinions:
- Ian: find a way for companies to publish own templates and archetypes.
- Erik: no/poor channel for translations back to int'l CKM.
Erik: could companies use forks of CKM-mirror and paste in their own archetypes in sub-folders?
Erik: can we find a way for companies to easily publish their own models, with 0 effort?