SynapseDirect

Graham:

I was thinking exactly the same thing .. the word macros is being over loaded here.

 

I'm not quite sure which word processing program first coined the term "macro" for blocks of text (and/or inserted keystrokes as well--in effect a mini-program) inserted with a single keystroke but I think it was Word Perfect.  Word would call a word processing field that displays a data field a "Form Field" or just a "Field".  Titling a text widget that gets its data from another column in the database a "Field" seems pretty generic to me.  "Element" sounds like "data element" which wouldn't be quite right either.  SQL would call a table subset or superset a "view" (unless it was a query).  "Repeated Data Field" would be fairly accurate, but "Autofilled Data Field" or just "Autofilled Field" or even "Auto Field" sort of gets at the desired action.

Graham:

New video showing the construction of a mixed gui and word macro.

I got super excited when I saw that template pop up !

:)

After some feverish debate, this new method of pulling vitals into a note is going to be called

"Macro Variables" 

But,

in the documentation it could be referred to a "automatically pulling data" into the visit note.  As to be more descriptive to users.  :)

jparkdo:

I'm not quite sure which word processing program first coined the term "macro" for blocks of text (and/or inserted keystrokes as well--in effect a mini-program) inserted with a single keystroke but I think it was Word Perfect.  Word would call a word processing field that displays a data field a "Form Field" or just a "Field".  Titling a text widget that gets its data from another column in the database a "Field" seems pretty generic to me.  "Element" sounds like "data element" which wouldn't be quite right either.  SQL would call a table subset or superset a "view" (unless it was a query).  "Repeated Data Field" would be fairly accurate, but "Autofilled Data Field" or just "Autofilled Field" or even "Auto Field" sort of gets at the desired action.

Oh Hi jparkdo ...I missed this.

:) Great little summary of Computing here.

Long live WordPefect 5.1 for DOS, the great WP of all time.

I like Jerry's "Autofilled" Data Field.

Let's go with calling them Data Fields.

Autofilled Data Fields has a nice ring.

Jason:

I like Jerry's "Autofilled" Data Field.

Let's go with calling them Data Fields.

Autofilled Data Fields has a nice ring.

 

Jason, that's a hilarious screen from WP 5.1 - I still remember some of the keystrokes (shift+F7 =print, etc).  I was just rambling back to see if I could think of anything that has any historical or logical basis for a descriptive name.  Maybe it would be more intuitive to users if it had some basis in previous usage.

jparkdo:

I still remember some of the keystrokes (shift+F7 =print, etc). 

Funny, that's the only one I remember as well 

Jason:

Graham:

New video showing the construction of a mixed gui and word macro.

I got super excited when I saw that template pop up !

Only 2-3 days of my spare time trying to get that working !! 

This is working now in a template macro

Hb @718-7,3

leads to this type of output

Hb 15-Sep-2007 164.0 g/L        OCR
21-Jul-2007 159.0 g/L        M.P.S
31-May-2007 166.0 g/L        OCR

ie. it pulls in the last 3 Hb results for this patient

Now this is pretty cool ...

I can define a word macro *ESR* as "Serial ESRs @4537-7,3" and this pulls in the last three ESRs.

My feeling is that the text macros are pretty functional now with the ability to pull in results from the patient record ( data records ), and bring up GUI templates for more complex examinations.

Sure there might be some more enhancements possible ... like where there is only one choice, it is done for you automatically .. but the time has come to start building some hybrid templates to see where if there are any "gotchas" in the process.

Patient just called me with a problem about her medications .. time to template this.  Should only ever have to document this once.

He called to report some problems with *medications* with *some* side effects of *drugSideEffects*.

I advised him to *temporarily* stop his *medications* and get some blood testing done. 

*followup-phone-appt*
 

Graham:

Patient just called me with a problem about her medications .. time to template this.  Should only ever have to document this once.

He called to report some problems with *medications* with *some* side effects of *drugSideEffects*.

I advised him to *temporarily* stop his *medications* and get some blood testing done. 

*followup-phone-appt*
 

 Yes, I agree that efficient template construction requires a lot of thought, even when the general roadmap seems clear.  I try to be accurate about how long it really takes to use a given template in action, and have literally used a stopwatch to time it in the past.  I know that it is possible to consistently do good ENT documentation in 2 minutes or less (including the prescriptions) with mostly just positives.  My current short term goal is to design an ENT template that consistently documents the negatives and postives in the same time.  I think the ability to mix GUI templates, word macros and Autofilled Fields is very good, and agree that it's "showtime".

A new video showing the documentation of an uncomplicated UTI using the directed template or wizard or daisy chaining technique.

daisy chaining is a great term .. but selectively branching templates might be more intuitive to the NON NERD endusers :)