Sponsored & Brought to you by

Do Logic Apps support error handling?Howard Edidin

https://twitter.com/hsedidin

http://www.linkedin.com/in/hedidin

Do Logic Apps support error handling?

Howard S. Edidin

05/01/2023 3

Agenda

• Use Cases• DocumentDB • The “Skip and Go Naked” design pattern• Demo• Next steps

05/01/2023 4

Use Case

• Logging – Log original message from CRMOL. • A fairly common Use Case in EDI

• Error Handling– Log Response Errors returned from Receiver– Viewing the Errors

05/01/2023 5

HL7 FHIR – Appointment Resource

• Appointment resources are used to provide information about a planned meeting that may be in the future or past.

• The resource only describes a single meeting, a series of repeating visits would require multiple appointment resources be created for each instance.

• Examples include a scheduled surgery, a follow-up for a clinical visit, a scheduled conference call between clinicians to discuss a case, the reservation of a piece of diagnostic equipment for a particular use, etc.

• The visit scheduled by an appointment may be in person or remote (by phone, video conference, etc.) All that matters is that the time and usage of one or more individuals, locations and/or pieces of equipment is being fully or partially reserved for a designated period of time.

05/01/2023 6

HL7 FHIR – Appointment Resource

• Use Case– A scheduled conference call between clinicians to

discuss a case

05/01/2023 7

JSON Request Template{ "resourceType" : "Appointment", // from Resource: id, meta, implicitRules, and language // from DomainResource: text, contained, extension, and modifierExtension "identifier" : [{ Identifier }], // External Ids for this item "status" : "<code>", // R! proposed | pending | booked | arrived | fulfilled | cancelled | noshow "type" : { CodeableConcept }, // The type of appointment that is being booked "reason" : { CodeableConcept }, // Reason this appointment is scheduled "priority" : "<unsignedInt>", // Used to make informed decisions if needing to re-prioritize "description" : "<string>", // Shown on a subject line in a meeting request, or appointment list "start" : "<instant>", // When appointment is to take place "end" : "<instant>", // When appointment is to conclude "minutesDuration" : "<positiveInt>", // Can be less than start/end (e.g. estimate) "slot" : [{ Reference(Slot) }], // If provided, then no schedule and start/end values MUST match slot "comment" : "<string>", // Additional comments "participant" : [{ // R! Participants involved in appointment "type" : [{ CodeableConcept }], // Role of participant in the appointment "actor" : { Reference(Patient|Practitioner|RelatedPerson|Device| HealthcareService|Location) }, // Person, Location/HealthcareService or Device "required" : "<code>", // required | optional | information-only "status" : "<code>" // R! accepted | declined | tentative | needs-action }]}

05/01/2023 8

JSON Response Template

{ "resourceType" : "AppointmentResponse", // from Resource: id, meta, implicitRules, and language // from DomainResource: text, contained, extension, and modifierExtension "identifier" : [{ Identifier }], // External Ids for this item "appointment" : { Reference(Appointment) }, // R! Appointment this response relates to "start" : "<instant>", // Time from appointment, or requested new start time "end" : "<instant>", // Time from appointment, or requested new end time "participantType" : [{ CodeableConcept }], // Role of participant in the appointment "actor" : { Reference(Patient|Practitioner|RelatedPerson|Device| HealthcareService|Location) }, // Person, Location/HealthcareService or Device "participantStatus" : "<code>", // R! accepted | declined | tentative | in-process | completed | needs-action "comment" : "<string>" // Additional comments}

05/01/2023 9

The Logic App

05/01/2023 10

Demo

1. We will POST an Appointment request to our Logic App2. Post a new Log Document (record) to a DocumentDB Collection

1. View the Log Document3. Convert text comments into speech (audio file)4. Create new DocumentDB Attachment for the audio file5. Validate for success or failure6. If Failed, then post Error Document (record) to a DocumentDB Collection

1. View the Error document7. If Success, create Appointment Response message

1. Post the Response Message back to CRM.

05/01/2023 11

Next step

• The complete Logging and Error Handling tutorial will be published on the Azure Logic App examples and scenarios page.

• The source code will be available

05/01/2023 12

Contact Information

Howard S. Edidin MCTS, MCP, MSSenior Azure Solution Architect

Microsoft MVP – Azure | Data PlatformMicrosoft Integration P-TSP (Healthcare and Life Sciences)Microsoft Azure Advisory GroupDocumentDB Wizard

100 Menlo Park, Suite 302B, Edison NJ 08837 Office: (732) 474-6844 Cell: (224) 360-3200Toll Free: (855) VNB CONSEmail : howard.edidin@vnbconsulting.comWeb : www.vnbconsulting.com

HL7 Gold Member