In this builders session, learn how to create serverless functions with AWS Lambda, call them with Amazon API Gateway, and how to enable interoperability interfaces for healthcare messaging applications. Ask questions to a Senior Solutions Architect who is working in the healthcare industry.

2. © 2018, Amazon Web Services, Inc. or its affiliates. All rights reserved.
Creating Serverless Functions for
Healthcare Messaging Applications
Navneet Srivastava
Sr. Solutions Architect, GLS
Amazon Web Services
H L C 4 0 2

3. © 2018, Amazon Web Services, Inc. or its affiliates. All rights reserved.
Agenda
Introductions
Messaging applications in healthcare
Amazon MQ with serverless architecture
Reference architecture of the builder session
Build on
Q&A

4. © 2018, Amazon Web Services, Inc. or its affiliates. All rights reserved.

5. © 2018, Amazon Web Services, Inc. or its affiliates. All rights reserved.
Messaging applications in healthcare
Interoperability
HL7/FHIR
Third-party messages integration messages
EHR Workflows
Clinician workflow
Medication order, signing deficiencies, patient registration, and so forth
Devices stream
Glucometers, blood pressure monitors, IoT devices, and the like
Enterprise service bus/big data ecosystem
Multiple data sources, transformation, workflow orchestration, broadcasting messages to a
number of subscribers

6. © 2018, Amazon Web Services, Inc. or its affiliates. All rights reserved.
Messaging with serverless components
Message broker (Apache ActiveMQ, Amazon MQ)
Message brokers allow different software systems—often using different programming
languages, and on different platforms—to communicate and exchange information
Messaging is the communications backbone that connects and integrates the components of
distributed applications, such as order processing
Serverless function as subscriber (AWS Lambda)
Serverless function subscribes to message brokers and receives the incoming message
Serverless function as worker (AWS Lambda)
Serverless function that acts on the incoming message and performs the operations like
transformation or calls another process for processing

7. © 2018, Amazon Web Services, Inc. or its affiliates. All rights reserved.
Message broker sample architecture

8. © 2018, Amazon Web Services, Inc. or its affiliates. All rights reserved.

9. © 2018, Amazon Web Services, Inc. or its affiliates. All rights reserved.
Builder session use case
Use case (using a managed message queue service and serverless functions):
Register a list of patients with observations from a client application using FHIR and
message broker
Process incoming blood glucose values from device streams like glucometers, IoT
device, or a third-party application
AWS services used
AWS Cloud 9, Amazon MQ, AWS Lambda, Amazon RDS

10. © 2018, Amazon Web Services, Inc. or its affiliates. All rights reserved.
Builder session: Reference architecture
AWS cloud
AWS Lambda
subscriber
AWS Lambda
patient data
processor
AWS Lambda
patient glucose
data processor
DynamoDBAmazon MQ -
message broker

11. Thank you!
© 2018, Amazon Web Services, Inc. or its affiliates. All rights reserved.
Navneet Srivastava
navneesr@amazon.com

12. © 2018, Amazon Web Services, Inc. or its affiliates. All rights reserved.