Stream: implementers
Topic: Observation
rahul kumar (Mar 12 2018 at 12:41):
Doctor found that patient had "no family history of diseases 'X' here x is in general " so what could be resource type of this Resource. i believe that observation ll be suitable for that .
and how can we utilize " No family history of (contextual qualifier) (qualifier value)
SCTID: 47009004 " for this resource ??
Rob Hausam (Mar 12 2018 at 13:22):
You could do this with FamilyMemberHistory (http://build.fhir.org/familymemberhistory.html#9.4.2.4). And if you want to use that SNOMED CT concept for "no family history of diseases 'X'" you'll need to create a valid SNOMED CT compositional grammar expression and use that as your condition.code, if there isn't an existing pre-coordinated concept for the particular 'X' that you're looking for. That's certainly allowed and encouraged. But a lot of people try to avoid it as they don't want to deal with the complexity of post-coordination.
rahul kumar (Mar 12 2018 at 14:06):
You could do this with FamilyMemberHistory (http://build.fhir.org/familymemberhistory.html#9.4.2.4). And if you want to use that SNOMED CT concept for "no family history of diseases 'X'" you'll need to create a valid SNOMED CT compositional grammar expression and use that as your condition.code, if there isn't an existing pre-coordinated concept for the particular 'X' that you're looking for. That's certainly allowed and encouraged. But a lot of people try to avoid it as they don't want to deal with the complexity of post-coordination.
ok so what we have to use in "relationship" of resource??
mohammad navab husain (Feb 18 2019 at 07:07):
Hi All,
Can we make slicing for Observation resource directly? Can anyone suggest me??
Thanks in advance.
Lloyd McKenzie (Feb 18 2019 at 16:01):
Slicing is only possible on elements within a resource, not on the resource root. And you can only slice elements that either repeat or that support multiple types.
Eric Haas (Feb 18 2019 at 17:35):
Maybe you mean profile on Observation???
mohammad navab husain (Feb 19 2019 at 06:10):
Thank you @Lloyd McKenzie and @Eric Haas .Yes, it is of Observation Profile.
and Can we make extension for Observation resource??
Lloyd McKenzie (Feb 19 2019 at 06:21):
You can make extensions on many things. What are you trying to accomplish?
rekha (Feb 19 2019 at 06:23):
I mean Can we make extension for Observation resource
mohammad navab husain (Feb 19 2019 at 06:34):
Whether we can use extention for observation resource or not?
Lloyd McKenzie (Feb 19 2019 at 06:36):
Extension is allowed on all resources that extend DomainResource, including Observation. However, you shouldn't need to make any extension if you want to capture "family history of disease" - you just need an appropriate Observation.code
mohammad navab husain (Feb 19 2019 at 06:39):
Thank you@Lloyd Mckenzie
mohammad navab husain (Feb 21 2019 at 05:36):
Can we use extension for observation.codeableconcept.coding
Lloyd McKenzie (Feb 21 2019 at 05:38):
Can you, sure. The question is whether you need to. What are you trying to do? Nothing that's been described so far seems to be something that requires the use of extensions.
mohammad navab husain (Feb 21 2019 at 05:53):
To create chestaxilla examination profile ,under the child values of profile we are having different different values to represent so that we are trying to use extension. can we use?
Lloyd McKenzie (Feb 21 2019 at 06:04):
Typically you'd use different Observation instances for each value - or sometimes components within a single Observation. It's pretty rare to need to use extensions.
Lloyd McKenzie (Feb 21 2019 at 06:05):
Extensions should only be used if you can't say what you need to say using the standard resources. They should never be used because you want to reduce the number of resources used because that's not going to help interoperability at all - which is the whole reason for using FHIR in the first place.
Dharani Ranasinghe (May 07 2021 at 10:19):
We have a parameter called Testicular volume and the code is SCTID: 251828008. It has two sub parameters as :
· Testis left – 65421000052108
· Testis right – 65411000052100
In our EHR system we use two keywords as Testis left & Testis right to register the Testicular volume. Further when one of our third pary product, requesting data, they use 65421000052108 & 65411000052100 codes . My question is what is the ideal way of designing the profile to communicate the Testicular volume out of following suggestions ?
3 Suggestions:
-
Use two profiles for Testis left and Testis right
-
Use one profile called Testicular volume and use two codes in a value set of Code attribute
-
User one profile and have two slices under the Component attribute for two testis as given in below picture. And add the code of Testicular volume to the code attribute.
Lloyd McKenzie (May 07 2021 at 13:15):
Are the left and right volumes ever accessed and used independently of each other and the overall volume? Is the overall volume calculated from the left and right?
Dharani Ranasinghe (May 09 2021 at 15:05):
Lloyd McKenzie said:
Are the left and right volumes ever accessed and used independently of each other and the overall volume? Is the overall volume calculated from the left and right?
No @Lloyd McKenzie . Left and right volumes are accessed independently. There is nothing called overall volume and no such calculation is required.
Lloyd McKenzie (May 10 2021 at 02:51):
Ok, so "testicular volume" doesn't have a value, it's just a grouper for the left and right observations? If the left and right are meaningful on their own, then you'd have separate observations for each and you could have a 'grouping' observation with "hasMember" links to the left and right measurements.
Dav (May 10 2021 at 10:09):
Hi expert, after adding the library hapi fhir in my spring project
<dependency>
<groupId>ca.uhn.hapi.fhir</groupId>
<artifactId>hapi-fhir-structures-r4</artifactId>
<version>${project.version}</version>
</dependency>
I notice during building project that in the method where I pass JsonObjectFormatVisitor from com.fasterxml.jackson.databind.jsonFormatVisitors the method became unresolved.
Cannot resolve method 'depositSchemaProperty(com.fasterxml.jackson.databind.jsonFormatVisitors.JsonObjectFormatVisitor)
'
The version hapi fhir is the 5.3.3 How can I avoid this issue and mantain both library?
David Pyke (May 10 2021 at 12:21):
You'll get better answers in the #hapi stream
Dharani Ranasinghe (Nov 16 2021 at 01:40):
Dharani Ranasinghe said:
Lloyd McKenzie said:
Are the left and right volumes ever accessed and used independently of each other and the overall volume? Is the overall volume calculated from the left and right?
No Lloyd McKenzie . Left and right volumes are accessed independently. There is nothing called overall volume and no such calculation is required.
Thank you @Lloyd McKenzie
Last updated: Apr 12 2022 at 19:14 UTC
