2023.1:XML Schema Integration (Functionality): Difference between revisions

From Grooper Wiki
Changes made to About and How To, image added // Edit via Wikitext Extension for VSCode
EDI Standards section completed // Edit via Wikitext Extension for VSCode
Line 6: Line 6:
|style="font-size:14pt; color:#f89420; border: 2px solid #f89420; width:40px"|[[File:Asset 22@4x.png]]
|style="font-size:14pt; color:#f89420; border: 2px solid #f89420; width:40px"|[[File:Asset 22@4x.png]]
|style="border: 2px solid #f89420"|
|style="border: 2px solid #f89420"|
You may download and import the file(s) below into your own Grooper environment (version 2023.1).  There is a '''Batch''' with the example document(s) discussed in this tutorial, as well as a '''Project''' configured according to its instructions.
You may download and import the file(s) below into your own Grooper environment (version 2023.1).  There is a '''[[Batch]]''' with the example document(s) discussed in this tutorial, as well as a '''[[Project]]''' configured according to its instructions.
Given the proprietary nature of SharePoint and Database connections, the connection objects and their configuriations cannot be shared.
Given the proprietary nature of SharePoint and Database connections, the connection objects and their configuriations cannot be shared.
<br>
<br>
Line 23: Line 23:


=== EDI Standards ===
=== EDI Standards ===
'''XML Schema Integration''' was actually born from a necessity for '''Grooper''' to efficiently collect data from medical [https://en.wikipedia.org/wiki/Electronic_data_interchange EDI] files, therefore, we will begin our understanding by learning how to work withm them.
'''XML Schema Integration''' was actually born from a necessity for '''Grooper''' to efficiently collect data from medical [https://en.wikipedia.org/wiki/Electronic_data_interchange EDI] files, therefore, we will begin our understanding by learning how to work withm them. Below we will work with a mocked up [https://en.wikipedia.org/wiki/Explanation_of_benefits EOB] form.
<br><br>
<br><br>
Follow the instructions in the screenshots below.
Follow the instructions in the screenshots below.
Line 29: Line 29:
[[image:2023.1_XML-Schema-Integration_02_How-To_01.png]]
[[image:2023.1_XML-Schema-Integration_02_How-To_01.png]]


==== Selecting an EDI Schema ====
There is a massive library of EDI standars, and '''Grooper''' has built into a small selection of [https://en.wikipedia.org/wiki/ASC_X12 X12] schemas to choose from. These act as templates that will populate a '''Data Model''' with all the appropriate '''[[Data Element|Data Elements]]''' necessary to house all data from a given format.
<br><br>
[[image:2023.1_XML-Schema-Integration_02_How-To_02.png]]
<br><br>
[[image:2023.1_XML-Schema-Integration_02_How-To_03.png]]
==== Execute Activity to Collect Data ====
Extraction using EDI Schemas does not leverage the standard '''[[Extract]]''' activity. Instead, the '''[[Execute]]''' activity will be used.
<br><br>
[[image:2023.1_XML-Schema-Integration_02_How-To_04.png]]
<br><br>
[[image:2023.1_XML-Schema-Integration_02_How-To_05.png]]
<br><br>
[[image:2023.1_XML-Schema-Integration_02_How-To_06.png]]
<br><br>
[[image:2023.1_XML-Schema-Integration_02_How-To_07.png]]


[[Category:Articles]]
[[Category:Articles]]
[[Category:Version 2023.1]]
[[Category:Version 2023.1]]

Revision as of 15:41, 21 December 2023

XML schemas are common formats that Grooper can leverage for generating models and exporting data.

About

You may download and import the file(s) below into your own Grooper environment (version 2023.1). There is a Batch with the example document(s) discussed in this tutorial, as well as a Project configured according to its instructions. Given the proprietary nature of SharePoint and Database connections, the connection objects and their configuriations cannot be shared.
Please upload the Project to your Grooper environment before uploading the Batch. This will allow the documents within the Batch to maintain their classification status.
The XML Schemas and Files.zip file is not a Grooper ZIP file, therefore it is not meant to be uploaded into Grooper. Instead, unzip the contents of this file normally.

The XML format has been around since 1996 and, from a business perspective, can play a large role in your ability to organize data. This article will focus chiefly on XML Schemas and how Grooper can leverage them to define Data Model structures as control how data is exported out of Grooper.

How To

EDI Standards

XML Schema Integration was actually born from a necessity for Grooper to efficiently collect data from medical EDI files, therefore, we will begin our understanding by learning how to work withm them. Below we will work with a mocked up EOB form.

Follow the instructions in the screenshots below.

Selecting an EDI Schema

There is a massive library of EDI standars, and Grooper has built into a small selection of X12 schemas to choose from. These act as templates that will populate a Data Model with all the appropriate Data Elements necessary to house all data from a given format.



Execute Activity to Collect Data

Extraction using EDI Schemas does not leverage the standard Extract activity. Instead, the Execute activity will be used.