In this integration, MedGEO receives information about products from the hospital, and uses that when capturing usage of surgeries later. MedGEO supports multiple standards to do this, like FHIR and receiving products in XML over HTTP requests or XML in files over SFTP.

In this document, we will detail what fields does MedGEO support receiving for product information, and how to send this information through different protocols and data formats.

Communication Protocol
  • FHIR: If the partner can offer item master information through a FHIR server, for example using Device or SupplyDelivery endpoints, then MedGEO would be able to read the information from it.
  • XML/JSON over HTTPS or SFTP:MedGEO can offer endpoints to read item master products sent in Json or XML formats. The format can be flexible and agreed on with the partner, as long as it contains the required fields.
  • XML/JSON over HTTPS or SFTP:If the partner offers an API where MedGEO can call to get this information, then we can configure the integration service of MedGEO to call the API of the partner and parse the data in the agreed upon format with the partner to read master product information
  • HL7 over HTTPS, SFTP or MLLP:This is not a common way of reading item master information but if this information is available in OMS and OMN messages then MedGEO's integration service can be configured to read it from those messages.
Supported Fields
    • Item Master Fields:
      • Device Id
      • Version Model Number
      • Description
      • size
      • FDA Product Code Name
      • GMDN PT Name
      • Issueing Agency
      • Package Type
      • Package Quantity
      • UDI
      • Lot
      • Batch
      • Serial
      • Manufacturing Date
      • Expiration Date
      • Asset Type
      • Cost
Example of JSON Schema for Item Master
JSON Example: 
                {
                    "DeviceId": "987654321",
                    "VersionModelNumber": "VM2024",
                    "Description": "High Precision Medical Tool",
                    "Size": "Medium",
                    "FDAProductCodeName": "ABC123",
                    "GMDNPTName": "Global Medical Device Nomenclature",
                    "IssuingAgency": "FDA",
                    "PackageType": "Box",
                    "PackageQuantity": "20",
                    "UDI": "U98765432109876543210",
                    "Lot": "LOT202404",
                    "Batch": "BATCH202404",
                    "Serial": "SN20240401",
                    "ManufacturingDate": "2023-01-20",
                    "ExpirationDate": "2028-01-20",
                    "AssetType": "Consumable",
                    "Cost": 149.99
                }

This JSON schema represents a simple model for transmitting item master data, which can be customized to fit partner-specific requirements for integration.
Example of XML Schema for Item Master
XML Example: 
                <ItemMaster>
                    <DeviceId>987654321</DeviceId>
                    <VersionModelNumber>VM2024</VersionModelNumber>
                    <Description>High Precision Medical Tool</Description>
                    <Size>Medium</Size>
                    <FDAProductCodeName>ABC123</FDAProductCodeName>
                    <GMDNPTName>Global Medical Device Nomenclature</GMDNPTName>
                    <IssuingAgency>FDA</IssuingAgency>
                    <PackageType>Box</PackageType>
                    <PackageQuantity>20</PackageQuantity>
                    <UDI>U98765432109876543210</UDI>
                    <Lot>LOT202404</Lot>
                    <Batch>BATCH202404</Batch>
                    <Serial>SN20240401</Serial>
                    <ManufacturingDate>2023-01-20</ManufacturingDate>
                    <ExpirationDate>2028-01-20</ExpirationDate>
                    <AssetType>Consumable</AssetType>
                    <Cost>149.99</Cost>
                </ItemMaster>

This XML schema illustrates a potential structure for item master data, adaptable to various formats according to partner specifications to ensure accurate data exchange.

Data Submission Methods
  • API Submission: MedGEO accepts JSON or XML data via HTTPS POST requests to endpoints like /api/v1/inbound/products and /api/v1/inbound/products/xml. This facilitates real-time updates and integration.
  • SFTP Submission: Files in JSON or XML format can also be securely uploaded to our SFTP server. MedGEO provides a directory specific to each partner, ensuring secure and structured data storage and retrieval.
  • API Read: MedGEO has the ability to call the API of the partner to get product information. this is a long polling call where it is performed once a day to load all of the prices.