Stream: implementers
Topic: Forge Observation.value[x]
Brian Reinhold (Apr 11 2017 at 14:03):
When I open up the value[x] element in an Observation structure definition, the Quantity, string, SampledData, and CodeableConcept appear twice. I do not know why.
Michel Rutten (Apr 11 2017 at 14:23):
@Brian Dunstan what version of Forge are you using? I cannot reproduce the issue in the 15.4 release on a new Observation profile.
Brian Reinhold (Apr 11 2017 at 14:40):
I am using 15.4 uploaded a few days ago. It may have something to do with the fact I checked these four options the other day and on reopening the project those four were shown checked in addition to duplicates of those four unchecked. Unchecking the options did not make them go away.
Michel Rutten (Apr 11 2017 at 14:55):
Possibly the profile got corrupted. You could try to open the XML in a text editor and manually remove the offending constraints.
Mounika (Apr 27 2017 at 12:23):
Hi all, we are trying to capture social history of a patient. Here my doubt is which resource we have to use either Observation or Questionnarie? Please clarify me
Lloyd McKenzie (Apr 27 2017 at 13:08):
Questionnaire is a tool for raw data capture - it can be used to define structures to capture any sort of information at all. However, it's not intended for data comparison/analysis/retrieval. So you might capture information using Questionnaire/QuestionnaireResponse, but then later propagate that information to the appropriate Observations, MedicationStatements, AllergyIntolerances, etc. Social history would typically live in Observation.
Mounika (Apr 27 2017 at 13:16):
Thank you @Lloyd McKenzie So, It's comes under Observation resource.We don't need to create questions in social history right?
Lloyd McKenzie (Apr 27 2017 at 14:22):
You never have to use Questionnaire. Questionnaire gives you tight control over exactly how questions are phrased, what order they're asked in, conditional rules about what questions should be asked in which circumstances, etc. However the data represented in a social history can always be captured using straight Observations
Mounika (Apr 28 2017 at 04:27):
Okay @Lloyd McKenzie Thank you
Mounika (Apr 28 2017 at 05:51):
In our Ipad app we are capturing social history. In that we have observations like smoking, alcohol intake, Drug abuse and etc. So these all are comes under in one observation or we need to take them as different types of observations? Plaese help me
Mounika (Apr 28 2017 at 05:57):
For ex:Social-hist.PNG
Lloyd McKenzie (Apr 28 2017 at 13:49):
They should be separate observations - though you can have another observation that groups them into a "panel" if you wish. Sticking things into a single observation (with component) is generally limited to data that can't be reasonably interpreted independently and that must always be captured together. Things like the pieces of an APGAR, the susceptability + the organism or the systolic and diastolic values of a blood pressure. There is no such tight relationship between smoking history and alcohol history
Mounika (May 02 2017 at 06:22):
Thank you @Lloyd McKenzie
Mounika (May 02 2017 at 13:16):
Hi @Lloyd McKenzie In our ipad app, we have social History like smoking,alcohol,drug and etc... for example In smoking history see this Social-hist.PNG , in alochol alcohol.PNG How to implement these categories? please give me some suggestions.
Lloyd McKenzie (May 02 2017 at 13:29):
That's sort of what I meant by a separate Observation to represent the "panel". So you can have a general Observation labeled "Smoking History" that points to the individual Observations that capture "packs/day", etc.
Mounika (May 02 2017 at 13:31):
@Lloyd McKenzie actually i am not getting how to map these feilds to observation resource?
Lloyd McKenzie (May 02 2017 at 14:59):
Each field will be a separate Observation - code defining the observation, answer being in value.
Eric Haas (May 02 2017 at 16:28):
See this example for smoking for example
Mounika (May 03 2017 at 04:34):
@Lloyd McKenzie Thank you
Mounika (May 03 2017 at 04:34):
@Eric Haas Thank you
Last updated: Apr 12 2022 at 19:14 UTC
