FHIR works on AWS server not allowing to keep customized id as primary key
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.
Hello,
I suggest posting this directly in the "issues" section of the solution's github repository:
https://github.com/awslabs/fhir-works-on-aws-deployment/issues
Relevant questions
Is it possible to use AWS RDS SQL Server as an AAG target from on premise primary?
asked 7 months agoFHIR works on AWS server not allowing to keep customized id as primary key
asked 23 days agoAre we working on improving the license plate numbers and VIN Numbers recognition from images?
asked 2 months agoWeb server not responding on AWS EC2 when sending larger http response
asked 8 months agoAWS DMS - primary key verification
Accepted Answerasked 5 months agoFHIR Works xml type example
asked 7 days agoAn beanstalk app that works fine until recently
asked 23 days agoHow to convert HL7v2 to FHIR in AWS
asked 24 days agoSuddenly the ports are closed and connection is not working
asked 3 years agoBuild succeeds but backend changes are not deployed
asked 3 months ago