David,
I think tiddlywiki could be a great tool for this, lean on us if you need
help.
This is a complex subject you ask questions about, here are a few tips.
My Gut feeling is to make the key object the patient not the complaint, but
if the complaint is selected from or arrives on a list then you should be
able to look at if from a complaint perspective. Its really good to design
your solution so that you can look at it from every possible perspective.
I am concerned your using tiddlers with a date in it. Why not use visit 1,
or patient - visit 1, patient - visit 2, date is only a detail I would put
in a date field.
Fields and their values can be represented as key value pairs, I think you
are making too much work for yourself adding key value pairs inside fields
because then you can use simple tiddlywiki field operators in filters. If
Creating a new tiddler you can provide key=value pairs to create fields.
There is no best practice for this in tiddlywiki for this to my knowledge,
there are best practice guides for designing any database, or practice
management, but that is a broad subject.
If you are *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.* then consider the following;
- Use tiddlers as objects *and *tiddlers as transactions, link the two
by tag or field eg; every transaction has a field or tag containing the
patient it belongs to.
- Let all tiddlers that represent real things, be known only by their
name, perhaps adding an object-type field that classifies them like
object-type = person.
- Don't get hung up on tiddler names for recurring items, use a simple
increment made unique to that which it applies eg "patient - visit N", or
have a separate visit number for each visit no matter who it is and assign
the person to it.
- Do not use compound values in any title, they are the "key" so don't
make life difficult.
In the database world they say
The data should be related to the key, the whole Key and nothing but the
key.
The data should be related to the key (person contains person info), the
whole Key (no compound keys) and nothing but the key (don't put visit
details, which can happen multiple times in a person tiddler).
Perhaps that can get you started.
Ask here for more detailed guidance in separate focused posts.
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/e31ee593-021d-427d-830a-53a0732e5a35%40googlegroups.com.
