Help with clinical modelling

Clinical
1

Hello everyone. I am looking for some help. I am supposed to model about 20 forms this month for our migration. I’m looking at doing up to 4 this week but I’d need some review to ensure that I’m modeling it right. I’ve modeled before, just not in production and I’ve seen videos of @Sidharth_Ramesh and @ian.mcnicoll modeling on YouTube.

I wanted to ask if there was anyone that’d be willing to help with this review just to confirm that I’m making the right modeling choices. An expert opinion would really help. Thanks

2

Hey @Anselm_Iwuanyanwu , you can send me a direct message here on discourse. I can provide some help.

3

Hi @Anselm_Iwuanyanwu i’m open to helping as well

.

4

Unless there are any legal issues with exposing drafts publicly, could I suggest posting them in public topics like this one instead of in private messages? Many more people will be able to help then :blush:

5

Hi Keisha, it’s been a minute. :slightly_smiling_face:

I’d reach out via DM

6

I would confirm this and share if there aren’t.

7

General advice:

  • Always start with a mindmap of the form/functionality you are planning to make
  • Identify the data you want to record (or migrate to, if I understand you correctly)
  • Download the archetypes from the CKM you find that match the data, and import them to the mindmap
  • Move them around in the mindmap, to reflect your use case, and identify which elements that match the data you want to record
    • It is smart to also add any value sets as comments or adjacent to the archetypes in the mindmap
  • And also: Which data in your requirements does NOT exist in one of your chosen archetypes?
  • You can have a look at other CKM’s as well, but note that they might not be updated to the most recent design, and are not safe to use
  • Missing archetypes? Two options:
    • Make one yourself, upload it to the CKM as a proposal. Be prepared to work with the International Editorial Board and/or the CKAs.
    • If the data is only to store data to fit your local requirements, or are not for re-use in a different setting, keep it as a local archetype, but remember to name it with an underscore, to differentiate it from (potentially) published version. For example: OBSERVATION.“very_special_only_for_my_usecase”_ng.v1 if your system are to be used in Nigeria, or with your company name after the underscore “xyz_healthstack.v1”
  • Doing the above BEFORE you make the template and form, will save you A LOT of work

Good luck! :smiley: