SynapseDirect

What I am doing now for temperature is use a reasonable range from which to pick the alternatives.  So, for Centrigrade, I have

*nn* . *n* where nn is 35 thru to 40 and n is 0 thru 9

what's the reasonable range for Fahrenheit?

Using text macros in that way sounds like a pretty reasonable accommodation - necessitates 2 popups, but the choices on each are fairly limited.  I hope it can work to mix GUI templates and text macros, as I think it will make it possible to mix the best features of both.  Fahrenheit ranges should probably go from 95 to 105 or even 106.  The lower range could be all the way down to the high 80's in the case of extreme hypothermia in  an ER setting.  In that case, you could probably have more than one temperature range to select from, because it would be a known hypothermia case to begin with.  Is anyone using synapse in an ER setting that you know of so far?

Not that I know of.

But I would think the nursing staff would enter the temperature via the vitals popup, and so what the template really needs to do is pull in the latest temperature etc from that data.

So, as *age* pulls in the age, perhaps *TempF* should pull in the temperature as last recorded.... 

But I would think the nursing staff would enter the temperature via the vitals popup, and so what the template really needs to do is pull in the latest temperature etc from that data.

So, as *age* pulls in the age, perhaps *TempF* should pull in the temperature as last recorded....

Yes, that would be the best for sure.  Bear with me as I become accustomed to where all the regular chart stuff is located in synapse.  Can *TempF* be done right now?
 

No, I was suggesting that we have more macros that pull in patient stuff like this.

So far we have ( add the *xxx* )

• age
• sex
• title
• surname
• fname
• occupation

Seems like we perhaps also need

• TempF
• TempC
• BP
• pulse
• O2
• Weight
• Height
• BMI
  

Anything else?

Seems like we perhaps also need

• TempF
• TempC
• BP
• pulse
• O2
• Weight
• Height
• BMI
  

Anything else?

Yes --- respirations, P02 -> pulse oximetry, head circumference, in the ER would need PCO2 for hypercapnea monitor, and peak flow.  If you use an EMR in the urgent care or ER, the ability to do reassessments is key, so repeat sets of PO2, peak flow, pulse, BP, respirations, temp are needed and particulars for each (BP-->R arm laying, Temp-->Axillary, etc.).  We use pulse oximetry and peak flow routinely in urgent care.  Some consider pulse oximetry to be a 5th vital sign.

jparkdo:

 

Yes --- respirations, P02 -> pulse oximetry, head circumference, in the ER would need PCO2 for hypercapnea monitor, and peak flow.  If you use an EMR in the urgent care or ER, the ability to do reassessments is key, so repeat sets of PO2, peak flow, pulse, BP, respirations, temp are needed and particulars for each (BP-->R arm laying, Temp-->Axillary, etc.).  We use pulse oximetry and peak flow routinely in urgent care.  Some consider pulse oximetry to be a 5th vital sign.

Ok, O2 saturation is already on the vitals popup, as is respirations.
Head circumeference though??  When is that useful?

PEFR ... could add that.
PC02 ... really only ER use I suspect.

Ok, O2 saturation is already on the vitals popup, as is respirations.
Head circumeference though??  When is that useful?

PEFR ... could add that.
PC02 ... really only ER use I suspect.

Oops, your right, I see O2 is plainly in front of me.

Yes, PCO2 would only be of interest to the ER.  I'm not sure if synapse would ever be used in that environment.

We do use PEFR on an ongoing basis in urgent care and a lot of primary offices do too with asthma tx and after nebulization tx.

Head circumference would be routinely tracked for the first few months at least by primary offices (GP, peds) treating neonates and infants.  The CDC has a head circumference vs age graph for it similar to the height and weight curve.

 

jparkdo:

Head circumference would be routinely tracked for the first few months at least by primary offices (GP, peds) treating neonates and infants.  The CDC has a head circumference vs age graph for it similar to the height and weight curve.

 

Using the quote button instead of the reply button

oh .. well Synapse does have a place to enter this data for growth charts.
 

R213B18

I have a macro called *PIPs* which is defined as "$PIPs: list of all the PIP joints"

The GUI definition for this is:

Title: PIPs: list of all the PIP joints
Type: O
Code:

group-box -1x-1 "" data [
 hcheck-group 30x25 data [
 "thumb IP" none
 "index PIP" none
 "middle PIP" none
 "ring PIP" none
 "little PIP" none
 ]
]

Now you can have this in a consult:

There was synovitis of his right *PIPs*

Which could translate into

There was synovitis  of his right PIPs:  index PIP,  middle PIP  

Beta 19 has these new macros that take the values from the vitals:

• *tempF* (Fahrenheit)
  
• *tempC* (Celcius)
  
• *o2*
• *resps*
• *bp*
• *systolic*
• *diastolic*
• *waist* (cms)
  
• *height* ( cms )
  
• *heightins* (inches)
  
• *weight* (kgs)
  
• *weightlbs* (lbs)
  
• *bmi*

Graham:

Beta 19 has these new macros that take the values from the vitals:

• *tempF* (Fahrenheit)
  
• *tempC* (Celcius)
  
• *o2*
• *resps*
• *bp*
• *systolic*
• *diastolic*
• *waist* (cms)
  
• *height* ( cms )
  
• *heightins* (inches)
  
• *weight* (kgs)
  
• *weightlbs* (lbs)
  
• *bmi*

 That sounds good, and should do it for vitals in the note.  I think for myself I will make a way, maybe a GUI template to insert sets of vitals that have been taken after for followup after treatments in urgent care.  I can just add the PEFR number when needed.

I'll get around to adding PEFR next time.

At present I am going to do a little video showing how the gui and word macros can be mixed.

Graham called these ..

Beta 19 has these new macros that take the values from the vitals:

• *tempF* (Fahrenheit)
  
• *tempC* (Celcius)
  
• *o2*
• *resps*
• *bp*
• *systolic*
• *diastolic*
• *waist* (cms)
  
• *height* ( cms )
  
• *heightins* (inches)
  
• *weight* (kgs)
  
• *weightlbs* (lbs)
  
• *bmi*

 

macros ...

We use the term macro already for systematically replacing text to generate a Visit Note.

Pulling data (either labs or vitals, or whatever) to generate a note is a much more impressive task.

We need a term that matches the coolness of this ....

ideas ?

AutoPull ?  AutoData ? 

I like the word Auto in it, because it requires little end user work (which is very good !).

MacroPull ?

AutoElement ? (ie. automatically pull data elements ?)

ideas .. ?

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