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
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.
I suggest posting this directly in the "issues" section of the solution's github repository:
Is it possible to use AWS RDS SQL Server as an AAG target from on premise primary?asked 7 months ago
FHIR works on AWS server not allowing to keep customized id as primary keyasked 23 days ago
Are we working on improving the license plate numbers and VIN Numbers recognition from images?asked 2 months ago
Web server not responding on AWS EC2 when sending larger http responseasked 8 months ago
AWS DMS - primary key verificationAccepted Answerasked 5 months ago
FHIR Works xml type exampleasked 7 days ago
An beanstalk app that works fine until recentlyasked 23 days ago
How to convert HL7v2 to FHIR in AWSasked 24 days ago
Suddenly the ports are closed and connection is not workingasked 3 years ago
Build succeeds but backend changes are not deployedasked 3 months ago