Stream: implementers
Topic: Patient's Personal/Life Goals
Aleksandra Pavlyshina (Sep 08 2016 at 12:29):
Is the Goal resource a correct choice for Patient's Personal/Life Goals?
Examples:
1 - Granddaughters graduation | May 12th 2017 | Western Kentucky University
(Comments: Patient expressed transportation needs. May be able to ride with a cousin- please follow up)
2 - Live to be 90 years old | October 14th 2020 | Patients Home
(Comments: Patient expressed that he would love a birthday party in his own home with close friends and family)
Suggested Mapping:
| Field Name | Type | FHIR Mapping |
|---|---|---|
| Goal | Text | Goal.description |
| Date | Date | Goal.targetDate |
| Location | Text | Goal.Extension.valueReference = Location |
| Comments | Text | Goal.note |
| Does the patient need Narus Health's assistance for this goal? | Yes/No | Contained QuestionnaireResponse |
Location here is the location of their personal goal. It may be at home or it may be in a different state or country even. The point in capturing the location of the goal is to be able to help the patient plan for achieving this goal (find transportation/buy plane tickets/bus tickets/coordinate with family or friends/ find housing, ect).
Lloyd McKenzie (Sep 08 2016 at 20:23):
Why would you use a nested QuestionnaireResponse instead of a boolean extension for "Does the patient need Narus Health's assistance"?
Aleksandra Pavlyshina (Sep 09 2016 at 11:04):
Thank you, Lloyd, for the notice. Certainly I'll use an extension here. BTW, are there any conventions on naming extensions?
Also I would like to indicate the Goal.category (set it by default for all Patient's Personal/Life goals, it won't be selected on the form). Does the concept Personal milestones (observable entity) SCTID: 160786009 seem a proper value for such goals? (There are also concepts Life event observable (observable entity) SCTID: 364706004 and Family milestone (observable entity) SCTID: 160852007).
So, the mapping will be the following:
| Field Name | Type | FHIR Mapping |
|---|---|---|
| Goal | Text | Goal.description |
| Date | Date | Goal.targetDate |
| Location | Text | Goal.Extension:goal-location.valueReference = Location |
| Comments | Text | Goal.note |
| Does the patient need Narus Health's assistance for this goal? | Yes/No | Goal.Extension:goal-isAssistanceNeeded.valueBolean |
Lloyd McKenzie (Sep 10 2016 at 14:37):
Hi @Aleksandra Pavlyshina - There's no particular naming standard for extensions. Good practice is for the URL to resolve to a human-readable (and ideally a computable) definition of the extension (based on the HTTP Accept header). And good practice is also for the name to be descriptive. The extension URL obviously needs to be unique. For HL7-defined extensions, we typically start resource-specific extensions with the resource name so they all group together. Beyond that, name as you see fit. In terms of SCT codes, I'm not sure. They all sound to me like codes for something that has happened rather than something that's desired to happen. However, I'll let those more familiar with the deep workings of SNOMED provide their opinions
Last updated: Apr 12 2022 at 19:14 UTC
