Amazon API Gateway to AWS Lambda to AWS HealthScribe using AWS SAM

Amazon API Gateway → AWS Lambda → AWS HealthScribe → S3 bucket

How to use AWS HealthScribe API to automatically generate clinical notes from patient-clinician conversations in a serverless architecture.

Amazon API Gateway receives the HTTP POST request which triggers the AWS Lambda function.
The AWS Lambda function calls AWS HealthScribe start_medical_scribe_job API using boto3 library. The audio content to be analysed is stored in an Amazon S3 bucket.
AWS HealthScribe transcription job analyses the patient-clinician conversations audio content and generates clinical notes from it.
The output is uploaded into the Amazon S3 bucket.

< Back to all patterns

GitHub icon Download this pattern (.zip)

GitHub icon View this pattern on GitHub


Clone repo

git clone https://github.com/aws-samples/serverless-patterns/cd serverless-patterns/apigw-lambda-healthscribe-sam

Deploy

sam deploy --guidedbash create_lambda_layer.sh


Testing

See the GitHub repo for detailed testing instructions.

Cleanup

Delete the Amazon S3 bucket content: aws s3 rm s3://{TranscribeNotesBucket} --recursive
Delete the stack: sam delete.
Delete Lambda Layer stack: bash delete_lambda_layer.sh.

Created by:

Biswanath Mukherjee

Biswanath Mukherjee

Sr. Solutions Architect working at AWS India.

Follow on LinkedIn

Rakshith Rao

Rakshith Rao

I am a Senior Solutions Architect at AWS and help our strategic customers build and operate their key workloads on AWS.

Follow on LinkedIn