Dave,
An alternative from a Single File Wiki enthusiast.
Since you want to share a custom wiki with each patient, I would maintain a
single master wiki (not OK) and use a custom template to generate their
wiki as needed. Set the $:/status/UserName field so if they do make edits
you can actually extract them if necessary.
An alternative to a custom template, is using the innerwiki plugin. You get
to set what tiddlers are including in addition to the core, in a new wiki
which appears in an iframe. If in the inner wiki you can save the whole
new wiki to a new wiki file, with only the tiddlers that the innerwiki
plugin included, or any subsequent edits. This would include the wiki
filename, based on the patient, the custom wiki tiddlers look and feel and
a single patients records. Also consider adding a version number and
published date to the Patient wiki, so you can ask over the phone if they
were possibly not on the most recent.
Sending updates to someone is sometimes best handled by you holding the
source of truth and just sending a totally updated result.
Regards
Tony
On Tuesday, April 28, 2020 at 2:46:54 PM UTC+10, Dave Parker wrote:
>
> I'm going to be keeping track of progress of patients across multiple
> visits, and I have a couple ideas of how to do that.
>
> [[cc1]] (short for chief complaint 1) would be the first complaint
> tiddler, lets say with an alias of "headaches"
>
> In that tiddler would be several fields filled in on the first visit, e.g.
> location, onset, quality, severity, frequency, etc.
>
> On each subsequent visits (visit tiddlers would be dates, e.g
> [[2020-04-27]]) there would have to be updates about that cc1 condition,
> say "VAS-high" and VAS-low" for the patient's pain levels between visits,
> and there would potentially be several more data points like that to record
> and keep track of over time (things in the general headings of Subjective,
> Objective, Assessment, and Plan Of Management)
>
> My initial thought (Visit-centric) would be to have in the visit tiddler
> ("2020-04-23") a field called cc1.vashi and cc1.vaslo and keep the info
> there:
> [[2020-04-23]]
> field "cc1.vashi"=9
> field "cc1.vaslo"=4
>
> The alternative (Complaint-centric) would be to have tiddlers called
> cc1.VAS-high etc (probably tagged with "cc1") and have them as data
> tiddlers with keyvalue pairs like:
> [[cc1.VAS-high]]
> 2020-04-23:9
> 2020-04-27:7
>
> Or maybe it would be better to put info into the visit tiddler as keyvalue
> pairs:
> [[2020-04-27]]
> cc1.vashi:7
> cc1.vaslo:3
>
> Having never done a really big TW project before I'm not sure if any of
> these makes more sense than the other, but I envision making notes on
> anywhere from 10-30 variables for each visit and I plan on being able to
> attempt to correlate changes in one variable to changes in others as a sort
> of in-office research project (do changes in leg length correlate to
> headaches or a certain treatment procedure, e.g.)
>
> • Question: Is there actually a "best practice" for a project like
> this, or is one data structure as good as the next?
>
> I guess I'm wanting the best way to A) track progress over time and B)
> find previously unseen data relationships and manipulate it the way TW
> nicely does.
>
> P.S. Does anyone ever put keyvalue pairs in fields (e.g. field="vashi"
> text="2020-04-23:9,2020-04-27:7", or would that be a nightmare to use in
> macros and filters later on?
>
>
> thanks,
> - Dave
>
--
You received this message because you are subscribed to the Google Groups
"TiddlyWiki" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to [email protected].
To view this discussion on the web visit
https://groups.google.com/d/msgid/tiddlywiki/57728113-2584-4bc8-b16b-68a185c376a6%40googlegroups.com.
