|
|
Dear OpenMRS experts, I am new to OpenMRS. And pardon me if my questions below is
too rudimentary. In my project, I need to model a cancer treatment summary
form in OpenMRS. For example, a chemotherapy treatment summary form may contain
such fields as name and address of institution where chemotherapy was given,
oncologist's name, nurse or nurse practitioner's name, and up to eight
medications used in the treatment. Each medication has five fields that needs
to be filled out: name of medication, dose per administration, number of doses,
cumulative dose and how given. My questions are: 1.
Is it OK to model this type of form as a single OpenMRS
encounter (i.e. chemotherapy treatment encounter)? 2.
Is there any other (and better) way to model this type
of form using existing OpenMRS entities? 3.
Can we model each chemotherapy medication as a separate
obs and add five notes to represent each of the medication's five attributes
(i.e. name, dose, etc) respectively? 4.
Is there a better way to model an observation with
multiple attributes (e.g. an OpenMRS data type with multiple sub-components)? 5.
Is there a way to link one encounter with another and
how? e.g. I may want to model an aggregated cancer treatment summary form
as an encounter, which contains all of the treatments received by a patient,
and link that form to multiple individual cancer treatment forms modeled also
as an encounter. Your answers and suggestions are highly appreciated! Hui Xiao Systems Engineer Medical
Informatics Regenstrief
Institute, Inc. 410 West 10th
Street, Suite 2000 Indianapolis, IN
46202-3012 Phone 317-423-5527 email: hxiao@... [hidden email] from OpenMRS Developers' mailing list |
|
Ben Wolfe (openmrs) |
|
|
To answer your 0th question:
Encounters do not have encounter_attributes yet. So you'd have to store them as obs and the value would go into obs.value_text maybe. You want to use obs groups for each medication probably. They would then be grouped. I /think/ that'd be the best dictionary mapping method: MEDICATION_ORDERED MEDICATION_NAME = ______ DOSE = ____ # = ____ CUML DOSE = ____ HOW = _____ Not sure on the last one. For 1.9+ it would fit into the Episode that has been modeled out. I'm not sure how it could be done now. You will have to create your own grouping object maybe. I've seen it down using a mashup of programworkflows and encounters before (see the inpatient module) Ben On 08/25/2010 11:45 AM, Hui Xiao wrote: > Dear OpenMRS experts, > > > > I am new to OpenMRS. And pardon me if my questions below is too rudimentary. > > > > In my project, I need to model a cancer treatment summary form in > OpenMRS. For example, a chemotherapy treatment summary form may contain > such fields as name and address of institution where chemotherapy was > given, oncologist's name, nurse or nurse practitioner's name, and up to > eight medications used in the treatment. Each medication has five fields > that needs to be filled out: name of medication, dose per > administration, number of doses, cumulative dose and how given. > > > > My questions are: > > > > 1. Is it OK to model this type of form as a single OpenMRS > encounter (i.e. chemotherapy treatment encounter)? > > 2. Is there any other (and better) way to model this type of form > using existing OpenMRS entities? > > 3. Can we model each chemotherapy medication as a separate obs and > add five notes to represent each of the medication's five attributes > (i.e. name, dose, etc) respectively? > > 4. Is there a better way to model an observation with multiple > attributes (e.g. an OpenMRS data type with multiple sub-components)? > > 5. Is there a way to link one encounter with another and how? e.g. > I may want to model an aggregated cancer treatment summary form as an > encounter, which contains all of the treatments received by a patient, > and link that form to multiple individual cancer treatment forms modeled > also as an encounter. > > > > Your answers and suggestions are highly appreciated! > > > > Hui Xiao > > Systems Engineer > > Medical Informatics > > Regenstrief Institute, Inc. > > 410 West 10th Street, Suite 2000 > > Indianapolis, IN 46202-3012 > > Phone 317-423-5527 > > email: [hidden email] > <https://owa.regenstrief.org/owa/redir.aspx?C=f7f3bb70e65a459c8c94a2d34ba308b3&URL=mailto%3atfrench%40regenstrief.org> > > > > ------------------------------------------------------------------------ > Click here to unsubscribe > <mailto:[hidden email]?body=SIGNOFF%20openmrs-devel-l> from > OpenMRS Developers' mailing list _________________________________________ To unsubscribe from OpenMRS Developers' mailing list, send an e-mail to [hidden email] with "SIGNOFF openmrs-devel-l" in the body (not the subject) of your e-mail. [mailto:[hidden email]?body=SIGNOFF%20openmrs-devel-l] |
|
Burke Mamlin |
|
|
On Aug 27, 2010, at 2:28 PM, Ben Wolfe wrote:
> To answer your 0th question: > Encounters do not have encounter_attributes yet. So you'd have to store > them as obs and the value would go into obs.value_text maybe. > > You want to use obs groups for each medication probably. They would > then be grouped. I /think/ that'd be the best dictionary mapping method: > MEDICATION_ORDERED > MEDICATION_NAME = ______ > DOSE = ____ > # = ____ > CUML DOSE = ____ > HOW = _____ > > Not sure on the last one. For 1.9+ it would fit into the Episode that > has been modeled out. I'm not sure how it could be done now. You will > have to create your own grouping object maybe. I've seen it down using > a mashup of programworkflows and encounters before (see the inpatient > module) We will have the notion of a "visit" in OpenMRS by 1.9 that will group encounters. In the meantime, grouping encounters requires a strategy for grouping that uses encounter dates, encounter types, and/or observations to form the groupings you need. Or, as Ben suggests, creation of a module to mimic our upcoming "visit" grouping. Cheers, -Burke > > Ben > > On 08/25/2010 11:45 AM, Hui Xiao wrote: >> Dear OpenMRS experts, >> >> >> >> I am new to OpenMRS. And pardon me if my questions below is too rudimentary. >> >> >> >> In my project, I need to model a cancer treatment summary form in >> OpenMRS. For example, a chemotherapy treatment summary form may contain >> such fields as name and address of institution where chemotherapy was >> given, oncologist's name, nurse or nurse practitioner's name, and up to >> eight medications used in the treatment. Each medication has five fields >> that needs to be filled out: name of medication, dose per >> administration, number of doses, cumulative dose and how given. >> >> >> >> My questions are: >> >> >> >> 1. Is it OK to model this type of form as a single OpenMRS >> encounter (i.e. chemotherapy treatment encounter)? >> >> 2. Is there any other (and better) way to model this type of form >> using existing OpenMRS entities? >> >> 3. Can we model each chemotherapy medication as a separate obs and >> add five notes to represent each of the medication's five attributes >> (i.e. name, dose, etc) respectively? >> >> 4. Is there a better way to model an observation with multiple >> attributes (e.g. an OpenMRS data type with multiple sub-components)? >> >> 5. Is there a way to link one encounter with another and how? e.g. >> I may want to model an aggregated cancer treatment summary form as an >> encounter, which contains all of the treatments received by a patient, >> and link that form to multiple individual cancer treatment forms modeled >> also as an encounter. >> >> >> >> Your answers and suggestions are highly appreciated! >> >> >> >> Hui Xiao >> >> Systems Engineer >> >> Medical Informatics >> >> Regenstrief Institute, Inc. >> >> 410 West 10th Street, Suite 2000 >> >> Indianapolis, IN 46202-3012 >> >> Phone 317-423-5527 >> >> email: [hidden email] >> <https://owa.regenstrief.org/owa/redir.aspx?C=f7f3bb70e65a459c8c94a2d34ba308b3&URL=mailto%3atfrench%40regenstrief.org> >> >> >> >> ------------------------------------------------------------------------ >> Click here to unsubscribe >> <mailto:[hidden email]?body=SIGNOFF%20openmrs-devel-l> from >> OpenMRS Developers' mailing list > > _________________________________________ > > To unsubscribe from OpenMRS Developers' mailing list, send an e-mail to [hidden email] with "SIGNOFF openmrs-devel-l" in the body (not the subject) of your e-mail. > > [mailto:[hidden email]?body=SIGNOFF%20openmrs-devel-l] _________________________________________ To unsubscribe from OpenMRS Developers' mailing list, send an e-mail to [hidden email] with "SIGNOFF openmrs-devel-l" in the body (not the subject) of your e-mail. [mailto:[hidden email]?body=SIGNOFF%20openmrs-devel-l] |
| Powered by Nabble | See how NAML generates this page |