Aller au contenu principal

SAP Billing

Category: EHR & Practice Mgmt
Node id: sap-billing

Standards: SOC2

Integrates with SAP IS-H for healthcare billing operations including invoices, charges, DRG, and insurance claims

What it does​

  • SAP IS-H invoice generation and retrieval
  • Healthcare charge management
  • DRG (Diagnosis Related Group) assignment queries
  • Insurance claim creation and management
  • OData-based SAP IS-H billing integration

Use cases​

  • Generate patient invoices from SAP billing system
  • Query hospital charges for revenue cycle management
  • Retrieve DRG assignments for inpatient billing
  • Create insurance claims from SAP clinical data

Runtime​

  • Performance tier: variable

Input ports​

NameTypeRequiredDescription
case_idtextNoCase ID for get_invoices, get_charges, and get_drg operations
invoice_datajsonNoInvoice data for create_invoice operation
patient_idtextNoPatient ID for get_insurance_claims operation

Output ports​

NameTypeRequiredDescription
invoicesjsonNoList of invoices
invoicejsonNoCreated invoice record
chargesjsonNoList of charges for a case
drgjsonNoDRG information for a case
insurance_claimsjsonNoList of insurance claims
http_statusnumberNoHTTP status code from SAP

Settings​

Basic​

SettingNameTypeRequiredDefaultAllowed valuesDescription
SAP URLsap_urlstringYesBase URL of the SAP IS-H instance
OperationoperationenumNoget_invoicesget_invoices, create_invoice, get_charges, get_drg, get_insurance_claimsBilling operation to perform

Auth​

SettingNameTypeRequiredDefaultAllowed valuesDescription
Auth Tokenauth_tokensecretNoBearer token for SAP authentication
API Keyapi_keysecretNoSAP API key

Advanced​

SettingNameTypeRequiredDefaultAllowed valuesDescription
SAP Clientsap_clientstringNo100SAP client number

Errors​

CodeDescription
SAP_URL_REQUIREDSAP system URL must be configured
AUTH_FAILEDAuthentication to SAP system failed
SAP_REQUEST_FAILEDHTTP request to SAP system failed
UNSUPPORTED_OPERATIONOperation not recognized

Runtime notes​

  • Only one output key is populated per execution depending on the operation
  • Output shape comes directly from SAP OData response; structure varies by IS-H version
  • case_id is optional for get_invoices (returns all) but required for get_charges and get_drg
  • http_status is always present alongside the data output

See Build any workflow for how to put nodes together and Ports, types and data flow for how port types connect.

Quelque chose n'est pas clair ? Envoyez vos commentaires sur la documentation par courriel.