FHIR在AWS服务器上工作不允许将自定义ID作为主要键

发布于 2025-01-26 15:33:44 字数 520 浏览 4 评论 0 原文

我们正在为FHIR(快速医疗保健互操作性资源)工作。

我们遵循“ FHIR在AWS上工作”,并部署了AWS在我们的AWS环境中给出的云形式模板。遵循我们已部署的模板

https://docs.aws.amazon.com/solutions/latest/fhir-works-on-aws/aws- cloudformation-template.html

要求:我们希望将特定于客户端/自定义ID作为服务器中的主要键。

问题:服务器不允许我们覆盖或Mainain客户端特定(自定义)ID作为主键。事实,在运行时,它正在生成自己的ID并忽略我们给出的ID。

We are working for FHIR(Fast Healthcare Interoperability Resources).

We have followed “FHIR works on AWS” and deployed the CloudFormation template given by AWS in our AWS environment.Following is the template that we have deployed

https://docs.aws.amazon.com/solutions/latest/fhir-works-on-aws/aws-cloudformation-template.html

Requirement : we want to maintain client specific/customized ids as primary key in the server.

Problem : server not allowing us to override or mainain client specific (customized ) ids as primary key .Infact , in the runtime, it is generating its own ids and ignoring the id given by us.

如果你对这篇内容有疑问,欢迎到本站社区发帖提问 参与讨论,获取更多帮助,或者扫码二维码加入 Web 技术交流群。

扫码二维码加入Web技术交流群

发布评论

需要 登录 才能够评论, 你可以免费 注册 一个本站的账号。

评论(2

飘然心甜 2025-02-02 15:33:44

FHIR规格允许您在使用“更新为创建”时定义自己的ID。这是您在服务器中创建新资源的时候,但请对要创建的ID(例如 detter/1 )使用put(update)请求,而不是帖子(创建)请求到资源URL。服务器应返回 201创建状态,而不是 200 OK 。有关更多信息,请参见 https://hl7.org/fhir/fhir/http.http.html#upsert

并非每个FHIR服务器都支持这一点,但是如果AWS这样做,则可能是如何工作的。此功能的能力阶段中的字段是 cablecitionStatement.Rest.Rest.UPDATECREATE

edit:

这是可以通过修改传递给部署repo repo

const dynamoDbDataService = new DynamoDbDataService(DynamoDb, false, { enableMultiTenancy });

默认情况

const dynamoDbDataService = new DynamoDbDataService(DynamoDb, true, { enableMultiTenancy });

The FHIR spec allows for you to define your own IDs when using "update as create". This is when you create a new resource in the server, but use a PUT (update) request to the ID you want to create, such as Patient/1, instead of a POST (create) request to the resource URL. The server should return a 201 Created status instead of 200 OK. For more information see https://hl7.org/fhir/http.html#upsert

Not every FHIR server supports this, but if AWS does this is likely how it would work. The field in the CapabilityStatement for this feature is CapabilityStatement.rest.resource.updateCreate

EDIT:

This is possible by modifying the parameters passed to the DynamoDbDataService constructor in the deployment repo's src/config.ts

By default supportUpdateCreate, the second parameter, is set to false

const dynamoDbDataService = new DynamoDbDataService(DynamoDb, false, { enableMultiTenancy });

but you can set it to true to enable this functionality

const dynamoDbDataService = new DynamoDbDataService(DynamoDb, true, { enableMultiTenancy });
滿滿的愛 2025-02-02 15:33:44

看一下此评论:

set set support support> support> support upportupdatecreate > dynamodbdataservice 构造函数,您必须知道应该使用put而不是发布!

Take a look at this comment:

https://github.com/awslabs/fhir-works-on-aws-deployment/issues/629#issuecomment-1448755536

After set supportUpdateCreate to true on DynamoDbDataService constructor, you must know that you should use PUT instead of POST!

~没有更多了~
我们使用 Cookies 和其他技术来定制您的体验包括您的登录状态等。通过阅读我们的 隐私政策 了解更多相关信息。 单击 接受 或继续使用网站,即表示您同意使用 Cookies 和您的相关数据。
原文