Stream: implementers
Topic: One profile for different clinical paramters
Dharani Ranasinghe (Sep 09 2020 at 11:39):
There is a project which we can send clinical parameter data in our system to an external application. We are going to use observation type profiles to communicate. That external application requests data using the SNOMED codes. Following are some of those parameters which have different SNOMED codes even though those are in the same context . Body height, Sitting Height , Father height, Mother height, Target height.
My question is :
is it enough to create one profile ( derriving this : https://www.hl7.org/fhir/bodyheight.html) common to all the above parameters ? or do I need to create profile for each parameter?
Lloyd McKenzie (Sep 09 2020 at 13:50):
It depends on how tight you want the profile to be. If there are different rules for different types of height measurements, you may want to have different profiles. If you just want to list all of the different Observation.code values possible, you can have a single profile that defines a value set of allowed codes. In your case, body height would have to adhere to the core vital signs profile (meaning you'd need a LOINC code in addition to the SNOMED code).
Dharani Ranasinghe (Sep 10 2020 at 10:03):
@Lloyd McKenzie : Thank you!
Last updated: Apr 12 2022 at 19:14 UTC
