Generated UML - roadmap for PlantUML to replace MagicDraw
Likely to be a 6m - 1y project, but could be interesting. We should invite Borut@NeoEHR to present.
ES, TB: take a parallel approach -
SI: lots of details to take care of - moving to BMM as primary rep is a big change; getting descriptions from UML tool would be good.
SEC: make sure we have a REAL need
need to consider cost of work v value
potentially get Borut Jures to present in new year.
Making the documentation easier to use
Possible initial ideas:
specifications website; move conformance down?
dev v tool builder flavours?
SI: integrate specs into integrated page layout - ongoing
ask your devs!!!!!
Discuss on Discourse - informal survey on ‘what would you like on the specs site, what’s annoying?'; what order; what docs do you most often use? First time versus experienced use.
Augmented demographics model.
See #general in slack Discourse
ES: in REST API, we want URNs that may point to demographics, but also other things, e.g. ‘batch’, ‘result’, ‘device’ - ‘entities’
(Possibly also discuss adding REGISTRY class etc, inspired by the EHR class in some later release of the RM)
Sebastian Iancu Confluence page.