This is the second of a three-part series. The following is the agenda for Part 2 – Review of DocumentDB REST API Understanding the overall problem High-level Design How Swagger fits in Design and development Next steps

1. Sponsored & Brought to you by
Azure DocumentDB for
Healthcare Integration – Part 2
Howard Edidin
https://twitter.com/hsedidin
http://www.linkedin.com/in/hedidin

2. Azure DocumentDB for Healthcare Integration - Part 2
Howard S. Edidin
Microsoft Partner Technical Specialist (BizTalk, Azure) for Healthcare
Gold Member

3. About the series
• The overall objective is to utilize DocumentDB as a repository for HL7
FHIR©.
• By developing an “Azure API Connector for DocumentDB” that will be
used with an Azure Logic App (Manual) and the HTTP Connector, we
will be able to expose the entire DocumentDB REST API.

4. About the series
• Client applications include BizTalk On-Premise, Office 365, Dynamics
CRM, Mobile Engagements and other devices and applications that
support the HL7 FHIR© REST API.
• Eventually the Azure solution could act as an HL7 FHIR© Server.

5. Agenda
• Review of DocumentDB REST API
• Understanding the overall problem
• High-level Design
• How Swagger fits in
• Design and development
• Next steps

6. REVIEW OF DOCUMENTDB REST API
Azure DocumentDB for Healthcare Integration – Part 1
6

7. Azure DocumentDB for Healthcare
Integration
• Azure DocumentDB, features and capabilities
• Creating a DocumentDB database
• CRUD operations
• API’s
– REST
– SQL Query Language
– Server-side JavaScript
• Leveraging DocumentDB as a HL7 document repository
• Preview API and Logic Apps
7

8. DocumentDB
• DocumentDB is unique among NoSQL stores
– It was developed and delivered as a service
– It’s truly schema-free, queryable and JSON aware
– Offers transactional processing through language integrated JavaScript
– Predictable performance and tunable consistency
8

9. Resource Model
9

10. Access Model
• RESTful interaction over HTTP
• Standard HTTP verbs & semantics
• Can utilize BizTalk as a client
• Built-in support for TCP for smart clients
• Designed for Gateway as well as Direct Connectivity options
POST
Item
resource TenantFeed
URI
PUT
Item
resource
Item
URI
DELETE
Item
URI
GET
PATCH
TenantFeed Or Item
URI
Item URI
Create a new resource
/Execute a sprocs/trigger/query
Replace an existing resource
Delete an existing resource
Read/Query an existing
resource
*Selectively Edit an existing resource
Item
resource
POST http://myaccount.documents.azure.net/dbs
{ "name":"My Company Db"}
...
[201 Created]
{
"name": "My Company Db",
"id": "UoEi5w==",
"self": "dbs/UoEi5w==/",
"colls": "colls/",
"users": "users/"
}
10

11. UNDERSTANDING THE OVERALL PROBLEM
Azure DocumentDB for Healthcare Integration – Part 2
11

12. HIGH-LEVEL DESIGN
Azure DocumentDB for Healthcare Integration – Part 2
12

13. High-Level Design - Initial
13

14. High-Level Design – Rev 1
14

15. High-Level Design – Rev 1.1
15

16. High-Level Design – Release 1.0
16

17. High-Level Design – Release 2.0
17

18. High-Level Design – Release 3.0
18

19. High-Level Design – Release 4.0
19

20. HOW SWAGGER FITS IN
Azure DocumentDB for Healthcare Integration – Part 2
20

21. Creating a DocumentDB Swagger
21

22. Creating a DocumentDB Swagger
22

23. DESIGN AND DEVELOPMENT
Azure DocumentDB for Healthcare Integration – Part 2
23

24. Logic App
24

25. Logic App
25

26. Logic App Demo
26

27. NEXT STEPS
Azure DocumentDB for Healthcare Integration – Part 2
27

28. Azure DocumentDB for Healthcare Integration
28
Howard S. Edidin MCTS, MCP, Author, Trainer, TechNet Wiki Ninja
Microsoft Partner - Application Integration
|HL7|HIPAA
Microsoft Virtual Technical Specialist (BizTalk, Azure) for Healthcare
hedidin@edidingroup.net