简体   繁体   English

FHIR:任命原因是一种资源吗?

[英]FHIR : Appointment reasons as a resource?

I'm implementing FHIR at the moment and I'm having trouble dealing with appointment reasons. 我目前正在实施FHIR,但在处理约会原因时遇到了麻烦。

I know I can use the value set available here : https://www.hl7.org/fhir/valueset-encounter-reason.html 我知道我可以使用此处提供的值集: https : //www.hl7.org/fhir/valueset-encounter-reason.html

or implement my own value set for it but it's still problematic because reasons are a resource in my app and practitioners can add, modify and delete them. 或实现我自己的值集,但仍然存在问题,因为原因是我的应用程序中的资源,从业人员可以添加,修改和删除它们。 Reasons also have various fields such as a color, ... 原因也有各个领域,例如颜色,...

A value set won't be enough for my app. 设置的值不足以支持我的应用。

Do you have any hints / ideas on how could I implement such thing ? 您对我如何实施这种方法有任何暗示/想法吗?

So you want to point to Condition or Observation as a reason? 因此,您想指出“条件”还是“观察”作为原因? Or perhaps point to a ReferralRequest or ProcedureRequest the appointment is based on? 还是指向约会基于的ReferralRequest或ProcedureRequest? If so, submit a change request - having these things would also be in alignment with the Request pattern which Appointment should be trying to align with. 如果是这样,请提交变更请求-使这些事情也符合约会应尝试与之匹配的请求模式。 In the meantime, you're free to define an extension to convey the same meaning. 同时,您可以自由定义扩展以传达相同的含义。

For us, the "reason" basically indicates what type of service the appointment is going to provide, so we actually map reasons to services, which we represent reason as a HealthcareService resource. 对于我们来说,“原因”基本上指示约会将要提供的服务类型,因此我们实际上将原因映射到服务,我们将原因表示为HealthcareService资源。

Basically, from the patient's perspective, they care about the "reason" they are going to the doctor. 基本上,从患者的角度来看,他们关心他们要去看医生的“原因”。 But from the healthcare provider's perspective, they care about the type of service they will provide to treat the reason. 但是从医疗保健提供者的角度来看,他们关心他们将提供的服务类型以治疗原因。

声明:本站的技术帖子网页,遵循CC BY-SA 4.0协议,如果您需要转载,请注明本站网址或者原文地址。任何问题请咨询:yoyou2525@163.com.

 
粤ICP备18138465号  © 2020-2024 STACKOOM.COM