From 0abe9b2dc7bff03fc8dcfcf3876478009f31b18b Mon Sep 17 00:00:00 2001 From: Nisha Nizamuddin Date: Tue, 30 Jan 2024 15:19:52 -0800 Subject: [PATCH 1/3] Update sfdc-customization-guide.adoc --- retail/3.1/modules/ROOT/pages/sfdc-customization-guide.adoc | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/retail/3.1/modules/ROOT/pages/sfdc-customization-guide.adoc b/retail/3.1/modules/ROOT/pages/sfdc-customization-guide.adoc index 1eb487e32..4c16e48ca 100644 --- a/retail/3.1/modules/ROOT/pages/sfdc-customization-guide.adoc +++ b/retail/3.1/modules/ROOT/pages/sfdc-customization-guide.adoc @@ -250,7 +250,7 @@ Instead of adjusting permissions for each field as you go, if you are only makin === Additional Notes * The *Customer Status* picklist values are *Prospect*, *Onboarding*, *Active*, *Inactive*, *Closed*, *Deceased*, *Delinquent*, and *Dormant*. -* The *External Id Type* picklist values are *SALESFORCE_B2C*, *SALESFORCE_CORE*, *PIM*, *OFBIZ*, *SAP_4HANA*, *MDM*, *SAP_ECC*, *SALESFORCE_MARKETING*, and *ORACLE_EBS*. +* The *External Id Type* picklist values are *SALESFORCE_B2C*, *SALESFORCE_CORE*, *PIM*, *OFBIZ*, *SAP_4HANA*, *MDM*, *SAP_ECC*, *SALESFORCE_MARKETING*, *POS*, *SALESFORCE_DC*, *SALESFORCE_LM*, and *ORACLE_EBS*. * The *Object Type* picklist values are *BillingAddress*, *Customer*, *Email*, *Fax*, *Household*, *Individual*, *MailingAddress*, *MobilePhone*, *Organization*, *Phone*, *Product*, *SalesOrder*, and *ShippingAddress*. * The *Status* picklist values are *VALID*, *INVALID*. * All `Global_*_Id__c` fields should be visible in layouts (as described above) but made *read-only* to avoid issues with data synchronization. @@ -435,4 +435,4 @@ Follow these steps to create the Apex Triggers: == See Also * xref:prerequisites.adoc[Prerequisites] -* xref:index.adoc[MuleSoft Accelerator for Retail] \ No newline at end of file +* xref:index.adoc[MuleSoft Accelerator for Retail] From d31ccfbc16e576bb5098c949167e401591fdadd5 Mon Sep 17 00:00:00 2001 From: Kevin Kane <61329423+kckane-mulesoft@users.noreply.github.com> Date: Wed, 31 Jan 2024 16:43:27 -0400 Subject: [PATCH 2/3] Added pricing considerations page (#81) --- accelerators-home/modules/ROOT/nav.adoc | 1 + .../ROOT/pages/ubp-considerations.adoc | 94 +++++++++++++++++++ 2 files changed, 95 insertions(+) create mode 100644 accelerators-home/modules/ROOT/pages/ubp-considerations.adoc diff --git a/accelerators-home/modules/ROOT/nav.adoc b/accelerators-home/modules/ROOT/nav.adoc index 49823fdb4..27abd2c2b 100644 --- a/accelerators-home/modules/ROOT/nav.adoc +++ b/accelerators-home/modules/ROOT/nav.adoc @@ -9,6 +9,7 @@ * xref:shared-assets.adoc[Shared Assets] * xref:common-services.adoc[Common Services] * xref:cim-overview.adoc[Cloud Information Model] +* xref:ubp-considerations.adoc[Anypoint pricing model considerations] ** xref:cim-subject-areas.adoc[CIM Subject Areas] *** xref:cim-finance.adoc[Finance] *** xref:cim-fulfill.adoc[Fulfill] diff --git a/accelerators-home/modules/ROOT/pages/ubp-considerations.adoc b/accelerators-home/modules/ROOT/pages/ubp-considerations.adoc new file mode 100644 index 000000000..d485ffdf1 --- /dev/null +++ b/accelerators-home/modules/ROOT/pages/ubp-considerations.adoc @@ -0,0 +1,94 @@ +# Considerations for Usage-Based Pricing and Accelerator Assets + +The solutions developed for use cases supported by MuleSoft Accelerators were designed following the https://blogs.mulesoft.com/learn-apis/api-led-connectivity/[API-led connectivity] approach, which promotes a clean separation of application, process, and system integration layers while enabling a high level of reusability - particularly with System APIs. While this powerful approach remains valid today, and is highly recommended for organizations of all sizes to enable future growth while minimizing maintenance costs, there are some considerations that need to be taken into account for customers who have subscribed to the new usage pricing and packaging model. + +## The new pricing model + +As it pertains to the accelerators, applications deployed to CloudHub 1.0, CloudHub 2.0, or Anypoint Runtime Fabric will no longer be measured in terms of vCores when it comes to pricing. Instead, runtime pricing will be based on a combination of the following metrics: + +1. _Mule flow_: A flow within a deployed and running Mule app that contains a Mule event source or APIKit route handler. +2. _Mule message_: The data associated with the Mule event as it passes through one or more Mule flows in an application. +3. _Data throughput_: All of the network I/O bytes produced by the Mule Runtime server hosting a Mule application. + +### Individual metrics + +The following sections provide a brief description of each metric and how it contributes towards monthly subscription costs. For more complete details on these metrics, including those used for other products, refer to the https://docs.mulesoft.com/general/pricing-metrics[Usage and Pricing Metrics] guide. + +#### Mule flows + +A _Mule flow_ is a sequence of message processors grouped within a `` element in a Mule flow file. Mule flows typically consist of an event source, such as an Anypoint MQ subscriber or HTTP listener, and processors that act upon the _Mule message_ produced by that event source. More complex flows are typically broken up into sub-flows, which also include a sequence of processors grouped within a `` element but cannot include an event source. When sub-flows are referenced from top-level flows, the sub-flow contents are therefore included in-line to create a single monolithic flow at runtime. All APIkit route handlers - whether they are scaffolded from an API specification or explicitly mapped by hand - are considered top-level flows for pricing purposes. + +#### Mule messages + +A _Mule message_ is the data (payload and attributes) associated with a Mule event, which passes through one or more Mule flows in an application. This includes event sources such as incoming requests handled by an HTTP Listener (including those routed by APIkit), messages received from Anypoint MQ or VM Queues, file changed events, etc. All event messages processed count towards usage for pricing purposes. Additional messages or payloads created during processing do not count as event messages and therefore do not affect usage amounts. + +#### Data throughput + +Simply put, data throughput includes all network traffic that flows in or out of the instance or container hosting the Mule application. This includes business processes, such as publishing a message to MQ or making HTTP requests to downstream APIs, as well as health checks, external log forwarding, monitoring metrics transfer, etc. All data transfer in or out is taken into consideration for pricing purposes. + +### Metrics and pricing summary + +To summarize how the above metrics contribute towards usage costs in the new model, consider the following: + +1. The more endpoints (combination of resources and HTTP methods) an API specification contains, the more flows will be generated by the scaffolder. Each generated flow counts against the subscription allocation. +2. Sub-flows do not count towards usage costs as they do not contain event sources (flows without event sources also do not count but sub-flows are lighter-weight). +3. Health check requests (implemented in Mule applications) count towards both flow and message allocations. +4. Each "hop" (API to API request) included in the execution of a request counts towards both message and data throughput allocations. +5. Excessive use of logging processors (especially JSONLogger) and application-specific metrics collection count towards the data throughput allocation. + +## Accelerator assets and the new pricing model + +A consistent driving factor behind the design and implementation of use cases supported by the MuleSoft Accelerators has always been to keep the assets and corresponding solutions a simple as possible while still providing a solid, functional, and maintainable architecture for customers to build upon. We have achieved this through a few key principles when it comes to solution design: + +. Follow the API-led connectivity approach but create APIs only where necessary to support clean integration with external applications and systems. +. Keep exception handling clean and simple, allowing for straightforward extension and customization. +. Avoid the use of heavy logging, monitoring, or exception handling frameworks. +. Leverage a reusable canonical data model within the business process layer to simplify communication between layers. +. Use messaging only where it was deemed necessary to support high-volume deployments. +. Use inlined sub-flows instead top-level flows wherever possible. + +That said, the solutions were originally designed around a pricing model based on vCores. Since the intention of the accelerators has always been to provide customers with a starting point for implementing their own solutions, there are some aspects of the solutions that are not necessarily cost-effective when it comes to the new pricing and packaging model. These are discussed in more detail below. + +## Reducing runtime costs with accelerator assets + +As mentioned above, the assets developed for the MuleSoft Accelerators were intended to be flexible and extensible, supporting not just the use cases we have defined but other use cases needed by customers to support their business. For customers on the new pricing and packaging model, or who do not otherwise require such flexibility, there are a few ways that costs can be reduced without significantly sacrificing functionality. + +### Reducing the number Mule flows + +Given the signficance of Mule flows in the new model, reducing the number of flows can have a dramatic effect on cost reduction overall. The following are some specific steps you can take to reduce the number of flows in accelerator applications. + +#### Remove unused APIkit handlers + +Some of our API specifications - particularly System APIs - have been deliberately designed to support a wider range of use cases than what was strictly required to implement our own. This means that APIkit would have scaffolded flows you may not require for your own use cases. These can simply be removed from the main router flow file (usually the one named `*-api.xml`). There is no need to go through the trouble of changing the API specification and rescaffolding, since you would still have to edit the file manually to remove them anyway. + +#### Remove API health checks + +The `get:/ping` endpoint was provided for customers who may not have API Manager included in their subscription but still want a way to periodically evaluate the health status of deployed APIs. If not required, the handlers for these endpoints may be removed from the main APIkit flow file. Message and throughput costs may also be reduced by removing the checks for downstream dependencies (see below). + +#### Generalize event sources + +While we do not condone creating monolithic flows that listen to generic events, there is some cost-reduction that can be gained by combining finer-grained event sources into more granular events. For example, while we already created more general events for publishing Party (Individual, Household, etc.) and Party Role (Customer, Supplier, etc.) updates, the two update queues could be combined into one - bound to both Exchanges - and consumed by a single handler. A similar approach could be taken for VMQueue subscribers, SFTP listeners, etc. + +#### Reducing the number of APIs overall + +* Where back-end systems have a modern, well-designed API (e.g., Salesforce), and there is no need to perform extensive mapping between a canonical model and the back-end model, consider making calls directly to the system from the Process layer instead of through a System API only; this can also help reduce the number of message flows. +* When providing similar functionality to external applications via Experience APIs, look for opportunities to provide a single Experience API to support multiple channels, rather than one Experience API per channel. For example, multiple Salesforce Experience APIs could be combined into one or two APIs, reducing the number of handlers overall. + +### Reducing the number of Mule messages + +Mule messages are produced every time an event is received from an event source - including incoming API requests. One way to reduce the number of messages consumed is to reduce the number of API to API calls (e.g., Experience to Process, or Process to System) made during the course of handling a top level event. While the accelerator solution designs already avoid making unnecessary hops (e.g., Experience directly to System when no intermediate transformation, validation, or aggregation is required), there are a few ways this can be optimized further: + +* As described above, consider making calls to back-end systems directly from Process APIs where a well-defined interface exists. +* For health checks, remove the flows that also check the health of downstream systems when the `checkDependencies` flag is set. +* Replace the use of VMQueue or Anypoint MQ messaging if asynchronous processing is not truly required. These patterns were often provided with the expectation that customers may want to use them in high-volume deployments, which may not be the case for some customers. + +### Reducing data throughput + +As mentioned above, accelerator solutions already avoid unnecessary network traffic by reducing the number of hops and by not making use of any external logging, monitoring, or exception handling frameworks. A number of the cost reduction steps described above also apply to reducing data throughput. For your own deployments, be sure to take data throughput into account when considering the addition of any custom frameworks for logging, exception handling, etc. + +## See Also +_ +https://docs.mulesoft.com/general/pricing[Anypoint Platform Pricing] +https://docs.mulesoft.com/general/pricing-metrics[Usage and Pricing Metrics] +https://docs.mulesoft.com/general/usage-reports[Viewing Usage Reports] +https://blogs.mulesoft.com/learn-apis/api-led-connectivity/[API-led connectivity] From d307e5be9ae90e1981fe2a568cec96cc543b09eb Mon Sep 17 00:00:00 2001 From: Nisha Nizamuddin Date: Thu, 1 Feb 2024 14:34:22 -0800 Subject: [PATCH 3/3] Salesforce setup guide update --- .../ROOT/pages/additional-customizations.adoc | 6 +- .../modules/ROOT/pages/build-environment.adoc | 4 +- .../modules/ROOT/pages/cim-finance.adoc | 6 +- .../modules/ROOT/pages/cim-fulfill.adoc | 4 +- .../modules/ROOT/pages/cim-market.adoc | 4 +- .../modules/ROOT/pages/cim-overview.adoc | 2 +- .../modules/ROOT/pages/cim-produce.adoc | 4 +- .../modules/ROOT/pages/cim-sell.adoc | 4 +- .../modules/ROOT/pages/cim-setup.adoc | 4 +- .../modules/ROOT/pages/common-services.adoc | 8 +- .../modules/ROOT/pages/index.adoc | 6 +- .../modules/ROOT/pages/shared-assets.adoc | 12 +- .../3.0/modules/ROOT/pages/cg-assets.adoc | 50 +- .../3.0/modules/ROOT/pages/index.adoc | 8 +- .../3.0/modules/ROOT/pages/release-notes.adoc | 8 +- .../ROOT/pages/sap-s4hana-setup-guide.adoc | 54 +- .../4.0/modules/ROOT/pages/cg-assets.adoc | 50 +- .../4.0/modules/ROOT/pages/index.adoc | 8 +- .../4.0/modules/ROOT/pages/release-notes.adoc | 10 +- .../ROOT/pages/sap-s4hana-setup-guide.adoc | 54 +- .../5.0/modules/ROOT/pages/cg-assets.adoc | 58 +- .../5.0/modules/ROOT/pages/index.adoc | 10 +- .../5.0/modules/ROOT/pages/release-notes.adoc | 14 +- .../ROOT/pages/sap-s4hana-setup-guide.adoc | 54 +- .../5.1/modules/ROOT/pages/cg-assets.adoc | 54 +- .../5.1/modules/ROOT/pages/index.adoc | 6 +- .../ROOT/pages/sap-s4hana-setup-guide.adoc | 54 +- .../5.2/modules/ROOT/pages/cg-assets.adoc | 64 +- .../5.2/modules/ROOT/pages/index.adoc | 8 +- .../ROOT/pages/sap-s4hana-setup-guide.adoc | 54 +- .../_partials/custom-components-fragment.adoc | 10 +- .../_partials/experience-apis-fragment.adoc | 22 +- .../pages/_partials/listeners-fragment.adoc | 10 +- .../_partials/process-apis-fragment.adoc | 36 +- .../pages/_partials/system-apis-fragment.adoc | 50 +- .../ROOT/pages/anypointmq-setup-guide.adoc | 2 +- .../1.10/modules/ROOT/pages/bian-assets.adoc | 106 ++-- .../1.10/modules/ROOT/pages/fins-assets.adoc | 22 +- .../1.10/modules/ROOT/pages/index.adoc | 26 +- .../ROOT/pages/payments-setup-guide.adoc | 16 +- .../pages/sfdc-data-cloud-setup-guide.adoc | 54 +- .../ROOT/pages/sfdc-fsc-setup-guide.adoc | 10 +- .../ROOT/pages/sfdc-mc-setup-guide.adoc | 12 +- .../_partials/custom-components-fragment.adoc | 10 +- .../_partials/experience-apis-fragment.adoc | 22 +- .../pages/_partials/listeners-fragment.adoc | 10 +- .../_partials/process-apis-fragment.adoc | 36 +- .../pages/_partials/system-apis-fragment.adoc | 50 +- .../ROOT/pages/anypointmq-setup-guide.adoc | 2 +- .../1.8/modules/ROOT/pages/bian-assets.adoc | 106 ++-- .../1.8/modules/ROOT/pages/fins-assets.adoc | 22 +- .../1.8/modules/ROOT/pages/index.adoc | 22 +- .../ROOT/pages/payments-setup-guide.adoc | 16 +- .../1.8/modules/ROOT/pages/release-notes.adoc | 10 +- .../pages/sfdc-data-cloud-setup-guide.adoc | 54 +- .../ROOT/pages/sfdc-fsc-setup-guide.adoc | 10 +- .../ROOT/pages/sfdc-mc-setup-guide.adoc | 12 +- .../_partials/custom-components-fragment.adoc | 10 +- .../_partials/experience-apis-fragment.adoc | 22 +- .../pages/_partials/listeners-fragment.adoc | 10 +- .../_partials/process-apis-fragment.adoc | 36 +- .../pages/_partials/system-apis-fragment.adoc | 50 +- .../ROOT/pages/anypointmq-setup-guide.adoc | 2 +- .../1.9/modules/ROOT/pages/bian-assets.adoc | 106 ++-- .../1.9/modules/ROOT/pages/fins-assets.adoc | 22 +- .../1.9/modules/ROOT/pages/index.adoc | 24 +- .../ROOT/pages/payments-setup-guide.adoc | 16 +- .../pages/sfdc-data-cloud-setup-guide.adoc | 54 +- .../ROOT/pages/sfdc-fsc-setup-guide.adoc | 10 +- .../ROOT/pages/sfdc-mc-setup-guide.adoc | 12 +- .../ROOT/pages/ccda-fhir-converter.adoc | 4 +- .../modules/ROOT/pages/fhir-r4-assets.adoc | 6 +- .../modules/ROOT/pages/fhir-r4-resources.adoc | 598 +++++++++--------- .../ROOT/pages/fhir-r4-us-core-profiles.adoc | 94 +-- .../ROOT/pages/hl7-v2-fhir-converter.adoc | 4 +- healthcare/2.18/modules/ROOT/pages/index.adoc | 16 +- .../modules/ROOT/pages/release-notes.adoc | 216 +++---- .../pages/sfdc-data-cloud-setup-guide.adoc | 44 +- .../pages/sfdc-health-cloud-setup-guide.adoc | 6 +- .../modules/ROOT/pages/smart-fhir-okta.adoc | 8 +- .../ROOT/pages/x12-fhir-converter.adoc | 4 +- .../ROOT/pages/ccda-fhir-converter.adoc | 4 +- .../modules/ROOT/pages/fhir-r4-assets.adoc | 6 +- .../modules/ROOT/pages/fhir-r4-resources.adoc | 598 +++++++++--------- .../ROOT/pages/fhir-r4-us-core-profiles.adoc | 94 +-- .../ROOT/pages/hl7-v2-fhir-converter.adoc | 4 +- healthcare/2.19/modules/ROOT/pages/index.adoc | 16 +- .../modules/ROOT/pages/release-notes.adoc | 218 +++---- .../pages/sfdc-data-cloud-setup-guide.adoc | 44 +- .../pages/sfdc-health-cloud-setup-guide.adoc | 6 +- .../modules/ROOT/pages/smart-fhir-okta.adoc | 8 +- .../ROOT/pages/x12-fhir-converter.adoc | 4 +- .../ROOT/pages/ccda-fhir-converter.adoc | 4 +- .../modules/ROOT/pages/fhir-r4-assets.adoc | 6 +- .../modules/ROOT/pages/fhir-r4-resources.adoc | 598 +++++++++--------- .../ROOT/pages/fhir-r4-us-core-profiles.adoc | 94 +-- .../ROOT/pages/hl7-v2-fhir-converter.adoc | 4 +- healthcare/2.20/modules/ROOT/pages/index.adoc | 16 +- .../modules/ROOT/pages/release-notes.adoc | 224 +++---- .../pages/sfdc-data-cloud-setup-guide.adoc | 44 +- .../pages/sfdc-health-cloud-setup-guide.adoc | 6 +- .../modules/ROOT/pages/smart-fhir-okta.adoc | 8 +- .../ROOT/pages/x12-fhir-converter.adoc | 4 +- .../ROOT/pages/ccda-fhir-converter.adoc | 4 +- .../modules/ROOT/pages/fhir-r4-assets.adoc | 6 +- .../modules/ROOT/pages/fhir-r4-resources.adoc | 598 +++++++++--------- .../ROOT/pages/fhir-r4-us-core-profiles.adoc | 94 +-- .../ROOT/pages/hl7-v2-fhir-converter.adoc | 4 +- healthcare/2.21/modules/ROOT/pages/index.adoc | 16 +- .../pages/sfdc-data-cloud-setup-guide.adoc | 44 +- .../pages/sfdc-health-cloud-setup-guide.adoc | 6 +- .../modules/ROOT/pages/smart-fhir-okta.adoc | 8 +- .../ROOT/pages/x12-fhir-converter.adoc | 4 +- .../ROOT/pages/ccda-fhir-converter.adoc | 4 +- .../modules/ROOT/pages/fhir-r4-assets.adoc | 6 +- .../modules/ROOT/pages/fhir-r4-resources.adoc | 598 +++++++++--------- .../ROOT/pages/fhir-r4-us-core-profiles.adoc | 94 +-- .../ROOT/pages/hl7-v2-fhir-converter.adoc | 4 +- healthcare/2.22/modules/ROOT/pages/index.adoc | 18 +- .../pages/sfdc-data-cloud-setup-guide.adoc | 44 +- .../pages/sfdc-health-cloud-setup-guide.adoc | 6 +- .../modules/ROOT/pages/smart-fhir-okta.adoc | 8 +- .../ROOT/pages/x12-fhir-converter.adoc | 4 +- .../1.1/modules/ROOT/pages/index.adoc | 6 +- .../1.1/modules/ROOT/pages/ls-assets.adoc | 30 +- .../1.3/modules/ROOT/pages/index.adoc | 18 +- .../1.3/modules/ROOT/pages/mfg-assets.adoc | 114 ++-- .../modules/ROOT/pages/mfg-setup-guide.adoc | 4 +- .../1.3/modules/ROOT/pages/release-notes.adoc | 6 +- .../modules/ROOT/pages/sftp-setup-guide.adoc | 2 +- .../ROOT/pages/tableau-setup-guide.adoc | 10 +- .../1.4/modules/ROOT/pages/index.adoc | 18 +- .../1.4/modules/ROOT/pages/mfg-assets.adoc | 114 ++-- .../modules/ROOT/pages/mfg-setup-guide.adoc | 4 +- .../modules/ROOT/pages/sftp-setup-guide.adoc | 2 +- .../ROOT/pages/tableau-setup-guide.adoc | 10 +- modules/ROOT/pages/accel/shared-assets.adoc | 10 +- retail/2.7/modules/ROOT/pages/index.adoc | 12 +- retail/2.7/modules/ROOT/pages/rcg-assets.adoc | 148 ++--- .../pages/sap-custom-bapi-setup-guide.adoc | 98 +-- .../ROOT/pages/sap-s4hana-setup-guide.adoc | 54 +- .../pages/sfdc-data-cloud-setup-guide.adoc | 16 +- retail/3.0/modules/ROOT/pages/index.adoc | 12 +- retail/3.0/modules/ROOT/pages/rcg-assets.adoc | 148 ++--- .../pages/sap-custom-bapi-setup-guide.adoc | 98 +-- .../ROOT/pages/sap-s4hana-setup-guide.adoc | 54 +- .../ROOT/pages/sfdc-customization-guide.adoc | 2 +- .../pages/sfdc-data-cloud-setup-guide.adoc | 16 +- retail/3.1/modules/ROOT/pages/index.adoc | 14 +- retail/3.1/modules/ROOT/pages/rcg-assets.adoc | 152 ++--- .../pages/sap-custom-bapi-setup-guide.adoc | 98 +-- .../ROOT/pages/sap-s4hana-setup-guide.adoc | 54 +- .../ROOT/pages/sfdc-customization-guide.adoc | 2 +- .../pages/sfdc-data-cloud-setup-guide.adoc | 16 +- 154 files changed, 3868 insertions(+), 3868 deletions(-) diff --git a/accelerators-home/modules/ROOT/pages/additional-customizations.adoc b/accelerators-home/modules/ROOT/pages/additional-customizations.adoc index e8dfc6094..d4bc5342d 100644 --- a/accelerators-home/modules/ROOT/pages/additional-customizations.adoc +++ b/accelerators-home/modules/ROOT/pages/additional-customizations.adoc @@ -4,11 +4,11 @@ The following customizations can be made to tailor the accelerator components to == Maven POM Parent -All Accelerator projects inherit from a parent Maven POM. In addition to some global settings and repository references, this config also defines the versions of all MuleSoft connectors and modules used by applications. Refer to the https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/accelerator-pom-parent-src/[Accelerator POM Parent^] asset for more information about making changes to the POM parent file. +All Accelerator projects inherit from a parent Maven POM. In addition to some global settings and repository references, this config also defines the versions of all MuleSoft connectors and modules used by applications. Refer to the https://anypoint.mulesoft.com/exchange/org.mule.examples/accelerator-pom-parent-src/[Accelerator POM Parent^] asset for more information about making changes to the POM parent file. == Common Core Library -It is a best practice in MuleSoft application development to place common flows, configuration settings, and other resources into a shared library. The https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/accelerator-common-core-src/[Accelerator Common Core Library^] asset contains the source used by most implementation templates created for the accelerators. It is referenced as a Maven dependency only and is _not_ an application you can run. +It is a best practice in MuleSoft application development to place common flows, configuration settings, and other resources into a shared library. The https://anypoint.mulesoft.com/exchange/org.mule.examples/accelerator-common-core-src/[Accelerator Common Core Library^] asset contains the source used by most implementation templates created for the accelerators. It is referenced as a Maven dependency only and is _not_ an application you can run. If you need to make changes to it you will need to download the asset, extract the source, and then import it into Studio (use the `Anypoint Studio project from File System` wizard). As with the POM parent, update the version number before making any changes. See the `README.md` file in the project source for more details. @@ -42,7 +42,7 @@ For convenience, passwords, secrets, hostnames, URLs have been converted to plai To use secure properties, set an `encryption-key` (called "mule.key" in configurations) for encrypting secrets. Individual properties can then be encrypted and placed in the `config-secured-${mule.env}.yaml` file, as appropriate. These files will automatically be imported at runtime. For maximum security, use a different encryption key for each application. -Refer to the https://dev-docs-internal.kqa.msap.io/beta-accelerators/runtime-manager/secure-application-properties[MuleSoft documentation^] for more information. +Refer to the https://docs.mulesoft.com/runtime-manager/secure-application-properties[MuleSoft documentation^] for more information. == Application Messages diff --git a/accelerators-home/modules/ROOT/pages/build-environment.adoc b/accelerators-home/modules/ROOT/pages/build-environment.adoc index caabd3de7..acd53e139 100644 --- a/accelerators-home/modules/ROOT/pages/build-environment.adoc +++ b/accelerators-home/modules/ROOT/pages/build-environment.adoc @@ -35,10 +35,10 @@ Perform the following steps to prepare your workstation for building, deploying, === Configuring the Accelerator Build -. Download the https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/accelerator-common-resources-src[Accelerator Common Resources^] asset from Exchange and unpack the archive to a temporary directory. The directory should contain a single Studio project folder called `accelerator-common-resources`. +. Download the https://anypoint.mulesoft.com/exchange/org.mule.examples/accelerator-common-resources-src[Accelerator Common Resources^] asset from Exchange and unpack the archive to a temporary directory. The directory should contain a single Studio project folder called `accelerator-common-resources`. . Import the project folder into Studio using the *accel/Existing Projects into Workspace* wizard (not the Anypoint Studio project wizard). If the project does not import as `accelerator-common-resources`, you can select the project in the Package Explorer view and press F2 to rename it: + + -image:https://www.mulesoft.com/ext/solutions/draft/images/sfc-doc-setupguide_01.png[sfc-doc-setupguide_01.png,599] +image:https://www.mulesoft.com/ext/solutions/images/sfc-doc-setupguide_01.png[sfc-doc-setupguide_01.png,599] . Copy the contents of the `settings-accelerators.xml` file to your local Maven `settings.xml` file, which is usually located under `$HOME/.m2` on Linux/MacOS hosts and `%USERPROFILE%\.m2` on Windows hosts; create a new file if it does not exist. If the file already exists, make sure to merge the contents of the `settings-accelerators.xml` with the existing. You may also choose to keep the file separate and specify the `-s ` option when running Maven commands; in Studio you will also need to override the user settings path, which is under `Anypoint Studio/Maven/User Settings` in the Preferences dialog. [NOTE] This step is optional, if the project is intended to build only in Anypoint Studio. diff --git a/accelerators-home/modules/ROOT/pages/cim-finance.adoc b/accelerators-home/modules/ROOT/pages/cim-finance.adoc index 6e2748d12..842442f41 100644 --- a/accelerators-home/modules/ROOT/pages/cim-finance.adoc +++ b/accelerators-home/modules/ROOT/pages/cim-finance.adoc @@ -8,15 +8,15 @@ The following diagrams show the entities and relationships in this subject area, === Payment -image::https://www.mulesoft.com/ext/solutions/draft/images/cim/Payment.png[alt="Payment Diagram",link="https://www.mulesoft.com/ext/solutions/draft/images/cim/accel-cim-payment.png"] +image::https://www.mulesoft.com/ext/solutions/images/cim/Payment.png[alt="Payment Diagram",link="https://www.mulesoft.com/ext/solutions/images/cim/accel-cim-payment.png"] === Payment Method -image::https://www.mulesoft.com/ext/solutions/draft/images/cim/PaymentMethod.png[alt="Payment Method Diagram",link="https://www.mulesoft.com/ext/solutions/draft/images/cim/accel-cim-payment-method.png"] +image::https://www.mulesoft.com/ext/solutions/images/cim/PaymentMethod.png[alt="Payment Method Diagram",link="https://www.mulesoft.com/ext/solutions/images/cim/accel-cim-payment-method.png"] == Implementation -https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/accelerator-cim-finance-library[CIM Finance Library^] +https://anypoint.mulesoft.com/exchange/org.mule.examples/accelerator-cim-finance-library[CIM Finance Library^] == See Also diff --git a/accelerators-home/modules/ROOT/pages/cim-fulfill.adoc b/accelerators-home/modules/ROOT/pages/cim-fulfill.adoc index 5c57ad90b..5255684e4 100644 --- a/accelerators-home/modules/ROOT/pages/cim-fulfill.adoc +++ b/accelerators-home/modules/ROOT/pages/cim-fulfill.adoc @@ -8,11 +8,11 @@ The following diagrams show the entities and relationships in this subject area, === Shipment -image::https://www.mulesoft.com/ext/solutions/draft/images/cim/Shipment.png[alt="Shipment Diagram",link="https://www.mulesoft.com/ext/solutions/draft/images/cim/accel-cim-shipment.png"] +image::https://www.mulesoft.com/ext/solutions/images/cim/Shipment.png[alt="Shipment Diagram",link="https://www.mulesoft.com/ext/solutions/images/cim/accel-cim-shipment.png"] == Implementation -https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/accelerator-cim-fulfill-library[CIM Fulill Library^] +https://anypoint.mulesoft.com/exchange/org.mule.examples/accelerator-cim-fulfill-library[CIM Fulill Library^] == See Also diff --git a/accelerators-home/modules/ROOT/pages/cim-market.adoc b/accelerators-home/modules/ROOT/pages/cim-market.adoc index f7594ab95..c50f2e8eb 100644 --- a/accelerators-home/modules/ROOT/pages/cim-market.adoc +++ b/accelerators-home/modules/ROOT/pages/cim-market.adoc @@ -8,11 +8,11 @@ The following diagrams show the entities and relationships in this subject area, === Party -image::https://www.mulesoft.com/ext/solutions/draft/images/cim/Party.png[alt="Party Diagram",link="https://www.mulesoft.com/ext/solutions/draft/images/cim/accel-cim-party.png"] +image::https://www.mulesoft.com/ext/solutions/images/cim/Party.png[alt="Party Diagram",link="https://www.mulesoft.com/ext/solutions/images/cim/accel-cim-party.png"] == Implementation -https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/accelerator-cim-market-library[CIM Market Library^] +https://anypoint.mulesoft.com/exchange/org.mule.examples/accelerator-cim-market-library[CIM Market Library^] == See Also diff --git a/accelerators-home/modules/ROOT/pages/cim-overview.adoc b/accelerators-home/modules/ROOT/pages/cim-overview.adoc index 0d346c769..cafa8588e 100644 --- a/accelerators-home/modules/ROOT/pages/cim-overview.adoc +++ b/accelerators-home/modules/ROOT/pages/cim-overview.adoc @@ -26,7 +26,7 @@ The model content is organized into domains, or Subject Areas, which represent m The version of CIM used by the MuleSoft Accelerators is represented as a set of RAML library fragments. There is a core library for each domain, plus extension libraries that aggregate data types from multiple core libraries for a more complete representation of the model. The entities in each core library are logically grouped into related entities within that Subject Area. Each core library provides a set of examples and JSON schemas, which can be useful for defining metadata types when developing applications in Anypoint Studio. -Refer to the https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/accelerator-cim-global-library[Accelerator CIM Global Library^] home page to get started with using the model. +Refer to the https://anypoint.mulesoft.com/exchange/org.mule.examples/accelerator-cim-global-library[Accelerator CIM Global Library^] home page to get started with using the model. == See Also diff --git a/accelerators-home/modules/ROOT/pages/cim-produce.adoc b/accelerators-home/modules/ROOT/pages/cim-produce.adoc index 8670c75e4..be96389f5 100644 --- a/accelerators-home/modules/ROOT/pages/cim-produce.adoc +++ b/accelerators-home/modules/ROOT/pages/cim-produce.adoc @@ -8,11 +8,11 @@ The following diagrams show the entities and relationships in this subject area, === Product -image::https://www.mulesoft.com/ext/solutions/draft/images/cim/Product.png[alt="Product Diagram",link="https://www.mulesoft.com/ext/solutions/draft/images/cim/accel-cim-product.png"] +image::https://www.mulesoft.com/ext/solutions/images/cim/Product.png[alt="Product Diagram",link="https://www.mulesoft.com/ext/solutions/images/cim/accel-cim-product.png"] == Implementation -https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/accelerator-cim-produce-library[CIM Produce Library^] +https://anypoint.mulesoft.com/exchange/org.mule.examples/accelerator-cim-produce-library[CIM Produce Library^] == See Also diff --git a/accelerators-home/modules/ROOT/pages/cim-sell.adoc b/accelerators-home/modules/ROOT/pages/cim-sell.adoc index 11aa43d41..3f5fb8481 100644 --- a/accelerators-home/modules/ROOT/pages/cim-sell.adoc +++ b/accelerators-home/modules/ROOT/pages/cim-sell.adoc @@ -8,11 +8,11 @@ The following diagrams show the entities and relationships in this subject area, === Sales Order -image::https://www.mulesoft.com/ext/solutions/draft/images/cim/SalesOrder.png[alt="Sales Order Diagram",link="https://www.mulesoft.com/ext/solutions/draft/images/cim/accel-cim-salesorder.png"] +image::https://www.mulesoft.com/ext/solutions/images/cim/SalesOrder.png[alt="Sales Order Diagram",link="https://www.mulesoft.com/ext/solutions/images/cim/accel-cim-salesorder.png"] == Implementation -https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/accelerator-cim-sell-library[CIM Sell Library^] +https://anypoint.mulesoft.com/exchange/org.mule.examples/accelerator-cim-sell-library[CIM Sell Library^] == See Also diff --git a/accelerators-home/modules/ROOT/pages/cim-setup.adoc b/accelerators-home/modules/ROOT/pages/cim-setup.adoc index 0ccc42129..86659fb03 100644 --- a/accelerators-home/modules/ROOT/pages/cim-setup.adoc +++ b/accelerators-home/modules/ROOT/pages/cim-setup.adoc @@ -8,11 +8,11 @@ The following diagrams show the entities and relationships in this subject area, === Document -image:https://www.mulesoft.com/ext/solutions/draft/images/cim/accel-cim-document.png[alt="Document Diagram", link=https://www.mulesoft.com/ext/solutions/draft/images/cim/accel-cim-document.png] +image:https://www.mulesoft.com/ext/solutions/images/cim/accel-cim-document.png[alt="Document Diagram", link=https://www.mulesoft.com/ext/solutions/images/cim/accel-cim-document.png] == Implementation -https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/accelerator-cim-setup-library[CIM Setup Library^] +https://anypoint.mulesoft.com/exchange/org.mule.examples/accelerator-cim-setup-library[CIM Setup Library^] == See Also diff --git a/accelerators-home/modules/ROOT/pages/common-services.adoc b/accelerators-home/modules/ROOT/pages/common-services.adoc index 7ffe33343..ee389642b 100644 --- a/accelerators-home/modules/ROOT/pages/common-services.adoc +++ b/accelerators-home/modules/ROOT/pages/common-services.adoc @@ -12,7 +12,7 @@ The notification and scheduler services can be configured and installed as indep The Common Scheduling Service is an optional component that will run schedules and perform API calls. The benefit of having a common scheduler service is to have all the integration-level schedules maintained in one place. Here is a high-level view of how the scheduler service works: -image::https://www.mulesoft.com/ext/solutions/draft/images/accel-scheduling-service-diagram.png[accel-scheduling-service-diagram.png] +image::https://www.mulesoft.com/ext/solutions/images/accel-scheduling-service-diagram.png[accel-scheduling-service-diagram.png] The service may be built in two different ways, depending on the target deployment platform. The Anypoint Platform offers operational advantages to applications deployed in CloudHub when dealing with schedules. @@ -30,7 +30,7 @@ For service configuration details please refer to the xref:./getting-started.ado The solution provides an optional Notifications Process API, which consumes notification events and sends notifications to individuals or groups via SMS, email, or Slack via system APIs specific to those services. The high-level design is as follows: -image::https://www.mulesoft.com/ext/solutions/draft/images/accel-notification-service-diagram.png[accel-notification-service-diagram.png] +image::https://www.mulesoft.com/ext/solutions/images/accel-notification-service-diagram.png[accel-notification-service-diagram.png] As you can see, the API offloads incoming requests directly to a queue in order to avoid blocking calling apps. @@ -115,7 +115,7 @@ An easier way to apply policies to all APIs is to deploy them as Automated polic == See Also -* The https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/accelerator-mulesoft-api-template-src/[API Template Project^] is a generic implementation template that allows you to quickly create implementations for new API specifications. -* The https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/accelerator-mulesoft-api-archetype-src/[Maven Archetype Plugin^] is a Maven archetype pre-built with Accelerator best practices to help developers kick start their development of new APIs. +* The https://anypoint.mulesoft.com/exchange/org.mule.examples/accelerator-mulesoft-api-template-src/[API Template Project^] is a generic implementation template that allows you to quickly create implementations for new API specifications. +* The https://anypoint.mulesoft.com/exchange/org.mule.examples/accelerator-mulesoft-api-archetype-src/[Maven Archetype Plugin^] is a Maven archetype pre-built with Accelerator best practices to help developers kick start their development of new APIs. * The xref:./getting-started.adoc[Getting Started] guide provides detailed information about configuring and using these services. Refer to the navigation pages on the left for more information about these services from a functional perspective. * The xref:./index.adoc[MuleSoft Accelerators] main page. diff --git a/accelerators-home/modules/ROOT/pages/index.adoc b/accelerators-home/modules/ROOT/pages/index.adoc index 07dcdce81..bc15b09e1 100644 --- a/accelerators-home/modules/ROOT/pages/index.adoc +++ b/accelerators-home/modules/ROOT/pages/index.adoc @@ -11,13 +11,13 @@ To access any of the asset links described within the following Accelerators, yo [cols="10a,30a,60a"] |=== .^|image:cg-icon.png[Consumer Goods,100%] .^| xref:5.1@consumer-goods::index.adoc[MuleSoft Accelerator for Consumer Goods] .^| Helps consumer goods companies integrate their digital operations to gain visibility into trade promotion management and retail execution. -.^|image:dc-icon.png[Data Cloud,100%] .^| https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/mulesoft-accelerator-for-datacloud/[MuleSoft Accelerator for Data Cloud^] .^| Enable organizations to easily unlock and connect core systems of record for Data Cloud. +.^|image:dc-icon.png[Data Cloud,100%] .^| https://anypoint.mulesoft.com/exchange/org.mule.examples/mulesoft-accelerator-for-datacloud/[MuleSoft Accelerator for Data Cloud^] .^| Enable organizations to easily unlock and connect core systems of record for Data Cloud. .^|image:fs-icon.png[Financial Services,100%] .^| xref:1.9@financial-services::index.adoc[MuleSoft Accelerator for Financial Services] .^| Simplifies customer 360 initiatives by unlocking both core banking and insurance platforms, systems of engagement (such as CRM and ITSM), Insuretechs, and FinTech data. .^|image:hc-icon.png[Healthcare,100%] .^| xref:2.20@healthcare::index.adoc[MuleSoft Accelerator for Healthcare] .^| Equips Payer, Provider, and Life Sciences organizations with foundational assets to accelerate their digital transformation journey. .^|image:ls-icon.png[Life Sciences,100%] .^| xref:1.1@life-sciences::index.adoc[MuleSoft Accelerator for Life Sciences] .^| Helps pharmaceuticals, medical device companies, and contract research organizations (CROs) integrate digital operations and get their products to market faster. .^|image:mfg-icon.png[Manufacturing,100%] .^| xref:1.3@manufacturing::index.adoc[MuleSoft Accelerator for Manufacturing] .^| Equips discrete and process manufacturers with foundational assets for common use cases to accelerate their digital transformation journey. .^|image:retail-icon.png[Retail,100%] .^| xref:2.7@retail::index.adoc[MuleSoft Accelerator for Retail] .^| Empowers retail IT teams to unlock data from systems including ERP, CRM, MDM, commerce, and marketing to activate digital projects faster. -.^|image:sap-icon.png[SAP,100%] .^| https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/mulesoft-accelerator-for-sap/[MuleSoft Accelerator for SAP^] .^| Enable organizations to easily expose SAP ERP data for consumption by all. +.^|image:sap-icon.png[SAP,100%] .^| https://anypoint.mulesoft.com/exchange/org.mule.examples/mulesoft-accelerator-for-sap/[MuleSoft Accelerator for SAP^] .^| Enable organizations to easily expose SAP ERP data for consumption by all. |=== If you have any questions or feedback, let us know at solutions-questions@mulesoft.com. You can also engage with other users on the https://help.mulesoft.com/s/forum[MuleSoft Forum^] and submit ideas on the https://ideas.salesforce.com/[Salesforce Ideas Portal^]. @@ -25,4 +25,4 @@ If you have any questions or feedback, let us know at solutions-questions@muleso == See Also * xref:getting-started.adoc[Getting Started Guide] -* https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/mulesoft-accelerators-introduction/[MuleSoft Accelerators on Anypoint Exchange^]. +* https://anypoint.mulesoft.com/exchange/org.mule.examples/mulesoft-accelerators-introduction/[MuleSoft Accelerators on Anypoint Exchange^]. diff --git a/accelerators-home/modules/ROOT/pages/shared-assets.adoc b/accelerators-home/modules/ROOT/pages/shared-assets.adoc index da956e30e..12449fad0 100644 --- a/accelerators-home/modules/ROOT/pages/shared-assets.adoc +++ b/accelerators-home/modules/ROOT/pages/shared-assets.adoc @@ -10,7 +10,7 @@ The following RAML libraries are available for use in all API specifications. ==== US Exchange:: + -:anypoint-url: anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873 +:anypoint-url: anypoint.mulesoft.com/exchange/org.mule.examples include::_partials/api-libraries-fragment.adoc[] EU Exchange:: @@ -32,7 +32,7 @@ The following APIs are used by multiple accelerators to access and manage data i ==== US Exchange:: + -:anypoint-url: anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873 +:anypoint-url: anypoint.mulesoft.com/exchange/org.mule.examples include::_partials/system-apis-fragment.adoc[] EU Exchange:: @@ -54,7 +54,7 @@ The following APIs represent the reusable business processes that are leveraged ==== US Exchange:: + -:anypoint-url: anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873 +:anypoint-url: anypoint.mulesoft.com/exchange/org.mule.examples include::_partials/process-apis-fragment.adoc[] EU Exchange:: @@ -76,7 +76,7 @@ The following APIs provide tailor-made endpoints for specific applications to co ==== US Exchange:: + -:anypoint-url: anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873 +:anypoint-url: anypoint.mulesoft.com/exchange/org.mule.examples include::_partials/experience-apis-fragment.adoc[] EU Exchange:: @@ -98,7 +98,7 @@ The following applications provide key integrations but do not expose any APIs a ==== US Exchange:: + -:anypoint-url: anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873 +:anypoint-url: anypoint.mulesoft.com/exchange/org.mule.examples include::_partials/integrations-fragment.adoc[] EU Exchange:: @@ -120,7 +120,7 @@ The following non-application components are also used by multiple accelerators. ==== US Exchange:: + -:anypoint-url: anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873 +:anypoint-url: anypoint.mulesoft.com/exchange/org.mule.examples include::_partials/shared-components-fragment.adoc[] EU Exchange:: diff --git a/consumer-goods/3.0/modules/ROOT/pages/cg-assets.adoc b/consumer-goods/3.0/modules/ROOT/pages/cg-assets.adoc index 425427e1e..365e1d7bb 100644 --- a/consumer-goods/3.0/modules/ROOT/pages/cg-assets.adoc +++ b/consumer-goods/3.0/modules/ROOT/pages/cg-assets.adoc @@ -7,36 +7,36 @@ Accelerator assets include API specifications, implementation templates, custom [cols="40,30,30",width=100%] |=== | MDM System API -| https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/rcg-mdm-sys-api-spec/[API Specification^] -| https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/rcg-mdm-sys-api/[Implementation Template^] +| https://anypoint.mulesoft.com/exchange/org.mule.examples/rcg-mdm-sys-api-spec/[API Specification^] +| https://anypoint.mulesoft.com/exchange/org.mule.examples/rcg-mdm-sys-api/[Implementation Template^] | SAP S/4HANA Products System API -| https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/rcg-saphana-products-sys-api-spec/[API Specification^] -| https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/rcg-saphana-products-sys-api/[Implementation Template^] +| https://anypoint.mulesoft.com/exchange/org.mule.examples/rcg-saphana-products-sys-api-spec/[API Specification^] +| https://anypoint.mulesoft.com/exchange/org.mule.examples/rcg-saphana-products-sys-api/[Implementation Template^] | RCG Salesforce Consumer Goods Cloud System API -| https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/rcg-salesforce-cgcloud-sys-api-spec/[API Specification^] -| https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/rcg-salesforce-cgcloud-sys-api/[Implementation Template^] +| https://anypoint.mulesoft.com/exchange/org.mule.examples/rcg-salesforce-cgcloud-sys-api-spec/[API Specification^] +| https://anypoint.mulesoft.com/exchange/org.mule.examples/rcg-salesforce-cgcloud-sys-api/[Implementation Template^] | SAP S/4HANA Customers System API -| https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/rcg-saphana-customers-sys-api-spec/[API Specification^] -| https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/rcg-saphana-customers-sys-api/[Implementation Template^] +| https://anypoint.mulesoft.com/exchange/org.mule.examples/rcg-saphana-customers-sys-api-spec/[API Specification^] +| https://anypoint.mulesoft.com/exchange/org.mule.examples/rcg-saphana-customers-sys-api/[Implementation Template^] | RCG Salsify Products System API -| https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/rcg-salsify-products-sys-api-spec/[API Specification^] -| https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/rcg-salsify-products-sys-api/[Implementation Template^] +| https://anypoint.mulesoft.com/exchange/org.mule.examples/rcg-salsify-products-sys-api-spec/[API Specification^] +| https://anypoint.mulesoft.com/exchange/org.mule.examples/rcg-salsify-products-sys-api/[Implementation Template^] | RCG Trax System API -| https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/rcg-trax-sys-api-spec/[API Specification^] -| https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/rcg-trax-sys-api/[Implementation Template^] +| https://anypoint.mulesoft.com/exchange/org.mule.examples/rcg-trax-sys-api-spec/[API Specification^] +| https://anypoint.mulesoft.com/exchange/org.mule.examples/rcg-trax-sys-api/[Implementation Template^] | RCG Hyperforce System API -| https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/rcg-hyperforce-sys-api-spec/[API Specification^] -| https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/rcg-hyperforce-sys-api/[Implementation Template^] +| https://anypoint.mulesoft.com/exchange/org.mule.examples/rcg-hyperforce-sys-api-spec/[API Specification^] +| https://anypoint.mulesoft.com/exchange/org.mule.examples/rcg-hyperforce-sys-api/[Implementation Template^] | RCG CRM Analytics System API -| https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/rcg-crma-sys-api-spec/[API Specification^] -| https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/rcg-crma-sys-api/[Implementation Template^] +| https://anypoint.mulesoft.com/exchange/org.mule.examples/rcg-crma-sys-api-spec/[API Specification^] +| https://anypoint.mulesoft.com/exchange/org.mule.examples/rcg-crma-sys-api/[Implementation Template^] |=== == Process APIs @@ -44,20 +44,20 @@ Accelerator assets include API specifications, implementation templates, custom [cols="40,30,30",width=100%] |=== | RCG Products Process API -| https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/rcg-products-prc-api-spec/[API Specification^] -| https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/rcg-products-prc-api/[Implementation Template^] +| https://anypoint.mulesoft.com/exchange/org.mule.examples/rcg-products-prc-api-spec/[API Specification^] +| https://anypoint.mulesoft.com/exchange/org.mule.examples/rcg-products-prc-api/[Implementation Template^] | RCG Customers Process API -| https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/rcg-customers-prc-api-spec/[API Specification^] -| https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/rcg-customers-prc-api/[Implementation Template^] +| https://anypoint.mulesoft.com/exchange/org.mule.examples/rcg-customers-prc-api-spec/[API Specification^] +| https://anypoint.mulesoft.com/exchange/org.mule.examples/rcg-customers-prc-api/[Implementation Template^] | RCG Store Audit Process API -| https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/rcg-store-audit-prc-api-spec[API Specification^] -| https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/rcg-store-audit-prc-api/[Implementation Template^] +| https://anypoint.mulesoft.com/exchange/org.mule.examples/rcg-store-audit-prc-api-spec[API Specification^] +| https://anypoint.mulesoft.com/exchange/org.mule.examples/rcg-store-audit-prc-api/[Implementation Template^] | RCG Data Normalisation Process API -| https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/rcg-data-normalization-prc-api-spec[API Specification^] -| https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/rcg-data-normalization-prc-api/[Implementation Template^] +| https://anypoint.mulesoft.com/exchange/org.mule.examples/rcg-data-normalization-prc-api-spec[API Specification^] +| https://anypoint.mulesoft.com/exchange/org.mule.examples/rcg-data-normalization-prc-api/[Implementation Template^] |=== == Listener Applications @@ -65,7 +65,7 @@ Accelerator assets include API specifications, implementation templates, custom [cols="70,30",width=100%] |=== | Salsify Channel Listener -| https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/rcg-salsify-channel-listener/[Implementation Template^] +| https://anypoint.mulesoft.com/exchange/org.mule.examples/rcg-salsify-channel-listener/[Implementation Template^] |=== == See Also diff --git a/consumer-goods/3.0/modules/ROOT/pages/index.adoc b/consumer-goods/3.0/modules/ROOT/pages/index.adoc index 42316576f..8d8701f75 100644 --- a/consumer-goods/3.0/modules/ROOT/pages/index.adoc +++ b/consumer-goods/3.0/modules/ROOT/pages/index.adoc @@ -7,19 +7,19 @@ MuleSoft Accelerator for Consumer Goods helps consumer goods companies integrate === Product and Account Integration with Hierarchies -The https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/mulesoft-accelerator-for-consumergoods/minor/{cg-version}/pages/Use%20case%201%20-%20Product%20and%20Account%20Integration%20with%20Hierarchies/[Product and Account Integration with Hierarchies^] use case surfaces relevant product, customer, demand planning, and pricing information from ERP and PIM systems and easily consolidate this information into Trade Promotion Management (TPM) platforms like Salesforce Consumer Goods Cloud for informed promotional planning. +The https://anypoint.mulesoft.com/exchange/org.mule.examples/mulesoft-accelerator-for-consumergoods/minor/{cg-version}/pages/Use%20case%201%20-%20Product%20and%20Account%20Integration%20with%20Hierarchies/[Product and Account Integration with Hierarchies^] use case surfaces relevant product, customer, demand planning, and pricing information from ERP and PIM systems and easily consolidate this information into Trade Promotion Management (TPM) platforms like Salesforce Consumer Goods Cloud for informed promotional planning. === Retail execution -The https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/mulesoft-accelerator-for-consumergoods/minor/{cg-version}/pages/Use%20case%202%20-%20Retail%20execution/[Retail Execution^] use case unlocks shelf data to enable perfect retail execution with pre-built assets. Access store audit data from image recognition software, like Trax, and smoothly integrate into Retail Execution platforms, such as Salesforce Consumer Goods Cloud, to monitor at shelf performance in one platform. +The https://anypoint.mulesoft.com/exchange/org.mule.examples/mulesoft-accelerator-for-consumergoods/minor/{cg-version}/pages/Use%20case%202%20-%20Retail%20execution/[Retail Execution^] use case unlocks shelf data to enable perfect retail execution with pre-built assets. Access store audit data from image recognition software, like Trax, and smoothly integrate into Retail Execution platforms, such as Salesforce Consumer Goods Cloud, to monitor at shelf performance in one platform. === Trade Promotion Effectiveness -The https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/mulesoft-accelerator-for-consumergoods/minor/{cg-version}/pages/Use%20case%203%20-%20Trade%20promotion%20effectiveness/[Trade Promotion Effectiveness^] use case allows you to visualize your promotions in one integrated platform with pre-built assets that integrate Business Intelligence Tools (BI Tools), such as CRM Analytics, into a TPM platform like Salesforce Consumer Goods Cloud. +The https://anypoint.mulesoft.com/exchange/org.mule.examples/mulesoft-accelerator-for-consumergoods/minor/{cg-version}/pages/Use%20case%203%20-%20Trade%20promotion%20effectiveness/[Trade Promotion Effectiveness^] use case allows you to visualize your promotions in one integrated platform with pre-built assets that integrate Business Intelligence Tools (BI Tools), such as CRM Analytics, into a TPM platform like Salesforce Consumer Goods Cloud. == See Also * xref:accelerators-home::getting-started.adoc[Getting Started Guide] * xref:prerequisites.adoc[Prerequisites] * xref:release-notes.adoc[Release Notes] -* https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/mulesoft-accelerator-for-consumergoods/[MuleSoft Accelerator for Consumer Goods on Exchange^] +* https://anypoint.mulesoft.com/exchange/org.mule.examples/mulesoft-accelerator-for-consumergoods/[MuleSoft Accelerator for Consumer Goods on Exchange^] diff --git a/consumer-goods/3.0/modules/ROOT/pages/release-notes.adoc b/consumer-goods/3.0/modules/ROOT/pages/release-notes.adoc index b9f1a4364..013fa905b 100644 --- a/consumer-goods/3.0/modules/ROOT/pages/release-notes.adoc +++ b/consumer-goods/3.0/modules/ROOT/pages/release-notes.adoc @@ -6,28 +6,28 @@ === New use case -This release includes the https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/mulesoft-accelerator-for-consumergoods/minor/{cg-version}/pages/Use%20case%201b%20-%20Trade%20promotion%20effectiveness/[Trade promotion effectiveness^] use case, which helps visualize your promotions in one integrated platform with pre-built assets that integrate Business Intelligence Tools (BI Tools), such as CRM Analytics, into a TPM platform like Salesforce Consumer Goods Cloud. +This release includes the https://anypoint.mulesoft.com/exchange/org.mule.examples/mulesoft-accelerator-for-consumergoods/minor/{cg-version}/pages/Use%20case%201b%20-%20Trade%20promotion%20effectiveness/[Trade promotion effectiveness^] use case, which helps visualize your promotions in one integrated platform with pre-built assets that integrate Business Intelligence Tools (BI Tools), such as CRM Analytics, into a TPM platform like Salesforce Consumer Goods Cloud. == v2.0 25 October 2022 === New use case -This release includes the https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/mulesoft-accelerator-for-consumergoods/minor/{cg-version}/pages/Use%20case%202%20-%20Retail%20execution/[Retail Execution^] use case, which unlocks shelf data to enable perfect retail execution with pre-built assets and lets retailers access store audit data from image recognition software, like Trax, and integrate smoothly into a Retail Execution platform, such as Salesforce Consumer Goods Cloud, to monitor at shelf performance in one platform. +This release includes the https://anypoint.mulesoft.com/exchange/org.mule.examples/mulesoft-accelerator-for-consumergoods/minor/{cg-version}/pages/Use%20case%202%20-%20Retail%20execution/[Retail Execution^] use case, which unlocks shelf data to enable perfect retail execution with pre-built assets and lets retailers access store audit data from image recognition software, like Trax, and integrate smoothly into a Retail Execution platform, such as Salesforce Consumer Goods Cloud, to monitor at shelf performance in one platform. == v1.1 17 September 2022 === Updates to the Product and Account Integration with Hierarchies -This release includes updates to the https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/mulesoft-accelerator-for-consumergoods/minor/{cg-version}/pages/Use%20case%201%20-%20Product%20and%20Account%20Integration%20with%20Hierarchies/[Product and Account Integration with Hierarchies^] use case, which synchronizes relevant product, customer, demand planning, and pricing information from ERP and PIM systems and easily consolidates this information into Trade Promotion Management (TPM) platforms, like Salesforce Consumer Goods Cloud, in real time for informed promotional planning. +This release includes updates to the https://anypoint.mulesoft.com/exchange/org.mule.examples/mulesoft-accelerator-for-consumergoods/minor/{cg-version}/pages/Use%20case%201%20-%20Product%20and%20Account%20Integration%20with%20Hierarchies/[Product and Account Integration with Hierarchies^] use case, which synchronizes relevant product, customer, demand planning, and pricing information from ERP and PIM systems and easily consolidates this information into Trade Promotion Management (TPM) platforms, like Salesforce Consumer Goods Cloud, in real time for informed promotional planning. == v1.0 18 July 2022 === New use case -This release includes the https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/mulesoft-accelerator-for-consumergoods/minor/{cg-version}/pages/Use%20case%201%20-%20Product%20and%20Account%20Integration%20with%20Hierarchies/[Product and Account Integration with Hierarchies^] use case, which synchronizes relevant product, customer, demand planning, and pricing information from ERP and PIM systems and easily consolidates this information into Trade Promotion Management (TPM) platforms, like Salesforce Consumer Goods Cloud, for informed promotional planning. +This release includes the https://anypoint.mulesoft.com/exchange/org.mule.examples/mulesoft-accelerator-for-consumergoods/minor/{cg-version}/pages/Use%20case%201%20-%20Product%20and%20Account%20Integration%20with%20Hierarchies/[Product and Account Integration with Hierarchies^] use case, which synchronizes relevant product, customer, demand planning, and pricing information from ERP and PIM systems and easily consolidates this information into Trade Promotion Management (TPM) platforms, like Salesforce Consumer Goods Cloud, for informed promotional planning. == See Also diff --git a/consumer-goods/3.0/modules/ROOT/pages/sap-s4hana-setup-guide.adoc b/consumer-goods/3.0/modules/ROOT/pages/sap-s4hana-setup-guide.adoc index 38b38a0d0..274cef101 100644 --- a/consumer-goods/3.0/modules/ROOT/pages/sap-s4hana-setup-guide.adoc +++ b/consumer-goods/3.0/modules/ROOT/pages/sap-s4hana-setup-guide.adoc @@ -8,25 +8,25 @@ To make the necessary configurations in S/4HANA: . Create a *Communication System* in the corresponding Fiori app. This communication system represents the external system that will consume the S/4HANA Cloud SOAP service. In this example, it's named "COM_0009_SOAP_OUT": + + -image:https://www.mulesoft.com/ext/solutions/draft/images/retail-sap-s4hana-setup-guide-01.png[retail-sap-s4hana-setup-guide-01.png,799] + +image:https://www.mulesoft.com/ext/solutions/images/retail-sap-s4hana-setup-guide-01.png[retail-sap-s4hana-setup-guide-01.png,799] + + . For the 'Business System' name, use the same name of the System ID. . In the 'Host Name' field, enter the hostname of the Mule application deployed on Cloudhub (if you don't have it yet, you can enter a mock URL and then modify it later): + + -image:https://www.mulesoft.com/ext/solutions/draft/images/retail-sap-s4hana-setup-guide-02.png[retail-sap-s4hana-setup-guide-02.png,799] + +image:https://www.mulesoft.com/ext/solutions/images/retail-sap-s4hana-setup-guide-02.png[retail-sap-s4hana-setup-guide-02.png,799] + + . Create a user that will be used to connect to the Cloud Hub app for sending product information in the outbound scenario (this is necessary even though the Mule application does not validate the user; we used any user for outbound): + + -image:https://www.mulesoft.com/ext/solutions/draft/images/retail-sap-s4hana-setup-guide-03.png[retail-sap-s4hana-setup-guide-03.png,799] + +image:https://www.mulesoft.com/ext/solutions/images/retail-sap-s4hana-setup-guide-03.png[retail-sap-s4hana-setup-guide-03.png,799] + + . Use the *Communication Arrangement* Fiori app to create a new Communication Arrangement: + + -image:https://www.mulesoft.com/ext/solutions/draft/images/retail-sap-s4hana-setup-guide-04.png[retail-sap-s4hana-setup-guide-04.png,799] + +image:https://www.mulesoft.com/ext/solutions/images/retail-sap-s4hana-setup-guide-04.png[retail-sap-s4hana-setup-guide-04.png,799] + + . Create a new *Communication Arrangement*, select the communication scenario "SAP_COM_0009", and then define a specific name for the arrangement, "SAP_COM_0009_SOAP". . In the *Communication System* field, select the Communication System created in the previous step: + + -image:https://www.mulesoft.com/ext/solutions/draft/images/retail-sap-s4hana-setup-guide-05.png[retail-sap-s4hana-setup-guide-05.png,799] + +image:https://www.mulesoft.com/ext/solutions/images/retail-sap-s4hana-setup-guide-05.png[retail-sap-s4hana-setup-guide-05.png,799] + + . For outbound communication, select the previously-created user and configure the *Product Master - Replicate from SAP S/4HANA Cloud to Client* and include the following settings. Make sure to note the Path (`/sap/bc/srt/scs/sap/productmdmbulkreplicaterequest`) because we will use this path to configure the Mule application SOAP endpoint: ** Set the Service status to *Active* @@ -34,11 +34,11 @@ image:https://www.mulesoft.com/ext/solutions/draft/images/retail-sap-s4hana-setu ** Replication model = I (Initial) ** The Output Mode = D (Direct). + + -image:https://www.mulesoft.com/ext/solutions/draft/images/retail-sap-s4hana-setup-guide-06.png[retail-sap-s4hana-setup-guide-06.png,799] + +image:https://www.mulesoft.com/ext/solutions/images/retail-sap-s4hana-setup-guide-06.png[retail-sap-s4hana-setup-guide-06.png,799] + + -image:https://www.mulesoft.com/ext/solutions/draft/images/retail-sap-s4hana-setup-guide-07.png[retail-sap-s4hana-setup-guide-07.png,799] + +image:https://www.mulesoft.com/ext/solutions/images/retail-sap-s4hana-setup-guide-07.png[retail-sap-s4hana-setup-guide-07.png,799] + + -image:https://www.mulesoft.com/ext/solutions/draft/images/retail-sap-s4hana-setup-guide-08.png[retail-sap-s4hana-setup-guide-08.png,799] + +image:https://www.mulesoft.com/ext/solutions/images/retail-sap-s4hana-setup-guide-08.png[retail-sap-s4hana-setup-guide-08.png,799] + + . Save it. All configurations at S/4HANA Cloud side are finished and you will be able to download the WSDL that contains the metadata to import into the S/4HANA Cloud SOAP Connector into the Mule application. @@ -48,38 +48,38 @@ The following example describes how to create a Mule application using the Outbo . Create a Mule project and add the appropriate connector from Exchange to the Mule Palette: + + -image:https://www.mulesoft.com/ext/solutions/draft/images/retail-sap-s4hana-setup-guide-09.png[retail-sap-s4hana-setup-guide-09.png,799] + +image:https://www.mulesoft.com/ext/solutions/images/retail-sap-s4hana-setup-guide-09.png[retail-sap-s4hana-setup-guide-09.png,799] + + . Add and configure the *Outbound Message Listener* to the canvas: + + -image:https://www.mulesoft.com/ext/solutions/draft/images/retail-sap-s4hana-setup-guide-10.png[retail-sap-s4hana-setup-guide-10.png,799] + +image:https://www.mulesoft.com/ext/solutions/images/retail-sap-s4hana-setup-guide-10.png[retail-sap-s4hana-setup-guide-10.png,799] + + . Add the corresponding WSDL path to the WSDL you downloaded from S/4HANA Cloud and create the HTTP listener configuration: + + -image:https://www.mulesoft.com/ext/solutions/draft/images/retail-sap-s4hana-setup-guide-11.png[retail-sap-s4hana-setup-guide-11.png,799] + +image:https://www.mulesoft.com/ext/solutions/images/retail-sap-s4hana-setup-guide-11.png[retail-sap-s4hana-setup-guide-11.png,799] + + -image:https://www.mulesoft.com/ext/solutions/draft/images/retail-sap-s4hana-setup-guide-12.png[retail-sap-s4hana-setup-guide-12.png,799] + +image:https://www.mulesoft.com/ext/solutions/images/retail-sap-s4hana-setup-guide-12.png[retail-sap-s4hana-setup-guide-12.png,799] + + _*Note*: we are using no authentication on the Mule Application, so we used the Insecure option for the Trust Store Configuration. In the Keystore configuration, we used a test Keystore, which is mandatory for HTTPS communication:_ + + -image:https://www.mulesoft.com/ext/solutions/draft/images/retail-sap-s4hana-setup-guide-13.png[retail-sap-s4hana-setup-guide-13.png,799] + +image:https://www.mulesoft.com/ext/solutions/images/retail-sap-s4hana-setup-guide-13.png[retail-sap-s4hana-setup-guide-13.png,799] + + . Select the Message type that the connector expects to receive from SAP (the connector reads the metadata from the WSDL we configured): + + -image:https://www.mulesoft.com/ext/solutions/draft/images/retail-sap-s4hana-setup-guide-14.png[retail-sap-s4hana-setup-guide-14.png,799] + +image:https://www.mulesoft.com/ext/solutions/images/retail-sap-s4hana-setup-guide-14.png[retail-sap-s4hana-setup-guide-14.png,799] + + . On the Responses tab, use the status Code "202" and the Reason-Phrase "Accepted" because we want to send the same status that S/4HANA Cloud will send if the service invocation results OK. No payload will be returned as a response--just the Status code and Reason-phrase: + + -image:https://www.mulesoft.com/ext/solutions/draft/images/retail-sap-s4hana-setup-guide-15.png[retail-sap-s4hana-setup-guide-15.png,799] + +image:https://www.mulesoft.com/ext/solutions/images/retail-sap-s4hana-setup-guide-15.png[retail-sap-s4hana-setup-guide-15.png,799] + + . Use a *Logger* component to log the inbound XML payload: + + -image:https://www.mulesoft.com/ext/solutions/draft/images/retail-sap-s4hana-setup-guide-16.png[retail-sap-s4hana-setup-guide-16.png,799] + +image:https://www.mulesoft.com/ext/solutions/images/retail-sap-s4hana-setup-guide-16.png[retail-sap-s4hana-setup-guide-16.png,799] + + _The Mule flow should look like the following:_ + + -image:https://www.mulesoft.com/ext/solutions/draft/images/retail-sap-s4hana-setup-guide-17.png[retail-sap-s4hana-setup-guide-17.png,399] + +image:https://www.mulesoft.com/ext/solutions/images/retail-sap-s4hana-setup-guide-17.png[retail-sap-s4hana-setup-guide-17.png,399] + + . Deploy the application to Cloudhub. You're now ready to test the scenario. @@ -89,35 +89,35 @@ To test the scenario: . Create the following. You only need to create a material in the corresponding Fiori app of S/4HANA Cloud: + + -image:https://www.mulesoft.com/ext/solutions/draft/images/retail-sap-s4hana-setup-guide-18.png[retail-sap-s4hana-setup-guide-18.png,599] + +image:https://www.mulesoft.com/ext/solutions/images/retail-sap-s4hana-setup-guide-18.png[retail-sap-s4hana-setup-guide-18.png,599] + + -image:https://www.mulesoft.com/ext/solutions/draft/images/retail-sap-s4hana-setup-guide-19.png[retail-sap-s4hana-setup-guide-19.png,799] + +image:https://www.mulesoft.com/ext/solutions/images/retail-sap-s4hana-setup-guide-19.png[retail-sap-s4hana-setup-guide-19.png,799] + + -image:https://www.mulesoft.com/ext/solutions/draft/images/retail-sap-s4hana-setup-guide-20.png[retail-sap-s4hana-setup-guide-20.png,799] + +image:https://www.mulesoft.com/ext/solutions/images/retail-sap-s4hana-setup-guide-20.png[retail-sap-s4hana-setup-guide-20.png,799] + + -image:https://www.mulesoft.com/ext/solutions/draft/images/retail-sap-s4hana-setup-guide-21.png[retail-sap-s4hana-setup-guide-21.png,799] + +image:https://www.mulesoft.com/ext/solutions/images/retail-sap-s4hana-setup-guide-21.png[retail-sap-s4hana-setup-guide-21.png,799] + + _After you save the new material, you should see the following confirmation in S/4HANA Cloud:_ + + -image:https://www.mulesoft.com/ext/solutions/draft/images/retail-sap-s4hana-setup-guide-22.png[retail-sap-s4hana-setup-guide-22.png,399] + +image:https://www.mulesoft.com/ext/solutions/images/retail-sap-s4hana-setup-guide-22.png[retail-sap-s4hana-setup-guide-22.png,399] + + _The following shows the XML message received at the Mule application at the Runtime Manager on Cloudhub:_ + + -image:https://www.mulesoft.com/ext/solutions/draft/images/retail-sap-s4hana-setup-guide-23.png[retail-sap-s4hana-setup-guide-23.png,799] + +image:https://www.mulesoft.com/ext/solutions/images/retail-sap-s4hana-setup-guide-23.png[retail-sap-s4hana-setup-guide-23.png,799] + + . See the sent message in the Message Dashboard Fiori Application: + + -image:https://www.mulesoft.com/ext/solutions/draft/images/retail-sap-s4hana-setup-guide-24.png[retail-sap-s4hana-setup-guide-24.png,799] + +image:https://www.mulesoft.com/ext/solutions/images/retail-sap-s4hana-setup-guide-24.png[retail-sap-s4hana-setup-guide-24.png,799] + + . Select the date: + + -image:https://www.mulesoft.com/ext/solutions/draft/images/retail-sap-s4hana-setup-guide-25.png[retail-sap-s4hana-setup-guide-25.png,399] + +image:https://www.mulesoft.com/ext/solutions/images/retail-sap-s4hana-setup-guide-25.png[retail-sap-s4hana-setup-guide-25.png,399] + + . Search under *CMD:Product Integration - /CMDPR → Product Replication to Client via Service - PRDREQ_OUT/00001 namespace*: + + -image:https://www.mulesoft.com/ext/solutions/draft/images/retail-sap-s4hana-setup-guide-26.png[retail-sap-s4hana-setup-guide-26.png,799] + +image:https://www.mulesoft.com/ext/solutions/images/retail-sap-s4hana-setup-guide-26.png[retail-sap-s4hana-setup-guide-26.png,799] + + -image:https://www.mulesoft.com/ext/solutions/draft/images/retail-sap-s4hana-setup-guide-27.png[retail-sap-s4hana-setup-guide-27.png,799] +image:https://www.mulesoft.com/ext/solutions/images/retail-sap-s4hana-setup-guide-27.png[retail-sap-s4hana-setup-guide-27.png,799] == S/4HANA customization guide diff --git a/consumer-goods/4.0/modules/ROOT/pages/cg-assets.adoc b/consumer-goods/4.0/modules/ROOT/pages/cg-assets.adoc index 425427e1e..365e1d7bb 100644 --- a/consumer-goods/4.0/modules/ROOT/pages/cg-assets.adoc +++ b/consumer-goods/4.0/modules/ROOT/pages/cg-assets.adoc @@ -7,36 +7,36 @@ Accelerator assets include API specifications, implementation templates, custom [cols="40,30,30",width=100%] |=== | MDM System API -| https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/rcg-mdm-sys-api-spec/[API Specification^] -| https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/rcg-mdm-sys-api/[Implementation Template^] +| https://anypoint.mulesoft.com/exchange/org.mule.examples/rcg-mdm-sys-api-spec/[API Specification^] +| https://anypoint.mulesoft.com/exchange/org.mule.examples/rcg-mdm-sys-api/[Implementation Template^] | SAP S/4HANA Products System API -| https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/rcg-saphana-products-sys-api-spec/[API Specification^] -| https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/rcg-saphana-products-sys-api/[Implementation Template^] +| https://anypoint.mulesoft.com/exchange/org.mule.examples/rcg-saphana-products-sys-api-spec/[API Specification^] +| https://anypoint.mulesoft.com/exchange/org.mule.examples/rcg-saphana-products-sys-api/[Implementation Template^] | RCG Salesforce Consumer Goods Cloud System API -| https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/rcg-salesforce-cgcloud-sys-api-spec/[API Specification^] -| https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/rcg-salesforce-cgcloud-sys-api/[Implementation Template^] +| https://anypoint.mulesoft.com/exchange/org.mule.examples/rcg-salesforce-cgcloud-sys-api-spec/[API Specification^] +| https://anypoint.mulesoft.com/exchange/org.mule.examples/rcg-salesforce-cgcloud-sys-api/[Implementation Template^] | SAP S/4HANA Customers System API -| https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/rcg-saphana-customers-sys-api-spec/[API Specification^] -| https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/rcg-saphana-customers-sys-api/[Implementation Template^] +| https://anypoint.mulesoft.com/exchange/org.mule.examples/rcg-saphana-customers-sys-api-spec/[API Specification^] +| https://anypoint.mulesoft.com/exchange/org.mule.examples/rcg-saphana-customers-sys-api/[Implementation Template^] | RCG Salsify Products System API -| https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/rcg-salsify-products-sys-api-spec/[API Specification^] -| https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/rcg-salsify-products-sys-api/[Implementation Template^] +| https://anypoint.mulesoft.com/exchange/org.mule.examples/rcg-salsify-products-sys-api-spec/[API Specification^] +| https://anypoint.mulesoft.com/exchange/org.mule.examples/rcg-salsify-products-sys-api/[Implementation Template^] | RCG Trax System API -| https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/rcg-trax-sys-api-spec/[API Specification^] -| https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/rcg-trax-sys-api/[Implementation Template^] +| https://anypoint.mulesoft.com/exchange/org.mule.examples/rcg-trax-sys-api-spec/[API Specification^] +| https://anypoint.mulesoft.com/exchange/org.mule.examples/rcg-trax-sys-api/[Implementation Template^] | RCG Hyperforce System API -| https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/rcg-hyperforce-sys-api-spec/[API Specification^] -| https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/rcg-hyperforce-sys-api/[Implementation Template^] +| https://anypoint.mulesoft.com/exchange/org.mule.examples/rcg-hyperforce-sys-api-spec/[API Specification^] +| https://anypoint.mulesoft.com/exchange/org.mule.examples/rcg-hyperforce-sys-api/[Implementation Template^] | RCG CRM Analytics System API -| https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/rcg-crma-sys-api-spec/[API Specification^] -| https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/rcg-crma-sys-api/[Implementation Template^] +| https://anypoint.mulesoft.com/exchange/org.mule.examples/rcg-crma-sys-api-spec/[API Specification^] +| https://anypoint.mulesoft.com/exchange/org.mule.examples/rcg-crma-sys-api/[Implementation Template^] |=== == Process APIs @@ -44,20 +44,20 @@ Accelerator assets include API specifications, implementation templates, custom [cols="40,30,30",width=100%] |=== | RCG Products Process API -| https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/rcg-products-prc-api-spec/[API Specification^] -| https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/rcg-products-prc-api/[Implementation Template^] +| https://anypoint.mulesoft.com/exchange/org.mule.examples/rcg-products-prc-api-spec/[API Specification^] +| https://anypoint.mulesoft.com/exchange/org.mule.examples/rcg-products-prc-api/[Implementation Template^] | RCG Customers Process API -| https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/rcg-customers-prc-api-spec/[API Specification^] -| https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/rcg-customers-prc-api/[Implementation Template^] +| https://anypoint.mulesoft.com/exchange/org.mule.examples/rcg-customers-prc-api-spec/[API Specification^] +| https://anypoint.mulesoft.com/exchange/org.mule.examples/rcg-customers-prc-api/[Implementation Template^] | RCG Store Audit Process API -| https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/rcg-store-audit-prc-api-spec[API Specification^] -| https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/rcg-store-audit-prc-api/[Implementation Template^] +| https://anypoint.mulesoft.com/exchange/org.mule.examples/rcg-store-audit-prc-api-spec[API Specification^] +| https://anypoint.mulesoft.com/exchange/org.mule.examples/rcg-store-audit-prc-api/[Implementation Template^] | RCG Data Normalisation Process API -| https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/rcg-data-normalization-prc-api-spec[API Specification^] -| https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/rcg-data-normalization-prc-api/[Implementation Template^] +| https://anypoint.mulesoft.com/exchange/org.mule.examples/rcg-data-normalization-prc-api-spec[API Specification^] +| https://anypoint.mulesoft.com/exchange/org.mule.examples/rcg-data-normalization-prc-api/[Implementation Template^] |=== == Listener Applications @@ -65,7 +65,7 @@ Accelerator assets include API specifications, implementation templates, custom [cols="70,30",width=100%] |=== | Salsify Channel Listener -| https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/rcg-salsify-channel-listener/[Implementation Template^] +| https://anypoint.mulesoft.com/exchange/org.mule.examples/rcg-salsify-channel-listener/[Implementation Template^] |=== == See Also diff --git a/consumer-goods/4.0/modules/ROOT/pages/index.adoc b/consumer-goods/4.0/modules/ROOT/pages/index.adoc index 77363ee20..5799e6578 100644 --- a/consumer-goods/4.0/modules/ROOT/pages/index.adoc +++ b/consumer-goods/4.0/modules/ROOT/pages/index.adoc @@ -7,19 +7,19 @@ MuleSoft Accelerator for Consumer Goods helps consumer goods companies integrate === Product and Account Integration with Hierarchies -The https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/mulesoft-accelerator-for-consumergoods/minor/{cg-version}/pages/Use%20case%201%20-%20Product%20and%20Account%20Integration%20with%20Hierarchies/[Product and Account Integration with Hierarchies^] use case surfaces relevant product, customer, demand planning, and pricing information from ERP and PIM systems and easily consolidate this information into Trade Promotion Management (TPM) platforms like Salesforce Consumer Goods Cloud for informed promotional planning. +The https://anypoint.mulesoft.com/exchange/org.mule.examples/mulesoft-accelerator-for-consumergoods/minor/{cg-version}/pages/Use%20case%201%20-%20Product%20and%20Account%20Integration%20with%20Hierarchies/[Product and Account Integration with Hierarchies^] use case surfaces relevant product, customer, demand planning, and pricing information from ERP and PIM systems and easily consolidate this information into Trade Promotion Management (TPM) platforms like Salesforce Consumer Goods Cloud for informed promotional planning. === Retail Execution -The https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/mulesoft-accelerator-for-consumergoods/minor/{cg-version}/pages/Use%20case%202%20-%20Retail%20execution/[Retail Execution^] use case unlocks shelf data to enable perfect retail execution with pre-built assets. Access store audit data from image recognition software, like Trax, and smoothly integrate into Retail Execution platforms, such as Salesforce Consumer Goods Cloud, to monitor at shelf performance in one platform. +The https://anypoint.mulesoft.com/exchange/org.mule.examples/mulesoft-accelerator-for-consumergoods/minor/{cg-version}/pages/Use%20case%202%20-%20Retail%20execution/[Retail Execution^] use case unlocks shelf data to enable perfect retail execution with pre-built assets. Access store audit data from image recognition software, like Trax, and smoothly integrate into Retail Execution platforms, such as Salesforce Consumer Goods Cloud, to monitor at shelf performance in one platform. === Trade Promotion Effectiveness -The https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/mulesoft-accelerator-for-consumergoods/minor/{cg-version}/pages/Use%20case%203%20-%20Trade%20promotion%20effectiveness/[Trade Promotion Effectiveness^] use case allows you to visualize your promotions in one integrated platform with pre-built assets that integrate Business Intelligence Tools (BI Tools), such as CRM Analytics, into a TPM platform like Salesforce Consumer Goods Cloud. +The https://anypoint.mulesoft.com/exchange/org.mule.examples/mulesoft-accelerator-for-consumergoods/minor/{cg-version}/pages/Use%20case%203%20-%20Trade%20promotion%20effectiveness/[Trade Promotion Effectiveness^] use case allows you to visualize your promotions in one integrated platform with pre-built assets that integrate Business Intelligence Tools (BI Tools), such as CRM Analytics, into a TPM platform like Salesforce Consumer Goods Cloud. == See Also * xref:accelerators-home::getting-started.adoc[Getting Started Guide] * xref:prerequisites.adoc[Prerequisites] * xref:release-notes.adoc[Release Notes] -* https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/mulesoft-accelerator-for-consumergoods/[MuleSoft Accelerator for Consumer Goods on Exchange^] +* https://anypoint.mulesoft.com/exchange/org.mule.examples/mulesoft-accelerator-for-consumergoods/[MuleSoft Accelerator for Consumer Goods on Exchange^] diff --git a/consumer-goods/4.0/modules/ROOT/pages/release-notes.adoc b/consumer-goods/4.0/modules/ROOT/pages/release-notes.adoc index e792bd9ac..5e146bd46 100644 --- a/consumer-goods/4.0/modules/ROOT/pages/release-notes.adoc +++ b/consumer-goods/4.0/modules/ROOT/pages/release-notes.adoc @@ -7,7 +7,7 @@ === Updates to the Trade Promotion Effectiveness Use Case -This release includes updates to the https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/mulesoft-accelerator-for-consumergoods/minor/{cg-version}/pages/Use%20case%203b%20-%20Trade%20promotion%20effectiveness/[Trade Promotion Effectiveness^] use case, which helps visualize your promotions in one integrated platform with pre-built assets that integrate Business Intelligence Tools (BI Tools), such as CRM Analytics, into a TPM platform like Salesforce Consumer Goods Cloud. +This release includes updates to the https://anypoint.mulesoft.com/exchange/org.mule.examples/mulesoft-accelerator-for-consumergoods/minor/{cg-version}/pages/Use%20case%203b%20-%20Trade%20promotion%20effectiveness/[Trade Promotion Effectiveness^] use case, which helps visualize your promotions in one integrated platform with pre-built assets that integrate Business Intelligence Tools (BI Tools), such as CRM Analytics, into a TPM platform like Salesforce Consumer Goods Cloud. @@ -16,28 +16,28 @@ This release includes updates to the https://anypoint.mulesoft.com/exchange/0b4c === New use case -This release includes the https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/mulesoft-accelerator-for-consumergoods/minor/{cg-version}/pages/Use%20case%203b%20-%20Trade%20promotion%20effectiveness/[Trade promotion effectiveness^] use case, which helps visualize your promotions in one integrated platform with pre-built assets that integrate Business Intelligence Tools (BI Tools), such as CRM Analytics, into a TPM platform like Salesforce Consumer Goods Cloud. +This release includes the https://anypoint.mulesoft.com/exchange/org.mule.examples/mulesoft-accelerator-for-consumergoods/minor/{cg-version}/pages/Use%20case%203b%20-%20Trade%20promotion%20effectiveness/[Trade promotion effectiveness^] use case, which helps visualize your promotions in one integrated platform with pre-built assets that integrate Business Intelligence Tools (BI Tools), such as CRM Analytics, into a TPM platform like Salesforce Consumer Goods Cloud. == v2.0 25 October 2022 === New use case -This release includes the https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/mulesoft-accelerator-for-consumergoods/minor/{cg-version}/pages/Use%20case%202%20-%20Retail%20execution/[Retail Execution^] use case, which unlocks shelf data to enable perfect retail execution with pre-built assets and lets retailers access store audit data from image recognition software, like Trax, and integrate smoothly into a Retail Execution platform, such as Salesforce Consumer Goods Cloud, to monitor at shelf performance in one platform. +This release includes the https://anypoint.mulesoft.com/exchange/org.mule.examples/mulesoft-accelerator-for-consumergoods/minor/{cg-version}/pages/Use%20case%202%20-%20Retail%20execution/[Retail Execution^] use case, which unlocks shelf data to enable perfect retail execution with pre-built assets and lets retailers access store audit data from image recognition software, like Trax, and integrate smoothly into a Retail Execution platform, such as Salesforce Consumer Goods Cloud, to monitor at shelf performance in one platform. == v1.1 17 September 2022 === Updates to the Product and Account Integration with Hierarchies -This release includes updates to the https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/mulesoft-accelerator-for-consumergoods/minor/{cg-version}/pages/Use%20case%201%20-%20Product%20and%20Account%20Integration%20with%20Hierarchies/[Product and Account Integration with Hierarchies^] use case, which synchronizes relevant product, customer, demand planning, and pricing information from ERP and PIM systems and easily consolidates this information into Trade Promotion Management (TPM) platforms, like Salesforce Consumer Goods Cloud, in real time for informed promotional planning. +This release includes updates to the https://anypoint.mulesoft.com/exchange/org.mule.examples/mulesoft-accelerator-for-consumergoods/minor/{cg-version}/pages/Use%20case%201%20-%20Product%20and%20Account%20Integration%20with%20Hierarchies/[Product and Account Integration with Hierarchies^] use case, which synchronizes relevant product, customer, demand planning, and pricing information from ERP and PIM systems and easily consolidates this information into Trade Promotion Management (TPM) platforms, like Salesforce Consumer Goods Cloud, in real time for informed promotional planning. == v1.0 18 July 2022 === New use case -This release includes the https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/mulesoft-accelerator-for-consumergoods/minor/{cg-version}/pages/Use%20case%201%20-%20Product%20and%20Account%20Integration%20with%20Hierarchies/[Product and Account Integration with Hierarchies^] use case, which synchronizes relevant product, customer, demand planning, and pricing information from ERP and PIM systems and easily consolidates this information into Trade Promotion Management (TPM) platforms, like Salesforce Consumer Goods Cloud, for informed promotional planning. +This release includes the https://anypoint.mulesoft.com/exchange/org.mule.examples/mulesoft-accelerator-for-consumergoods/minor/{cg-version}/pages/Use%20case%201%20-%20Product%20and%20Account%20Integration%20with%20Hierarchies/[Product and Account Integration with Hierarchies^] use case, which synchronizes relevant product, customer, demand planning, and pricing information from ERP and PIM systems and easily consolidates this information into Trade Promotion Management (TPM) platforms, like Salesforce Consumer Goods Cloud, for informed promotional planning. == See Also diff --git a/consumer-goods/4.0/modules/ROOT/pages/sap-s4hana-setup-guide.adoc b/consumer-goods/4.0/modules/ROOT/pages/sap-s4hana-setup-guide.adoc index 38b38a0d0..274cef101 100644 --- a/consumer-goods/4.0/modules/ROOT/pages/sap-s4hana-setup-guide.adoc +++ b/consumer-goods/4.0/modules/ROOT/pages/sap-s4hana-setup-guide.adoc @@ -8,25 +8,25 @@ To make the necessary configurations in S/4HANA: . Create a *Communication System* in the corresponding Fiori app. This communication system represents the external system that will consume the S/4HANA Cloud SOAP service. In this example, it's named "COM_0009_SOAP_OUT": + + -image:https://www.mulesoft.com/ext/solutions/draft/images/retail-sap-s4hana-setup-guide-01.png[retail-sap-s4hana-setup-guide-01.png,799] + +image:https://www.mulesoft.com/ext/solutions/images/retail-sap-s4hana-setup-guide-01.png[retail-sap-s4hana-setup-guide-01.png,799] + + . For the 'Business System' name, use the same name of the System ID. . In the 'Host Name' field, enter the hostname of the Mule application deployed on Cloudhub (if you don't have it yet, you can enter a mock URL and then modify it later): + + -image:https://www.mulesoft.com/ext/solutions/draft/images/retail-sap-s4hana-setup-guide-02.png[retail-sap-s4hana-setup-guide-02.png,799] + +image:https://www.mulesoft.com/ext/solutions/images/retail-sap-s4hana-setup-guide-02.png[retail-sap-s4hana-setup-guide-02.png,799] + + . Create a user that will be used to connect to the Cloud Hub app for sending product information in the outbound scenario (this is necessary even though the Mule application does not validate the user; we used any user for outbound): + + -image:https://www.mulesoft.com/ext/solutions/draft/images/retail-sap-s4hana-setup-guide-03.png[retail-sap-s4hana-setup-guide-03.png,799] + +image:https://www.mulesoft.com/ext/solutions/images/retail-sap-s4hana-setup-guide-03.png[retail-sap-s4hana-setup-guide-03.png,799] + + . Use the *Communication Arrangement* Fiori app to create a new Communication Arrangement: + + -image:https://www.mulesoft.com/ext/solutions/draft/images/retail-sap-s4hana-setup-guide-04.png[retail-sap-s4hana-setup-guide-04.png,799] + +image:https://www.mulesoft.com/ext/solutions/images/retail-sap-s4hana-setup-guide-04.png[retail-sap-s4hana-setup-guide-04.png,799] + + . Create a new *Communication Arrangement*, select the communication scenario "SAP_COM_0009", and then define a specific name for the arrangement, "SAP_COM_0009_SOAP". . In the *Communication System* field, select the Communication System created in the previous step: + + -image:https://www.mulesoft.com/ext/solutions/draft/images/retail-sap-s4hana-setup-guide-05.png[retail-sap-s4hana-setup-guide-05.png,799] + +image:https://www.mulesoft.com/ext/solutions/images/retail-sap-s4hana-setup-guide-05.png[retail-sap-s4hana-setup-guide-05.png,799] + + . For outbound communication, select the previously-created user and configure the *Product Master - Replicate from SAP S/4HANA Cloud to Client* and include the following settings. Make sure to note the Path (`/sap/bc/srt/scs/sap/productmdmbulkreplicaterequest`) because we will use this path to configure the Mule application SOAP endpoint: ** Set the Service status to *Active* @@ -34,11 +34,11 @@ image:https://www.mulesoft.com/ext/solutions/draft/images/retail-sap-s4hana-setu ** Replication model = I (Initial) ** The Output Mode = D (Direct). + + -image:https://www.mulesoft.com/ext/solutions/draft/images/retail-sap-s4hana-setup-guide-06.png[retail-sap-s4hana-setup-guide-06.png,799] + +image:https://www.mulesoft.com/ext/solutions/images/retail-sap-s4hana-setup-guide-06.png[retail-sap-s4hana-setup-guide-06.png,799] + + -image:https://www.mulesoft.com/ext/solutions/draft/images/retail-sap-s4hana-setup-guide-07.png[retail-sap-s4hana-setup-guide-07.png,799] + +image:https://www.mulesoft.com/ext/solutions/images/retail-sap-s4hana-setup-guide-07.png[retail-sap-s4hana-setup-guide-07.png,799] + + -image:https://www.mulesoft.com/ext/solutions/draft/images/retail-sap-s4hana-setup-guide-08.png[retail-sap-s4hana-setup-guide-08.png,799] + +image:https://www.mulesoft.com/ext/solutions/images/retail-sap-s4hana-setup-guide-08.png[retail-sap-s4hana-setup-guide-08.png,799] + + . Save it. All configurations at S/4HANA Cloud side are finished and you will be able to download the WSDL that contains the metadata to import into the S/4HANA Cloud SOAP Connector into the Mule application. @@ -48,38 +48,38 @@ The following example describes how to create a Mule application using the Outbo . Create a Mule project and add the appropriate connector from Exchange to the Mule Palette: + + -image:https://www.mulesoft.com/ext/solutions/draft/images/retail-sap-s4hana-setup-guide-09.png[retail-sap-s4hana-setup-guide-09.png,799] + +image:https://www.mulesoft.com/ext/solutions/images/retail-sap-s4hana-setup-guide-09.png[retail-sap-s4hana-setup-guide-09.png,799] + + . Add and configure the *Outbound Message Listener* to the canvas: + + -image:https://www.mulesoft.com/ext/solutions/draft/images/retail-sap-s4hana-setup-guide-10.png[retail-sap-s4hana-setup-guide-10.png,799] + +image:https://www.mulesoft.com/ext/solutions/images/retail-sap-s4hana-setup-guide-10.png[retail-sap-s4hana-setup-guide-10.png,799] + + . Add the corresponding WSDL path to the WSDL you downloaded from S/4HANA Cloud and create the HTTP listener configuration: + + -image:https://www.mulesoft.com/ext/solutions/draft/images/retail-sap-s4hana-setup-guide-11.png[retail-sap-s4hana-setup-guide-11.png,799] + +image:https://www.mulesoft.com/ext/solutions/images/retail-sap-s4hana-setup-guide-11.png[retail-sap-s4hana-setup-guide-11.png,799] + + -image:https://www.mulesoft.com/ext/solutions/draft/images/retail-sap-s4hana-setup-guide-12.png[retail-sap-s4hana-setup-guide-12.png,799] + +image:https://www.mulesoft.com/ext/solutions/images/retail-sap-s4hana-setup-guide-12.png[retail-sap-s4hana-setup-guide-12.png,799] + + _*Note*: we are using no authentication on the Mule Application, so we used the Insecure option for the Trust Store Configuration. In the Keystore configuration, we used a test Keystore, which is mandatory for HTTPS communication:_ + + -image:https://www.mulesoft.com/ext/solutions/draft/images/retail-sap-s4hana-setup-guide-13.png[retail-sap-s4hana-setup-guide-13.png,799] + +image:https://www.mulesoft.com/ext/solutions/images/retail-sap-s4hana-setup-guide-13.png[retail-sap-s4hana-setup-guide-13.png,799] + + . Select the Message type that the connector expects to receive from SAP (the connector reads the metadata from the WSDL we configured): + + -image:https://www.mulesoft.com/ext/solutions/draft/images/retail-sap-s4hana-setup-guide-14.png[retail-sap-s4hana-setup-guide-14.png,799] + +image:https://www.mulesoft.com/ext/solutions/images/retail-sap-s4hana-setup-guide-14.png[retail-sap-s4hana-setup-guide-14.png,799] + + . On the Responses tab, use the status Code "202" and the Reason-Phrase "Accepted" because we want to send the same status that S/4HANA Cloud will send if the service invocation results OK. No payload will be returned as a response--just the Status code and Reason-phrase: + + -image:https://www.mulesoft.com/ext/solutions/draft/images/retail-sap-s4hana-setup-guide-15.png[retail-sap-s4hana-setup-guide-15.png,799] + +image:https://www.mulesoft.com/ext/solutions/images/retail-sap-s4hana-setup-guide-15.png[retail-sap-s4hana-setup-guide-15.png,799] + + . Use a *Logger* component to log the inbound XML payload: + + -image:https://www.mulesoft.com/ext/solutions/draft/images/retail-sap-s4hana-setup-guide-16.png[retail-sap-s4hana-setup-guide-16.png,799] + +image:https://www.mulesoft.com/ext/solutions/images/retail-sap-s4hana-setup-guide-16.png[retail-sap-s4hana-setup-guide-16.png,799] + + _The Mule flow should look like the following:_ + + -image:https://www.mulesoft.com/ext/solutions/draft/images/retail-sap-s4hana-setup-guide-17.png[retail-sap-s4hana-setup-guide-17.png,399] + +image:https://www.mulesoft.com/ext/solutions/images/retail-sap-s4hana-setup-guide-17.png[retail-sap-s4hana-setup-guide-17.png,399] + + . Deploy the application to Cloudhub. You're now ready to test the scenario. @@ -89,35 +89,35 @@ To test the scenario: . Create the following. You only need to create a material in the corresponding Fiori app of S/4HANA Cloud: + + -image:https://www.mulesoft.com/ext/solutions/draft/images/retail-sap-s4hana-setup-guide-18.png[retail-sap-s4hana-setup-guide-18.png,599] + +image:https://www.mulesoft.com/ext/solutions/images/retail-sap-s4hana-setup-guide-18.png[retail-sap-s4hana-setup-guide-18.png,599] + + -image:https://www.mulesoft.com/ext/solutions/draft/images/retail-sap-s4hana-setup-guide-19.png[retail-sap-s4hana-setup-guide-19.png,799] + +image:https://www.mulesoft.com/ext/solutions/images/retail-sap-s4hana-setup-guide-19.png[retail-sap-s4hana-setup-guide-19.png,799] + + -image:https://www.mulesoft.com/ext/solutions/draft/images/retail-sap-s4hana-setup-guide-20.png[retail-sap-s4hana-setup-guide-20.png,799] + +image:https://www.mulesoft.com/ext/solutions/images/retail-sap-s4hana-setup-guide-20.png[retail-sap-s4hana-setup-guide-20.png,799] + + -image:https://www.mulesoft.com/ext/solutions/draft/images/retail-sap-s4hana-setup-guide-21.png[retail-sap-s4hana-setup-guide-21.png,799] + +image:https://www.mulesoft.com/ext/solutions/images/retail-sap-s4hana-setup-guide-21.png[retail-sap-s4hana-setup-guide-21.png,799] + + _After you save the new material, you should see the following confirmation in S/4HANA Cloud:_ + + -image:https://www.mulesoft.com/ext/solutions/draft/images/retail-sap-s4hana-setup-guide-22.png[retail-sap-s4hana-setup-guide-22.png,399] + +image:https://www.mulesoft.com/ext/solutions/images/retail-sap-s4hana-setup-guide-22.png[retail-sap-s4hana-setup-guide-22.png,399] + + _The following shows the XML message received at the Mule application at the Runtime Manager on Cloudhub:_ + + -image:https://www.mulesoft.com/ext/solutions/draft/images/retail-sap-s4hana-setup-guide-23.png[retail-sap-s4hana-setup-guide-23.png,799] + +image:https://www.mulesoft.com/ext/solutions/images/retail-sap-s4hana-setup-guide-23.png[retail-sap-s4hana-setup-guide-23.png,799] + + . See the sent message in the Message Dashboard Fiori Application: + + -image:https://www.mulesoft.com/ext/solutions/draft/images/retail-sap-s4hana-setup-guide-24.png[retail-sap-s4hana-setup-guide-24.png,799] + +image:https://www.mulesoft.com/ext/solutions/images/retail-sap-s4hana-setup-guide-24.png[retail-sap-s4hana-setup-guide-24.png,799] + + . Select the date: + + -image:https://www.mulesoft.com/ext/solutions/draft/images/retail-sap-s4hana-setup-guide-25.png[retail-sap-s4hana-setup-guide-25.png,399] + +image:https://www.mulesoft.com/ext/solutions/images/retail-sap-s4hana-setup-guide-25.png[retail-sap-s4hana-setup-guide-25.png,399] + + . Search under *CMD:Product Integration - /CMDPR → Product Replication to Client via Service - PRDREQ_OUT/00001 namespace*: + + -image:https://www.mulesoft.com/ext/solutions/draft/images/retail-sap-s4hana-setup-guide-26.png[retail-sap-s4hana-setup-guide-26.png,799] + +image:https://www.mulesoft.com/ext/solutions/images/retail-sap-s4hana-setup-guide-26.png[retail-sap-s4hana-setup-guide-26.png,799] + + -image:https://www.mulesoft.com/ext/solutions/draft/images/retail-sap-s4hana-setup-guide-27.png[retail-sap-s4hana-setup-guide-27.png,799] +image:https://www.mulesoft.com/ext/solutions/images/retail-sap-s4hana-setup-guide-27.png[retail-sap-s4hana-setup-guide-27.png,799] == S/4HANA customization guide diff --git a/consumer-goods/5.0/modules/ROOT/pages/cg-assets.adoc b/consumer-goods/5.0/modules/ROOT/pages/cg-assets.adoc index 95ca42ee5..382d9dbc3 100644 --- a/consumer-goods/5.0/modules/ROOT/pages/cg-assets.adoc +++ b/consumer-goods/5.0/modules/ROOT/pages/cg-assets.adoc @@ -7,40 +7,40 @@ Accelerator assets include API specifications, implementation templates, custom [cols="40,30,30",width=100%] |=== | MDM System API -| https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/rcg-mdm-sys-api-spec/[API Specification^] -| https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/rcg-mdm-sys-api/[Implementation Template^] +| https://anypoint.mulesoft.com/exchange/org.mule.examples/rcg-mdm-sys-api-spec/[API Specification^] +| https://anypoint.mulesoft.com/exchange/org.mule.examples/rcg-mdm-sys-api/[Implementation Template^] | SAP S/4HANA Products System API -| https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/rcg-saphana-products-sys-api-spec/[API Specification^] -| https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/rcg-saphana-products-sys-api/[Implementation Template^] +| https://anypoint.mulesoft.com/exchange/org.mule.examples/rcg-saphana-products-sys-api-spec/[API Specification^] +| https://anypoint.mulesoft.com/exchange/org.mule.examples/rcg-saphana-products-sys-api/[Implementation Template^] | RCG Salesforce Consumer Goods Cloud System API -| https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/rcg-salesforce-cgcloud-sys-api-spec/[API Specification^] -| https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/rcg-salesforce-cgcloud-sys-api/[Implementation Template^] +| https://anypoint.mulesoft.com/exchange/org.mule.examples/rcg-salesforce-cgcloud-sys-api-spec/[API Specification^] +| https://anypoint.mulesoft.com/exchange/org.mule.examples/rcg-salesforce-cgcloud-sys-api/[Implementation Template^] | SAP S/4HANA Customers System API -| https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/rcg-saphana-customers-sys-api-spec/[API Specification^] -| https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/rcg-saphana-customers-sys-api/[Implementation Template^] +| https://anypoint.mulesoft.com/exchange/org.mule.examples/rcg-saphana-customers-sys-api-spec/[API Specification^] +| https://anypoint.mulesoft.com/exchange/org.mule.examples/rcg-saphana-customers-sys-api/[Implementation Template^] | RCG Salsify Products System API -| https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/rcg-salsify-products-sys-api-spec/[API Specification^] -| https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/rcg-salsify-products-sys-api/[Implementation Template^] +| https://anypoint.mulesoft.com/exchange/org.mule.examples/rcg-salsify-products-sys-api-spec/[API Specification^] +| https://anypoint.mulesoft.com/exchange/org.mule.examples/rcg-salsify-products-sys-api/[Implementation Template^] | RCG Trax System API -| https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/rcg-trax-sys-api-spec/[API Specification^] -| https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/rcg-trax-sys-api/[Implementation Template^] +| https://anypoint.mulesoft.com/exchange/org.mule.examples/rcg-trax-sys-api-spec/[API Specification^] +| https://anypoint.mulesoft.com/exchange/org.mule.examples/rcg-trax-sys-api/[Implementation Template^] | RCG Hyperforce System API -| https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/rcg-hyperforce-sys-api-spec/[API Specification^] -| https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/rcg-hyperforce-sys-api/[Implementation Template^] +| https://anypoint.mulesoft.com/exchange/org.mule.examples/rcg-hyperforce-sys-api-spec/[API Specification^] +| https://anypoint.mulesoft.com/exchange/org.mule.examples/rcg-hyperforce-sys-api/[Implementation Template^] | RCG CRM Analytics System API -| https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/rcg-crma-sys-api-spec/[API Specification^] -| https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/rcg-crma-sys-api/[Implementation Template^] +| https://anypoint.mulesoft.com/exchange/org.mule.examples/rcg-crma-sys-api-spec/[API Specification^] +| https://anypoint.mulesoft.com/exchange/org.mule.examples/rcg-crma-sys-api/[Implementation Template^] | RCG Salesforce Volume Management System API -| https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/rcg-salesforce-volume-mgmt-sys-api-spec/[API Specification^] -| https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/rcg-sfdc-volume-mgmt-sys-api/[Implementation Template^] +| https://anypoint.mulesoft.com/exchange/org.mule.examples/rcg-salesforce-volume-mgmt-sys-api-spec/[API Specification^] +| https://anypoint.mulesoft.com/exchange/org.mule.examples/rcg-sfdc-volume-mgmt-sys-api/[Implementation Template^] |=== @@ -49,24 +49,24 @@ Accelerator assets include API specifications, implementation templates, custom [cols="40,30,30",width=100%] |=== | RCG Products Process API -| https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/rcg-products-prc-api-spec/[API Specification^] -| https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/rcg-products-prc-api/[Implementation Template^] +| https://anypoint.mulesoft.com/exchange/org.mule.examples/rcg-products-prc-api-spec/[API Specification^] +| https://anypoint.mulesoft.com/exchange/org.mule.examples/rcg-products-prc-api/[Implementation Template^] | RCG Customers Process API -| https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/rcg-customers-prc-api-spec/[API Specification^] -| https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/rcg-customers-prc-api/[Implementation Template^] +| https://anypoint.mulesoft.com/exchange/org.mule.examples/rcg-customers-prc-api-spec/[API Specification^] +| https://anypoint.mulesoft.com/exchange/org.mule.examples/rcg-customers-prc-api/[Implementation Template^] | RCG Store Audit Process API -| https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/rcg-store-audit-prc-api-spec[API Specification^] -| https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/rcg-store-audit-prc-api/[Implementation Template^] +| https://anypoint.mulesoft.com/exchange/org.mule.examples/rcg-store-audit-prc-api-spec[API Specification^] +| https://anypoint.mulesoft.com/exchange/org.mule.examples/rcg-store-audit-prc-api/[Implementation Template^] | RCG Data Normalisation Process API -| https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/rcg-data-normalization-prc-api-spec[API Specification^] -| https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/rcg-data-normalization-prc-api/[Implementation Template^] +| https://anypoint.mulesoft.com/exchange/org.mule.examples/rcg-data-normalization-prc-api-spec[API Specification^] +| https://anypoint.mulesoft.com/exchange/org.mule.examples/rcg-data-normalization-prc-api/[Implementation Template^] | RCG Baseline Prediction Process API -| https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/rcg-baseline-prediction-prc-api-spec[API Specification^] -| https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/rcg-baseline-prediction-prc-api/[Implementation Template^] +| https://anypoint.mulesoft.com/exchange/org.mule.examples/rcg-baseline-prediction-prc-api-spec[API Specification^] +| https://anypoint.mulesoft.com/exchange/org.mule.examples/rcg-baseline-prediction-prc-api/[Implementation Template^] |=== == Listener Applications @@ -74,7 +74,7 @@ Accelerator assets include API specifications, implementation templates, custom [cols="70,30",width=100%] |=== | Salsify Channel Listener -| https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/rcg-salsify-channel-listener/[Implementation Template^] +| https://anypoint.mulesoft.com/exchange/org.mule.examples/rcg-salsify-channel-listener/[Implementation Template^] |=== == See Also diff --git a/consumer-goods/5.0/modules/ROOT/pages/index.adoc b/consumer-goods/5.0/modules/ROOT/pages/index.adoc index c08d2c90c..f7a28fdd2 100644 --- a/consumer-goods/5.0/modules/ROOT/pages/index.adoc +++ b/consumer-goods/5.0/modules/ROOT/pages/index.adoc @@ -7,23 +7,23 @@ MuleSoft Accelerator for Consumer Goods helps consumer goods companies integrate === Product and Account Integration with Hierarchies -The https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/mulesoft-accelerator-for-consumergoods/minor/{cg-version}/pages/Use%20case%201%20-%20Product%20and%20Account%20Integration%20with%20Hierarchies/[Product and Account Integration with Hierarchies^] use case surfaces relevant product, customer, demand planning, and pricing information from ERP and PIM systems and easily consolidate this information into Trade Promotion Management (TPM) platforms like Salesforce Consumer Goods Cloud for informed promotional planning. +The https://anypoint.mulesoft.com/exchange/org.mule.examples/mulesoft-accelerator-for-consumergoods/minor/{cg-version}/pages/Use%20case%201%20-%20Product%20and%20Account%20Integration%20with%20Hierarchies/[Product and Account Integration with Hierarchies^] use case surfaces relevant product, customer, demand planning, and pricing information from ERP and PIM systems and easily consolidate this information into Trade Promotion Management (TPM) platforms like Salesforce Consumer Goods Cloud for informed promotional planning. === Retail Execution -The https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/mulesoft-accelerator-for-consumergoods/minor/{cg-version}/pages/Use%20case%202%20-%20Retail%20execution/[Retail Execution^] use case unlocks shelf data to enable perfect retail execution with pre-built assets. Access store audit data from image recognition software, like Trax, and smoothly integrate into Retail Execution platforms, such as Salesforce Consumer Goods Cloud, to monitor at shelf performance in one platform. +The https://anypoint.mulesoft.com/exchange/org.mule.examples/mulesoft-accelerator-for-consumergoods/minor/{cg-version}/pages/Use%20case%202%20-%20Retail%20execution/[Retail Execution^] use case unlocks shelf data to enable perfect retail execution with pre-built assets. Access store audit data from image recognition software, like Trax, and smoothly integrate into Retail Execution platforms, such as Salesforce Consumer Goods Cloud, to monitor at shelf performance in one platform. === Trade Promotion Effectiveness -The https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/mulesoft-accelerator-for-consumergoods/minor/{cg-version}/pages/Use%20case%203%20-%20Trade%20promotion%20effectiveness/[Trade Promotion Effectiveness^] use case allows you to visualize your promotions in one integrated platform with pre-built assets that integrate Business Intelligence Tools (BI Tools), such as CRM Analytics, into a TPM platform like Salesforce Consumer Goods Cloud. +The https://anypoint.mulesoft.com/exchange/org.mule.examples/mulesoft-accelerator-for-consumergoods/minor/{cg-version}/pages/Use%20case%203%20-%20Trade%20promotion%20effectiveness/[Trade Promotion Effectiveness^] use case allows you to visualize your promotions in one integrated platform with pre-built assets that integrate Business Intelligence Tools (BI Tools), such as CRM Analytics, into a TPM platform like Salesforce Consumer Goods Cloud. === Trade Promotion Optimization -The https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/mulesoft-accelerator-for-consumergoods/minor/{cg-version}/pages/Use%20case%204%20-%20Trade%20promotion%20optimization/[Trade Promotion Optimization^] use case allows you to visualize your promotions in one integrated platform with pre-built assets that integrate Business Intelligence Tools (BI Tools), such as CRM Analytics, into a TPM platform like Salesforce Consumer Goods Cloud. +The https://anypoint.mulesoft.com/exchange/org.mule.examples/mulesoft-accelerator-for-consumergoods/minor/{cg-version}/pages/Use%20case%204%20-%20Trade%20promotion%20optimization/[Trade Promotion Optimization^] use case allows you to visualize your promotions in one integrated platform with pre-built assets that integrate Business Intelligence Tools (BI Tools), such as CRM Analytics, into a TPM platform like Salesforce Consumer Goods Cloud. == See Also * xref:accelerators-home::getting-started.adoc[Getting Started Guide] * xref:prerequisites.adoc[Prerequisites] * xref:release-notes.adoc[Release Notes] -* https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/mulesoft-accelerator-for-consumergoods/[MuleSoft Accelerator for Consumer Goods on Exchange^] +* https://anypoint.mulesoft.com/exchange/org.mule.examples/mulesoft-accelerator-for-consumergoods/[MuleSoft Accelerator for Consumer Goods on Exchange^] diff --git a/consumer-goods/5.0/modules/ROOT/pages/release-notes.adoc b/consumer-goods/5.0/modules/ROOT/pages/release-notes.adoc index c52911625..fd6201826 100644 --- a/consumer-goods/5.0/modules/ROOT/pages/release-notes.adoc +++ b/consumer-goods/5.0/modules/ROOT/pages/release-notes.adoc @@ -6,46 +6,46 @@ === New use case -This release introduces the https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/mulesoft-accelerator-for-consumergoods/minor/{cg-version}/pages/Use%20case%204%20-%20Trade%20promotion%20optimization/[Trade Promotion Optimization^] use case, which integrates predictive baseline data from CRM Analytics into Hyperforce to optimize trade promotions. Optimizing trade promotions enables data-driven insights to maximize promotion effectiveness, aids in designing targeted promotions that align with consumer behavior, and facilitates accurate ROI calculations by assessing market risks. +This release introduces the https://anypoint.mulesoft.com/exchange/org.mule.examples/mulesoft-accelerator-for-consumergoods/minor/{cg-version}/pages/Use%20case%204%20-%20Trade%20promotion%20optimization/[Trade Promotion Optimization^] use case, which integrates predictive baseline data from CRM Analytics into Hyperforce to optimize trade promotions. Optimizing trade promotions enables data-driven insights to maximize promotion effectiveness, aids in designing targeted promotions that align with consumer behavior, and facilitates accurate ROI calculations by assessing market risks. === Updates to the Trade Promotion Effectiveness Use Case -This release updates the https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/mulesoft-accelerator-for-consumergoods/minor/{cg-version}/pages/Use%20case%203b%20-%20Trade%20promotion%20effectiveness/[Trade Promotion Effectiveness^] use case with full and incremental load, which helps visualize your promotions in one integrated platform with pre-built assets that integrate Business Intelligence Tools (BI Tools), such as CRM Analytics, into a TPM platform like Salesforce Consumer Goods Cloud. +This release updates the https://anypoint.mulesoft.com/exchange/org.mule.examples/mulesoft-accelerator-for-consumergoods/minor/{cg-version}/pages/Use%20case%203b%20-%20Trade%20promotion%20effectiveness/[Trade Promotion Effectiveness^] use case with full and incremental load, which helps visualize your promotions in one integrated platform with pre-built assets that integrate Business Intelligence Tools (BI Tools), such as CRM Analytics, into a TPM platform like Salesforce Consumer Goods Cloud. == 4.0 *June 2, 2023* === Updates to the Trade Promotion Effectiveness Use Case -This release includes updates to the https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/mulesoft-accelerator-for-consumergoods/minor/{cg-version}/pages/Use%20case%203b%20-%20Trade%20promotion%20effectiveness/[Trade Promotion Effectiveness^] use case, which helps visualize your promotions in one integrated platform with pre-built assets that integrate Business Intelligence Tools (BI Tools), such as CRM Analytics, into a TPM platform like Salesforce Consumer Goods Cloud. +This release includes updates to the https://anypoint.mulesoft.com/exchange/org.mule.examples/mulesoft-accelerator-for-consumergoods/minor/{cg-version}/pages/Use%20case%203b%20-%20Trade%20promotion%20effectiveness/[Trade Promotion Effectiveness^] use case, which helps visualize your promotions in one integrated platform with pre-built assets that integrate Business Intelligence Tools (BI Tools), such as CRM Analytics, into a TPM platform like Salesforce Consumer Goods Cloud. == v3.0 30 January 2023 === New use case -This release includes the https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/mulesoft-accelerator-for-consumergoods/minor/{cg-version}/pages/Use%20case%203b%20-%20Trade%20promotion%20effectiveness/[Trade promotion effectiveness^] use case, which helps visualize your promotions in one integrated platform with pre-built assets that integrate Business Intelligence Tools (BI Tools), such as CRM Analytics, into a TPM platform like Salesforce Consumer Goods Cloud. +This release includes the https://anypoint.mulesoft.com/exchange/org.mule.examples/mulesoft-accelerator-for-consumergoods/minor/{cg-version}/pages/Use%20case%203b%20-%20Trade%20promotion%20effectiveness/[Trade promotion effectiveness^] use case, which helps visualize your promotions in one integrated platform with pre-built assets that integrate Business Intelligence Tools (BI Tools), such as CRM Analytics, into a TPM platform like Salesforce Consumer Goods Cloud. == v2.0 25 October 2022 === New use case -This release includes the https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/mulesoft-accelerator-for-consumergoods/minor/{cg-version}/pages/Use%20case%202%20-%20Retail%20execution/[Retail Execution^] use case, which unlocks shelf data to enable perfect retail execution with pre-built assets and lets retailers access store audit data from image recognition software, like Trax, and integrate smoothly into a Retail Execution platform, such as Salesforce Consumer Goods Cloud, to monitor at shelf performance in one platform. +This release includes the https://anypoint.mulesoft.com/exchange/org.mule.examples/mulesoft-accelerator-for-consumergoods/minor/{cg-version}/pages/Use%20case%202%20-%20Retail%20execution/[Retail Execution^] use case, which unlocks shelf data to enable perfect retail execution with pre-built assets and lets retailers access store audit data from image recognition software, like Trax, and integrate smoothly into a Retail Execution platform, such as Salesforce Consumer Goods Cloud, to monitor at shelf performance in one platform. == v1.1 17 September 2022 === Updates to the Product and Account Integration with Hierarchies -This release includes updates to the https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/mulesoft-accelerator-for-consumergoods/minor/{cg-version}/pages/Use%20case%201%20-%20Product%20and%20Account%20Integration%20with%20Hierarchies/[Product and Account Integration with Hierarchies^] use case, which synchronizes relevant product, customer, demand planning, and pricing information from ERP and PIM systems and easily consolidates this information into Trade Promotion Management (TPM) platforms, like Salesforce Consumer Goods Cloud, in real time for informed promotional planning. +This release includes updates to the https://anypoint.mulesoft.com/exchange/org.mule.examples/mulesoft-accelerator-for-consumergoods/minor/{cg-version}/pages/Use%20case%201%20-%20Product%20and%20Account%20Integration%20with%20Hierarchies/[Product and Account Integration with Hierarchies^] use case, which synchronizes relevant product, customer, demand planning, and pricing information from ERP and PIM systems and easily consolidates this information into Trade Promotion Management (TPM) platforms, like Salesforce Consumer Goods Cloud, in real time for informed promotional planning. == v1.0 18 July 2022 === New use case -This release includes the https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/mulesoft-accelerator-for-consumergoods/minor/{cg-version}/pages/Use%20case%201%20-%20Product%20and%20Account%20Integration%20with%20Hierarchies/[Product and Account Integration with Hierarchies^] use case, which synchronizes relevant product, customer, demand planning, and pricing information from ERP and PIM systems and easily consolidates this information into Trade Promotion Management (TPM) platforms, like Salesforce Consumer Goods Cloud, for informed promotional planning. +This release includes the https://anypoint.mulesoft.com/exchange/org.mule.examples/mulesoft-accelerator-for-consumergoods/minor/{cg-version}/pages/Use%20case%201%20-%20Product%20and%20Account%20Integration%20with%20Hierarchies/[Product and Account Integration with Hierarchies^] use case, which synchronizes relevant product, customer, demand planning, and pricing information from ERP and PIM systems and easily consolidates this information into Trade Promotion Management (TPM) platforms, like Salesforce Consumer Goods Cloud, for informed promotional planning. == See Also diff --git a/consumer-goods/5.0/modules/ROOT/pages/sap-s4hana-setup-guide.adoc b/consumer-goods/5.0/modules/ROOT/pages/sap-s4hana-setup-guide.adoc index 38b38a0d0..274cef101 100644 --- a/consumer-goods/5.0/modules/ROOT/pages/sap-s4hana-setup-guide.adoc +++ b/consumer-goods/5.0/modules/ROOT/pages/sap-s4hana-setup-guide.adoc @@ -8,25 +8,25 @@ To make the necessary configurations in S/4HANA: . Create a *Communication System* in the corresponding Fiori app. This communication system represents the external system that will consume the S/4HANA Cloud SOAP service. In this example, it's named "COM_0009_SOAP_OUT": + + -image:https://www.mulesoft.com/ext/solutions/draft/images/retail-sap-s4hana-setup-guide-01.png[retail-sap-s4hana-setup-guide-01.png,799] + +image:https://www.mulesoft.com/ext/solutions/images/retail-sap-s4hana-setup-guide-01.png[retail-sap-s4hana-setup-guide-01.png,799] + + . For the 'Business System' name, use the same name of the System ID. . In the 'Host Name' field, enter the hostname of the Mule application deployed on Cloudhub (if you don't have it yet, you can enter a mock URL and then modify it later): + + -image:https://www.mulesoft.com/ext/solutions/draft/images/retail-sap-s4hana-setup-guide-02.png[retail-sap-s4hana-setup-guide-02.png,799] + +image:https://www.mulesoft.com/ext/solutions/images/retail-sap-s4hana-setup-guide-02.png[retail-sap-s4hana-setup-guide-02.png,799] + + . Create a user that will be used to connect to the Cloud Hub app for sending product information in the outbound scenario (this is necessary even though the Mule application does not validate the user; we used any user for outbound): + + -image:https://www.mulesoft.com/ext/solutions/draft/images/retail-sap-s4hana-setup-guide-03.png[retail-sap-s4hana-setup-guide-03.png,799] + +image:https://www.mulesoft.com/ext/solutions/images/retail-sap-s4hana-setup-guide-03.png[retail-sap-s4hana-setup-guide-03.png,799] + + . Use the *Communication Arrangement* Fiori app to create a new Communication Arrangement: + + -image:https://www.mulesoft.com/ext/solutions/draft/images/retail-sap-s4hana-setup-guide-04.png[retail-sap-s4hana-setup-guide-04.png,799] + +image:https://www.mulesoft.com/ext/solutions/images/retail-sap-s4hana-setup-guide-04.png[retail-sap-s4hana-setup-guide-04.png,799] + + . Create a new *Communication Arrangement*, select the communication scenario "SAP_COM_0009", and then define a specific name for the arrangement, "SAP_COM_0009_SOAP". . In the *Communication System* field, select the Communication System created in the previous step: + + -image:https://www.mulesoft.com/ext/solutions/draft/images/retail-sap-s4hana-setup-guide-05.png[retail-sap-s4hana-setup-guide-05.png,799] + +image:https://www.mulesoft.com/ext/solutions/images/retail-sap-s4hana-setup-guide-05.png[retail-sap-s4hana-setup-guide-05.png,799] + + . For outbound communication, select the previously-created user and configure the *Product Master - Replicate from SAP S/4HANA Cloud to Client* and include the following settings. Make sure to note the Path (`/sap/bc/srt/scs/sap/productmdmbulkreplicaterequest`) because we will use this path to configure the Mule application SOAP endpoint: ** Set the Service status to *Active* @@ -34,11 +34,11 @@ image:https://www.mulesoft.com/ext/solutions/draft/images/retail-sap-s4hana-setu ** Replication model = I (Initial) ** The Output Mode = D (Direct). + + -image:https://www.mulesoft.com/ext/solutions/draft/images/retail-sap-s4hana-setup-guide-06.png[retail-sap-s4hana-setup-guide-06.png,799] + +image:https://www.mulesoft.com/ext/solutions/images/retail-sap-s4hana-setup-guide-06.png[retail-sap-s4hana-setup-guide-06.png,799] + + -image:https://www.mulesoft.com/ext/solutions/draft/images/retail-sap-s4hana-setup-guide-07.png[retail-sap-s4hana-setup-guide-07.png,799] + +image:https://www.mulesoft.com/ext/solutions/images/retail-sap-s4hana-setup-guide-07.png[retail-sap-s4hana-setup-guide-07.png,799] + + -image:https://www.mulesoft.com/ext/solutions/draft/images/retail-sap-s4hana-setup-guide-08.png[retail-sap-s4hana-setup-guide-08.png,799] + +image:https://www.mulesoft.com/ext/solutions/images/retail-sap-s4hana-setup-guide-08.png[retail-sap-s4hana-setup-guide-08.png,799] + + . Save it. All configurations at S/4HANA Cloud side are finished and you will be able to download the WSDL that contains the metadata to import into the S/4HANA Cloud SOAP Connector into the Mule application. @@ -48,38 +48,38 @@ The following example describes how to create a Mule application using the Outbo . Create a Mule project and add the appropriate connector from Exchange to the Mule Palette: + + -image:https://www.mulesoft.com/ext/solutions/draft/images/retail-sap-s4hana-setup-guide-09.png[retail-sap-s4hana-setup-guide-09.png,799] + +image:https://www.mulesoft.com/ext/solutions/images/retail-sap-s4hana-setup-guide-09.png[retail-sap-s4hana-setup-guide-09.png,799] + + . Add and configure the *Outbound Message Listener* to the canvas: + + -image:https://www.mulesoft.com/ext/solutions/draft/images/retail-sap-s4hana-setup-guide-10.png[retail-sap-s4hana-setup-guide-10.png,799] + +image:https://www.mulesoft.com/ext/solutions/images/retail-sap-s4hana-setup-guide-10.png[retail-sap-s4hana-setup-guide-10.png,799] + + . Add the corresponding WSDL path to the WSDL you downloaded from S/4HANA Cloud and create the HTTP listener configuration: + + -image:https://www.mulesoft.com/ext/solutions/draft/images/retail-sap-s4hana-setup-guide-11.png[retail-sap-s4hana-setup-guide-11.png,799] + +image:https://www.mulesoft.com/ext/solutions/images/retail-sap-s4hana-setup-guide-11.png[retail-sap-s4hana-setup-guide-11.png,799] + + -image:https://www.mulesoft.com/ext/solutions/draft/images/retail-sap-s4hana-setup-guide-12.png[retail-sap-s4hana-setup-guide-12.png,799] + +image:https://www.mulesoft.com/ext/solutions/images/retail-sap-s4hana-setup-guide-12.png[retail-sap-s4hana-setup-guide-12.png,799] + + _*Note*: we are using no authentication on the Mule Application, so we used the Insecure option for the Trust Store Configuration. In the Keystore configuration, we used a test Keystore, which is mandatory for HTTPS communication:_ + + -image:https://www.mulesoft.com/ext/solutions/draft/images/retail-sap-s4hana-setup-guide-13.png[retail-sap-s4hana-setup-guide-13.png,799] + +image:https://www.mulesoft.com/ext/solutions/images/retail-sap-s4hana-setup-guide-13.png[retail-sap-s4hana-setup-guide-13.png,799] + + . Select the Message type that the connector expects to receive from SAP (the connector reads the metadata from the WSDL we configured): + + -image:https://www.mulesoft.com/ext/solutions/draft/images/retail-sap-s4hana-setup-guide-14.png[retail-sap-s4hana-setup-guide-14.png,799] + +image:https://www.mulesoft.com/ext/solutions/images/retail-sap-s4hana-setup-guide-14.png[retail-sap-s4hana-setup-guide-14.png,799] + + . On the Responses tab, use the status Code "202" and the Reason-Phrase "Accepted" because we want to send the same status that S/4HANA Cloud will send if the service invocation results OK. No payload will be returned as a response--just the Status code and Reason-phrase: + + -image:https://www.mulesoft.com/ext/solutions/draft/images/retail-sap-s4hana-setup-guide-15.png[retail-sap-s4hana-setup-guide-15.png,799] + +image:https://www.mulesoft.com/ext/solutions/images/retail-sap-s4hana-setup-guide-15.png[retail-sap-s4hana-setup-guide-15.png,799] + + . Use a *Logger* component to log the inbound XML payload: + + -image:https://www.mulesoft.com/ext/solutions/draft/images/retail-sap-s4hana-setup-guide-16.png[retail-sap-s4hana-setup-guide-16.png,799] + +image:https://www.mulesoft.com/ext/solutions/images/retail-sap-s4hana-setup-guide-16.png[retail-sap-s4hana-setup-guide-16.png,799] + + _The Mule flow should look like the following:_ + + -image:https://www.mulesoft.com/ext/solutions/draft/images/retail-sap-s4hana-setup-guide-17.png[retail-sap-s4hana-setup-guide-17.png,399] + +image:https://www.mulesoft.com/ext/solutions/images/retail-sap-s4hana-setup-guide-17.png[retail-sap-s4hana-setup-guide-17.png,399] + + . Deploy the application to Cloudhub. You're now ready to test the scenario. @@ -89,35 +89,35 @@ To test the scenario: . Create the following. You only need to create a material in the corresponding Fiori app of S/4HANA Cloud: + + -image:https://www.mulesoft.com/ext/solutions/draft/images/retail-sap-s4hana-setup-guide-18.png[retail-sap-s4hana-setup-guide-18.png,599] + +image:https://www.mulesoft.com/ext/solutions/images/retail-sap-s4hana-setup-guide-18.png[retail-sap-s4hana-setup-guide-18.png,599] + + -image:https://www.mulesoft.com/ext/solutions/draft/images/retail-sap-s4hana-setup-guide-19.png[retail-sap-s4hana-setup-guide-19.png,799] + +image:https://www.mulesoft.com/ext/solutions/images/retail-sap-s4hana-setup-guide-19.png[retail-sap-s4hana-setup-guide-19.png,799] + + -image:https://www.mulesoft.com/ext/solutions/draft/images/retail-sap-s4hana-setup-guide-20.png[retail-sap-s4hana-setup-guide-20.png,799] + +image:https://www.mulesoft.com/ext/solutions/images/retail-sap-s4hana-setup-guide-20.png[retail-sap-s4hana-setup-guide-20.png,799] + + -image:https://www.mulesoft.com/ext/solutions/draft/images/retail-sap-s4hana-setup-guide-21.png[retail-sap-s4hana-setup-guide-21.png,799] + +image:https://www.mulesoft.com/ext/solutions/images/retail-sap-s4hana-setup-guide-21.png[retail-sap-s4hana-setup-guide-21.png,799] + + _After you save the new material, you should see the following confirmation in S/4HANA Cloud:_ + + -image:https://www.mulesoft.com/ext/solutions/draft/images/retail-sap-s4hana-setup-guide-22.png[retail-sap-s4hana-setup-guide-22.png,399] + +image:https://www.mulesoft.com/ext/solutions/images/retail-sap-s4hana-setup-guide-22.png[retail-sap-s4hana-setup-guide-22.png,399] + + _The following shows the XML message received at the Mule application at the Runtime Manager on Cloudhub:_ + + -image:https://www.mulesoft.com/ext/solutions/draft/images/retail-sap-s4hana-setup-guide-23.png[retail-sap-s4hana-setup-guide-23.png,799] + +image:https://www.mulesoft.com/ext/solutions/images/retail-sap-s4hana-setup-guide-23.png[retail-sap-s4hana-setup-guide-23.png,799] + + . See the sent message in the Message Dashboard Fiori Application: + + -image:https://www.mulesoft.com/ext/solutions/draft/images/retail-sap-s4hana-setup-guide-24.png[retail-sap-s4hana-setup-guide-24.png,799] + +image:https://www.mulesoft.com/ext/solutions/images/retail-sap-s4hana-setup-guide-24.png[retail-sap-s4hana-setup-guide-24.png,799] + + . Select the date: + + -image:https://www.mulesoft.com/ext/solutions/draft/images/retail-sap-s4hana-setup-guide-25.png[retail-sap-s4hana-setup-guide-25.png,399] + +image:https://www.mulesoft.com/ext/solutions/images/retail-sap-s4hana-setup-guide-25.png[retail-sap-s4hana-setup-guide-25.png,399] + + . Search under *CMD:Product Integration - /CMDPR → Product Replication to Client via Service - PRDREQ_OUT/00001 namespace*: + + -image:https://www.mulesoft.com/ext/solutions/draft/images/retail-sap-s4hana-setup-guide-26.png[retail-sap-s4hana-setup-guide-26.png,799] + +image:https://www.mulesoft.com/ext/solutions/images/retail-sap-s4hana-setup-guide-26.png[retail-sap-s4hana-setup-guide-26.png,799] + + -image:https://www.mulesoft.com/ext/solutions/draft/images/retail-sap-s4hana-setup-guide-27.png[retail-sap-s4hana-setup-guide-27.png,799] +image:https://www.mulesoft.com/ext/solutions/images/retail-sap-s4hana-setup-guide-27.png[retail-sap-s4hana-setup-guide-27.png,799] == S/4HANA customization guide diff --git a/consumer-goods/5.1/modules/ROOT/pages/cg-assets.adoc b/consumer-goods/5.1/modules/ROOT/pages/cg-assets.adoc index d7d2b4ab0..415d9c2c1 100644 --- a/consumer-goods/5.1/modules/ROOT/pages/cg-assets.adoc +++ b/consumer-goods/5.1/modules/ROOT/pages/cg-assets.adoc @@ -7,40 +7,40 @@ Accelerator assets include API specifications, implementation templates, custom [cols="40,30,30",width=100%] |=== | MDM System API -| https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/rcg-mdm-sys-api-spec/[API Specification^] -| https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/rcg-mdm-sys-api/[Implementation Template^] +| https://anypoint.mulesoft.com/exchange/org.mule.examples/rcg-mdm-sys-api-spec/[API Specification^] +| https://anypoint.mulesoft.com/exchange/org.mule.examples/rcg-mdm-sys-api/[Implementation Template^] | SAP S/4HANA Products System API -| https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/rcg-saphana-products-sys-api-spec/[API Specification^] -| https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/rcg-saphana-products-sys-api/[Implementation Template^] +| https://anypoint.mulesoft.com/exchange/org.mule.examples/rcg-saphana-products-sys-api-spec/[API Specification^] +| https://anypoint.mulesoft.com/exchange/org.mule.examples/rcg-saphana-products-sys-api/[Implementation Template^] | RCG Salesforce Consumer Goods Cloud System API -| https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/rcg-salesforce-cgcloud-sys-api-spec/[API Specification^] -| https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/rcg-salesforce-cgcloud-sys-api/[Implementation Template^] +| https://anypoint.mulesoft.com/exchange/org.mule.examples/rcg-salesforce-cgcloud-sys-api-spec/[API Specification^] +| https://anypoint.mulesoft.com/exchange/org.mule.examples/rcg-salesforce-cgcloud-sys-api/[Implementation Template^] | SAP S/4HANA Customers System API -| https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/rcg-saphana-customers-sys-api-spec/[API Specification^] -| https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/rcg-saphana-customers-sys-api/[Implementation Template^] +| https://anypoint.mulesoft.com/exchange/org.mule.examples/rcg-saphana-customers-sys-api-spec/[API Specification^] +| https://anypoint.mulesoft.com/exchange/org.mule.examples/rcg-saphana-customers-sys-api/[Implementation Template^] | RCG Salsify Products System API -| https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/rcg-salsify-products-sys-api-spec/[API Specification^] -| https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/rcg-salsify-products-sys-api/[Implementation Template^] +| https://anypoint.mulesoft.com/exchange/org.mule.examples/rcg-salsify-products-sys-api-spec/[API Specification^] +| https://anypoint.mulesoft.com/exchange/org.mule.examples/rcg-salsify-products-sys-api/[Implementation Template^] | RCG Trax System API -| https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/rcg-trax-sys-api-spec/[API Specification^] -| https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/rcg-trax-sys-api/[Implementation Template^] +| https://anypoint.mulesoft.com/exchange/org.mule.examples/rcg-trax-sys-api-spec/[API Specification^] +| https://anypoint.mulesoft.com/exchange/org.mule.examples/rcg-trax-sys-api/[Implementation Template^] | RCG Hyperforce System API -| https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/rcg-hyperforce-sys-api-spec/[API Specification^] -| https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/rcg-hyperforce-sys-api/[Implementation Template^] +| https://anypoint.mulesoft.com/exchange/org.mule.examples/rcg-hyperforce-sys-api-spec/[API Specification^] +| https://anypoint.mulesoft.com/exchange/org.mule.examples/rcg-hyperforce-sys-api/[Implementation Template^] | RCG Salesforce Volume Management System API -| https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/rcg-salesforce-volume-mgmt-sys-api-spec/[API Specification^] -| https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/rcg-sfdc-volume-mgmt-sys-api/[Implementation Template^] +| https://anypoint.mulesoft.com/exchange/org.mule.examples/rcg-salesforce-volume-mgmt-sys-api-spec/[API Specification^] +| https://anypoint.mulesoft.com/exchange/org.mule.examples/rcg-sfdc-volume-mgmt-sys-api/[Implementation Template^] | RCG CRM Analytics System API -| https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/rcg-crma-sys-api-spec/[API Specification^] -| https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/rcg-crma-sys-api/[Implementation Template^] +| https://anypoint.mulesoft.com/exchange/org.mule.examples/rcg-crma-sys-api-spec/[API Specification^] +| https://anypoint.mulesoft.com/exchange/org.mule.examples/rcg-crma-sys-api/[Implementation Template^] |=== == Process APIs @@ -48,20 +48,20 @@ Accelerator assets include API specifications, implementation templates, custom [cols="40,30,30",width=100%] |=== | RCG Products Process API -| https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/rcg-products-prc-api-spec/[API Specification^] -| https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/rcg-products-prc-api/[Implementation Template^] +| https://anypoint.mulesoft.com/exchange/org.mule.examples/rcg-products-prc-api-spec/[API Specification^] +| https://anypoint.mulesoft.com/exchange/org.mule.examples/rcg-products-prc-api/[Implementation Template^] | RCG Customers Process API -| https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/rcg-customers-prc-api-spec/[API Specification^] -| https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/rcg-customers-prc-api/[Implementation Template^] +| https://anypoint.mulesoft.com/exchange/org.mule.examples/rcg-customers-prc-api-spec/[API Specification^] +| https://anypoint.mulesoft.com/exchange/org.mule.examples/rcg-customers-prc-api/[Implementation Template^] | RCG Store Audit Process API -| https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/rcg-store-audit-prc-api-spec[API Specification^] -| https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/rcg-store-audit-prc-api/[Implementation Template^] +| https://anypoint.mulesoft.com/exchange/org.mule.examples/rcg-store-audit-prc-api-spec[API Specification^] +| https://anypoint.mulesoft.com/exchange/org.mule.examples/rcg-store-audit-prc-api/[Implementation Template^] | RCG Data Normalization Process API -| https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/rcg-data-normalization-prc-api-spec[API Specification^] -| https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/rcg-data-normalization-prc-api/[Implementation Template^] +| https://anypoint.mulesoft.com/exchange/org.mule.examples/rcg-data-normalization-prc-api-spec[API Specification^] +| https://anypoint.mulesoft.com/exchange/org.mule.examples/rcg-data-normalization-prc-api/[Implementation Template^] |=== == Listener Applications @@ -69,7 +69,7 @@ Accelerator assets include API specifications, implementation templates, custom [cols="70,30",width=100%] |=== | Salsify Channel Listener -| https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/rcg-salsify-channel-listener/[Implementation Template^] +| https://anypoint.mulesoft.com/exchange/org.mule.examples/rcg-salsify-channel-listener/[Implementation Template^] |=== == See Also diff --git a/consumer-goods/5.1/modules/ROOT/pages/index.adoc b/consumer-goods/5.1/modules/ROOT/pages/index.adoc index 981811e47..db75963ec 100644 --- a/consumer-goods/5.1/modules/ROOT/pages/index.adoc +++ b/consumer-goods/5.1/modules/ROOT/pages/index.adoc @@ -11,15 +11,15 @@ The https://anypoint.mulesoft.com/exchange//mulesoft-accelerator-for-consumergoo === Retail Execution -The https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/mulesoft-accelerator-for-consumergoods/minor/{cg-version}/pages/Use%20case%202%20-%20Retail%20execution/[Retail Execution^] use case unlocks shelf data to enable perfect retail execution with pre-built assets. Access store audit data from image recognition software, like Trax, and smoothly integrate into Retail Execution platforms, such as Salesforce Consumer Goods Cloud, to monitor at shelf performance in one platform. +The https://anypoint.mulesoft.com/exchange/org.mule.examples/mulesoft-accelerator-for-consumergoods/minor/{cg-version}/pages/Use%20case%202%20-%20Retail%20execution/[Retail Execution^] use case unlocks shelf data to enable perfect retail execution with pre-built assets. Access store audit data from image recognition software, like Trax, and smoothly integrate into Retail Execution platforms, such as Salesforce Consumer Goods Cloud, to monitor at shelf performance in one platform. === Trade Promotion Effectiveness -The https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/mulesoft-accelerator-for-consumergoods/minor/{cg-version}/pages/Use%20case%203%20-%20Trade%20promotion%20effectiveness/[Trade Promotion Effectiveness^] use case allows you to visualize your promotions in one integrated platform with pre-built assets that integrate Business Intelligence Tools (BI Tools), such as CRM Analytics, into a TPM platform like Salesforce Consumer Goods Cloud. +The https://anypoint.mulesoft.com/exchange/org.mule.examples/mulesoft-accelerator-for-consumergoods/minor/{cg-version}/pages/Use%20case%203%20-%20Trade%20promotion%20effectiveness/[Trade Promotion Effectiveness^] use case allows you to visualize your promotions in one integrated platform with pre-built assets that integrate Business Intelligence Tools (BI Tools), such as CRM Analytics, into a TPM platform like Salesforce Consumer Goods Cloud. === Trade Promotion Optimization -The https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/mulesoft-accelerator-for-consumergoods/minor/{cg-version}/pages/Use%20case%204%20-%20Trade%20promotion%20optimization/[Trade Promotion Optimization^] use case allows you to visualize your promotions in one integrated platform with pre-built assets that integrate Business Intelligence Tools (BI Tools), such as CRM Analytics, into a TPM platform like Salesforce Consumer Goods Cloud. +The https://anypoint.mulesoft.com/exchange/org.mule.examples/mulesoft-accelerator-for-consumergoods/minor/{cg-version}/pages/Use%20case%204%20-%20Trade%20promotion%20optimization/[Trade Promotion Optimization^] use case allows you to visualize your promotions in one integrated platform with pre-built assets that integrate Business Intelligence Tools (BI Tools), such as CRM Analytics, into a TPM platform like Salesforce Consumer Goods Cloud. == See Also diff --git a/consumer-goods/5.1/modules/ROOT/pages/sap-s4hana-setup-guide.adoc b/consumer-goods/5.1/modules/ROOT/pages/sap-s4hana-setup-guide.adoc index 38b38a0d0..274cef101 100644 --- a/consumer-goods/5.1/modules/ROOT/pages/sap-s4hana-setup-guide.adoc +++ b/consumer-goods/5.1/modules/ROOT/pages/sap-s4hana-setup-guide.adoc @@ -8,25 +8,25 @@ To make the necessary configurations in S/4HANA: . Create a *Communication System* in the corresponding Fiori app. This communication system represents the external system that will consume the S/4HANA Cloud SOAP service. In this example, it's named "COM_0009_SOAP_OUT": + + -image:https://www.mulesoft.com/ext/solutions/draft/images/retail-sap-s4hana-setup-guide-01.png[retail-sap-s4hana-setup-guide-01.png,799] + +image:https://www.mulesoft.com/ext/solutions/images/retail-sap-s4hana-setup-guide-01.png[retail-sap-s4hana-setup-guide-01.png,799] + + . For the 'Business System' name, use the same name of the System ID. . In the 'Host Name' field, enter the hostname of the Mule application deployed on Cloudhub (if you don't have it yet, you can enter a mock URL and then modify it later): + + -image:https://www.mulesoft.com/ext/solutions/draft/images/retail-sap-s4hana-setup-guide-02.png[retail-sap-s4hana-setup-guide-02.png,799] + +image:https://www.mulesoft.com/ext/solutions/images/retail-sap-s4hana-setup-guide-02.png[retail-sap-s4hana-setup-guide-02.png,799] + + . Create a user that will be used to connect to the Cloud Hub app for sending product information in the outbound scenario (this is necessary even though the Mule application does not validate the user; we used any user for outbound): + + -image:https://www.mulesoft.com/ext/solutions/draft/images/retail-sap-s4hana-setup-guide-03.png[retail-sap-s4hana-setup-guide-03.png,799] + +image:https://www.mulesoft.com/ext/solutions/images/retail-sap-s4hana-setup-guide-03.png[retail-sap-s4hana-setup-guide-03.png,799] + + . Use the *Communication Arrangement* Fiori app to create a new Communication Arrangement: + + -image:https://www.mulesoft.com/ext/solutions/draft/images/retail-sap-s4hana-setup-guide-04.png[retail-sap-s4hana-setup-guide-04.png,799] + +image:https://www.mulesoft.com/ext/solutions/images/retail-sap-s4hana-setup-guide-04.png[retail-sap-s4hana-setup-guide-04.png,799] + + . Create a new *Communication Arrangement*, select the communication scenario "SAP_COM_0009", and then define a specific name for the arrangement, "SAP_COM_0009_SOAP". . In the *Communication System* field, select the Communication System created in the previous step: + + -image:https://www.mulesoft.com/ext/solutions/draft/images/retail-sap-s4hana-setup-guide-05.png[retail-sap-s4hana-setup-guide-05.png,799] + +image:https://www.mulesoft.com/ext/solutions/images/retail-sap-s4hana-setup-guide-05.png[retail-sap-s4hana-setup-guide-05.png,799] + + . For outbound communication, select the previously-created user and configure the *Product Master - Replicate from SAP S/4HANA Cloud to Client* and include the following settings. Make sure to note the Path (`/sap/bc/srt/scs/sap/productmdmbulkreplicaterequest`) because we will use this path to configure the Mule application SOAP endpoint: ** Set the Service status to *Active* @@ -34,11 +34,11 @@ image:https://www.mulesoft.com/ext/solutions/draft/images/retail-sap-s4hana-setu ** Replication model = I (Initial) ** The Output Mode = D (Direct). + + -image:https://www.mulesoft.com/ext/solutions/draft/images/retail-sap-s4hana-setup-guide-06.png[retail-sap-s4hana-setup-guide-06.png,799] + +image:https://www.mulesoft.com/ext/solutions/images/retail-sap-s4hana-setup-guide-06.png[retail-sap-s4hana-setup-guide-06.png,799] + + -image:https://www.mulesoft.com/ext/solutions/draft/images/retail-sap-s4hana-setup-guide-07.png[retail-sap-s4hana-setup-guide-07.png,799] + +image:https://www.mulesoft.com/ext/solutions/images/retail-sap-s4hana-setup-guide-07.png[retail-sap-s4hana-setup-guide-07.png,799] + + -image:https://www.mulesoft.com/ext/solutions/draft/images/retail-sap-s4hana-setup-guide-08.png[retail-sap-s4hana-setup-guide-08.png,799] + +image:https://www.mulesoft.com/ext/solutions/images/retail-sap-s4hana-setup-guide-08.png[retail-sap-s4hana-setup-guide-08.png,799] + + . Save it. All configurations at S/4HANA Cloud side are finished and you will be able to download the WSDL that contains the metadata to import into the S/4HANA Cloud SOAP Connector into the Mule application. @@ -48,38 +48,38 @@ The following example describes how to create a Mule application using the Outbo . Create a Mule project and add the appropriate connector from Exchange to the Mule Palette: + + -image:https://www.mulesoft.com/ext/solutions/draft/images/retail-sap-s4hana-setup-guide-09.png[retail-sap-s4hana-setup-guide-09.png,799] + +image:https://www.mulesoft.com/ext/solutions/images/retail-sap-s4hana-setup-guide-09.png[retail-sap-s4hana-setup-guide-09.png,799] + + . Add and configure the *Outbound Message Listener* to the canvas: + + -image:https://www.mulesoft.com/ext/solutions/draft/images/retail-sap-s4hana-setup-guide-10.png[retail-sap-s4hana-setup-guide-10.png,799] + +image:https://www.mulesoft.com/ext/solutions/images/retail-sap-s4hana-setup-guide-10.png[retail-sap-s4hana-setup-guide-10.png,799] + + . Add the corresponding WSDL path to the WSDL you downloaded from S/4HANA Cloud and create the HTTP listener configuration: + + -image:https://www.mulesoft.com/ext/solutions/draft/images/retail-sap-s4hana-setup-guide-11.png[retail-sap-s4hana-setup-guide-11.png,799] + +image:https://www.mulesoft.com/ext/solutions/images/retail-sap-s4hana-setup-guide-11.png[retail-sap-s4hana-setup-guide-11.png,799] + + -image:https://www.mulesoft.com/ext/solutions/draft/images/retail-sap-s4hana-setup-guide-12.png[retail-sap-s4hana-setup-guide-12.png,799] + +image:https://www.mulesoft.com/ext/solutions/images/retail-sap-s4hana-setup-guide-12.png[retail-sap-s4hana-setup-guide-12.png,799] + + _*Note*: we are using no authentication on the Mule Application, so we used the Insecure option for the Trust Store Configuration. In the Keystore configuration, we used a test Keystore, which is mandatory for HTTPS communication:_ + + -image:https://www.mulesoft.com/ext/solutions/draft/images/retail-sap-s4hana-setup-guide-13.png[retail-sap-s4hana-setup-guide-13.png,799] + +image:https://www.mulesoft.com/ext/solutions/images/retail-sap-s4hana-setup-guide-13.png[retail-sap-s4hana-setup-guide-13.png,799] + + . Select the Message type that the connector expects to receive from SAP (the connector reads the metadata from the WSDL we configured): + + -image:https://www.mulesoft.com/ext/solutions/draft/images/retail-sap-s4hana-setup-guide-14.png[retail-sap-s4hana-setup-guide-14.png,799] + +image:https://www.mulesoft.com/ext/solutions/images/retail-sap-s4hana-setup-guide-14.png[retail-sap-s4hana-setup-guide-14.png,799] + + . On the Responses tab, use the status Code "202" and the Reason-Phrase "Accepted" because we want to send the same status that S/4HANA Cloud will send if the service invocation results OK. No payload will be returned as a response--just the Status code and Reason-phrase: + + -image:https://www.mulesoft.com/ext/solutions/draft/images/retail-sap-s4hana-setup-guide-15.png[retail-sap-s4hana-setup-guide-15.png,799] + +image:https://www.mulesoft.com/ext/solutions/images/retail-sap-s4hana-setup-guide-15.png[retail-sap-s4hana-setup-guide-15.png,799] + + . Use a *Logger* component to log the inbound XML payload: + + -image:https://www.mulesoft.com/ext/solutions/draft/images/retail-sap-s4hana-setup-guide-16.png[retail-sap-s4hana-setup-guide-16.png,799] + +image:https://www.mulesoft.com/ext/solutions/images/retail-sap-s4hana-setup-guide-16.png[retail-sap-s4hana-setup-guide-16.png,799] + + _The Mule flow should look like the following:_ + + -image:https://www.mulesoft.com/ext/solutions/draft/images/retail-sap-s4hana-setup-guide-17.png[retail-sap-s4hana-setup-guide-17.png,399] + +image:https://www.mulesoft.com/ext/solutions/images/retail-sap-s4hana-setup-guide-17.png[retail-sap-s4hana-setup-guide-17.png,399] + + . Deploy the application to Cloudhub. You're now ready to test the scenario. @@ -89,35 +89,35 @@ To test the scenario: . Create the following. You only need to create a material in the corresponding Fiori app of S/4HANA Cloud: + + -image:https://www.mulesoft.com/ext/solutions/draft/images/retail-sap-s4hana-setup-guide-18.png[retail-sap-s4hana-setup-guide-18.png,599] + +image:https://www.mulesoft.com/ext/solutions/images/retail-sap-s4hana-setup-guide-18.png[retail-sap-s4hana-setup-guide-18.png,599] + + -image:https://www.mulesoft.com/ext/solutions/draft/images/retail-sap-s4hana-setup-guide-19.png[retail-sap-s4hana-setup-guide-19.png,799] + +image:https://www.mulesoft.com/ext/solutions/images/retail-sap-s4hana-setup-guide-19.png[retail-sap-s4hana-setup-guide-19.png,799] + + -image:https://www.mulesoft.com/ext/solutions/draft/images/retail-sap-s4hana-setup-guide-20.png[retail-sap-s4hana-setup-guide-20.png,799] + +image:https://www.mulesoft.com/ext/solutions/images/retail-sap-s4hana-setup-guide-20.png[retail-sap-s4hana-setup-guide-20.png,799] + + -image:https://www.mulesoft.com/ext/solutions/draft/images/retail-sap-s4hana-setup-guide-21.png[retail-sap-s4hana-setup-guide-21.png,799] + +image:https://www.mulesoft.com/ext/solutions/images/retail-sap-s4hana-setup-guide-21.png[retail-sap-s4hana-setup-guide-21.png,799] + + _After you save the new material, you should see the following confirmation in S/4HANA Cloud:_ + + -image:https://www.mulesoft.com/ext/solutions/draft/images/retail-sap-s4hana-setup-guide-22.png[retail-sap-s4hana-setup-guide-22.png,399] + +image:https://www.mulesoft.com/ext/solutions/images/retail-sap-s4hana-setup-guide-22.png[retail-sap-s4hana-setup-guide-22.png,399] + + _The following shows the XML message received at the Mule application at the Runtime Manager on Cloudhub:_ + + -image:https://www.mulesoft.com/ext/solutions/draft/images/retail-sap-s4hana-setup-guide-23.png[retail-sap-s4hana-setup-guide-23.png,799] + +image:https://www.mulesoft.com/ext/solutions/images/retail-sap-s4hana-setup-guide-23.png[retail-sap-s4hana-setup-guide-23.png,799] + + . See the sent message in the Message Dashboard Fiori Application: + + -image:https://www.mulesoft.com/ext/solutions/draft/images/retail-sap-s4hana-setup-guide-24.png[retail-sap-s4hana-setup-guide-24.png,799] + +image:https://www.mulesoft.com/ext/solutions/images/retail-sap-s4hana-setup-guide-24.png[retail-sap-s4hana-setup-guide-24.png,799] + + . Select the date: + + -image:https://www.mulesoft.com/ext/solutions/draft/images/retail-sap-s4hana-setup-guide-25.png[retail-sap-s4hana-setup-guide-25.png,399] + +image:https://www.mulesoft.com/ext/solutions/images/retail-sap-s4hana-setup-guide-25.png[retail-sap-s4hana-setup-guide-25.png,399] + + . Search under *CMD:Product Integration - /CMDPR → Product Replication to Client via Service - PRDREQ_OUT/00001 namespace*: + + -image:https://www.mulesoft.com/ext/solutions/draft/images/retail-sap-s4hana-setup-guide-26.png[retail-sap-s4hana-setup-guide-26.png,799] + +image:https://www.mulesoft.com/ext/solutions/images/retail-sap-s4hana-setup-guide-26.png[retail-sap-s4hana-setup-guide-26.png,799] + + -image:https://www.mulesoft.com/ext/solutions/draft/images/retail-sap-s4hana-setup-guide-27.png[retail-sap-s4hana-setup-guide-27.png,799] +image:https://www.mulesoft.com/ext/solutions/images/retail-sap-s4hana-setup-guide-27.png[retail-sap-s4hana-setup-guide-27.png,799] == S/4HANA customization guide diff --git a/consumer-goods/5.2/modules/ROOT/pages/cg-assets.adoc b/consumer-goods/5.2/modules/ROOT/pages/cg-assets.adoc index 8d8ae8251..6d3bc3b2a 100644 --- a/consumer-goods/5.2/modules/ROOT/pages/cg-assets.adoc +++ b/consumer-goods/5.2/modules/ROOT/pages/cg-assets.adoc @@ -7,44 +7,44 @@ Accelerator assets include API specifications, implementation templates, custom [cols="40,30,30",width=100%] |=== | MDM System API -| https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/rcg-mdm-sys-api-spec/[API Specification^] -| https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/rcg-mdm-sys-api/[Implementation Template^] +| https://anypoint.mulesoft.com/exchange/org.mule.examples/rcg-mdm-sys-api-spec/[API Specification^] +| https://anypoint.mulesoft.com/exchange/org.mule.examples/rcg-mdm-sys-api/[Implementation Template^] | SAP S/4HANA Products System API -| https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/rcg-saphana-products-sys-api-spec/[API Specification^] -| https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/rcg-saphana-products-sys-api/[Implementation Template^] +| https://anypoint.mulesoft.com/exchange/org.mule.examples/rcg-saphana-products-sys-api-spec/[API Specification^] +| https://anypoint.mulesoft.com/exchange/org.mule.examples/rcg-saphana-products-sys-api/[Implementation Template^] | RCG Salesforce Consumer Goods Cloud System API -| https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/rcg-salesforce-cgcloud-sys-api-spec/[API Specification^] -| https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/rcg-salesforce-cgcloud-sys-api/[Implementation Template^] +| https://anypoint.mulesoft.com/exchange/org.mule.examples/rcg-salesforce-cgcloud-sys-api-spec/[API Specification^] +| https://anypoint.mulesoft.com/exchange/org.mule.examples/rcg-salesforce-cgcloud-sys-api/[Implementation Template^] | SAP S/4HANA Customers System API -| https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/rcg-saphana-customers-sys-api-spec/[API Specification^] -| https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/rcg-saphana-customers-sys-api/[Implementation Template^] +| https://anypoint.mulesoft.com/exchange/org.mule.examples/rcg-saphana-customers-sys-api-spec/[API Specification^] +| https://anypoint.mulesoft.com/exchange/org.mule.examples/rcg-saphana-customers-sys-api/[Implementation Template^] | RCG Salsify Products System API -| https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/rcg-salsify-products-sys-api-spec/[API Specification^] -| https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/rcg-salsify-products-sys-api/[Implementation Template^] +| https://anypoint.mulesoft.com/exchange/org.mule.examples/rcg-salsify-products-sys-api-spec/[API Specification^] +| https://anypoint.mulesoft.com/exchange/org.mule.examples/rcg-salsify-products-sys-api/[Implementation Template^] | RCG Trax System API -| https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/rcg-trax-sys-api-spec/[API Specification^] -| https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/rcg-trax-sys-api/[Implementation Template^] +| https://anypoint.mulesoft.com/exchange/org.mule.examples/rcg-trax-sys-api-spec/[API Specification^] +| https://anypoint.mulesoft.com/exchange/org.mule.examples/rcg-trax-sys-api/[Implementation Template^] | RCG Hyperforce System API -| https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/rcg-hyperforce-sys-api-spec/[API Specification^] -| https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/rcg-hyperforce-sys-api/[Implementation Template^] +| https://anypoint.mulesoft.com/exchange/org.mule.examples/rcg-hyperforce-sys-api-spec/[API Specification^] +| https://anypoint.mulesoft.com/exchange/org.mule.examples/rcg-hyperforce-sys-api/[Implementation Template^] | RCG Salesforce Volume Management System API -| https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/rcg-salesforce-volume-mgmt-sys-api-spec/[API Specification^] -| https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/rcg-sfdc-volume-mgmt-sys-api/[Implementation Template^] +| https://anypoint.mulesoft.com/exchange/org.mule.examples/rcg-salesforce-volume-mgmt-sys-api-spec/[API Specification^] +| https://anypoint.mulesoft.com/exchange/org.mule.examples/rcg-sfdc-volume-mgmt-sys-api/[Implementation Template^] | RCG CRM Analytics System API -| https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/rcg-crma-sys-api-spec/[API Specification^] -| https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/rcg-crma-sys-api/[Implementation Template^] +| https://anypoint.mulesoft.com/exchange/org.mule.examples/rcg-crma-sys-api-spec/[API Specification^] +| https://anypoint.mulesoft.com/exchange/org.mule.examples/rcg-crma-sys-api/[Implementation Template^] | RCG Salesforce Data Cloud System API -| https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/rcg-salesforce-cdp-sys-api-spec/[API Specification^] -| https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/rcg-salesforce-cdp-sys-api/[Implementation Template^] +| https://anypoint.mulesoft.com/exchange/org.mule.examples/rcg-salesforce-cdp-sys-api-spec/[API Specification^] +| https://anypoint.mulesoft.com/exchange/org.mule.examples/rcg-salesforce-cdp-sys-api/[Implementation Template^] |=== == Process APIs @@ -52,24 +52,24 @@ Accelerator assets include API specifications, implementation templates, custom [cols="40,30,30",width=100%] |=== | RCG Products Process API -| https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/rcg-products-prc-api-spec/[API Specification^] -| https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/rcg-products-prc-api/[Implementation Template^] +| https://anypoint.mulesoft.com/exchange/org.mule.examples/rcg-products-prc-api-spec/[API Specification^] +| https://anypoint.mulesoft.com/exchange/org.mule.examples/rcg-products-prc-api/[Implementation Template^] | RCG Customers Process API -| https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/rcg-customers-prc-api-spec/[API Specification^] -| https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/rcg-customers-prc-api/[Implementation Template^] +| https://anypoint.mulesoft.com/exchange/org.mule.examples/rcg-customers-prc-api-spec/[API Specification^] +| https://anypoint.mulesoft.com/exchange/org.mule.examples/rcg-customers-prc-api/[Implementation Template^] | RCG Store Audit Process API -| https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/rcg-store-audit-prc-api-spec[API Specification^] -| https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/rcg-store-audit-prc-api/[Implementation Template^] +| https://anypoint.mulesoft.com/exchange/org.mule.examples/rcg-store-audit-prc-api-spec[API Specification^] +| https://anypoint.mulesoft.com/exchange/org.mule.examples/rcg-store-audit-prc-api/[Implementation Template^] | RCG Data Normalization Process API -| https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/rcg-data-normalization-prc-api-spec[API Specification^] -| https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/rcg-data-normalization-prc-api/[Implementation Template^] +| https://anypoint.mulesoft.com/exchange/org.mule.examples/rcg-data-normalization-prc-api-spec[API Specification^] +| https://anypoint.mulesoft.com/exchange/org.mule.examples/rcg-data-normalization-prc-api/[Implementation Template^] | Accelerator Orders Process API -| https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/accel-slsorder-sync-prc-api-spec[API Specification^] -| https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/accel-slsorder-sync-prc-api/[Implementation Template^] +| https://anypoint.mulesoft.com/exchange/org.mule.examples/accel-slsorder-sync-prc-api-spec[API Specification^] +| https://anypoint.mulesoft.com/exchange/org.mule.examples/accel-slsorder-sync-prc-api/[Implementation Template^] |=== == Listener Applications @@ -77,10 +77,10 @@ Accelerator assets include API specifications, implementation templates, custom [cols="70,30",width=100%] |=== | Salsify Channel Listener -| https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/rcg-salsify-channel-listener/[Implementation Template^] +| https://anypoint.mulesoft.com/exchange/org.mule.examples/rcg-salsify-channel-listener/[Implementation Template^] | POS Event Listener -| https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/rcg-predictspring-event-listener/[Implementation Template^] +| https://anypoint.mulesoft.com/exchange/org.mule.examples/rcg-predictspring-event-listener/[Implementation Template^] |=== == See Also diff --git a/consumer-goods/5.2/modules/ROOT/pages/index.adoc b/consumer-goods/5.2/modules/ROOT/pages/index.adoc index 2d5676f7a..77eba5968 100644 --- a/consumer-goods/5.2/modules/ROOT/pages/index.adoc +++ b/consumer-goods/5.2/modules/ROOT/pages/index.adoc @@ -11,19 +11,19 @@ The https://anypoint.mulesoft.com/exchange//mulesoft-accelerator-for-consumergoo === Retail Execution -The https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/mulesoft-accelerator-for-consumergoods/minor/{cg-version}/pages/Use%20case%202%20-%20Retail%20execution/[Retail Execution^] use case unlocks shelf data to enable perfect retail execution with pre-built assets. Access store audit data from image recognition software, like Trax, and smoothly integrate into Retail Execution platforms, such as Salesforce Consumer Goods Cloud, to monitor at shelf performance in one platform. +The https://anypoint.mulesoft.com/exchange/org.mule.examples/mulesoft-accelerator-for-consumergoods/minor/{cg-version}/pages/Use%20case%202%20-%20Retail%20execution/[Retail Execution^] use case unlocks shelf data to enable perfect retail execution with pre-built assets. Access store audit data from image recognition software, like Trax, and smoothly integrate into Retail Execution platforms, such as Salesforce Consumer Goods Cloud, to monitor at shelf performance in one platform. === Trade Promotion Effectiveness -The https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/mulesoft-accelerator-for-consumergoods/minor/{cg-version}/pages/Use%20case%203%20-%20Trade%20promotion%20effectiveness/[Trade Promotion Effectiveness^] use case allows you to visualize your promotions in one integrated platform with pre-built assets that integrate Business Intelligence Tools (BI Tools), such as CRM Analytics, into a TPM platform like Salesforce Consumer Goods Cloud. +The https://anypoint.mulesoft.com/exchange/org.mule.examples/mulesoft-accelerator-for-consumergoods/minor/{cg-version}/pages/Use%20case%203%20-%20Trade%20promotion%20effectiveness/[Trade Promotion Effectiveness^] use case allows you to visualize your promotions in one integrated platform with pre-built assets that integrate Business Intelligence Tools (BI Tools), such as CRM Analytics, into a TPM platform like Salesforce Consumer Goods Cloud. === Trade Promotion Optimization -The https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/mulesoft-accelerator-for-consumergoods/minor/{cg-version}/pages/Use%20case%204%20-%20Trade%20promotion%20optimization/[Trade Promotion Optimization^] use case allows you to visualize your promotions in one integrated platform with pre-built assets that integrate Business Intelligence Tools (BI Tools), such as CRM Analytics, into a TPM platform like Salesforce Consumer Goods Cloud. +The https://anypoint.mulesoft.com/exchange/org.mule.examples/mulesoft-accelerator-for-consumergoods/minor/{cg-version}/pages/Use%20case%204%20-%20Trade%20promotion%20optimization/[Trade Promotion Optimization^] use case allows you to visualize your promotions in one integrated platform with pre-built assets that integrate Business Intelligence Tools (BI Tools), such as CRM Analytics, into a TPM platform like Salesforce Consumer Goods Cloud. === POS Integration -The https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/mulesoft-accelerator-for-consumer-goods/minor/{cg-version}/pages/Use%20case%206%20-%20POS%20integration/[POS Integration^] use case enables retail developers to leverage pre-built integrations to connect order and loyalty data from Point of Sale (POS) systems to Data Cloud. +The https://anypoint.mulesoft.com/exchange/org.mule.examples/mulesoft-accelerator-for-consumer-goods/minor/{cg-version}/pages/Use%20case%206%20-%20POS%20integration/[POS Integration^] use case enables retail developers to leverage pre-built integrations to connect order and loyalty data from Point of Sale (POS) systems to Data Cloud. == See Also diff --git a/consumer-goods/5.2/modules/ROOT/pages/sap-s4hana-setup-guide.adoc b/consumer-goods/5.2/modules/ROOT/pages/sap-s4hana-setup-guide.adoc index 38b38a0d0..274cef101 100644 --- a/consumer-goods/5.2/modules/ROOT/pages/sap-s4hana-setup-guide.adoc +++ b/consumer-goods/5.2/modules/ROOT/pages/sap-s4hana-setup-guide.adoc @@ -8,25 +8,25 @@ To make the necessary configurations in S/4HANA: . Create a *Communication System* in the corresponding Fiori app. This communication system represents the external system that will consume the S/4HANA Cloud SOAP service. In this example, it's named "COM_0009_SOAP_OUT": + + -image:https://www.mulesoft.com/ext/solutions/draft/images/retail-sap-s4hana-setup-guide-01.png[retail-sap-s4hana-setup-guide-01.png,799] + +image:https://www.mulesoft.com/ext/solutions/images/retail-sap-s4hana-setup-guide-01.png[retail-sap-s4hana-setup-guide-01.png,799] + + . For the 'Business System' name, use the same name of the System ID. . In the 'Host Name' field, enter the hostname of the Mule application deployed on Cloudhub (if you don't have it yet, you can enter a mock URL and then modify it later): + + -image:https://www.mulesoft.com/ext/solutions/draft/images/retail-sap-s4hana-setup-guide-02.png[retail-sap-s4hana-setup-guide-02.png,799] + +image:https://www.mulesoft.com/ext/solutions/images/retail-sap-s4hana-setup-guide-02.png[retail-sap-s4hana-setup-guide-02.png,799] + + . Create a user that will be used to connect to the Cloud Hub app for sending product information in the outbound scenario (this is necessary even though the Mule application does not validate the user; we used any user for outbound): + + -image:https://www.mulesoft.com/ext/solutions/draft/images/retail-sap-s4hana-setup-guide-03.png[retail-sap-s4hana-setup-guide-03.png,799] + +image:https://www.mulesoft.com/ext/solutions/images/retail-sap-s4hana-setup-guide-03.png[retail-sap-s4hana-setup-guide-03.png,799] + + . Use the *Communication Arrangement* Fiori app to create a new Communication Arrangement: + + -image:https://www.mulesoft.com/ext/solutions/draft/images/retail-sap-s4hana-setup-guide-04.png[retail-sap-s4hana-setup-guide-04.png,799] + +image:https://www.mulesoft.com/ext/solutions/images/retail-sap-s4hana-setup-guide-04.png[retail-sap-s4hana-setup-guide-04.png,799] + + . Create a new *Communication Arrangement*, select the communication scenario "SAP_COM_0009", and then define a specific name for the arrangement, "SAP_COM_0009_SOAP". . In the *Communication System* field, select the Communication System created in the previous step: + + -image:https://www.mulesoft.com/ext/solutions/draft/images/retail-sap-s4hana-setup-guide-05.png[retail-sap-s4hana-setup-guide-05.png,799] + +image:https://www.mulesoft.com/ext/solutions/images/retail-sap-s4hana-setup-guide-05.png[retail-sap-s4hana-setup-guide-05.png,799] + + . For outbound communication, select the previously-created user and configure the *Product Master - Replicate from SAP S/4HANA Cloud to Client* and include the following settings. Make sure to note the Path (`/sap/bc/srt/scs/sap/productmdmbulkreplicaterequest`) because we will use this path to configure the Mule application SOAP endpoint: ** Set the Service status to *Active* @@ -34,11 +34,11 @@ image:https://www.mulesoft.com/ext/solutions/draft/images/retail-sap-s4hana-setu ** Replication model = I (Initial) ** The Output Mode = D (Direct). + + -image:https://www.mulesoft.com/ext/solutions/draft/images/retail-sap-s4hana-setup-guide-06.png[retail-sap-s4hana-setup-guide-06.png,799] + +image:https://www.mulesoft.com/ext/solutions/images/retail-sap-s4hana-setup-guide-06.png[retail-sap-s4hana-setup-guide-06.png,799] + + -image:https://www.mulesoft.com/ext/solutions/draft/images/retail-sap-s4hana-setup-guide-07.png[retail-sap-s4hana-setup-guide-07.png,799] + +image:https://www.mulesoft.com/ext/solutions/images/retail-sap-s4hana-setup-guide-07.png[retail-sap-s4hana-setup-guide-07.png,799] + + -image:https://www.mulesoft.com/ext/solutions/draft/images/retail-sap-s4hana-setup-guide-08.png[retail-sap-s4hana-setup-guide-08.png,799] + +image:https://www.mulesoft.com/ext/solutions/images/retail-sap-s4hana-setup-guide-08.png[retail-sap-s4hana-setup-guide-08.png,799] + + . Save it. All configurations at S/4HANA Cloud side are finished and you will be able to download the WSDL that contains the metadata to import into the S/4HANA Cloud SOAP Connector into the Mule application. @@ -48,38 +48,38 @@ The following example describes how to create a Mule application using the Outbo . Create a Mule project and add the appropriate connector from Exchange to the Mule Palette: + + -image:https://www.mulesoft.com/ext/solutions/draft/images/retail-sap-s4hana-setup-guide-09.png[retail-sap-s4hana-setup-guide-09.png,799] + +image:https://www.mulesoft.com/ext/solutions/images/retail-sap-s4hana-setup-guide-09.png[retail-sap-s4hana-setup-guide-09.png,799] + + . Add and configure the *Outbound Message Listener* to the canvas: + + -image:https://www.mulesoft.com/ext/solutions/draft/images/retail-sap-s4hana-setup-guide-10.png[retail-sap-s4hana-setup-guide-10.png,799] + +image:https://www.mulesoft.com/ext/solutions/images/retail-sap-s4hana-setup-guide-10.png[retail-sap-s4hana-setup-guide-10.png,799] + + . Add the corresponding WSDL path to the WSDL you downloaded from S/4HANA Cloud and create the HTTP listener configuration: + + -image:https://www.mulesoft.com/ext/solutions/draft/images/retail-sap-s4hana-setup-guide-11.png[retail-sap-s4hana-setup-guide-11.png,799] + +image:https://www.mulesoft.com/ext/solutions/images/retail-sap-s4hana-setup-guide-11.png[retail-sap-s4hana-setup-guide-11.png,799] + + -image:https://www.mulesoft.com/ext/solutions/draft/images/retail-sap-s4hana-setup-guide-12.png[retail-sap-s4hana-setup-guide-12.png,799] + +image:https://www.mulesoft.com/ext/solutions/images/retail-sap-s4hana-setup-guide-12.png[retail-sap-s4hana-setup-guide-12.png,799] + + _*Note*: we are using no authentication on the Mule Application, so we used the Insecure option for the Trust Store Configuration. In the Keystore configuration, we used a test Keystore, which is mandatory for HTTPS communication:_ + + -image:https://www.mulesoft.com/ext/solutions/draft/images/retail-sap-s4hana-setup-guide-13.png[retail-sap-s4hana-setup-guide-13.png,799] + +image:https://www.mulesoft.com/ext/solutions/images/retail-sap-s4hana-setup-guide-13.png[retail-sap-s4hana-setup-guide-13.png,799] + + . Select the Message type that the connector expects to receive from SAP (the connector reads the metadata from the WSDL we configured): + + -image:https://www.mulesoft.com/ext/solutions/draft/images/retail-sap-s4hana-setup-guide-14.png[retail-sap-s4hana-setup-guide-14.png,799] + +image:https://www.mulesoft.com/ext/solutions/images/retail-sap-s4hana-setup-guide-14.png[retail-sap-s4hana-setup-guide-14.png,799] + + . On the Responses tab, use the status Code "202" and the Reason-Phrase "Accepted" because we want to send the same status that S/4HANA Cloud will send if the service invocation results OK. No payload will be returned as a response--just the Status code and Reason-phrase: + + -image:https://www.mulesoft.com/ext/solutions/draft/images/retail-sap-s4hana-setup-guide-15.png[retail-sap-s4hana-setup-guide-15.png,799] + +image:https://www.mulesoft.com/ext/solutions/images/retail-sap-s4hana-setup-guide-15.png[retail-sap-s4hana-setup-guide-15.png,799] + + . Use a *Logger* component to log the inbound XML payload: + + -image:https://www.mulesoft.com/ext/solutions/draft/images/retail-sap-s4hana-setup-guide-16.png[retail-sap-s4hana-setup-guide-16.png,799] + +image:https://www.mulesoft.com/ext/solutions/images/retail-sap-s4hana-setup-guide-16.png[retail-sap-s4hana-setup-guide-16.png,799] + + _The Mule flow should look like the following:_ + + -image:https://www.mulesoft.com/ext/solutions/draft/images/retail-sap-s4hana-setup-guide-17.png[retail-sap-s4hana-setup-guide-17.png,399] + +image:https://www.mulesoft.com/ext/solutions/images/retail-sap-s4hana-setup-guide-17.png[retail-sap-s4hana-setup-guide-17.png,399] + + . Deploy the application to Cloudhub. You're now ready to test the scenario. @@ -89,35 +89,35 @@ To test the scenario: . Create the following. You only need to create a material in the corresponding Fiori app of S/4HANA Cloud: + + -image:https://www.mulesoft.com/ext/solutions/draft/images/retail-sap-s4hana-setup-guide-18.png[retail-sap-s4hana-setup-guide-18.png,599] + +image:https://www.mulesoft.com/ext/solutions/images/retail-sap-s4hana-setup-guide-18.png[retail-sap-s4hana-setup-guide-18.png,599] + + -image:https://www.mulesoft.com/ext/solutions/draft/images/retail-sap-s4hana-setup-guide-19.png[retail-sap-s4hana-setup-guide-19.png,799] + +image:https://www.mulesoft.com/ext/solutions/images/retail-sap-s4hana-setup-guide-19.png[retail-sap-s4hana-setup-guide-19.png,799] + + -image:https://www.mulesoft.com/ext/solutions/draft/images/retail-sap-s4hana-setup-guide-20.png[retail-sap-s4hana-setup-guide-20.png,799] + +image:https://www.mulesoft.com/ext/solutions/images/retail-sap-s4hana-setup-guide-20.png[retail-sap-s4hana-setup-guide-20.png,799] + + -image:https://www.mulesoft.com/ext/solutions/draft/images/retail-sap-s4hana-setup-guide-21.png[retail-sap-s4hana-setup-guide-21.png,799] + +image:https://www.mulesoft.com/ext/solutions/images/retail-sap-s4hana-setup-guide-21.png[retail-sap-s4hana-setup-guide-21.png,799] + + _After you save the new material, you should see the following confirmation in S/4HANA Cloud:_ + + -image:https://www.mulesoft.com/ext/solutions/draft/images/retail-sap-s4hana-setup-guide-22.png[retail-sap-s4hana-setup-guide-22.png,399] + +image:https://www.mulesoft.com/ext/solutions/images/retail-sap-s4hana-setup-guide-22.png[retail-sap-s4hana-setup-guide-22.png,399] + + _The following shows the XML message received at the Mule application at the Runtime Manager on Cloudhub:_ + + -image:https://www.mulesoft.com/ext/solutions/draft/images/retail-sap-s4hana-setup-guide-23.png[retail-sap-s4hana-setup-guide-23.png,799] + +image:https://www.mulesoft.com/ext/solutions/images/retail-sap-s4hana-setup-guide-23.png[retail-sap-s4hana-setup-guide-23.png,799] + + . See the sent message in the Message Dashboard Fiori Application: + + -image:https://www.mulesoft.com/ext/solutions/draft/images/retail-sap-s4hana-setup-guide-24.png[retail-sap-s4hana-setup-guide-24.png,799] + +image:https://www.mulesoft.com/ext/solutions/images/retail-sap-s4hana-setup-guide-24.png[retail-sap-s4hana-setup-guide-24.png,799] + + . Select the date: + + -image:https://www.mulesoft.com/ext/solutions/draft/images/retail-sap-s4hana-setup-guide-25.png[retail-sap-s4hana-setup-guide-25.png,399] + +image:https://www.mulesoft.com/ext/solutions/images/retail-sap-s4hana-setup-guide-25.png[retail-sap-s4hana-setup-guide-25.png,399] + + . Search under *CMD:Product Integration - /CMDPR → Product Replication to Client via Service - PRDREQ_OUT/00001 namespace*: + + -image:https://www.mulesoft.com/ext/solutions/draft/images/retail-sap-s4hana-setup-guide-26.png[retail-sap-s4hana-setup-guide-26.png,799] + +image:https://www.mulesoft.com/ext/solutions/images/retail-sap-s4hana-setup-guide-26.png[retail-sap-s4hana-setup-guide-26.png,799] + + -image:https://www.mulesoft.com/ext/solutions/draft/images/retail-sap-s4hana-setup-guide-27.png[retail-sap-s4hana-setup-guide-27.png,799] +image:https://www.mulesoft.com/ext/solutions/images/retail-sap-s4hana-setup-guide-27.png[retail-sap-s4hana-setup-guide-27.png,799] == S/4HANA customization guide diff --git a/financial-services/1.10/modules/ROOT/pages/_partials/custom-components-fragment.adoc b/financial-services/1.10/modules/ROOT/pages/_partials/custom-components-fragment.adoc index 4d7df4589..362076363 100644 --- a/financial-services/1.10/modules/ROOT/pages/_partials/custom-components-fragment.adoc +++ b/financial-services/1.10/modules/ROOT/pages/_partials/custom-components-fragment.adoc @@ -2,9 +2,9 @@ The following non-application components provide additional functionality in sup [cols="70,30",width=100%] |=== -| FINS Common Resources | https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fins-common-resources-src[ Source^] -| FINS Financial Account Sync Lightning Web Component | https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fins-financial-account-sync-lwc-src[ Source^] -| FINS Fraud Analysis Application | https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fins-fraud-analysis-application-src[ Source^] -| FINS Open Banking Library | https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fins-openbanking-library[ Source^] -| FINS Payments Frontend Web UI | https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fins-payments-frontend-webui-src[ Source^] +| FINS Common Resources | https://anypoint.mulesoft.com/exchange/org.mule.examples/fins-common-resources-src[ Source^] +| FINS Financial Account Sync Lightning Web Component | https://anypoint.mulesoft.com/exchange/org.mule.examples/fins-financial-account-sync-lwc-src[ Source^] +| FINS Fraud Analysis Application | https://anypoint.mulesoft.com/exchange/org.mule.examples/fins-fraud-analysis-application-src[ Source^] +| FINS Open Banking Library | https://anypoint.mulesoft.com/exchange/org.mule.examples/fins-openbanking-library[ Source^] +| FINS Payments Frontend Web UI | https://anypoint.mulesoft.com/exchange/org.mule.examples/fins-payments-frontend-webui-src[ Source^] |=== diff --git a/financial-services/1.10/modules/ROOT/pages/_partials/experience-apis-fragment.adoc b/financial-services/1.10/modules/ROOT/pages/_partials/experience-apis-fragment.adoc index 7a68e4bb1..0b302dce0 100644 --- a/financial-services/1.10/modules/ROOT/pages/_partials/experience-apis-fragment.adoc +++ b/financial-services/1.10/modules/ROOT/pages/_partials/experience-apis-fragment.adoc @@ -2,15 +2,15 @@ The following APIs are provided for use by external systems to interact with fun [cols="40,30,30",width=100%] |=== -|FINS DocuSign Experience API | https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fins-docusign-exp-api-spec[API Specification^] | https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fins-docusign-exp-api[Implementation Template^] -|FINS Jack Henry Events Experience API | | https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fins-jackhenry-events-exp-api[Implementation Template^] -|FINS Mobile Experience API | https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fins-mobile-exp-api-spec[API Specification^] | https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fins-mobile-exp-api[Implementation Template^] -|FINS Open Banking Accounts Experience API | https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fins-openbanking-accounts-exp-api-spec[API Specification^] | https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fins-openbanking-accounts-exp-api[Implementation Template^] -|FINS Open Banking ASPSP Experience API | https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fins-openbanking-aspsp-exp-api-spec[API Specification^] | https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fins-openbanking-aspsp-exp-api[Implementation Template^] -|FINS Open Banking PISP Domestic Experience API | https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fins-openbanking-pisp-dom-exp-api-spec[API Specification^] | https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fins-openbanking-pisp-dom-exp-api[Implementation Template^] -|FINS Open Banking PISP International Experience API | https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fins-openbanking-pisp-intl-exp-api-spec[API Specification^] | https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fins-openbanking-pisp-intl-exp-api[Implementation Template^] -|FINS Payments Web UI Experience API | https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fins-payments-webui-exp-api-spec[API Specification^] | https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fins-payments-webui-exp-api[Implementation Template^] -|FINS Salesforce Financial Experience API | https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fins-salesforce-financial-exp-api-spec[API Specification^] | https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fins-salesforce-financial-exp-api[Implementation Template^] -|FINS Salesforce Insurance Experience API | https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fins-salesforce-insurance-exp-api-spec[API Specification^] | https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fins-salesforce-insurance-exp-api[Implementation Template^] -|FINS Salesforce Wealth Experience API | https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fins-salesforce-wealth-exp-api-spec[API Specification^] | https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fins-salesforce-wealth-exp-api[Implementation Template^] +|FINS DocuSign Experience API | https://anypoint.mulesoft.com/exchange/org.mule.examples/fins-docusign-exp-api-spec[API Specification^] | https://anypoint.mulesoft.com/exchange/org.mule.examples/fins-docusign-exp-api[Implementation Template^] +|FINS Jack Henry Events Experience API | | https://anypoint.mulesoft.com/exchange/org.mule.examples/fins-jackhenry-events-exp-api[Implementation Template^] +|FINS Mobile Experience API | https://anypoint.mulesoft.com/exchange/org.mule.examples/fins-mobile-exp-api-spec[API Specification^] | https://anypoint.mulesoft.com/exchange/org.mule.examples/fins-mobile-exp-api[Implementation Template^] +|FINS Open Banking Accounts Experience API | https://anypoint.mulesoft.com/exchange/org.mule.examples/fins-openbanking-accounts-exp-api-spec[API Specification^] | https://anypoint.mulesoft.com/exchange/org.mule.examples/fins-openbanking-accounts-exp-api[Implementation Template^] +|FINS Open Banking ASPSP Experience API | https://anypoint.mulesoft.com/exchange/org.mule.examples/fins-openbanking-aspsp-exp-api-spec[API Specification^] | https://anypoint.mulesoft.com/exchange/org.mule.examples/fins-openbanking-aspsp-exp-api[Implementation Template^] +|FINS Open Banking PISP Domestic Experience API | https://anypoint.mulesoft.com/exchange/org.mule.examples/fins-openbanking-pisp-dom-exp-api-spec[API Specification^] | https://anypoint.mulesoft.com/exchange/org.mule.examples/fins-openbanking-pisp-dom-exp-api[Implementation Template^] +|FINS Open Banking PISP International Experience API | https://anypoint.mulesoft.com/exchange/org.mule.examples/fins-openbanking-pisp-intl-exp-api-spec[API Specification^] | https://anypoint.mulesoft.com/exchange/org.mule.examples/fins-openbanking-pisp-intl-exp-api[Implementation Template^] +|FINS Payments Web UI Experience API | https://anypoint.mulesoft.com/exchange/org.mule.examples/fins-payments-webui-exp-api-spec[API Specification^] | https://anypoint.mulesoft.com/exchange/org.mule.examples/fins-payments-webui-exp-api[Implementation Template^] +|FINS Salesforce Financial Experience API | https://anypoint.mulesoft.com/exchange/org.mule.examples/fins-salesforce-financial-exp-api-spec[API Specification^] | https://anypoint.mulesoft.com/exchange/org.mule.examples/fins-salesforce-financial-exp-api[Implementation Template^] +|FINS Salesforce Insurance Experience API | https://anypoint.mulesoft.com/exchange/org.mule.examples/fins-salesforce-insurance-exp-api-spec[API Specification^] | https://anypoint.mulesoft.com/exchange/org.mule.examples/fins-salesforce-insurance-exp-api[Implementation Template^] +|FINS Salesforce Wealth Experience API | https://anypoint.mulesoft.com/exchange/org.mule.examples/fins-salesforce-wealth-exp-api-spec[API Specification^] | https://anypoint.mulesoft.com/exchange/org.mule.examples/fins-salesforce-wealth-exp-api[Implementation Template^] |=== diff --git a/financial-services/1.10/modules/ROOT/pages/_partials/listeners-fragment.adoc b/financial-services/1.10/modules/ROOT/pages/_partials/listeners-fragment.adoc index ac8366b48..6cf8a79c1 100644 --- a/financial-services/1.10/modules/ROOT/pages/_partials/listeners-fragment.adoc +++ b/financial-services/1.10/modules/ROOT/pages/_partials/listeners-fragment.adoc @@ -2,9 +2,9 @@ The following applications listen for events published by external systems and i [cols="70,30",width=100%] |=== -| FINS Payments ACH Listener | https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fins-payments-ach-listener[Source^] -| FINS Payments Fedwire Listener | https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fins-payments-fedwire-listener[Source^] -| FINS Payments SWIFT Listener | https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fins-payments-swift-listener[Source^] -| FINS Salesforce Marketing Listener | https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fins-salesforce-marketing-listener[Source^] -| FINS Salesforce Topic Listener | https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fins-salesforce-topic-listener[Source^] +| FINS Payments ACH Listener | https://anypoint.mulesoft.com/exchange/org.mule.examples/fins-payments-ach-listener[Source^] +| FINS Payments Fedwire Listener | https://anypoint.mulesoft.com/exchange/org.mule.examples/fins-payments-fedwire-listener[Source^] +| FINS Payments SWIFT Listener | https://anypoint.mulesoft.com/exchange/org.mule.examples/fins-payments-swift-listener[Source^] +| FINS Salesforce Marketing Listener | https://anypoint.mulesoft.com/exchange/org.mule.examples/fins-salesforce-marketing-listener[Source^] +| FINS Salesforce Topic Listener | https://anypoint.mulesoft.com/exchange/org.mule.examples/fins-salesforce-topic-listener[Source^] |=== diff --git a/financial-services/1.10/modules/ROOT/pages/_partials/process-apis-fragment.adoc b/financial-services/1.10/modules/ROOT/pages/_partials/process-apis-fragment.adoc index 74d34e2d0..bc4a0532d 100644 --- a/financial-services/1.10/modules/ROOT/pages/_partials/process-apis-fragment.adoc +++ b/financial-services/1.10/modules/ROOT/pages/_partials/process-apis-fragment.adoc @@ -2,22 +2,22 @@ The following APIs represent the core business processes that orchestrate the FI [cols="40,30,30",width=100%] |=== -| FINS Bank Accounts Process API | https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fins-bank-accounts-prc-api-spec[API Specification^] | https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fins-bank-accounts-prc-api[Implementation Template^] -| FINS Bank Loans Process API | https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fins-bank-loans-prc-api-spec[API Specification^] | https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fins-bank-loans-prc-api[Implementation Template^] -| FINS Core Banking Poller Process API | https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fins-core-banking-poller-prc-api-spec[API Specification^] | https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fins-core-banking-poller-prc-api[Implementation Template^] -| FINS Credit Card Poller Process API | https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fins-creditcard-poller-prc-api-spec[API Specification^] | https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fins-creditcard-poller-prc-api[Implementation Template^] -| FINS Customer Addresses Process API | https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fins-customer-addresses-prc-api-spec[API Specification^] | https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fins-customer-addresses-prc-api[Implementation Template^] -| FINS Customer Leads Process API | https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fins-customer-leads-prc-api-spec[API Specification^] | https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fins-customer-leads-prc-api[Implementation Template^] -| FINS Customers Process API | https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fins-customers-prc-api-spec[API Specification^] | https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fins-customers-prc-api[Implementation Template^] -| FINS Marketing Poller Process API | https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fins-marketing-poller-prc-api-spec[API Specification^] | https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fins-marketing-poller-prc-api[Implementation Template^] -| FINS Payments Initiation Process API | https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fins-bian-paymntinitiation-prc-api-spec[API Specification^] | https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fins-payments-initiation-prc-api[Implementation Template^] -| FINS Payments InterBank International Execution Process API | https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fins-bian-paymntexecution-prc-api-spec[API Specification^] | https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fins-payments-interbank-international-execution-prc-api[Implementation Template^] -| FINS Payments InterBank National Execution Process API | https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fins-bian-paymntexecution-prc-api-spec[API Specification^] | https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fins-payments-interbank-national-execution-prc-api[Implementation Template^] -| FINS Payments IntraBank International Execution Process API | https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fins-bian-paymntexecution-prc-api-spec[API Specification^] | https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fins-payments-intrabank-international-execution-prc-api[Implementation Template^] -| FINS Payments IntraBank National Execution Process API | https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fins-bian-paymntexecution-prc-api-spec[API Specification^] | https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fins-payments-intrabank-national-execution-prc-api[Implementation Template^] -| FINS Payments Order Process API | https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fins-bian-paymntorder-prc-api-spec[API Specification^] | https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fins-payments-order-prc-api[Implementation Template^] -| FINS Payments Remittances Process API | https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fins-bian-paymntexecution-prc-api-spec[API Specification^] | https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fins-payments-remittances-prc-api[Implementation Template^] -| FINS Payments Router Process API | https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fins-payments-router-prc-api-spec[API Specification^] | https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fins-payments-router-prc-api[Implementation Template^] -| FINS Payments Simulator Process API | https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fins-payments-simulator-prc-api-spec[API Specification^] | https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fins-payments-simulator-prc-api[Implementation Template^] -| FINS Reconciliation Process API | https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fins-reconciliation-prc-api-spec[API Specification^] | https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fins-reconciliation-prc-api[Implementation Template^] +| FINS Bank Accounts Process API | https://anypoint.mulesoft.com/exchange/org.mule.examples/fins-bank-accounts-prc-api-spec[API Specification^] | https://anypoint.mulesoft.com/exchange/org.mule.examples/fins-bank-accounts-prc-api[Implementation Template^] +| FINS Bank Loans Process API | https://anypoint.mulesoft.com/exchange/org.mule.examples/fins-bank-loans-prc-api-spec[API Specification^] | https://anypoint.mulesoft.com/exchange/org.mule.examples/fins-bank-loans-prc-api[Implementation Template^] +| FINS Core Banking Poller Process API | https://anypoint.mulesoft.com/exchange/org.mule.examples/fins-core-banking-poller-prc-api-spec[API Specification^] | https://anypoint.mulesoft.com/exchange/org.mule.examples/fins-core-banking-poller-prc-api[Implementation Template^] +| FINS Credit Card Poller Process API | https://anypoint.mulesoft.com/exchange/org.mule.examples/fins-creditcard-poller-prc-api-spec[API Specification^] | https://anypoint.mulesoft.com/exchange/org.mule.examples/fins-creditcard-poller-prc-api[Implementation Template^] +| FINS Customer Addresses Process API | https://anypoint.mulesoft.com/exchange/org.mule.examples/fins-customer-addresses-prc-api-spec[API Specification^] | https://anypoint.mulesoft.com/exchange/org.mule.examples/fins-customer-addresses-prc-api[Implementation Template^] +| FINS Customer Leads Process API | https://anypoint.mulesoft.com/exchange/org.mule.examples/fins-customer-leads-prc-api-spec[API Specification^] | https://anypoint.mulesoft.com/exchange/org.mule.examples/fins-customer-leads-prc-api[Implementation Template^] +| FINS Customers Process API | https://anypoint.mulesoft.com/exchange/org.mule.examples/fins-customers-prc-api-spec[API Specification^] | https://anypoint.mulesoft.com/exchange/org.mule.examples/fins-customers-prc-api[Implementation Template^] +| FINS Marketing Poller Process API | https://anypoint.mulesoft.com/exchange/org.mule.examples/fins-marketing-poller-prc-api-spec[API Specification^] | https://anypoint.mulesoft.com/exchange/org.mule.examples/fins-marketing-poller-prc-api[Implementation Template^] +| FINS Payments Initiation Process API | https://anypoint.mulesoft.com/exchange/org.mule.examples/fins-bian-paymntinitiation-prc-api-spec[API Specification^] | https://anypoint.mulesoft.com/exchange/org.mule.examples/fins-payments-initiation-prc-api[Implementation Template^] +| FINS Payments InterBank International Execution Process API | https://anypoint.mulesoft.com/exchange/org.mule.examples/fins-bian-paymntexecution-prc-api-spec[API Specification^] | https://anypoint.mulesoft.com/exchange/org.mule.examples/fins-payments-interbank-international-execution-prc-api[Implementation Template^] +| FINS Payments InterBank National Execution Process API | https://anypoint.mulesoft.com/exchange/org.mule.examples/fins-bian-paymntexecution-prc-api-spec[API Specification^] | https://anypoint.mulesoft.com/exchange/org.mule.examples/fins-payments-interbank-national-execution-prc-api[Implementation Template^] +| FINS Payments IntraBank International Execution Process API | https://anypoint.mulesoft.com/exchange/org.mule.examples/fins-bian-paymntexecution-prc-api-spec[API Specification^] | https://anypoint.mulesoft.com/exchange/org.mule.examples/fins-payments-intrabank-international-execution-prc-api[Implementation Template^] +| FINS Payments IntraBank National Execution Process API | https://anypoint.mulesoft.com/exchange/org.mule.examples/fins-bian-paymntexecution-prc-api-spec[API Specification^] | https://anypoint.mulesoft.com/exchange/org.mule.examples/fins-payments-intrabank-national-execution-prc-api[Implementation Template^] +| FINS Payments Order Process API | https://anypoint.mulesoft.com/exchange/org.mule.examples/fins-bian-paymntorder-prc-api-spec[API Specification^] | https://anypoint.mulesoft.com/exchange/org.mule.examples/fins-payments-order-prc-api[Implementation Template^] +| FINS Payments Remittances Process API | https://anypoint.mulesoft.com/exchange/org.mule.examples/fins-bian-paymntexecution-prc-api-spec[API Specification^] | https://anypoint.mulesoft.com/exchange/org.mule.examples/fins-payments-remittances-prc-api[Implementation Template^] +| FINS Payments Router Process API | https://anypoint.mulesoft.com/exchange/org.mule.examples/fins-payments-router-prc-api-spec[API Specification^] | https://anypoint.mulesoft.com/exchange/org.mule.examples/fins-payments-router-prc-api[Implementation Template^] +| FINS Payments Simulator Process API | https://anypoint.mulesoft.com/exchange/org.mule.examples/fins-payments-simulator-prc-api-spec[API Specification^] | https://anypoint.mulesoft.com/exchange/org.mule.examples/fins-payments-simulator-prc-api[Implementation Template^] +| FINS Reconciliation Process API | https://anypoint.mulesoft.com/exchange/org.mule.examples/fins-reconciliation-prc-api-spec[API Specification^] | https://anypoint.mulesoft.com/exchange/org.mule.examples/fins-reconciliation-prc-api[Implementation Template^] |=== diff --git a/financial-services/1.10/modules/ROOT/pages/_partials/system-apis-fragment.adoc b/financial-services/1.10/modules/ROOT/pages/_partials/system-apis-fragment.adoc index 3e25513b6..f51eef764 100644 --- a/financial-services/1.10/modules/ROOT/pages/_partials/system-apis-fragment.adoc +++ b/financial-services/1.10/modules/ROOT/pages/_partials/system-apis-fragment.adoc @@ -2,29 +2,29 @@ The following APIs are used to access and manage data in various external system [cols="40,30,30",width=100%] |=== -| FINS Address Validation System API | https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fins-address-validation-sys-api-spec[API Specification^] | https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fins-address-validation-sys-api[Implementation Template^] -| FINS Blockchain System API | https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fins-blockchain-sys-api-spec[API Specification^] | https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fins-blockchain-sys-api[Implementation Template^] -| FINS Core Banking Accounts System API | https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fins-core-banking-accounts-sys-api-spec[API Specification^] | https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fins-core-banking-accounts-sys-api[Implementation Template^] -| FINS Core Banking Customers System API | https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fins-core-banking-customers-sys-api-spec[API Specification^] | https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fins-core-banking-customers-sys-api[Implementation Template^] -| FINS CoreLogic System API | https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fins-corelogic-sys-api-spec[API Specification^] | https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fins-corelogic-sys-api[Implementation Template^] -| FINS Credit Bureau System API | https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fins-credit-bureau-sys-api-spec[API Specification^] | https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fins-credit-bureau-sys-api[Implementation Template^] -| FINS Credit Card System API | https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fins-creditcard-sys-api-spec[API Specification^] | https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fins-creditcard-sys-api[Implementation Template^] -| FINS Databricks Engagements System API | https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fins-engagements-datacloud-sys-api-spec/[API Specification] | https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fins-databricks-engagements-sys-api/[Implementation Template] -| FINS DocuSign System API | https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fins-docusign-sys-api-spec[API Specification^] | https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fins-docusign-sys-api[Implementation Template^] -| FINS Financial Institutions System API | https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fins-financial-institutions-sys-api-spec[API Specification^] | https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fins-financial-institutions-sys-api[Implementation Template^] -| FINS Foreign Exchange System API | https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fins-foreign-exchange-sys-api-spec[API Specification^] | https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fins-foreign-exchange-sys-api[Implementation Template^] -| FINS Fraud Analysis System API | https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fins-fraud-analysis-sys-api-spec[API Specification^] | https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fins-fraud-analysis-sys-api[Implementation Template^] -| FINS Loan Origination System API | https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fins-loan-origination-sys-api-spec[API Specification^] | https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fins-loan-origination-sys-api[Implementation Template^] -| FINS Payments ACH System API | https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fins-payments-ach-sys-api-spec[API Specification^] | https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fins-payments-ach-sys-api[Implementation Template^] -| FINS Payments Fedwire System API | https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fins-payments-fedwire-sys-api-spec[API Specification^] | https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fins-payments-fedwire-sys-api[Implementation Template^] -| FINS Payments SWIFT System API | https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fins-payments-swift-sys-api-spec[API Specification^] | https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fins-payments-swift-sys-api[Implementation Template^] -| Salesforce CDP System API | https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fins-salesforce-cdp-sys-api-spec/[API Specification] | https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fins-salesforce-cdp-sys-api/[Implementation Template] -| FINS Salesforce Customers System API | https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fins-salesforce-customers-sys-api-spec[API Specification^] | https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fins-salesforce-customers-sys-api[Implementation Template^] -| FINS Salesforce Financial System API | https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fins-salesforce-financial-sys-api-spec[API Specification^] | https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fins-salesforce-financial-sys-api[Implementation Template^] -| FINS Salesforce Insurance System API | https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fins-salesforce-insurance-sys-api-spec[API Specification^] | https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fins-salesforce-insurance-sys-api[Implementation Template^] -| FINS Salesforce Marketing System API | https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/rcg-salesforce-marketing-sys-api-spec[API Specification^] | https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fins-salesforce-marketing-sys-api[Implementation Template^] -| SilverLake Accounts System API | https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fins-core-banking-accounts-sys-api-spec/[API Specification] | https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fins-silverlake-accounts-sys-api/[Implementation Template] -| SilverLake Customers System API | https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fins-core-banking-customers-sys-api-spec/[API Specification] | https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fins-silverlake-customers-sys-api/[Implementation Template] -| Snowflake Financial System API | https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fins-financial-datacloud-sys-api-spec/[API Specification] | https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fins-snowflake-financial-sys-api/[Implementation Template] -| Synergy Documents System API | https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fins-core-banking-documents-sys-api-spec/[API Specification] | https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fins-synergy-documents-sys-api/[Implementation Template] +| FINS Address Validation System API | https://anypoint.mulesoft.com/exchange/org.mule.examples/fins-address-validation-sys-api-spec[API Specification^] | https://anypoint.mulesoft.com/exchange/org.mule.examples/fins-address-validation-sys-api[Implementation Template^] +| FINS Blockchain System API | https://anypoint.mulesoft.com/exchange/org.mule.examples/fins-blockchain-sys-api-spec[API Specification^] | https://anypoint.mulesoft.com/exchange/org.mule.examples/fins-blockchain-sys-api[Implementation Template^] +| FINS Core Banking Accounts System API | https://anypoint.mulesoft.com/exchange/org.mule.examples/fins-core-banking-accounts-sys-api-spec[API Specification^] | https://anypoint.mulesoft.com/exchange/org.mule.examples/fins-core-banking-accounts-sys-api[Implementation Template^] +| FINS Core Banking Customers System API | https://anypoint.mulesoft.com/exchange/org.mule.examples/fins-core-banking-customers-sys-api-spec[API Specification^] | https://anypoint.mulesoft.com/exchange/org.mule.examples/fins-core-banking-customers-sys-api[Implementation Template^] +| FINS CoreLogic System API | https://anypoint.mulesoft.com/exchange/org.mule.examples/fins-corelogic-sys-api-spec[API Specification^] | https://anypoint.mulesoft.com/exchange/org.mule.examples/fins-corelogic-sys-api[Implementation Template^] +| FINS Credit Bureau System API | https://anypoint.mulesoft.com/exchange/org.mule.examples/fins-credit-bureau-sys-api-spec[API Specification^] | https://anypoint.mulesoft.com/exchange/org.mule.examples/fins-credit-bureau-sys-api[Implementation Template^] +| FINS Credit Card System API | https://anypoint.mulesoft.com/exchange/org.mule.examples/fins-creditcard-sys-api-spec[API Specification^] | https://anypoint.mulesoft.com/exchange/org.mule.examples/fins-creditcard-sys-api[Implementation Template^] +| FINS Databricks Engagements System API | https://anypoint.mulesoft.com/exchange/org.mule.examples/fins-engagements-datacloud-sys-api-spec/[API Specification] | https://anypoint.mulesoft.com/exchange/org.mule.examples/fins-databricks-engagements-sys-api/[Implementation Template] +| FINS DocuSign System API | https://anypoint.mulesoft.com/exchange/org.mule.examples/fins-docusign-sys-api-spec[API Specification^] | https://anypoint.mulesoft.com/exchange/org.mule.examples/fins-docusign-sys-api[Implementation Template^] +| FINS Financial Institutions System API | https://anypoint.mulesoft.com/exchange/org.mule.examples/fins-financial-institutions-sys-api-spec[API Specification^] | https://anypoint.mulesoft.com/exchange/org.mule.examples/fins-financial-institutions-sys-api[Implementation Template^] +| FINS Foreign Exchange System API | https://anypoint.mulesoft.com/exchange/org.mule.examples/fins-foreign-exchange-sys-api-spec[API Specification^] | https://anypoint.mulesoft.com/exchange/org.mule.examples/fins-foreign-exchange-sys-api[Implementation Template^] +| FINS Fraud Analysis System API | https://anypoint.mulesoft.com/exchange/org.mule.examples/fins-fraud-analysis-sys-api-spec[API Specification^] | https://anypoint.mulesoft.com/exchange/org.mule.examples/fins-fraud-analysis-sys-api[Implementation Template^] +| FINS Loan Origination System API | https://anypoint.mulesoft.com/exchange/org.mule.examples/fins-loan-origination-sys-api-spec[API Specification^] | https://anypoint.mulesoft.com/exchange/org.mule.examples/fins-loan-origination-sys-api[Implementation Template^] +| FINS Payments ACH System API | https://anypoint.mulesoft.com/exchange/org.mule.examples/fins-payments-ach-sys-api-spec[API Specification^] | https://anypoint.mulesoft.com/exchange/org.mule.examples/fins-payments-ach-sys-api[Implementation Template^] +| FINS Payments Fedwire System API | https://anypoint.mulesoft.com/exchange/org.mule.examples/fins-payments-fedwire-sys-api-spec[API Specification^] | https://anypoint.mulesoft.com/exchange/org.mule.examples/fins-payments-fedwire-sys-api[Implementation Template^] +| FINS Payments SWIFT System API | https://anypoint.mulesoft.com/exchange/org.mule.examples/fins-payments-swift-sys-api-spec[API Specification^] | https://anypoint.mulesoft.com/exchange/org.mule.examples/fins-payments-swift-sys-api[Implementation Template^] +| Salesforce CDP System API | https://anypoint.mulesoft.com/exchange/org.mule.examples/fins-salesforce-cdp-sys-api-spec/[API Specification] | https://anypoint.mulesoft.com/exchange/org.mule.examples/fins-salesforce-cdp-sys-api/[Implementation Template] +| FINS Salesforce Customers System API | https://anypoint.mulesoft.com/exchange/org.mule.examples/fins-salesforce-customers-sys-api-spec[API Specification^] | https://anypoint.mulesoft.com/exchange/org.mule.examples/fins-salesforce-customers-sys-api[Implementation Template^] +| FINS Salesforce Financial System API | https://anypoint.mulesoft.com/exchange/org.mule.examples/fins-salesforce-financial-sys-api-spec[API Specification^] | https://anypoint.mulesoft.com/exchange/org.mule.examples/fins-salesforce-financial-sys-api[Implementation Template^] +| FINS Salesforce Insurance System API | https://anypoint.mulesoft.com/exchange/org.mule.examples/fins-salesforce-insurance-sys-api-spec[API Specification^] | https://anypoint.mulesoft.com/exchange/org.mule.examples/fins-salesforce-insurance-sys-api[Implementation Template^] +| FINS Salesforce Marketing System API | https://anypoint.mulesoft.com/exchange/org.mule.examples/rcg-salesforce-marketing-sys-api-spec[API Specification^] | https://anypoint.mulesoft.com/exchange/org.mule.examples/fins-salesforce-marketing-sys-api[Implementation Template^] +| SilverLake Accounts System API | https://anypoint.mulesoft.com/exchange/org.mule.examples/fins-core-banking-accounts-sys-api-spec/[API Specification] | https://anypoint.mulesoft.com/exchange/org.mule.examples/fins-silverlake-accounts-sys-api/[Implementation Template] +| SilverLake Customers System API | https://anypoint.mulesoft.com/exchange/org.mule.examples/fins-core-banking-customers-sys-api-spec/[API Specification] | https://anypoint.mulesoft.com/exchange/org.mule.examples/fins-silverlake-customers-sys-api/[Implementation Template] +| Snowflake Financial System API | https://anypoint.mulesoft.com/exchange/org.mule.examples/fins-financial-datacloud-sys-api-spec/[API Specification] | https://anypoint.mulesoft.com/exchange/org.mule.examples/fins-snowflake-financial-sys-api/[Implementation Template] +| Synergy Documents System API | https://anypoint.mulesoft.com/exchange/org.mule.examples/fins-core-banking-documents-sys-api-spec/[API Specification] | https://anypoint.mulesoft.com/exchange/org.mule.examples/fins-synergy-documents-sys-api/[Implementation Template] |=== diff --git a/financial-services/1.10/modules/ROOT/pages/anypointmq-setup-guide.adoc b/financial-services/1.10/modules/ROOT/pages/anypointmq-setup-guide.adoc index c8b239d96..12e680ff3 100644 --- a/financial-services/1.10/modules/ROOT/pages/anypointmq-setup-guide.adoc +++ b/financial-services/1.10/modules/ROOT/pages/anypointmq-setup-guide.adoc @@ -1,6 +1,6 @@ = Anypoint MQ Setup Guide -The Postman collection `Anypoint-MQ-Configuration` can be used to pre-create all Anypoint MQ destinations required by the accelerator components. This collection can be found in the https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fins-common-resources-src/[FINS Common Resources project^]. +The Postman collection `Anypoint-MQ-Configuration` can be used to pre-create all Anypoint MQ destinations required by the accelerator components. This collection can be found in the https://anypoint.mulesoft.com/exchange/org.mule.examples/fins-common-resources-src/[FINS Common Resources project^]. == Environment Settings diff --git a/financial-services/1.10/modules/ROOT/pages/bian-assets.adoc b/financial-services/1.10/modules/ROOT/pages/bian-assets.adoc index f2cb3951a..d65736179 100644 --- a/financial-services/1.10/modules/ROOT/pages/bian-assets.adoc +++ b/financial-services/1.10/modules/ROOT/pages/bian-assets.adoc @@ -6,63 +6,63 @@ This solution provides a collection of BIAN-compliant assets that allow MuleSoft * BIAN assists banks with improving their architectural maturity and implementing their digital banking initiatives, like Open Banking * BIAN APIs are not required; however, they are available to simplify digital transformation. -The following table lists the BIAN API specifications and implementation template starter assets that are made available as part of the https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/mulesoft-accelerator-for-financial-services[MuleSoft Accelerator for Financial Services^]. +The following table lists the BIAN API specifications and implementation template starter assets that are made available as part of the https://anypoint.mulesoft.com/exchange/org.mule.examples/mulesoft-accelerator-for-financial-services[MuleSoft Accelerator for Financial Services^]. [%header%autowidth.spread^] |=== | Category | Business domain | Service domain | API specification | Implementation template -| Products Domain | Loans and Deposits | Loan | https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fins-bian-loan-prc-api-spec/[FINS BIAN Loan Process API - Specification^] | https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fins-bian-loan-prc-api/[FINS BIAN Loan Process API - Implementation Template^] -| Products Domain | Loans and Deposits | Leasing | https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fins-bian-leasing-prc-api-spec/[FINS BIAN Leasing Process API - Specification^] | https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fins-bian-leasing-prc-api/[FINS BIAN Leasing Process API - Implementation Template^] -| Products Domain | Loans and Deposits | Current Account | https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fins-bian-currentaccount-prc-api-spec/[FINS BIAN Current Account Process API - Specification^] | https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fins-bian-currentaccount-prc-api/[FINS BIAN Current Account Process API - Implementation Template^] -| Products Domain | Loans and Deposits | Corporate Current Account | https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fins-bian-corpcuracct-prc-api-spec/[FINS BIAN Corporate Current Account Process API - Specification^] | https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fins-bian-corpcuracct-prc-api/[FINS BIAN Corporate Current Account Process API - Implementation Template^] -| Products Domain | Loans and Deposits | Consumer Loan | https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fins-bian-consumerloan-prc-api-spec/[FINS BIAN Consumer Loan Process API - Specification^] | https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fins-bian-consumerloan-prc-api/[FINS BIAN Consumer Loan Process API - Implementation Template^] -| Products Domain | Loans and Deposits | Corporate Loan | https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fins-bian-corporateloan-prc-api-spec/[FINS BIAN Corporate Loan Process API - Specification^] | https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fins-bian-corporateloan-prc-api/[FINS BIAN Corporate Loan Process API - Implementation Template^] -| Products Domain | Loans and Deposits | Term Deposit | https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fins-bian-termdeposit-prc-api-spec/[FINS BIAN Term Deposit Process API - Specification^] | https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fins-bian-termdeposit-prc-api/[FINS BIAN Term Deposit Process API - Implementation Template^] -| Products Domain | Loans and Deposits | Corporate Lease | https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fins-bian-corporatelease-prc-api-spec/[FINS BIAN Corporate Lease Process API - Specification^] | https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fins-bian-corporatelease-prc-api/[FINS BIAN Corporate Lease Process API - Implementation Template^] -| Products Domain | Loans and Deposits | Merchandising Loan | https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fins-bian-merchloan-prc-api-spec/[FINS BIAN Merchandising Loan Process API - Specification^] | https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fins-bian-merchloan-prc-api/[FINS BIAN Merchandising Loan Process API - Implementation Template^] -| Products Domain | Loans and Deposits | Mortgage Loan | https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fins-bian-mortgageloan-prc-api-spec/[FINS BIAN Mortgage Loan Process API - Specification^] | https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fins-bian-mortgageloan-prc-api/[FINS BIAN Mortgage Loan Process API - Implementation Template^] -| Products Domain | Loans and Deposits | Fiduciary Agreement | https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fins-bian-fidagreement-prc-api-spec/[FINS BIAN Fiduciary Agreement Process API - Specification^] | https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fins-bian-fidagreement-prc-api/[FINS BIAN Fiduciary Agreement Process API - Implementation Template^] -| Products Domain | Loans and Deposits | Savings Account | https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fins-bian-savingsaccount-prc-api-spec/[FINS BIAN Savings Account Process API - Specification^] | https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fins-bian-savingsaccount-prc-api/[FINS BIAN Savings Account Process API - Implementation Template^] -| Products Domain | Loans and Deposits | Virtual Account | https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fins-bian-virtualaccount-prc-api-spec/[FINS BIAN Virtual Account Process API - Specification^] | https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fins-bian-virtualaccount-prc-api/[FINS BIAN Virtual Account Process API - Implementation Template^] -| Products Domain | Loans and Deposits | Standing Order | https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fins-bian-standingorder-prc-api-spec/[FINS BIAN Standing Order Process API - Specification^] | https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fins-bian-standingorder-prc-api/[FINS BIAN Standing Order Process API - Implementation Template^] -| Products Domain | Cards | Credit Card | https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fins-bian-creditcard-prc-api-spec/[FINS BIAN Credit Card Process API - Specification^] | https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fins-bian-creditcard-prc-api/[FINS BIAN Credit Card Process API - Implementation Template^] -| Products Domain | Cards | Card Authorization | https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fins-bian-cardauth-prc-api-spec/[FINS BIAN Card Authorization Process API - Specification^] | https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fins-bian-cardauth-prc-api/[FINS BIAN Card Authorization Process API - Implementation Template^] -| Products Domain | Cards | Merchant Relations | https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fins-bian-merchrelations-prc-api-spec/[FINS BIAN Merchant Relations Process API - Specification^] | https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fins-bian-merchrelations-prc-api/[FINS BIAN Merchant Relations Process API - Implementation Template^] -| Products Domain | Cards | Card Network Partipant Facility | https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fins-bian-cardnpf-prc-api-spec/[FINS BIAN Card Network Partipant Facility Process API - Specification^] | https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fins-bian-cardnpf-prc-api/[FINS BIAN Card Network Partipant Facility Process API - Implementation Template^] -| Products Domain | Cards | Merchant Acquiring Facility | https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fins-bian-cardmaf-prc-api-spec/[FINS BIAN Merchant Acquiring Facility Process API - Specification^] | https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fins-bian-cardmaf-prc-api/[FINS BIAN Merchant Acquiring Facility Process API - Implementation Template^] -| Products Domain | Cards | Card Capture | https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fins-bian-cardcapture-prc-api-spec/[FINS BIAN Card Capture Process API - Specification^] | https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fins-bian-cardcapture-prc-api/[FINS BIAN Card Capture Process API - Implementation Template^] -| Customer Domain | Sales | Prospect Camapign Execution | https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fins-bian-salespce-prc-api-spec/[FINS BIAN Prospect Camapign Execution Process API - Specification^] | https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fins-bian-salespce-prc-api/[FINS BIAN Prospect Camapign Execution Process API - Implementation Template^] -| Customer Domain | Sales | Lead and Opportunity Management | https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fins-bian-saleslom-prc-api-spec/[FINS BIAN Lead and Opportunity Management Process API - Specification^] | https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fins-bian-saleslom-prc-api/[FINS BIAN Lead and Opportunity Management Process API - Implementation Template^] -| Customer Domain | Sales | Party Lifecycle Management | https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fins-bian-salesplm-prc-api-spec/[FINS BIAN Party Lifecycle Management Process API - Specification^] | https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fins-bian-salesplm-prc-api/[FINS BIAN Party Lifecycle Management Process API - Implementation Template^] -| Customer Domain | Sales | Customer Campaign Execution | https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fins-bian-custcampaignexec-prc-api-spec/[FINS BIAN Customer Campaign Execution Process API - Specification^] | https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fins-bian-custcampaignexec-prc-api/[FINS BIAN Customer Campaign Execution Process API - Implementation Template^] -| Customer Domain | Sales | Customer Offer | https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fins-bian-customeroffer-prc-api-spec/[FINS BIAN Customer Offer Process API - Specification^] | https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fins-bian-customeroffer-prc-api/[FINS BIAN Customer Offer Process API - Implementation Template^] -| Customer Domain | Sales | Underwriting | https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fins-bian-underwriting-prc-api-spec/[FINS BIAN Underwriting Process API - Specification^] | https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fins-bian-underwriting-prc-api/[FINS BIAN Underwriting Process API - Implementation Template^] -| Customer Domain | Sales | Commission Agreement | https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fins-bian-salescommagr-prc-api-spec/[FINS BIAN Commission Agreement Process API - Specification^] | https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fins-bian-salescommagr-prc-api/[FINS BIAN Commission Agreement Process API - Implementation Template^] -| Customer Domain | Sales | Commissions | https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fins-bian-commissions-prc-api-spec/[FINS BIAN Commissions Process API - Specification^] | https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fins-bian-commissions-prc-api/[FINS BIAN Commissions Process API - Implementation Template^] -| Customer Domain | Sales | Product Matching | https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fins-bian-productmatching-prc-api-spec/[FINS BIAN Product Matching Process API - Specification^] | https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fins-bian-productmatching-prc-api/[FINS BIAN Product Matching Process API - Implementation Template^] -| Customer Domain | Sales | Product Expert Sales Support | https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fins-bian-productexpertss-prc-api-spec/[FINS BIAN Product Expert Sales Support Process API - Specification^] | https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fins-bian-productexpertss-prc-api/[FINS BIAN Product Expert Sales Support Process API - Implementation Template^] -| Customer Domain | Sales | Product Sales Support | https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fins-bian-productss-prc-api-spec/[FINS BIAN Product Sales Support Process API - Specification^] | https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fins-bian-productss-prc-api/[FINS BIAN Product Sales Support Process API - Implementation Template^] -| Customer Domain | Sales | Sales Product | https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fins-bian-salesproduct-prc-api-spec/[FINS BIAN Sales Product Process API - Specification^] | https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fins-bian-salesproduct-prc-api/[FINS BIAN Sales Product Process API - Implementation Template^] -| Channels | Servicing | Servicing Issue | https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fins-bian-servicingissue-prc-api-spec/[FINS BIAN Servicing Issue Process API - Specification^] | https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fins-bian-servicingissue-prc-api/[FINS BIAN Servicing Issue Process API - Implementation Template^] -| Channels | Servicing | Customer Case Management | https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fins-bian-customercasemgmt-prc-api-spec/[FINS BIAN Customer Case Management Process API - Specification^] | https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fins-bian-customercasemgmt-prc-api/[FINS BIAN Customer Case Management Process API - Implementation Template^] -| Channels | Servicing | Case Root Cause Analysis | https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fins-bian-casertcauseanlys-prc-api-spec/[FINS BIAN Case Root Cause Analysis Process API - Specification^] | https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fins-bian-casertcauseanlys-prc-api/[FINS BIAN Case Root Cause Analysis Process API - Implementation Template^] -| Channels | Servicing | Customer Case | https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fins-bian-customercase-prc-api-spec/[FINS BIAN Customer Case Process API - Specification^] | https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fins-bian-customercase-prc-api/[FINS BIAN Customer Case Process API - Implementation Template^] -| Channels | Servicing | Servicing Order | https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fins-bian-servicingorder-prc-api-spec/[FINS BIAN Servicing Order Process API - Specification^] | https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fins-bian-servicingorder-prc-api/[FINS BIAN Servicing Order Process API - Implementation Template^] -| Channels | Servicing | Servicing Mandate | https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fins-bian-servicingmandate-prc-api-spec/[FINS BIAN Servicing Mandate Process API - Specification^] | https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fins-bian-servicingmandate-prc-api/[FINS BIAN Servicing Mandate Process API - Implementation Template^] -| Channels | Servicing | Payment Execution | https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fins-bian-paymntexecution-prc-api-spec/[FINS BIAN Payment Execution Process API - Specification^] | https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fins-bian-paymntexecution-prc-api/[FINS BIAN Payment Execution Process API - Implementation Template^] -| Channels | Servicing | Payment Initiation | https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fins-bian-paymntinitiation-prc-api-spec/[FINS BIAN Payment Initiation Process API - Specification^] | https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fins-bian-paymntinitiation-prc-api/[FINS BIAN Payment Initiation Process API - Implementation Template^] -| Channels | Servicing | Payment Order | https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fins-bian-paymntorder-prc-api-spec/[FINS BIAN Payment Order Process API - Specification^] | https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fins-bian-paymntorder-prc-api/[FINS BIAN Payment Order Process API - Implementation Template^] -| Sales and Service | Customer Management | Party Reference Data Directory | https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fins-bian-partyrefdatadir-prc-api-spec/[FINS BIAN Party Reference Data Directory Process API - Specification^] | https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fins-bian-partyrefdatadir-prc-api/[FINS BIAN Party Reference Data Directory Process API - Implementation Template^] -| Sales and Service | Cross Channel | Party Authentication | https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fins-bian-partyauth-prc-api-spec/[FINS BIAN Party Authentication Process API - Specification^] | https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fins-bian-partyauth-prc-api/[FINS BIAN Party Authentication Process API - Implementation Template^] -| Sales and Service | Cross Channel | Transaction Authorization | https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fins-bian-transactionauth-prc-api-spec/[FINS BIAN Transaction Authorization Process API - Specification^] | https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fins-bian-transactionauth-prc-api/[FINS BIAN Transaction Authorization Process API - Implementation Template^] -| Sales and Service | Cross Channel | Point of Service | https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fins-bian-pointofservice-prc-api-spec/[FINS BIAN Point of Service Process API - Specification^] | https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fins-bian-pointofservice-prc-api/[FINS BIAN Point of Service Process API - Implementation Template^] -| Sales and Service | Cross Channel | Service Event History | https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fins-bian-svceventhistory-prc-api-spec/[FINS BIAN Service Event History Process API - Specification^] | https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fins-bian-svceventhistory-prc-api/[FINS BIAN Service Event History Process API - Implementation Template^] -| Sales and Service | Cross Channel | Contact Routing | https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fins-bian-contactrouting-prc-api-spec/[FINS BIAN Contact Routing Process API - Specification^] | https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fins-bian-contactrouting-prc-api/[FINS BIAN Contact Routing Process API - Implementation Template^] -| Sales and Service | Cross Channel | Session Dialogue | https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fins-bian-sessiondialogue-prc-api-spec/[FINS BIAN Session Dialogue Process API - Specification^] | https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fins-bian-sessiondialogue-prc-api/[FINS BIAN Session Dialogue Process API - Implementation Template^] -| Sales and Service | Cross Channel | Interactive Help | https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fins-bian-interactivehelp-prc-api-spec/[FINS BIAN Interactive Help Process API - Specification^] | https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fins-bian-interactivehelp-prc-api/[FINS BIAN Interactive Help Process API - Implementation Template^] -| Sales and Service | Cross Channel | Contact Handler | https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fins-bian-contacthandler-prc-api-spec/[FINS BIAN Contact Handler Process API - Specification^] | https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fins-bian-contacthandler-prc-api/[FINS BIAN Contact Handler Process API - Implementation Template^] -| Sales and Service | Cross Channel | Customer Workbench | https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fins-bian-custworkbench-prc-api-spec/[FINS BIAN Customer Workbench Process API - Specification^] | https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fins-bian-custworkbench-prc-api/[FINS BIAN Customer Workbench Process API - Implementation Template^] -| Sales and Service | Cross Channel | Servicing Activity Analysis | https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fins-bian-svcactivityanlys-prc-api-spec/[FINS BIAN Servicing Activity Analysis Process API - Specification^] | https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fins-bian-svcactivityanlys-prc-api/[FINS BIAN Servicing Activity Analysis Process API - Implementation Template^] +| Products Domain | Loans and Deposits | Loan | https://anypoint.mulesoft.com/exchange/org.mule.examples/fins-bian-loan-prc-api-spec/[FINS BIAN Loan Process API - Specification^] | https://anypoint.mulesoft.com/exchange/org.mule.examples/fins-bian-loan-prc-api/[FINS BIAN Loan Process API - Implementation Template^] +| Products Domain | Loans and Deposits | Leasing | https://anypoint.mulesoft.com/exchange/org.mule.examples/fins-bian-leasing-prc-api-spec/[FINS BIAN Leasing Process API - Specification^] | https://anypoint.mulesoft.com/exchange/org.mule.examples/fins-bian-leasing-prc-api/[FINS BIAN Leasing Process API - Implementation Template^] +| Products Domain | Loans and Deposits | Current Account | https://anypoint.mulesoft.com/exchange/org.mule.examples/fins-bian-currentaccount-prc-api-spec/[FINS BIAN Current Account Process API - Specification^] | https://anypoint.mulesoft.com/exchange/org.mule.examples/fins-bian-currentaccount-prc-api/[FINS BIAN Current Account Process API - Implementation Template^] +| Products Domain | Loans and Deposits | Corporate Current Account | https://anypoint.mulesoft.com/exchange/org.mule.examples/fins-bian-corpcuracct-prc-api-spec/[FINS BIAN Corporate Current Account Process API - Specification^] | https://anypoint.mulesoft.com/exchange/org.mule.examples/fins-bian-corpcuracct-prc-api/[FINS BIAN Corporate Current Account Process API - Implementation Template^] +| Products Domain | Loans and Deposits | Consumer Loan | https://anypoint.mulesoft.com/exchange/org.mule.examples/fins-bian-consumerloan-prc-api-spec/[FINS BIAN Consumer Loan Process API - Specification^] | https://anypoint.mulesoft.com/exchange/org.mule.examples/fins-bian-consumerloan-prc-api/[FINS BIAN Consumer Loan Process API - Implementation Template^] +| Products Domain | Loans and Deposits | Corporate Loan | https://anypoint.mulesoft.com/exchange/org.mule.examples/fins-bian-corporateloan-prc-api-spec/[FINS BIAN Corporate Loan Process API - Specification^] | https://anypoint.mulesoft.com/exchange/org.mule.examples/fins-bian-corporateloan-prc-api/[FINS BIAN Corporate Loan Process API - Implementation Template^] +| Products Domain | Loans and Deposits | Term Deposit | https://anypoint.mulesoft.com/exchange/org.mule.examples/fins-bian-termdeposit-prc-api-spec/[FINS BIAN Term Deposit Process API - Specification^] | https://anypoint.mulesoft.com/exchange/org.mule.examples/fins-bian-termdeposit-prc-api/[FINS BIAN Term Deposit Process API - Implementation Template^] +| Products Domain | Loans and Deposits | Corporate Lease | https://anypoint.mulesoft.com/exchange/org.mule.examples/fins-bian-corporatelease-prc-api-spec/[FINS BIAN Corporate Lease Process API - Specification^] | https://anypoint.mulesoft.com/exchange/org.mule.examples/fins-bian-corporatelease-prc-api/[FINS BIAN Corporate Lease Process API - Implementation Template^] +| Products Domain | Loans and Deposits | Merchandising Loan | https://anypoint.mulesoft.com/exchange/org.mule.examples/fins-bian-merchloan-prc-api-spec/[FINS BIAN Merchandising Loan Process API - Specification^] | https://anypoint.mulesoft.com/exchange/org.mule.examples/fins-bian-merchloan-prc-api/[FINS BIAN Merchandising Loan Process API - Implementation Template^] +| Products Domain | Loans and Deposits | Mortgage Loan | https://anypoint.mulesoft.com/exchange/org.mule.examples/fins-bian-mortgageloan-prc-api-spec/[FINS BIAN Mortgage Loan Process API - Specification^] | https://anypoint.mulesoft.com/exchange/org.mule.examples/fins-bian-mortgageloan-prc-api/[FINS BIAN Mortgage Loan Process API - Implementation Template^] +| Products Domain | Loans and Deposits | Fiduciary Agreement | https://anypoint.mulesoft.com/exchange/org.mule.examples/fins-bian-fidagreement-prc-api-spec/[FINS BIAN Fiduciary Agreement Process API - Specification^] | https://anypoint.mulesoft.com/exchange/org.mule.examples/fins-bian-fidagreement-prc-api/[FINS BIAN Fiduciary Agreement Process API - Implementation Template^] +| Products Domain | Loans and Deposits | Savings Account | https://anypoint.mulesoft.com/exchange/org.mule.examples/fins-bian-savingsaccount-prc-api-spec/[FINS BIAN Savings Account Process API - Specification^] | https://anypoint.mulesoft.com/exchange/org.mule.examples/fins-bian-savingsaccount-prc-api/[FINS BIAN Savings Account Process API - Implementation Template^] +| Products Domain | Loans and Deposits | Virtual Account | https://anypoint.mulesoft.com/exchange/org.mule.examples/fins-bian-virtualaccount-prc-api-spec/[FINS BIAN Virtual Account Process API - Specification^] | https://anypoint.mulesoft.com/exchange/org.mule.examples/fins-bian-virtualaccount-prc-api/[FINS BIAN Virtual Account Process API - Implementation Template^] +| Products Domain | Loans and Deposits | Standing Order | https://anypoint.mulesoft.com/exchange/org.mule.examples/fins-bian-standingorder-prc-api-spec/[FINS BIAN Standing Order Process API - Specification^] | https://anypoint.mulesoft.com/exchange/org.mule.examples/fins-bian-standingorder-prc-api/[FINS BIAN Standing Order Process API - Implementation Template^] +| Products Domain | Cards | Credit Card | https://anypoint.mulesoft.com/exchange/org.mule.examples/fins-bian-creditcard-prc-api-spec/[FINS BIAN Credit Card Process API - Specification^] | https://anypoint.mulesoft.com/exchange/org.mule.examples/fins-bian-creditcard-prc-api/[FINS BIAN Credit Card Process API - Implementation Template^] +| Products Domain | Cards | Card Authorization | https://anypoint.mulesoft.com/exchange/org.mule.examples/fins-bian-cardauth-prc-api-spec/[FINS BIAN Card Authorization Process API - Specification^] | https://anypoint.mulesoft.com/exchange/org.mule.examples/fins-bian-cardauth-prc-api/[FINS BIAN Card Authorization Process API - Implementation Template^] +| Products Domain | Cards | Merchant Relations | https://anypoint.mulesoft.com/exchange/org.mule.examples/fins-bian-merchrelations-prc-api-spec/[FINS BIAN Merchant Relations Process API - Specification^] | https://anypoint.mulesoft.com/exchange/org.mule.examples/fins-bian-merchrelations-prc-api/[FINS BIAN Merchant Relations Process API - Implementation Template^] +| Products Domain | Cards | Card Network Partipant Facility | https://anypoint.mulesoft.com/exchange/org.mule.examples/fins-bian-cardnpf-prc-api-spec/[FINS BIAN Card Network Partipant Facility Process API - Specification^] | https://anypoint.mulesoft.com/exchange/org.mule.examples/fins-bian-cardnpf-prc-api/[FINS BIAN Card Network Partipant Facility Process API - Implementation Template^] +| Products Domain | Cards | Merchant Acquiring Facility | https://anypoint.mulesoft.com/exchange/org.mule.examples/fins-bian-cardmaf-prc-api-spec/[FINS BIAN Merchant Acquiring Facility Process API - Specification^] | https://anypoint.mulesoft.com/exchange/org.mule.examples/fins-bian-cardmaf-prc-api/[FINS BIAN Merchant Acquiring Facility Process API - Implementation Template^] +| Products Domain | Cards | Card Capture | https://anypoint.mulesoft.com/exchange/org.mule.examples/fins-bian-cardcapture-prc-api-spec/[FINS BIAN Card Capture Process API - Specification^] | https://anypoint.mulesoft.com/exchange/org.mule.examples/fins-bian-cardcapture-prc-api/[FINS BIAN Card Capture Process API - Implementation Template^] +| Customer Domain | Sales | Prospect Camapign Execution | https://anypoint.mulesoft.com/exchange/org.mule.examples/fins-bian-salespce-prc-api-spec/[FINS BIAN Prospect Camapign Execution Process API - Specification^] | https://anypoint.mulesoft.com/exchange/org.mule.examples/fins-bian-salespce-prc-api/[FINS BIAN Prospect Camapign Execution Process API - Implementation Template^] +| Customer Domain | Sales | Lead and Opportunity Management | https://anypoint.mulesoft.com/exchange/org.mule.examples/fins-bian-saleslom-prc-api-spec/[FINS BIAN Lead and Opportunity Management Process API - Specification^] | https://anypoint.mulesoft.com/exchange/org.mule.examples/fins-bian-saleslom-prc-api/[FINS BIAN Lead and Opportunity Management Process API - Implementation Template^] +| Customer Domain | Sales | Party Lifecycle Management | https://anypoint.mulesoft.com/exchange/org.mule.examples/fins-bian-salesplm-prc-api-spec/[FINS BIAN Party Lifecycle Management Process API - Specification^] | https://anypoint.mulesoft.com/exchange/org.mule.examples/fins-bian-salesplm-prc-api/[FINS BIAN Party Lifecycle Management Process API - Implementation Template^] +| Customer Domain | Sales | Customer Campaign Execution | https://anypoint.mulesoft.com/exchange/org.mule.examples/fins-bian-custcampaignexec-prc-api-spec/[FINS BIAN Customer Campaign Execution Process API - Specification^] | https://anypoint.mulesoft.com/exchange/org.mule.examples/fins-bian-custcampaignexec-prc-api/[FINS BIAN Customer Campaign Execution Process API - Implementation Template^] +| Customer Domain | Sales | Customer Offer | https://anypoint.mulesoft.com/exchange/org.mule.examples/fins-bian-customeroffer-prc-api-spec/[FINS BIAN Customer Offer Process API - Specification^] | https://anypoint.mulesoft.com/exchange/org.mule.examples/fins-bian-customeroffer-prc-api/[FINS BIAN Customer Offer Process API - Implementation Template^] +| Customer Domain | Sales | Underwriting | https://anypoint.mulesoft.com/exchange/org.mule.examples/fins-bian-underwriting-prc-api-spec/[FINS BIAN Underwriting Process API - Specification^] | https://anypoint.mulesoft.com/exchange/org.mule.examples/fins-bian-underwriting-prc-api/[FINS BIAN Underwriting Process API - Implementation Template^] +| Customer Domain | Sales | Commission Agreement | https://anypoint.mulesoft.com/exchange/org.mule.examples/fins-bian-salescommagr-prc-api-spec/[FINS BIAN Commission Agreement Process API - Specification^] | https://anypoint.mulesoft.com/exchange/org.mule.examples/fins-bian-salescommagr-prc-api/[FINS BIAN Commission Agreement Process API - Implementation Template^] +| Customer Domain | Sales | Commissions | https://anypoint.mulesoft.com/exchange/org.mule.examples/fins-bian-commissions-prc-api-spec/[FINS BIAN Commissions Process API - Specification^] | https://anypoint.mulesoft.com/exchange/org.mule.examples/fins-bian-commissions-prc-api/[FINS BIAN Commissions Process API - Implementation Template^] +| Customer Domain | Sales | Product Matching | https://anypoint.mulesoft.com/exchange/org.mule.examples/fins-bian-productmatching-prc-api-spec/[FINS BIAN Product Matching Process API - Specification^] | https://anypoint.mulesoft.com/exchange/org.mule.examples/fins-bian-productmatching-prc-api/[FINS BIAN Product Matching Process API - Implementation Template^] +| Customer Domain | Sales | Product Expert Sales Support | https://anypoint.mulesoft.com/exchange/org.mule.examples/fins-bian-productexpertss-prc-api-spec/[FINS BIAN Product Expert Sales Support Process API - Specification^] | https://anypoint.mulesoft.com/exchange/org.mule.examples/fins-bian-productexpertss-prc-api/[FINS BIAN Product Expert Sales Support Process API - Implementation Template^] +| Customer Domain | Sales | Product Sales Support | https://anypoint.mulesoft.com/exchange/org.mule.examples/fins-bian-productss-prc-api-spec/[FINS BIAN Product Sales Support Process API - Specification^] | https://anypoint.mulesoft.com/exchange/org.mule.examples/fins-bian-productss-prc-api/[FINS BIAN Product Sales Support Process API - Implementation Template^] +| Customer Domain | Sales | Sales Product | https://anypoint.mulesoft.com/exchange/org.mule.examples/fins-bian-salesproduct-prc-api-spec/[FINS BIAN Sales Product Process API - Specification^] | https://anypoint.mulesoft.com/exchange/org.mule.examples/fins-bian-salesproduct-prc-api/[FINS BIAN Sales Product Process API - Implementation Template^] +| Channels | Servicing | Servicing Issue | https://anypoint.mulesoft.com/exchange/org.mule.examples/fins-bian-servicingissue-prc-api-spec/[FINS BIAN Servicing Issue Process API - Specification^] | https://anypoint.mulesoft.com/exchange/org.mule.examples/fins-bian-servicingissue-prc-api/[FINS BIAN Servicing Issue Process API - Implementation Template^] +| Channels | Servicing | Customer Case Management | https://anypoint.mulesoft.com/exchange/org.mule.examples/fins-bian-customercasemgmt-prc-api-spec/[FINS BIAN Customer Case Management Process API - Specification^] | https://anypoint.mulesoft.com/exchange/org.mule.examples/fins-bian-customercasemgmt-prc-api/[FINS BIAN Customer Case Management Process API - Implementation Template^] +| Channels | Servicing | Case Root Cause Analysis | https://anypoint.mulesoft.com/exchange/org.mule.examples/fins-bian-casertcauseanlys-prc-api-spec/[FINS BIAN Case Root Cause Analysis Process API - Specification^] | https://anypoint.mulesoft.com/exchange/org.mule.examples/fins-bian-casertcauseanlys-prc-api/[FINS BIAN Case Root Cause Analysis Process API - Implementation Template^] +| Channels | Servicing | Customer Case | https://anypoint.mulesoft.com/exchange/org.mule.examples/fins-bian-customercase-prc-api-spec/[FINS BIAN Customer Case Process API - Specification^] | https://anypoint.mulesoft.com/exchange/org.mule.examples/fins-bian-customercase-prc-api/[FINS BIAN Customer Case Process API - Implementation Template^] +| Channels | Servicing | Servicing Order | https://anypoint.mulesoft.com/exchange/org.mule.examples/fins-bian-servicingorder-prc-api-spec/[FINS BIAN Servicing Order Process API - Specification^] | https://anypoint.mulesoft.com/exchange/org.mule.examples/fins-bian-servicingorder-prc-api/[FINS BIAN Servicing Order Process API - Implementation Template^] +| Channels | Servicing | Servicing Mandate | https://anypoint.mulesoft.com/exchange/org.mule.examples/fins-bian-servicingmandate-prc-api-spec/[FINS BIAN Servicing Mandate Process API - Specification^] | https://anypoint.mulesoft.com/exchange/org.mule.examples/fins-bian-servicingmandate-prc-api/[FINS BIAN Servicing Mandate Process API - Implementation Template^] +| Channels | Servicing | Payment Execution | https://anypoint.mulesoft.com/exchange/org.mule.examples/fins-bian-paymntexecution-prc-api-spec/[FINS BIAN Payment Execution Process API - Specification^] | https://anypoint.mulesoft.com/exchange/org.mule.examples/fins-bian-paymntexecution-prc-api/[FINS BIAN Payment Execution Process API - Implementation Template^] +| Channels | Servicing | Payment Initiation | https://anypoint.mulesoft.com/exchange/org.mule.examples/fins-bian-paymntinitiation-prc-api-spec/[FINS BIAN Payment Initiation Process API - Specification^] | https://anypoint.mulesoft.com/exchange/org.mule.examples/fins-bian-paymntinitiation-prc-api/[FINS BIAN Payment Initiation Process API - Implementation Template^] +| Channels | Servicing | Payment Order | https://anypoint.mulesoft.com/exchange/org.mule.examples/fins-bian-paymntorder-prc-api-spec/[FINS BIAN Payment Order Process API - Specification^] | https://anypoint.mulesoft.com/exchange/org.mule.examples/fins-bian-paymntorder-prc-api/[FINS BIAN Payment Order Process API - Implementation Template^] +| Sales and Service | Customer Management | Party Reference Data Directory | https://anypoint.mulesoft.com/exchange/org.mule.examples/fins-bian-partyrefdatadir-prc-api-spec/[FINS BIAN Party Reference Data Directory Process API - Specification^] | https://anypoint.mulesoft.com/exchange/org.mule.examples/fins-bian-partyrefdatadir-prc-api/[FINS BIAN Party Reference Data Directory Process API - Implementation Template^] +| Sales and Service | Cross Channel | Party Authentication | https://anypoint.mulesoft.com/exchange/org.mule.examples/fins-bian-partyauth-prc-api-spec/[FINS BIAN Party Authentication Process API - Specification^] | https://anypoint.mulesoft.com/exchange/org.mule.examples/fins-bian-partyauth-prc-api/[FINS BIAN Party Authentication Process API - Implementation Template^] +| Sales and Service | Cross Channel | Transaction Authorization | https://anypoint.mulesoft.com/exchange/org.mule.examples/fins-bian-transactionauth-prc-api-spec/[FINS BIAN Transaction Authorization Process API - Specification^] | https://anypoint.mulesoft.com/exchange/org.mule.examples/fins-bian-transactionauth-prc-api/[FINS BIAN Transaction Authorization Process API - Implementation Template^] +| Sales and Service | Cross Channel | Point of Service | https://anypoint.mulesoft.com/exchange/org.mule.examples/fins-bian-pointofservice-prc-api-spec/[FINS BIAN Point of Service Process API - Specification^] | https://anypoint.mulesoft.com/exchange/org.mule.examples/fins-bian-pointofservice-prc-api/[FINS BIAN Point of Service Process API - Implementation Template^] +| Sales and Service | Cross Channel | Service Event History | https://anypoint.mulesoft.com/exchange/org.mule.examples/fins-bian-svceventhistory-prc-api-spec/[FINS BIAN Service Event History Process API - Specification^] | https://anypoint.mulesoft.com/exchange/org.mule.examples/fins-bian-svceventhistory-prc-api/[FINS BIAN Service Event History Process API - Implementation Template^] +| Sales and Service | Cross Channel | Contact Routing | https://anypoint.mulesoft.com/exchange/org.mule.examples/fins-bian-contactrouting-prc-api-spec/[FINS BIAN Contact Routing Process API - Specification^] | https://anypoint.mulesoft.com/exchange/org.mule.examples/fins-bian-contactrouting-prc-api/[FINS BIAN Contact Routing Process API - Implementation Template^] +| Sales and Service | Cross Channel | Session Dialogue | https://anypoint.mulesoft.com/exchange/org.mule.examples/fins-bian-sessiondialogue-prc-api-spec/[FINS BIAN Session Dialogue Process API - Specification^] | https://anypoint.mulesoft.com/exchange/org.mule.examples/fins-bian-sessiondialogue-prc-api/[FINS BIAN Session Dialogue Process API - Implementation Template^] +| Sales and Service | Cross Channel | Interactive Help | https://anypoint.mulesoft.com/exchange/org.mule.examples/fins-bian-interactivehelp-prc-api-spec/[FINS BIAN Interactive Help Process API - Specification^] | https://anypoint.mulesoft.com/exchange/org.mule.examples/fins-bian-interactivehelp-prc-api/[FINS BIAN Interactive Help Process API - Implementation Template^] +| Sales and Service | Cross Channel | Contact Handler | https://anypoint.mulesoft.com/exchange/org.mule.examples/fins-bian-contacthandler-prc-api-spec/[FINS BIAN Contact Handler Process API - Specification^] | https://anypoint.mulesoft.com/exchange/org.mule.examples/fins-bian-contacthandler-prc-api/[FINS BIAN Contact Handler Process API - Implementation Template^] +| Sales and Service | Cross Channel | Customer Workbench | https://anypoint.mulesoft.com/exchange/org.mule.examples/fins-bian-custworkbench-prc-api-spec/[FINS BIAN Customer Workbench Process API - Specification^] | https://anypoint.mulesoft.com/exchange/org.mule.examples/fins-bian-custworkbench-prc-api/[FINS BIAN Customer Workbench Process API - Implementation Template^] +| Sales and Service | Cross Channel | Servicing Activity Analysis | https://anypoint.mulesoft.com/exchange/org.mule.examples/fins-bian-svcactivityanlys-prc-api-spec/[FINS BIAN Servicing Activity Analysis Process API - Specification^] | https://anypoint.mulesoft.com/exchange/org.mule.examples/fins-bian-svcactivityanlys-prc-api/[FINS BIAN Servicing Activity Analysis Process API - Implementation Template^] |=== == See Also diff --git a/financial-services/1.10/modules/ROOT/pages/fins-assets.adoc b/financial-services/1.10/modules/ROOT/pages/fins-assets.adoc index 0f55e4456..ae9d90416 100644 --- a/financial-services/1.10/modules/ROOT/pages/fins-assets.adoc +++ b/financial-services/1.10/modules/ROOT/pages/fins-assets.adoc @@ -28,10 +28,10 @@ The following shared APIs are are leveraged by this accelerator. [cols="40,30,30"] |=== -| Accelerator Email System API | https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/accelerator-email-sys-api[API Specification^] | https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/accel-email-sys-api[Implementation Template^] -| Accelerator Slack System API | https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/accelerator-slack-sys-api[API Specification^] | https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/accel-slack-sys-api[Implementation Template^] -| Accelerator SMS System API | https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/accelerator-sms-sys-api[API Specification^] | https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/accel-sms-sys-api[Implementation Template^] -| Accelerator Notifications Process API | https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/accelerator-notifications-prc-api[API Specification^] | https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/accel-notifications-prc-api/[Implementation Template^] +| Accelerator Email System API | https://anypoint.mulesoft.com/exchange/org.mule.examples/accelerator-email-sys-api[API Specification^] | https://anypoint.mulesoft.com/exchange/org.mule.examples/accel-email-sys-api[Implementation Template^] +| Accelerator Slack System API | https://anypoint.mulesoft.com/exchange/org.mule.examples/accelerator-slack-sys-api[API Specification^] | https://anypoint.mulesoft.com/exchange/org.mule.examples/accel-slack-sys-api[Implementation Template^] +| Accelerator SMS System API | https://anypoint.mulesoft.com/exchange/org.mule.examples/accelerator-sms-sys-api[API Specification^] | https://anypoint.mulesoft.com/exchange/org.mule.examples/accel-sms-sys-api[Implementation Template^] +| Accelerator Notifications Process API | https://anypoint.mulesoft.com/exchange/org.mule.examples/accelerator-notifications-prc-api[API Specification^] | https://anypoint.mulesoft.com/exchange/org.mule.examples/accel-notifications-prc-api/[Implementation Template^] |=== == Accelerator Shared Components @@ -40,13 +40,13 @@ The following shared components are leveraged by this accelerator. [cols="70,30"] |=== -| Accelerator CIM Global Library | https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/accelerator-cim-global-library[Source^] -| Accelerator CIM Market Library | https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/accelerator-cim-market-library[Source^] -| Accelerator CIM FINS Extension Library | https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/accelerator-cim-fins-ext-library[Source^] -| Accelerator Common Core | https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/accelerator-common-core-src[Source^] -| Accelerator ID Graph Lightning Web Component | https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/accelerator-idgraph-lwc-src[Source^] -| Accelerator Knit Maven Plugin | https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/accelerator-knit-plugin-src[Source^] -| Accelerator POM Parent | https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/accelerator-pom-parent-src[Source^] +| Accelerator CIM Global Library | https://anypoint.mulesoft.com/exchange/org.mule.examples/accelerator-cim-global-library[Source^] +| Accelerator CIM Market Library | https://anypoint.mulesoft.com/exchange/org.mule.examples/accelerator-cim-market-library[Source^] +| Accelerator CIM FINS Extension Library | https://anypoint.mulesoft.com/exchange/org.mule.examples/accelerator-cim-fins-ext-library[Source^] +| Accelerator Common Core | https://anypoint.mulesoft.com/exchange/org.mule.examples/accelerator-common-core-src[Source^] +| Accelerator ID Graph Lightning Web Component | https://anypoint.mulesoft.com/exchange/org.mule.examples/accelerator-idgraph-lwc-src[Source^] +| Accelerator Knit Maven Plugin | https://anypoint.mulesoft.com/exchange/org.mule.examples/accelerator-knit-plugin-src[Source^] +| Accelerator POM Parent | https://anypoint.mulesoft.com/exchange/org.mule.examples/accelerator-pom-parent-src[Source^] |=== == See Also diff --git a/financial-services/1.10/modules/ROOT/pages/index.adoc b/financial-services/1.10/modules/ROOT/pages/index.adoc index d6a825561..9b6405a14 100644 --- a/financial-services/1.10/modules/ROOT/pages/index.adoc +++ b/financial-services/1.10/modules/ROOT/pages/index.adoc @@ -8,47 +8,47 @@ MuleSoft Accelerator for Financial Services simplifies customer 360 initiatives === Core Banking Foundation The Core Banking Foundation use case enables a 360 view of your customers' financial information. There are two variations of this use case: one to jumpstart the unlocking of any core, and one to unlock a specific core. -* https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/mulesoft-accelerator-for-financial-services/minor/{fins-version}/pages/Use%20case%201a%20-%20Unlock%20any%20core/[Unlock any core^] - Unlock and display financial summaries from multiple systems. -* https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/mulesoft-accelerator-for-financial-services/minor/{fins-version}/pages/Use%20case%201b%20-%20Unlock%20Jack%20Henry%20SilverLake%20core/[Unlock Jack Henry SilverLake core^] - Accelerate the delivery of your customer 360 initiatives by unlocking your Jack Henry SilverLake core. -* https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/mulesoft-accelerator-for-financial-services/minor/{fins-version}/pages/Use%20case%201c%20-%20Unlock%20Thought%20Machine%20Vault%20Core[Unlock Thought Machine Vault Core] - Accelerate the delivery of your customer 360 initiatives by unlocking your Thought Machine Vault Core. +* https://anypoint.mulesoft.com/exchange/org.mule.examples/mulesoft-accelerator-for-financial-services/minor/{fins-version}/pages/Use%20case%201a%20-%20Unlock%20any%20core/[Unlock any core^] - Unlock and display financial summaries from multiple systems. +* https://anypoint.mulesoft.com/exchange/org.mule.examples/mulesoft-accelerator-for-financial-services/minor/{fins-version}/pages/Use%20case%201b%20-%20Unlock%20Jack%20Henry%20SilverLake%20core/[Unlock Jack Henry SilverLake core^] - Accelerate the delivery of your customer 360 initiatives by unlocking your Jack Henry SilverLake core. +* https://anypoint.mulesoft.com/exchange/org.mule.examples/mulesoft-accelerator-for-financial-services/minor/{fins-version}/pages/Use%20case%201c%20-%20Unlock%20Thought%20Machine%20Vault%20Core[Unlock Thought Machine Vault Core] - Accelerate the delivery of your customer 360 initiatives by unlocking your Thought Machine Vault Core. === Onboarding This use case accelerates the delivery and development of an enhanced onboarding solution to streamline banking loan origination and wealth management client account opening procedures. There are two extensions for this use case: -* https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/mulesoft-accelerator-for-financial-services/minor/{fins-version}/pages/Use%20case%202a%20-%20Customer%20onboarding%20-%20Banking/[Customer Onboarding - Banking^] - Create an easy and straightforward onboarding experience by empowering consumers to apply for a loan via a digital channel. +* https://anypoint.mulesoft.com/exchange/org.mule.examples/mulesoft-accelerator-for-financial-services/minor/{fins-version}/pages/Use%20case%202a%20-%20Customer%20onboarding%20-%20Banking/[Customer Onboarding - Banking^] - Create an easy and straightforward onboarding experience by empowering consumers to apply for a loan via a digital channel. -* https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/mulesoft-accelerator-for-financial-services/minor/{fins-version}/pages/Use%20case%202b%20-%20Client%20onboarding%20-%20Wealth%20management/[Client Onboarding - Wealth management^] - Accelerate the delivery and development of a streamlined and automated client onboarding solution. +* https://anypoint.mulesoft.com/exchange/org.mule.examples/mulesoft-accelerator-for-financial-services/minor/{fins-version}/pages/Use%20case%202b%20-%20Client%20onboarding%20-%20Wealth%20management/[Client Onboarding - Wealth management^] - Accelerate the delivery and development of a streamlined and automated client onboarding solution. === Payments Modernization -The https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/mulesoft-accelerator-for-financial-services/minor/{fins-version}/pages/Use%20case%203%20-%20Payments%20modernization/[Payments Modernization^] use case accelerates the development of modern payment solutions for Financial Institutions. Banks and Credit Unions will be able to deliver a diverse payments landscape that can address multiple types of financial transactions and customer needs. +The https://anypoint.mulesoft.com/exchange/org.mule.examples/mulesoft-accelerator-for-financial-services/minor/{fins-version}/pages/Use%20case%203%20-%20Payments%20modernization/[Payments Modernization^] use case accelerates the development of modern payment solutions for Financial Institutions. Banks and Credit Unions will be able to deliver a diverse payments landscape that can address multiple types of financial transactions and customer needs. === Address Change Orchestration This use case accelerates the delivery and development of a home address validation solution for streamlining downstream processes impacted by postal address changes. There are two extensions for this use case: -* https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/mulesoft-accelerator-for-financial-services/minor/{fins-version}/pages/Use%20case%204a%20-%20Address%20change%20orchestration%20-%20Insurance/[Address Change Orchestration: Insurance^] - Streamline downstream events that result from policyholder or carrier postal address adjustments. +* https://anypoint.mulesoft.com/exchange/org.mule.examples/mulesoft-accelerator-for-financial-services/minor/{fins-version}/pages/Use%20case%204a%20-%20Address%20change%20orchestration%20-%20Insurance/[Address Change Orchestration: Insurance^] - Streamline downstream events that result from policyholder or carrier postal address adjustments. -* https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/mulesoft-accelerator-for-financial-services/minor/{fins-version}/pages/Use%20case%204b%20-%20Address%20change%20orchestration%20-%20Banking/[Address Change Orchestration: Banking^] - Enhance customer service teams to upsell, cross-sell, and service opportunities that result from customer postal code address changes. +* https://anypoint.mulesoft.com/exchange/org.mule.examples/mulesoft-accelerator-for-financial-services/minor/{fins-version}/pages/Use%20case%204b%20-%20Address%20change%20orchestration%20-%20Banking/[Address Change Orchestration: Banking^] - Enhance customer service teams to upsell, cross-sell, and service opportunities that result from customer postal code address changes. === Optimize Customer Experiences -The https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/mulesoft-accelerator-for-financial-services/minor/{fins-version}/pages/Use%20case%205%20-%20Optimize%20customer%20experiences%20with%20CDP/[Optimize Customer Experiences with Salesforce CDP^] use case provides support for ingesting data from multiple sources into Data Cloud and then using the results of Data Cloud activations to optimize customer experiences by providing Customer Service Representatives (CSRs) with marketing insights. +The https://anypoint.mulesoft.com/exchange/org.mule.examples/mulesoft-accelerator-for-financial-services/minor/{fins-version}/pages/Use%20case%205%20-%20Optimize%20customer%20experiences%20with%20CDP/[Optimize Customer Experiences with Salesforce CDP^] use case provides support for ingesting data from multiple sources into Data Cloud and then using the results of Data Cloud activations to optimize customer experiences by providing Customer Service Representatives (CSRs) with marketing insights. === Salesforce Org Sync -The https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/mulesoft-accelerator-for-financial-services/minor/{fins-version}/pages/Use%20case%206%20-%20Salesforce%20org%20sync/[Salesforce Org Sync^] use case enables financial institutions using a multi-org strategy to sync customer data across Salesforce Financial Services Cloud, Sales Cloud, and Service Cloud orgs. +The https://anypoint.mulesoft.com/exchange/org.mule.examples/mulesoft-accelerator-for-financial-services/minor/{fins-version}/pages/Use%20case%206%20-%20Salesforce%20org%20sync/[Salesforce Org Sync^] use case enables financial institutions using a multi-org strategy to sync customer data across Salesforce Financial Services Cloud, Sales Cloud, and Service Cloud orgs. === Unlock AMS Through Hyperautomation for Insurance Brokers -The https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/mulesoft-accelerator-for-financial-services/minor/{fins-version}/pages/Use%20case%207%20-%20Unlock%20AMS%20through%20hyperautomation%20for%20insurance%20brokers/[Unlock AMS Through Hyperautomation for Insurance Brokers] use case enables insurance brokers to view policy data from an Agency Management System (AMS) platform in their CRM platform. +The https://anypoint.mulesoft.com/exchange/org.mule.examples/mulesoft-accelerator-for-financial-services/minor/{fins-version}/pages/Use%20case%207%20-%20Unlock%20AMS%20through%20hyperautomation%20for%20insurance%20brokers/[Unlock AMS Through Hyperautomation for Insurance Brokers] use case enables insurance brokers to view policy data from an Agency Management System (AMS) platform in their CRM platform. === Additional Assets The following *use-case agnostic* assets are also available: -* https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/mulesoft-accelerator-for-financial-services/minor/{fins-version}/pages/BIAN%20assets/[BIAN assets^] - Jumpstart your BIAN standard implementation using these BIAN-compliant assets, including API specs and implementation templates. +* https://anypoint.mulesoft.com/exchange/org.mule.examples/mulesoft-accelerator-for-financial-services/minor/{fins-version}/pages/BIAN%20assets/[BIAN assets^] - Jumpstart your BIAN standard implementation using these BIAN-compliant assets, including API specs and implementation templates. == See Also @@ -56,4 +56,4 @@ The following *use-case agnostic* assets are also available: * xref:prerequisites.adoc[Prerequisites] * xref:release-notes::accelerators/financial-services/financial-services-release-notes.adoc[Release Notes] * xref:upgrade-notes.adoc[Upgrade Notes] -* https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/mulesoft-accelerator-for-financial-services/[MuleSoft Accelerator for Financial Services on Exchange^] +* https://anypoint.mulesoft.com/exchange/org.mule.examples/mulesoft-accelerator-for-financial-services/[MuleSoft Accelerator for Financial Services on Exchange^] diff --git a/financial-services/1.10/modules/ROOT/pages/payments-setup-guide.adoc b/financial-services/1.10/modules/ROOT/pages/payments-setup-guide.adoc index e84ae2406..b614ba3b6 100644 --- a/financial-services/1.10/modules/ROOT/pages/payments-setup-guide.adoc +++ b/financial-services/1.10/modules/ROOT/pages/payments-setup-guide.adoc @@ -9,7 +9,7 @@ This guide provides instructions for setting up all the components required to r * Moov.io containers will be used to simulate the processing of ACH and Fedwire messages * A third-party Java library will be used to simulate the processing of SWIFT messages * A custom process will be used to simulate incoming payment confirmations -* A https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fins-payments-frontend-webui-src/[Payments Front-end Web UI^] has been built to demonstrate the functionality implemented by this use case +* A https://anypoint.mulesoft.com/exchange/org.mule.examples/fins-payments-frontend-webui-src/[Payments Front-end Web UI^] has been built to demonstrate the functionality implemented by this use case * MultiChain Wallet Node is used to support processing of BlockChain Transactions == Setup @@ -20,20 +20,20 @@ The following containerized services are deployed on docker. For demo purposes, * moov.io ACH service * moov.io Fedwire service -* https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fins-payments-frontend-webui-src/[Payments Front-end Web UI^] +* https://anypoint.mulesoft.com/exchange/org.mule.examples/fins-payments-frontend-webui-src/[Payments Front-end Web UI^] * Blockchain based on https://www.multichain.com/[MultiChain^] -The https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fins-payments-frontend-webui-src/[Payments Front-end Web UI^] can also be run locally, outside of a container, by following the instructions provided in its README file. +The https://anypoint.mulesoft.com/exchange/org.mule.examples/fins-payments-frontend-webui-src/[Payments Front-end Web UI^] can also be run locally, outside of a container, by following the instructions provided in its README file. *Payments Front-end Web UI recommended setup:* . Install Docker and its dependencies on the server of your choice. -. Configure the https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fins-payments-frontend-webui-src/[Payments Front-end Web UI^] by modifying the following properties in the .env file: - ** `REACT_APP_PAYMENTS_WEBUI_EXP_API_ENDPOINT` should point to an instance of the https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fins-payments-webui-exp-api-spec/[Payments Web UI Experience API^] - ** `REACT_APP_PAYMENTS_WEBUI_EXP_API_WEBSOCKET_ENDPOINT` should point to an instance of the https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fins-payments-webui-exp-api-spec/[Payments Web UI Experience API^] +. Configure the https://anypoint.mulesoft.com/exchange/org.mule.examples/fins-payments-frontend-webui-src/[Payments Front-end Web UI^] by modifying the following properties in the .env file: + ** `REACT_APP_PAYMENTS_WEBUI_EXP_API_ENDPOINT` should point to an instance of the https://anypoint.mulesoft.com/exchange/org.mule.examples/fins-payments-webui-exp-api-spec/[Payments Web UI Experience API^] + ** `REACT_APP_PAYMENTS_WEBUI_EXP_API_WEBSOCKET_ENDPOINT` should point to an instance of the https://anypoint.mulesoft.com/exchange/org.mule.examples/fins-payments-webui-exp-api-spec/[Payments Web UI Experience API^] . Build the docker image by running its docker-build.sh script. . Start the docker container by running the docker-run.sh script on the machine running the Docker server, or use a Docker administration UI to manage the containers. -. Update `https.cors.allow-url` property in the https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fins-payments-webui-exp-api/[Payments Web UI Experience API^] with the Payments Front-end Web UI endpoint to allow CORS. +. Update `https.cors.allow-url` property in the https://anypoint.mulesoft.com/exchange/org.mule.examples/fins-payments-webui-exp-api/[Payments Web UI Experience API^] with the Payments Front-end Web UI endpoint to allow CORS. *Moov.io recommended setup:* @@ -43,7 +43,7 @@ The moov.io images are provided pre-built as-is. They can be started on the Dock To run the MultiChain node as a docker container, perform the following steps: -. Use the Dockerfile from the scripts folder in the https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fins-blockchain-sys-api-spec/[Blockchain System API^] to build the MultiChain image. +. Use the Dockerfile from the scripts folder in the https://anypoint.mulesoft.com/exchange/org.mule.examples/fins-blockchain-sys-api-spec/[Blockchain System API^] to build the MultiChain image. . Run the `docker-run.sh` script to deploy the container and setup network ports. Run `docker-exec.sh` to create MultiChain and configure the json-rpc service to interact with the MultiChain container. == See Also diff --git a/financial-services/1.10/modules/ROOT/pages/sfdc-data-cloud-setup-guide.adoc b/financial-services/1.10/modules/ROOT/pages/sfdc-data-cloud-setup-guide.adoc index 963031073..404a73bbc 100644 --- a/financial-services/1.10/modules/ROOT/pages/sfdc-data-cloud-setup-guide.adoc +++ b/financial-services/1.10/modules/ROOT/pages/sfdc-data-cloud-setup-guide.adoc @@ -1,7 +1,7 @@ = Salesforce Data Cloud Setup Guide :fins-version: {page-component-version} -The following provides guidance on Salesforce Data Cloud setup required for the https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/mulesoft-accelerator-for-financial-services/minor/{fins-version}/pages/Use%20case%205%20-%20Optimize%20customer%20experiences%20with%20CDP/[Optimize Customer Experiences with Data Cloud^] use case. A few of these steps can be omitted if deploying the https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fins-salesforce-cdp-sys-api[FINS Salesforce Data Cloud System API^] independently of the use case. +The following provides guidance on Salesforce Data Cloud setup required for the https://anypoint.mulesoft.com/exchange/org.mule.examples/mulesoft-accelerator-for-financial-services/minor/{fins-version}/pages/Use%20case%205%20-%20Optimize%20customer%20experiences%20with%20CDP/[Optimize Customer Experiences with Data Cloud^] use case. A few of these steps can be omitted if deploying the https://anypoint.mulesoft.com/exchange/org.mule.examples/fins-salesforce-cdp-sys-api[FINS Salesforce Data Cloud System API^] independently of the use case. == Data Cloud provisioning @@ -13,7 +13,7 @@ If the Data Cloud instance is already provisioned, skip this section. If not fol . Click `Get Started` to provision the Data Cloud Instance and it can take a few minutes. Correct any issues reported and finish the setup. The Data Cloud instance is considered to be successfully set up if there is a green tick mark for all the steps and you do not need to do anything. + + -image:https://www.mulesoft.com/ext/solutions/draft/images/fins-cdp-setup-cdp-provisioning.png[fins-cdp-setup-cdp-provisioning.png,79%] +image:https://www.mulesoft.com/ext/solutions/images/fins-cdp-setup-cdp-provisioning.png[fins-cdp-setup-cdp-provisioning.png,79%] + == Create data connectors @@ -22,7 +22,7 @@ Connectors are specialized data streams that communicate with external sources t === Use case requirements -The https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/mulesoft-accelerator-for-financial-services/minor/{fins-version}/pages/Use%20case%205%20-%20Optimize%20customer%20experiences%20with%20CDP/[Optimize Customer Experiences with CDP^] use case uses the following connectors: +The https://anypoint.mulesoft.com/exchange/org.mule.examples/mulesoft-accelerator-for-financial-services/minor/{fins-version}/pages/Use%20case%205%20-%20Optimize%20customer%20experiences%20with%20CDP/[Optimize Customer Experiences with CDP^] use case uses the following connectors: * Salesforce CRM - to connect data from a Salesforce CRM instance to Data Cloud. * Marketing Cloud - to receive segmentation results for marketing purposes. @@ -48,7 +48,7 @@ In Data Cloud, you can establish a connection to other Salesforce orgs built upo Once the connection is established, the Data Cloud admin can either use bundles that can automatically deploy data or set up their own data streams; we will walk through the latter approach, below. -For the https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/mulesoft-accelerator-for-financial-services/minor/{fins-version}/pages/Use%20case%205%20-%20Optimize%20customer%20experiences%20with%20CDP/[Optimize Customer Experiences with CDP^] use case, hover over the `Connector Name` field of the new connection and click the pencil icon to change the name of the Connector to `Salesforce FSC Banking`. This is the name that will appear under the `Salesforce Org` dropdown while creating a new Data Stream. +For the https://anypoint.mulesoft.com/exchange/org.mule.examples/mulesoft-accelerator-for-financial-services/minor/{fins-version}/pages/Use%20case%205%20-%20Optimize%20customer%20experiences%20with%20CDP/[Optimize Customer Experiences with CDP^] use case, hover over the `Connector Name` field of the new connection and click the pencil icon to change the name of the Connector to `Salesforce FSC Banking`. This is the name that will appear under the `Salesforce Org` dropdown while creating a new Data Stream. === Marketing Cloud Connector @@ -56,7 +56,7 @@ A Marketing Cloud Connector is required in order to use Marketing Cloud as eithe . Select `Marketing Cloud` from the left navigation menu in the `Data Cloud Setup` app. . Enter the Credentials to authenticate your Marketing Cloud account. You can proceed with the next step in the setup only if the authentication is successful. -. Data Source setup - this step is optional, and only needs to be set up if you are planning to ingest data from Marketing Cloud into Data Cloud. This step is not required for the https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/mulesoft-accelerator-for-financial-services/minor/{fins-version}/pages/Use%20case%205%20-%20Optimize%20customer%20experiences%20with%20CDP/[Optimize Customer Experiences with CDP^] use case. +. Data Source setup - this step is optional, and only needs to be set up if you are planning to ingest data from Marketing Cloud into Data Cloud. This step is not required for the https://anypoint.mulesoft.com/exchange/org.mule.examples/mulesoft-accelerator-for-financial-services/minor/{fins-version}/pages/Use%20case%205%20-%20Optimize%20customer%20experiences%20with%20CDP/[Optimize Customer Experiences with CDP^] use case. . Select Business Units to activate - select the business units to publish segments to Marketing Cloud. Ensure all configured items show a green circle before using the connector. @@ -65,7 +65,7 @@ Ensure all configured items show a green circle before using the connector. You can push data from an external system into Data Cloud via the Ingestion API. This RESTful API offers two interaction patterns: bulk and streaming. The streaming pattern accepts incremental updates to a data set as those changes are captured, while the bulk pattern accepts CSV files in cases where data syncs occur periodically. The same data stream can accept data from the streaming and the bulk interaction. -For the https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/mulesoft-accelerator-for-financial-services/minor/{fins-version}/pages/Use%20case%205%20-%20Optimize%20customer%20experiences%20with%20CDP/[Optimize Customer Experiences with CDP^] use case, the external systems Snowflake, Databricks, and Amazon S3 contain data to be pushed to Data Cloud through MuleSoft's Salesforce CDP connector using the Ingestion API. The schema file for the Ingestion API can be found in the https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fins-salesforce-cdp-sys-api/[FINS Salesforce CDP System API^] implementation template. This schema includes definitions for the following objects: +For the https://anypoint.mulesoft.com/exchange/org.mule.examples/mulesoft-accelerator-for-financial-services/minor/{fins-version}/pages/Use%20case%205%20-%20Optimize%20customer%20experiences%20with%20CDP/[Optimize Customer Experiences with CDP^] use case, the external systems Snowflake, Databricks, and Amazon S3 contain data to be pushed to Data Cloud through MuleSoft's Salesforce CDP connector using the Ingestion API. The schema file for the Ingestion API can be found in the https://anypoint.mulesoft.com/exchange/org.mule.examples/fins-salesforce-cdp-sys-api/[FINS Salesforce CDP System API^] implementation template. This schema includes definitions for the following objects: * FinancialAccount * FinancialTransaction @@ -83,7 +83,7 @@ Follow the steps below to setup and configure an ingestion API to push data from . Click `New`, enter a name for the API source (for example, 'FINS_Banking-Data-Connector'), then click `Save`. . On the details page for the new connector, you must upload a schema file in OpenAPI (OAS) format with a `.yaml` file extension. The schema file describes how data transferred via the API is structured. + *Note:* Ingestion API schemas have set requirements - review the schema requirements below if having issues uploading the schema. -. Click `Upload Schema` and navigate to the location of the file you want to use. Select the file and click Open. For the https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/mulesoft-accelerator-for-financial-services/minor/{fins-version}/pages/Use%20case%205%20-%20Optimize%20customer%20experiences%20with%20CDP/[Optimize Customer Experiences with CDP^] use case, the schema file `mule-cdp-connector-schema.yaml` is available under `src/test/resources/cdp-schema` of the https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fins-salesforce-cdp-sys-api/[FINS Salesforce CDP System API^] implementation template. +. Click `Upload Schema` and navigate to the location of the file you want to use. Select the file and click Open. For the https://anypoint.mulesoft.com/exchange/org.mule.examples/mulesoft-accelerator-for-financial-services/minor/{fins-version}/pages/Use%20case%205%20-%20Optimize%20customer%20experiences%20with%20CDP/[Optimize Customer Experiences with CDP^] use case, the schema file `mule-cdp-connector-schema.yaml` is available under `src/test/resources/cdp-schema` of the https://anypoint.mulesoft.com/exchange/org.mule.examples/fins-salesforce-cdp-sys-api/[FINS Salesforce CDP System API^] implementation template. . Preview all the detected objects and their attributes in your schema. . Click `Save`. @@ -108,7 +108,7 @@ Before you can send data into Data Cloud using Ingestion API via Mulesoft's Sale ** `Perform requests on your behalf at any time (refresh_token, offline_access)` . Click `Save` and then `Done` to create the connected app. -After creating the connected app, click the `Manage Consumer Details` button from the app detail page, confirm your identity, and then record the `Consumer Key` and `Consumer Secret` values: you will need these to configure the https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fins-salesforce-cdp-sys-api/[FINS Salesforce CDP System API] implementation template for deployment. This application uses the MuleSoft Connector for Salesforce CDP, which provides customers a pipeline to send data into Data Cloud. Refer to the https://dev-docs-internal.kqa.msap.io/beta-accelerators/salesforce-cdp-connector/1.0/[Salesforce CDP Connector documentation] for additional details on configuration and available operations. +After creating the connected app, click the `Manage Consumer Details` button from the app detail page, confirm your identity, and then record the `Consumer Key` and `Consumer Secret` values: you will need these to configure the https://anypoint.mulesoft.com/exchange/org.mule.examples/fins-salesforce-cdp-sys-api/[FINS Salesforce CDP System API] implementation template for deployment. This application uses the MuleSoft Connector for Salesforce CDP, which provides customers a pipeline to send data into Data Cloud. Refer to the https://docs.mulesoft.com/salesforce-cdp-connector/1.0/[Salesforce CDP Connector documentation] for additional details on configuration and available operations. ==== Schema requirements @@ -150,7 +150,7 @@ To begin the flow of data from a Salesforce CRM data source (such as your Salesf ==== Use case requirements -For the https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/mulesoft-accelerator-for-financial-services/minor/{fins-version}/pages/Use%20case%205%20-%20Optimize%20customer%20experiences%20with%20CDP/[Optimize Customer Experiences with CDP^] use case, a separate data stream for each of the following objects must be created to pull required data from your Salesforce FSC instance: +For the https://anypoint.mulesoft.com/exchange/org.mule.examples/mulesoft-accelerator-for-financial-services/minor/{fins-version}/pages/Use%20case%205%20-%20Optimize%20customer%20experiences%20with%20CDP/[Optimize Customer Experiences with CDP^] use case, a separate data stream for each of the following objects must be created to pull required data from your Salesforce FSC instance: |=== | Object in Salesforce CRM | Name of the DataStream @@ -257,7 +257,7 @@ NOTE: If you are prompted with an error stating those objects cannot be added, y ==== Add formula fields -Once the data streams for standard objects have been created, we need to add a formula field to identify whether or not the associated party represents an Individual. This is required for proper identity resolution and segmentation for the https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/mulesoft-accelerator-for-financial-services/minor/{fins-version}/pages/Use%20case%205%20-%20Optimize%20customer%20experiences%20with%20CDP/[Optimize Customer Experiences with CDP^] use case. Repeat the following steps for both data streams created above: +Once the data streams for standard objects have been created, we need to add a formula field to identify whether or not the associated party represents an Individual. This is required for proper identity resolution and segmentation for the https://anypoint.mulesoft.com/exchange/org.mule.examples/mulesoft-accelerator-for-financial-services/minor/{fins-version}/pages/Use%20case%205%20-%20Optimize%20customer%20experiences%20with%20CDP/[Optimize Customer Experiences with CDP^] use case. Repeat the following steps for both data streams created above: . Click the data stream from the 'Data Streams' list view to bring up the details page. . Select the `New Formula Field` action from the top right action list. You may need to click the 'more' down arrow to find the action. @@ -284,7 +284,7 @@ If you encounter object access errors in Data Cloud when creating data streams, . Enable Read and View All permissions for the object and Read Access for each field. Use the table above for reference. . Click Save. -Repeat these steps for all objects and fields you want to ingest into Data Cloud. For the https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/mulesoft-accelerator-for-financial-services/minor/{fins-version}/pages/Use%20case%205%20-%20Optimize%20customer%20experiences%20with%20CDP/[Optimize Customer Experiences with CDP^] use case, this includes the `Account` and `Contact` objects. +Repeat these steps for all objects and fields you want to ingest into Data Cloud. For the https://anypoint.mulesoft.com/exchange/org.mule.examples/mulesoft-accelerator-for-financial-services/minor/{fins-version}/pages/Use%20case%205%20-%20Optimize%20customer%20experiences%20with%20CDP/[Optimize Customer Experiences with CDP^] use case, this includes the `Account` and `Contact` objects. === Create an Ingestion API data stream @@ -292,7 +292,7 @@ If you have not already done so, < / " : ? | , _ &+` . Click `Save`. -This completes the configuration of Data Cloud required for the https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/mulesoft-accelerator-for-financial-services/minor/{fins-version}/pages/Use%20case%205%20-%20Optimize%20customer%20experiences%20with%20CDP/[Optimize Customer Experiences with CDP^] use case. +This completes the configuration of Data Cloud required for the https://anypoint.mulesoft.com/exchange/org.mule.examples/mulesoft-accelerator-for-financial-services/minor/{fins-version}/pages/Use%20case%205%20-%20Optimize%20customer%20experiences%20with%20CDP/[Optimize Customer Experiences with CDP^] use case. == See Also diff --git a/financial-services/1.10/modules/ROOT/pages/sfdc-fsc-setup-guide.adoc b/financial-services/1.10/modules/ROOT/pages/sfdc-fsc-setup-guide.adoc index d60590e73..3a9693e77 100644 --- a/financial-services/1.10/modules/ROOT/pages/sfdc-fsc-setup-guide.adoc +++ b/financial-services/1.10/modules/ROOT/pages/sfdc-fsc-setup-guide.adoc @@ -429,7 +429,7 @@ The following fields must be created in the corresponding objects. === Create via Apex Script -An Apex class called `CustomFieldUtility` can be used to create custom fields programmatically. The source for this class can be found in the https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fins-common-resources-src[FINS Common Resources^] project. Download this project and follow the steps below. +An Apex class called `CustomFieldUtility` can be used to create custom fields programmatically. The source for this class can be found in the https://anypoint.mulesoft.com/exchange/org.mule.examples/fins-common-resources-src[FINS Common Resources^] project. Download this project and follow the steps below. . Click on Salesforce Setup icon and select `Developer Console` to open a new console window . Go to `+File -> New -> Apex class+` and create a new class named `CustomFieldUtility` @@ -532,7 +532,7 @@ If desired, click the *Currency Setup* button to add support for additional curr == Create Platform Events and Apex Triggers -The following Platform Event Objects and Apex Triggers must be created in order to capture updates from Salesforce. The scripts to create these Apex Triggers and add fields to Platform Event Objects are located in the https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fins-common-resources-src/[FINS Common Resources] project. +The following Platform Event Objects and Apex Triggers must be created in order to capture updates from Salesforce. The scripts to create these Apex Triggers and add fields to Platform Event Objects are located in the https://anypoint.mulesoft.com/exchange/org.mule.examples/fins-common-resources-src/[FINS Common Resources] project. |=== | Salesforce Object | Salesforce Platform Event Object | Salesforce Platform Event API Name | Apex Trigger Name @@ -590,7 +590,7 @@ This implementation requires creation of Platform Events in Salesforce. To creat . Login to Salesforce. . Click Setup to search for Platform Events in Quick Find Box. Platform Events Page under Integrations section appears with list of available Platform Events. . Click *New Platform Event* button to create an Object and enter Platform Information Details fields like Label, Plural Label and Object with Object Name and Event API Names as above table. Click Save. Repeat this step for creating multiple Salesforce Platform Event Objects as mentioned in the above table. -. To add Custom Fields & Relationships to Platform Event Definitions, run the utility scripts (`CreatePlatformEventsCustomFields.txt`) available in the https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fins-common-resources-src/[FINS Common Resources^] under the `/salesforce` folder. +. To add Custom Fields & Relationships to Platform Event Definitions, run the utility scripts (`CreatePlatformEventsCustomFields.txt`) available in the https://anypoint.mulesoft.com/exchange/org.mule.examples/fins-common-resources-src/[FINS Common Resources^] under the `/salesforce` folder. === Create Apex Triggers @@ -600,7 +600,7 @@ Follow the below steps to create the Apex Triggers . Click Setup to search for Object Manager in Quick Find Box. . Search for the Salesforce Object. A page appears with Details of the Object. . Click Triggers unders the Details section to see list of available triggers on the Object. Click New. -. Copy the Trigger Script code searching by Apex Trigger Name (mentioned in the above table for the SalesforceObject) in CreateApexTriggers.txt of https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fins-common-resources-src/[FINS Common Resources] to the script editor. CreateApexTriggers.txt file is available under /salesforce folder. +. Copy the Trigger Script code searching by Apex Trigger Name (mentioned in the above table for the SalesforceObject) in CreateApexTriggers.txt of https://anypoint.mulesoft.com/exchange/org.mule.examples/fins-common-resources-src/[FINS Common Resources] to the script editor. CreateApexTriggers.txt file is available under /salesforce folder. . Obtain the `LastModifiedById` and `RecordTypeId` (if it exists) by running the queries mentioned in the trigger from Developer Console. . Replace the values in the script and Save the trigger. . Click Save and ensure isActive checkbox is ticked. @@ -677,7 +677,7 @@ You now need to copy the `Consumer Key` and `Consumer Secret` values for use in . Verify your identity by entering the verification code that was emailed to you. . Copy the key and secret values and update your `settings.xml` file as described above. -Download the https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fins-common-resources-src[FINS Common Resources project^] for a sample `settings.xml` file that can be used as a starting point. +Download the https://anypoint.mulesoft.com/exchange/org.mule.examples/fins-common-resources-src[FINS Common Resources project^] for a sample `settings.xml` file that can be used as a starting point. == Generating Security Token for Service Account diff --git a/financial-services/1.10/modules/ROOT/pages/sfdc-mc-setup-guide.adoc b/financial-services/1.10/modules/ROOT/pages/sfdc-mc-setup-guide.adoc index be8885537..54d157d0b 100644 --- a/financial-services/1.10/modules/ROOT/pages/sfdc-mc-setup-guide.adoc +++ b/financial-services/1.10/modules/ROOT/pages/sfdc-mc-setup-guide.adoc @@ -1,12 +1,12 @@ = Salesforce Marketing Cloud Setup Guide :fins-version: {page-component-version} -This guide provides the setup instructions for Marketing Cloud for the following use cases that are part of the https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/mulesoft-accelerator-for-financial-services/[MuleSoft Accelerator for Financial Services^]: +This guide provides the setup instructions for Marketing Cloud for the following use cases that are part of the https://anypoint.mulesoft.com/exchange/org.mule.examples/mulesoft-accelerator-for-financial-services/[MuleSoft Accelerator for Financial Services^]: -* https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/mulesoft-accelerator-for-financial-services/minor/{fins-version}/pages/Use%20case%202b%20-%20Client%20onboarding%20-%20Wealth%20management/[Use case 2b - Client onboarding - Wealth management^] -* https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/mulesoft-accelerator-for-financial-services/minor/{fins-version}/pages/Use%20case%204a%20-%20Address%20change%20orchestration%20-%20Insurance/[Use case 4a - Address change orchestration - Insurance^] -* https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/mulesoft-accelerator-for-financial-services/minor/{fins-version}/pages/Use%20case%204b%20-%20Address%20change%20orchestration%20-%20Banking/[Use case 4b - Address change orchestration - Banking^] -* https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/mulesoft-accelerator-for-financial-services/minor/{fins-version}/pages/Use%20case%205%20-%20Optimize%20customer%20experiences%20with%20CDP/[Use case 5 - Optimize customer experiences with CDP^] +* https://anypoint.mulesoft.com/exchange/org.mule.examples/mulesoft-accelerator-for-financial-services/minor/{fins-version}/pages/Use%20case%202b%20-%20Client%20onboarding%20-%20Wealth%20management/[Use case 2b - Client onboarding - Wealth management^] +* https://anypoint.mulesoft.com/exchange/org.mule.examples/mulesoft-accelerator-for-financial-services/minor/{fins-version}/pages/Use%20case%204a%20-%20Address%20change%20orchestration%20-%20Insurance/[Use case 4a - Address change orchestration - Insurance^] +* https://anypoint.mulesoft.com/exchange/org.mule.examples/mulesoft-accelerator-for-financial-services/minor/{fins-version}/pages/Use%20case%204b%20-%20Address%20change%20orchestration%20-%20Banking/[Use case 4b - Address change orchestration - Banking^] +* https://anypoint.mulesoft.com/exchange/org.mule.examples/mulesoft-accelerator-for-financial-services/minor/{fins-version}/pages/Use%20case%205%20-%20Optimize%20customer%20experiences%20with%20CDP/[Use case 5 - Optimize customer experiences with CDP^] == Create Data Extension for Sync Process @@ -101,7 +101,7 @@ Journey Builder is used to trigger emails to a list of email addresses. The foll === Create Online Submission Form -This is the form that the client will submit so that the https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fins-salesforce-wealth-exp-api/[Salesforce Wealth Experience API] will be invoked to create a lead in FSC: +This is the form that the client will submit so that the https://anypoint.mulesoft.com/exchange/org.mule.examples/fins-salesforce-wealth-exp-api/[Salesforce Wealth Experience API] will be invoked to create a lead in FSC: * Navigate to Web Studio and click Cloudpages * Create a Collection diff --git a/financial-services/1.8/modules/ROOT/pages/_partials/custom-components-fragment.adoc b/financial-services/1.8/modules/ROOT/pages/_partials/custom-components-fragment.adoc index 4d7df4589..362076363 100644 --- a/financial-services/1.8/modules/ROOT/pages/_partials/custom-components-fragment.adoc +++ b/financial-services/1.8/modules/ROOT/pages/_partials/custom-components-fragment.adoc @@ -2,9 +2,9 @@ The following non-application components provide additional functionality in sup [cols="70,30",width=100%] |=== -| FINS Common Resources | https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fins-common-resources-src[ Source^] -| FINS Financial Account Sync Lightning Web Component | https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fins-financial-account-sync-lwc-src[ Source^] -| FINS Fraud Analysis Application | https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fins-fraud-analysis-application-src[ Source^] -| FINS Open Banking Library | https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fins-openbanking-library[ Source^] -| FINS Payments Frontend Web UI | https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fins-payments-frontend-webui-src[ Source^] +| FINS Common Resources | https://anypoint.mulesoft.com/exchange/org.mule.examples/fins-common-resources-src[ Source^] +| FINS Financial Account Sync Lightning Web Component | https://anypoint.mulesoft.com/exchange/org.mule.examples/fins-financial-account-sync-lwc-src[ Source^] +| FINS Fraud Analysis Application | https://anypoint.mulesoft.com/exchange/org.mule.examples/fins-fraud-analysis-application-src[ Source^] +| FINS Open Banking Library | https://anypoint.mulesoft.com/exchange/org.mule.examples/fins-openbanking-library[ Source^] +| FINS Payments Frontend Web UI | https://anypoint.mulesoft.com/exchange/org.mule.examples/fins-payments-frontend-webui-src[ Source^] |=== diff --git a/financial-services/1.8/modules/ROOT/pages/_partials/experience-apis-fragment.adoc b/financial-services/1.8/modules/ROOT/pages/_partials/experience-apis-fragment.adoc index 7a68e4bb1..0b302dce0 100644 --- a/financial-services/1.8/modules/ROOT/pages/_partials/experience-apis-fragment.adoc +++ b/financial-services/1.8/modules/ROOT/pages/_partials/experience-apis-fragment.adoc @@ -2,15 +2,15 @@ The following APIs are provided for use by external systems to interact with fun [cols="40,30,30",width=100%] |=== -|FINS DocuSign Experience API | https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fins-docusign-exp-api-spec[API Specification^] | https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fins-docusign-exp-api[Implementation Template^] -|FINS Jack Henry Events Experience API | | https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fins-jackhenry-events-exp-api[Implementation Template^] -|FINS Mobile Experience API | https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fins-mobile-exp-api-spec[API Specification^] | https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fins-mobile-exp-api[Implementation Template^] -|FINS Open Banking Accounts Experience API | https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fins-openbanking-accounts-exp-api-spec[API Specification^] | https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fins-openbanking-accounts-exp-api[Implementation Template^] -|FINS Open Banking ASPSP Experience API | https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fins-openbanking-aspsp-exp-api-spec[API Specification^] | https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fins-openbanking-aspsp-exp-api[Implementation Template^] -|FINS Open Banking PISP Domestic Experience API | https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fins-openbanking-pisp-dom-exp-api-spec[API Specification^] | https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fins-openbanking-pisp-dom-exp-api[Implementation Template^] -|FINS Open Banking PISP International Experience API | https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fins-openbanking-pisp-intl-exp-api-spec[API Specification^] | https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fins-openbanking-pisp-intl-exp-api[Implementation Template^] -|FINS Payments Web UI Experience API | https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fins-payments-webui-exp-api-spec[API Specification^] | https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fins-payments-webui-exp-api[Implementation Template^] -|FINS Salesforce Financial Experience API | https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fins-salesforce-financial-exp-api-spec[API Specification^] | https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fins-salesforce-financial-exp-api[Implementation Template^] -|FINS Salesforce Insurance Experience API | https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fins-salesforce-insurance-exp-api-spec[API Specification^] | https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fins-salesforce-insurance-exp-api[Implementation Template^] -|FINS Salesforce Wealth Experience API | https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fins-salesforce-wealth-exp-api-spec[API Specification^] | https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fins-salesforce-wealth-exp-api[Implementation Template^] +|FINS DocuSign Experience API | https://anypoint.mulesoft.com/exchange/org.mule.examples/fins-docusign-exp-api-spec[API Specification^] | https://anypoint.mulesoft.com/exchange/org.mule.examples/fins-docusign-exp-api[Implementation Template^] +|FINS Jack Henry Events Experience API | | https://anypoint.mulesoft.com/exchange/org.mule.examples/fins-jackhenry-events-exp-api[Implementation Template^] +|FINS Mobile Experience API | https://anypoint.mulesoft.com/exchange/org.mule.examples/fins-mobile-exp-api-spec[API Specification^] | https://anypoint.mulesoft.com/exchange/org.mule.examples/fins-mobile-exp-api[Implementation Template^] +|FINS Open Banking Accounts Experience API | https://anypoint.mulesoft.com/exchange/org.mule.examples/fins-openbanking-accounts-exp-api-spec[API Specification^] | https://anypoint.mulesoft.com/exchange/org.mule.examples/fins-openbanking-accounts-exp-api[Implementation Template^] +|FINS Open Banking ASPSP Experience API | https://anypoint.mulesoft.com/exchange/org.mule.examples/fins-openbanking-aspsp-exp-api-spec[API Specification^] | https://anypoint.mulesoft.com/exchange/org.mule.examples/fins-openbanking-aspsp-exp-api[Implementation Template^] +|FINS Open Banking PISP Domestic Experience API | https://anypoint.mulesoft.com/exchange/org.mule.examples/fins-openbanking-pisp-dom-exp-api-spec[API Specification^] | https://anypoint.mulesoft.com/exchange/org.mule.examples/fins-openbanking-pisp-dom-exp-api[Implementation Template^] +|FINS Open Banking PISP International Experience API | https://anypoint.mulesoft.com/exchange/org.mule.examples/fins-openbanking-pisp-intl-exp-api-spec[API Specification^] | https://anypoint.mulesoft.com/exchange/org.mule.examples/fins-openbanking-pisp-intl-exp-api[Implementation Template^] +|FINS Payments Web UI Experience API | https://anypoint.mulesoft.com/exchange/org.mule.examples/fins-payments-webui-exp-api-spec[API Specification^] | https://anypoint.mulesoft.com/exchange/org.mule.examples/fins-payments-webui-exp-api[Implementation Template^] +|FINS Salesforce Financial Experience API | https://anypoint.mulesoft.com/exchange/org.mule.examples/fins-salesforce-financial-exp-api-spec[API Specification^] | https://anypoint.mulesoft.com/exchange/org.mule.examples/fins-salesforce-financial-exp-api[Implementation Template^] +|FINS Salesforce Insurance Experience API | https://anypoint.mulesoft.com/exchange/org.mule.examples/fins-salesforce-insurance-exp-api-spec[API Specification^] | https://anypoint.mulesoft.com/exchange/org.mule.examples/fins-salesforce-insurance-exp-api[Implementation Template^] +|FINS Salesforce Wealth Experience API | https://anypoint.mulesoft.com/exchange/org.mule.examples/fins-salesforce-wealth-exp-api-spec[API Specification^] | https://anypoint.mulesoft.com/exchange/org.mule.examples/fins-salesforce-wealth-exp-api[Implementation Template^] |=== diff --git a/financial-services/1.8/modules/ROOT/pages/_partials/listeners-fragment.adoc b/financial-services/1.8/modules/ROOT/pages/_partials/listeners-fragment.adoc index ac8366b48..6cf8a79c1 100644 --- a/financial-services/1.8/modules/ROOT/pages/_partials/listeners-fragment.adoc +++ b/financial-services/1.8/modules/ROOT/pages/_partials/listeners-fragment.adoc @@ -2,9 +2,9 @@ The following applications listen for events published by external systems and i [cols="70,30",width=100%] |=== -| FINS Payments ACH Listener | https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fins-payments-ach-listener[Source^] -| FINS Payments Fedwire Listener | https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fins-payments-fedwire-listener[Source^] -| FINS Payments SWIFT Listener | https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fins-payments-swift-listener[Source^] -| FINS Salesforce Marketing Listener | https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fins-salesforce-marketing-listener[Source^] -| FINS Salesforce Topic Listener | https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fins-salesforce-topic-listener[Source^] +| FINS Payments ACH Listener | https://anypoint.mulesoft.com/exchange/org.mule.examples/fins-payments-ach-listener[Source^] +| FINS Payments Fedwire Listener | https://anypoint.mulesoft.com/exchange/org.mule.examples/fins-payments-fedwire-listener[Source^] +| FINS Payments SWIFT Listener | https://anypoint.mulesoft.com/exchange/org.mule.examples/fins-payments-swift-listener[Source^] +| FINS Salesforce Marketing Listener | https://anypoint.mulesoft.com/exchange/org.mule.examples/fins-salesforce-marketing-listener[Source^] +| FINS Salesforce Topic Listener | https://anypoint.mulesoft.com/exchange/org.mule.examples/fins-salesforce-topic-listener[Source^] |=== diff --git a/financial-services/1.8/modules/ROOT/pages/_partials/process-apis-fragment.adoc b/financial-services/1.8/modules/ROOT/pages/_partials/process-apis-fragment.adoc index 74d34e2d0..bc4a0532d 100644 --- a/financial-services/1.8/modules/ROOT/pages/_partials/process-apis-fragment.adoc +++ b/financial-services/1.8/modules/ROOT/pages/_partials/process-apis-fragment.adoc @@ -2,22 +2,22 @@ The following APIs represent the core business processes that orchestrate the FI [cols="40,30,30",width=100%] |=== -| FINS Bank Accounts Process API | https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fins-bank-accounts-prc-api-spec[API Specification^] | https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fins-bank-accounts-prc-api[Implementation Template^] -| FINS Bank Loans Process API | https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fins-bank-loans-prc-api-spec[API Specification^] | https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fins-bank-loans-prc-api[Implementation Template^] -| FINS Core Banking Poller Process API | https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fins-core-banking-poller-prc-api-spec[API Specification^] | https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fins-core-banking-poller-prc-api[Implementation Template^] -| FINS Credit Card Poller Process API | https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fins-creditcard-poller-prc-api-spec[API Specification^] | https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fins-creditcard-poller-prc-api[Implementation Template^] -| FINS Customer Addresses Process API | https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fins-customer-addresses-prc-api-spec[API Specification^] | https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fins-customer-addresses-prc-api[Implementation Template^] -| FINS Customer Leads Process API | https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fins-customer-leads-prc-api-spec[API Specification^] | https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fins-customer-leads-prc-api[Implementation Template^] -| FINS Customers Process API | https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fins-customers-prc-api-spec[API Specification^] | https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fins-customers-prc-api[Implementation Template^] -| FINS Marketing Poller Process API | https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fins-marketing-poller-prc-api-spec[API Specification^] | https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fins-marketing-poller-prc-api[Implementation Template^] -| FINS Payments Initiation Process API | https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fins-bian-paymntinitiation-prc-api-spec[API Specification^] | https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fins-payments-initiation-prc-api[Implementation Template^] -| FINS Payments InterBank International Execution Process API | https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fins-bian-paymntexecution-prc-api-spec[API Specification^] | https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fins-payments-interbank-international-execution-prc-api[Implementation Template^] -| FINS Payments InterBank National Execution Process API | https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fins-bian-paymntexecution-prc-api-spec[API Specification^] | https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fins-payments-interbank-national-execution-prc-api[Implementation Template^] -| FINS Payments IntraBank International Execution Process API | https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fins-bian-paymntexecution-prc-api-spec[API Specification^] | https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fins-payments-intrabank-international-execution-prc-api[Implementation Template^] -| FINS Payments IntraBank National Execution Process API | https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fins-bian-paymntexecution-prc-api-spec[API Specification^] | https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fins-payments-intrabank-national-execution-prc-api[Implementation Template^] -| FINS Payments Order Process API | https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fins-bian-paymntorder-prc-api-spec[API Specification^] | https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fins-payments-order-prc-api[Implementation Template^] -| FINS Payments Remittances Process API | https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fins-bian-paymntexecution-prc-api-spec[API Specification^] | https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fins-payments-remittances-prc-api[Implementation Template^] -| FINS Payments Router Process API | https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fins-payments-router-prc-api-spec[API Specification^] | https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fins-payments-router-prc-api[Implementation Template^] -| FINS Payments Simulator Process API | https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fins-payments-simulator-prc-api-spec[API Specification^] | https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fins-payments-simulator-prc-api[Implementation Template^] -| FINS Reconciliation Process API | https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fins-reconciliation-prc-api-spec[API Specification^] | https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fins-reconciliation-prc-api[Implementation Template^] +| FINS Bank Accounts Process API | https://anypoint.mulesoft.com/exchange/org.mule.examples/fins-bank-accounts-prc-api-spec[API Specification^] | https://anypoint.mulesoft.com/exchange/org.mule.examples/fins-bank-accounts-prc-api[Implementation Template^] +| FINS Bank Loans Process API | https://anypoint.mulesoft.com/exchange/org.mule.examples/fins-bank-loans-prc-api-spec[API Specification^] | https://anypoint.mulesoft.com/exchange/org.mule.examples/fins-bank-loans-prc-api[Implementation Template^] +| FINS Core Banking Poller Process API | https://anypoint.mulesoft.com/exchange/org.mule.examples/fins-core-banking-poller-prc-api-spec[API Specification^] | https://anypoint.mulesoft.com/exchange/org.mule.examples/fins-core-banking-poller-prc-api[Implementation Template^] +| FINS Credit Card Poller Process API | https://anypoint.mulesoft.com/exchange/org.mule.examples/fins-creditcard-poller-prc-api-spec[API Specification^] | https://anypoint.mulesoft.com/exchange/org.mule.examples/fins-creditcard-poller-prc-api[Implementation Template^] +| FINS Customer Addresses Process API | https://anypoint.mulesoft.com/exchange/org.mule.examples/fins-customer-addresses-prc-api-spec[API Specification^] | https://anypoint.mulesoft.com/exchange/org.mule.examples/fins-customer-addresses-prc-api[Implementation Template^] +| FINS Customer Leads Process API | https://anypoint.mulesoft.com/exchange/org.mule.examples/fins-customer-leads-prc-api-spec[API Specification^] | https://anypoint.mulesoft.com/exchange/org.mule.examples/fins-customer-leads-prc-api[Implementation Template^] +| FINS Customers Process API | https://anypoint.mulesoft.com/exchange/org.mule.examples/fins-customers-prc-api-spec[API Specification^] | https://anypoint.mulesoft.com/exchange/org.mule.examples/fins-customers-prc-api[Implementation Template^] +| FINS Marketing Poller Process API | https://anypoint.mulesoft.com/exchange/org.mule.examples/fins-marketing-poller-prc-api-spec[API Specification^] | https://anypoint.mulesoft.com/exchange/org.mule.examples/fins-marketing-poller-prc-api[Implementation Template^] +| FINS Payments Initiation Process API | https://anypoint.mulesoft.com/exchange/org.mule.examples/fins-bian-paymntinitiation-prc-api-spec[API Specification^] | https://anypoint.mulesoft.com/exchange/org.mule.examples/fins-payments-initiation-prc-api[Implementation Template^] +| FINS Payments InterBank International Execution Process API | https://anypoint.mulesoft.com/exchange/org.mule.examples/fins-bian-paymntexecution-prc-api-spec[API Specification^] | https://anypoint.mulesoft.com/exchange/org.mule.examples/fins-payments-interbank-international-execution-prc-api[Implementation Template^] +| FINS Payments InterBank National Execution Process API | https://anypoint.mulesoft.com/exchange/org.mule.examples/fins-bian-paymntexecution-prc-api-spec[API Specification^] | https://anypoint.mulesoft.com/exchange/org.mule.examples/fins-payments-interbank-national-execution-prc-api[Implementation Template^] +| FINS Payments IntraBank International Execution Process API | https://anypoint.mulesoft.com/exchange/org.mule.examples/fins-bian-paymntexecution-prc-api-spec[API Specification^] | https://anypoint.mulesoft.com/exchange/org.mule.examples/fins-payments-intrabank-international-execution-prc-api[Implementation Template^] +| FINS Payments IntraBank National Execution Process API | https://anypoint.mulesoft.com/exchange/org.mule.examples/fins-bian-paymntexecution-prc-api-spec[API Specification^] | https://anypoint.mulesoft.com/exchange/org.mule.examples/fins-payments-intrabank-national-execution-prc-api[Implementation Template^] +| FINS Payments Order Process API | https://anypoint.mulesoft.com/exchange/org.mule.examples/fins-bian-paymntorder-prc-api-spec[API Specification^] | https://anypoint.mulesoft.com/exchange/org.mule.examples/fins-payments-order-prc-api[Implementation Template^] +| FINS Payments Remittances Process API | https://anypoint.mulesoft.com/exchange/org.mule.examples/fins-bian-paymntexecution-prc-api-spec[API Specification^] | https://anypoint.mulesoft.com/exchange/org.mule.examples/fins-payments-remittances-prc-api[Implementation Template^] +| FINS Payments Router Process API | https://anypoint.mulesoft.com/exchange/org.mule.examples/fins-payments-router-prc-api-spec[API Specification^] | https://anypoint.mulesoft.com/exchange/org.mule.examples/fins-payments-router-prc-api[Implementation Template^] +| FINS Payments Simulator Process API | https://anypoint.mulesoft.com/exchange/org.mule.examples/fins-payments-simulator-prc-api-spec[API Specification^] | https://anypoint.mulesoft.com/exchange/org.mule.examples/fins-payments-simulator-prc-api[Implementation Template^] +| FINS Reconciliation Process API | https://anypoint.mulesoft.com/exchange/org.mule.examples/fins-reconciliation-prc-api-spec[API Specification^] | https://anypoint.mulesoft.com/exchange/org.mule.examples/fins-reconciliation-prc-api[Implementation Template^] |=== diff --git a/financial-services/1.8/modules/ROOT/pages/_partials/system-apis-fragment.adoc b/financial-services/1.8/modules/ROOT/pages/_partials/system-apis-fragment.adoc index 3e25513b6..f51eef764 100644 --- a/financial-services/1.8/modules/ROOT/pages/_partials/system-apis-fragment.adoc +++ b/financial-services/1.8/modules/ROOT/pages/_partials/system-apis-fragment.adoc @@ -2,29 +2,29 @@ The following APIs are used to access and manage data in various external system [cols="40,30,30",width=100%] |=== -| FINS Address Validation System API | https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fins-address-validation-sys-api-spec[API Specification^] | https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fins-address-validation-sys-api[Implementation Template^] -| FINS Blockchain System API | https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fins-blockchain-sys-api-spec[API Specification^] | https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fins-blockchain-sys-api[Implementation Template^] -| FINS Core Banking Accounts System API | https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fins-core-banking-accounts-sys-api-spec[API Specification^] | https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fins-core-banking-accounts-sys-api[Implementation Template^] -| FINS Core Banking Customers System API | https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fins-core-banking-customers-sys-api-spec[API Specification^] | https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fins-core-banking-customers-sys-api[Implementation Template^] -| FINS CoreLogic System API | https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fins-corelogic-sys-api-spec[API Specification^] | https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fins-corelogic-sys-api[Implementation Template^] -| FINS Credit Bureau System API | https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fins-credit-bureau-sys-api-spec[API Specification^] | https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fins-credit-bureau-sys-api[Implementation Template^] -| FINS Credit Card System API | https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fins-creditcard-sys-api-spec[API Specification^] | https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fins-creditcard-sys-api[Implementation Template^] -| FINS Databricks Engagements System API | https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fins-engagements-datacloud-sys-api-spec/[API Specification] | https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fins-databricks-engagements-sys-api/[Implementation Template] -| FINS DocuSign System API | https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fins-docusign-sys-api-spec[API Specification^] | https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fins-docusign-sys-api[Implementation Template^] -| FINS Financial Institutions System API | https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fins-financial-institutions-sys-api-spec[API Specification^] | https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fins-financial-institutions-sys-api[Implementation Template^] -| FINS Foreign Exchange System API | https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fins-foreign-exchange-sys-api-spec[API Specification^] | https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fins-foreign-exchange-sys-api[Implementation Template^] -| FINS Fraud Analysis System API | https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fins-fraud-analysis-sys-api-spec[API Specification^] | https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fins-fraud-analysis-sys-api[Implementation Template^] -| FINS Loan Origination System API | https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fins-loan-origination-sys-api-spec[API Specification^] | https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fins-loan-origination-sys-api[Implementation Template^] -| FINS Payments ACH System API | https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fins-payments-ach-sys-api-spec[API Specification^] | https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fins-payments-ach-sys-api[Implementation Template^] -| FINS Payments Fedwire System API | https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fins-payments-fedwire-sys-api-spec[API Specification^] | https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fins-payments-fedwire-sys-api[Implementation Template^] -| FINS Payments SWIFT System API | https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fins-payments-swift-sys-api-spec[API Specification^] | https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fins-payments-swift-sys-api[Implementation Template^] -| Salesforce CDP System API | https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fins-salesforce-cdp-sys-api-spec/[API Specification] | https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fins-salesforce-cdp-sys-api/[Implementation Template] -| FINS Salesforce Customers System API | https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fins-salesforce-customers-sys-api-spec[API Specification^] | https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fins-salesforce-customers-sys-api[Implementation Template^] -| FINS Salesforce Financial System API | https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fins-salesforce-financial-sys-api-spec[API Specification^] | https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fins-salesforce-financial-sys-api[Implementation Template^] -| FINS Salesforce Insurance System API | https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fins-salesforce-insurance-sys-api-spec[API Specification^] | https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fins-salesforce-insurance-sys-api[Implementation Template^] -| FINS Salesforce Marketing System API | https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/rcg-salesforce-marketing-sys-api-spec[API Specification^] | https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fins-salesforce-marketing-sys-api[Implementation Template^] -| SilverLake Accounts System API | https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fins-core-banking-accounts-sys-api-spec/[API Specification] | https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fins-silverlake-accounts-sys-api/[Implementation Template] -| SilverLake Customers System API | https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fins-core-banking-customers-sys-api-spec/[API Specification] | https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fins-silverlake-customers-sys-api/[Implementation Template] -| Snowflake Financial System API | https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fins-financial-datacloud-sys-api-spec/[API Specification] | https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fins-snowflake-financial-sys-api/[Implementation Template] -| Synergy Documents System API | https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fins-core-banking-documents-sys-api-spec/[API Specification] | https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fins-synergy-documents-sys-api/[Implementation Template] +| FINS Address Validation System API | https://anypoint.mulesoft.com/exchange/org.mule.examples/fins-address-validation-sys-api-spec[API Specification^] | https://anypoint.mulesoft.com/exchange/org.mule.examples/fins-address-validation-sys-api[Implementation Template^] +| FINS Blockchain System API | https://anypoint.mulesoft.com/exchange/org.mule.examples/fins-blockchain-sys-api-spec[API Specification^] | https://anypoint.mulesoft.com/exchange/org.mule.examples/fins-blockchain-sys-api[Implementation Template^] +| FINS Core Banking Accounts System API | https://anypoint.mulesoft.com/exchange/org.mule.examples/fins-core-banking-accounts-sys-api-spec[API Specification^] | https://anypoint.mulesoft.com/exchange/org.mule.examples/fins-core-banking-accounts-sys-api[Implementation Template^] +| FINS Core Banking Customers System API | https://anypoint.mulesoft.com/exchange/org.mule.examples/fins-core-banking-customers-sys-api-spec[API Specification^] | https://anypoint.mulesoft.com/exchange/org.mule.examples/fins-core-banking-customers-sys-api[Implementation Template^] +| FINS CoreLogic System API | https://anypoint.mulesoft.com/exchange/org.mule.examples/fins-corelogic-sys-api-spec[API Specification^] | https://anypoint.mulesoft.com/exchange/org.mule.examples/fins-corelogic-sys-api[Implementation Template^] +| FINS Credit Bureau System API | https://anypoint.mulesoft.com/exchange/org.mule.examples/fins-credit-bureau-sys-api-spec[API Specification^] | https://anypoint.mulesoft.com/exchange/org.mule.examples/fins-credit-bureau-sys-api[Implementation Template^] +| FINS Credit Card System API | https://anypoint.mulesoft.com/exchange/org.mule.examples/fins-creditcard-sys-api-spec[API Specification^] | https://anypoint.mulesoft.com/exchange/org.mule.examples/fins-creditcard-sys-api[Implementation Template^] +| FINS Databricks Engagements System API | https://anypoint.mulesoft.com/exchange/org.mule.examples/fins-engagements-datacloud-sys-api-spec/[API Specification] | https://anypoint.mulesoft.com/exchange/org.mule.examples/fins-databricks-engagements-sys-api/[Implementation Template] +| FINS DocuSign System API | https://anypoint.mulesoft.com/exchange/org.mule.examples/fins-docusign-sys-api-spec[API Specification^] | https://anypoint.mulesoft.com/exchange/org.mule.examples/fins-docusign-sys-api[Implementation Template^] +| FINS Financial Institutions System API | https://anypoint.mulesoft.com/exchange/org.mule.examples/fins-financial-institutions-sys-api-spec[API Specification^] | https://anypoint.mulesoft.com/exchange/org.mule.examples/fins-financial-institutions-sys-api[Implementation Template^] +| FINS Foreign Exchange System API | https://anypoint.mulesoft.com/exchange/org.mule.examples/fins-foreign-exchange-sys-api-spec[API Specification^] | https://anypoint.mulesoft.com/exchange/org.mule.examples/fins-foreign-exchange-sys-api[Implementation Template^] +| FINS Fraud Analysis System API | https://anypoint.mulesoft.com/exchange/org.mule.examples/fins-fraud-analysis-sys-api-spec[API Specification^] | https://anypoint.mulesoft.com/exchange/org.mule.examples/fins-fraud-analysis-sys-api[Implementation Template^] +| FINS Loan Origination System API | https://anypoint.mulesoft.com/exchange/org.mule.examples/fins-loan-origination-sys-api-spec[API Specification^] | https://anypoint.mulesoft.com/exchange/org.mule.examples/fins-loan-origination-sys-api[Implementation Template^] +| FINS Payments ACH System API | https://anypoint.mulesoft.com/exchange/org.mule.examples/fins-payments-ach-sys-api-spec[API Specification^] | https://anypoint.mulesoft.com/exchange/org.mule.examples/fins-payments-ach-sys-api[Implementation Template^] +| FINS Payments Fedwire System API | https://anypoint.mulesoft.com/exchange/org.mule.examples/fins-payments-fedwire-sys-api-spec[API Specification^] | https://anypoint.mulesoft.com/exchange/org.mule.examples/fins-payments-fedwire-sys-api[Implementation Template^] +| FINS Payments SWIFT System API | https://anypoint.mulesoft.com/exchange/org.mule.examples/fins-payments-swift-sys-api-spec[API Specification^] | https://anypoint.mulesoft.com/exchange/org.mule.examples/fins-payments-swift-sys-api[Implementation Template^] +| Salesforce CDP System API | https://anypoint.mulesoft.com/exchange/org.mule.examples/fins-salesforce-cdp-sys-api-spec/[API Specification] | https://anypoint.mulesoft.com/exchange/org.mule.examples/fins-salesforce-cdp-sys-api/[Implementation Template] +| FINS Salesforce Customers System API | https://anypoint.mulesoft.com/exchange/org.mule.examples/fins-salesforce-customers-sys-api-spec[API Specification^] | https://anypoint.mulesoft.com/exchange/org.mule.examples/fins-salesforce-customers-sys-api[Implementation Template^] +| FINS Salesforce Financial System API | https://anypoint.mulesoft.com/exchange/org.mule.examples/fins-salesforce-financial-sys-api-spec[API Specification^] | https://anypoint.mulesoft.com/exchange/org.mule.examples/fins-salesforce-financial-sys-api[Implementation Template^] +| FINS Salesforce Insurance System API | https://anypoint.mulesoft.com/exchange/org.mule.examples/fins-salesforce-insurance-sys-api-spec[API Specification^] | https://anypoint.mulesoft.com/exchange/org.mule.examples/fins-salesforce-insurance-sys-api[Implementation Template^] +| FINS Salesforce Marketing System API | https://anypoint.mulesoft.com/exchange/org.mule.examples/rcg-salesforce-marketing-sys-api-spec[API Specification^] | https://anypoint.mulesoft.com/exchange/org.mule.examples/fins-salesforce-marketing-sys-api[Implementation Template^] +| SilverLake Accounts System API | https://anypoint.mulesoft.com/exchange/org.mule.examples/fins-core-banking-accounts-sys-api-spec/[API Specification] | https://anypoint.mulesoft.com/exchange/org.mule.examples/fins-silverlake-accounts-sys-api/[Implementation Template] +| SilverLake Customers System API | https://anypoint.mulesoft.com/exchange/org.mule.examples/fins-core-banking-customers-sys-api-spec/[API Specification] | https://anypoint.mulesoft.com/exchange/org.mule.examples/fins-silverlake-customers-sys-api/[Implementation Template] +| Snowflake Financial System API | https://anypoint.mulesoft.com/exchange/org.mule.examples/fins-financial-datacloud-sys-api-spec/[API Specification] | https://anypoint.mulesoft.com/exchange/org.mule.examples/fins-snowflake-financial-sys-api/[Implementation Template] +| Synergy Documents System API | https://anypoint.mulesoft.com/exchange/org.mule.examples/fins-core-banking-documents-sys-api-spec/[API Specification] | https://anypoint.mulesoft.com/exchange/org.mule.examples/fins-synergy-documents-sys-api/[Implementation Template] |=== diff --git a/financial-services/1.8/modules/ROOT/pages/anypointmq-setup-guide.adoc b/financial-services/1.8/modules/ROOT/pages/anypointmq-setup-guide.adoc index c8b239d96..12e680ff3 100644 --- a/financial-services/1.8/modules/ROOT/pages/anypointmq-setup-guide.adoc +++ b/financial-services/1.8/modules/ROOT/pages/anypointmq-setup-guide.adoc @@ -1,6 +1,6 @@ = Anypoint MQ Setup Guide -The Postman collection `Anypoint-MQ-Configuration` can be used to pre-create all Anypoint MQ destinations required by the accelerator components. This collection can be found in the https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fins-common-resources-src/[FINS Common Resources project^]. +The Postman collection `Anypoint-MQ-Configuration` can be used to pre-create all Anypoint MQ destinations required by the accelerator components. This collection can be found in the https://anypoint.mulesoft.com/exchange/org.mule.examples/fins-common-resources-src/[FINS Common Resources project^]. == Environment Settings diff --git a/financial-services/1.8/modules/ROOT/pages/bian-assets.adoc b/financial-services/1.8/modules/ROOT/pages/bian-assets.adoc index f2cb3951a..d65736179 100644 --- a/financial-services/1.8/modules/ROOT/pages/bian-assets.adoc +++ b/financial-services/1.8/modules/ROOT/pages/bian-assets.adoc @@ -6,63 +6,63 @@ This solution provides a collection of BIAN-compliant assets that allow MuleSoft * BIAN assists banks with improving their architectural maturity and implementing their digital banking initiatives, like Open Banking * BIAN APIs are not required; however, they are available to simplify digital transformation. -The following table lists the BIAN API specifications and implementation template starter assets that are made available as part of the https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/mulesoft-accelerator-for-financial-services[MuleSoft Accelerator for Financial Services^]. +The following table lists the BIAN API specifications and implementation template starter assets that are made available as part of the https://anypoint.mulesoft.com/exchange/org.mule.examples/mulesoft-accelerator-for-financial-services[MuleSoft Accelerator for Financial Services^]. [%header%autowidth.spread^] |=== | Category | Business domain | Service domain | API specification | Implementation template -| Products Domain | Loans and Deposits | Loan | https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fins-bian-loan-prc-api-spec/[FINS BIAN Loan Process API - Specification^] | https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fins-bian-loan-prc-api/[FINS BIAN Loan Process API - Implementation Template^] -| Products Domain | Loans and Deposits | Leasing | https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fins-bian-leasing-prc-api-spec/[FINS BIAN Leasing Process API - Specification^] | https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fins-bian-leasing-prc-api/[FINS BIAN Leasing Process API - Implementation Template^] -| Products Domain | Loans and Deposits | Current Account | https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fins-bian-currentaccount-prc-api-spec/[FINS BIAN Current Account Process API - Specification^] | https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fins-bian-currentaccount-prc-api/[FINS BIAN Current Account Process API - Implementation Template^] -| Products Domain | Loans and Deposits | Corporate Current Account | https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fins-bian-corpcuracct-prc-api-spec/[FINS BIAN Corporate Current Account Process API - Specification^] | https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fins-bian-corpcuracct-prc-api/[FINS BIAN Corporate Current Account Process API - Implementation Template^] -| Products Domain | Loans and Deposits | Consumer Loan | https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fins-bian-consumerloan-prc-api-spec/[FINS BIAN Consumer Loan Process API - Specification^] | https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fins-bian-consumerloan-prc-api/[FINS BIAN Consumer Loan Process API - Implementation Template^] -| Products Domain | Loans and Deposits | Corporate Loan | https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fins-bian-corporateloan-prc-api-spec/[FINS BIAN Corporate Loan Process API - Specification^] | https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fins-bian-corporateloan-prc-api/[FINS BIAN Corporate Loan Process API - Implementation Template^] -| Products Domain | Loans and Deposits | Term Deposit | https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fins-bian-termdeposit-prc-api-spec/[FINS BIAN Term Deposit Process API - Specification^] | https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fins-bian-termdeposit-prc-api/[FINS BIAN Term Deposit Process API - Implementation Template^] -| Products Domain | Loans and Deposits | Corporate Lease | https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fins-bian-corporatelease-prc-api-spec/[FINS BIAN Corporate Lease Process API - Specification^] | https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fins-bian-corporatelease-prc-api/[FINS BIAN Corporate Lease Process API - Implementation Template^] -| Products Domain | Loans and Deposits | Merchandising Loan | https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fins-bian-merchloan-prc-api-spec/[FINS BIAN Merchandising Loan Process API - Specification^] | https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fins-bian-merchloan-prc-api/[FINS BIAN Merchandising Loan Process API - Implementation Template^] -| Products Domain | Loans and Deposits | Mortgage Loan | https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fins-bian-mortgageloan-prc-api-spec/[FINS BIAN Mortgage Loan Process API - Specification^] | https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fins-bian-mortgageloan-prc-api/[FINS BIAN Mortgage Loan Process API - Implementation Template^] -| Products Domain | Loans and Deposits | Fiduciary Agreement | https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fins-bian-fidagreement-prc-api-spec/[FINS BIAN Fiduciary Agreement Process API - Specification^] | https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fins-bian-fidagreement-prc-api/[FINS BIAN Fiduciary Agreement Process API - Implementation Template^] -| Products Domain | Loans and Deposits | Savings Account | https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fins-bian-savingsaccount-prc-api-spec/[FINS BIAN Savings Account Process API - Specification^] | https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fins-bian-savingsaccount-prc-api/[FINS BIAN Savings Account Process API - Implementation Template^] -| Products Domain | Loans and Deposits | Virtual Account | https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fins-bian-virtualaccount-prc-api-spec/[FINS BIAN Virtual Account Process API - Specification^] | https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fins-bian-virtualaccount-prc-api/[FINS BIAN Virtual Account Process API - Implementation Template^] -| Products Domain | Loans and Deposits | Standing Order | https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fins-bian-standingorder-prc-api-spec/[FINS BIAN Standing Order Process API - Specification^] | https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fins-bian-standingorder-prc-api/[FINS BIAN Standing Order Process API - Implementation Template^] -| Products Domain | Cards | Credit Card | https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fins-bian-creditcard-prc-api-spec/[FINS BIAN Credit Card Process API - Specification^] | https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fins-bian-creditcard-prc-api/[FINS BIAN Credit Card Process API - Implementation Template^] -| Products Domain | Cards | Card Authorization | https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fins-bian-cardauth-prc-api-spec/[FINS BIAN Card Authorization Process API - Specification^] | https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fins-bian-cardauth-prc-api/[FINS BIAN Card Authorization Process API - Implementation Template^] -| Products Domain | Cards | Merchant Relations | https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fins-bian-merchrelations-prc-api-spec/[FINS BIAN Merchant Relations Process API - Specification^] | https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fins-bian-merchrelations-prc-api/[FINS BIAN Merchant Relations Process API - Implementation Template^] -| Products Domain | Cards | Card Network Partipant Facility | https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fins-bian-cardnpf-prc-api-spec/[FINS BIAN Card Network Partipant Facility Process API - Specification^] | https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fins-bian-cardnpf-prc-api/[FINS BIAN Card Network Partipant Facility Process API - Implementation Template^] -| Products Domain | Cards | Merchant Acquiring Facility | https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fins-bian-cardmaf-prc-api-spec/[FINS BIAN Merchant Acquiring Facility Process API - Specification^] | https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fins-bian-cardmaf-prc-api/[FINS BIAN Merchant Acquiring Facility Process API - Implementation Template^] -| Products Domain | Cards | Card Capture | https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fins-bian-cardcapture-prc-api-spec/[FINS BIAN Card Capture Process API - Specification^] | https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fins-bian-cardcapture-prc-api/[FINS BIAN Card Capture Process API - Implementation Template^] -| Customer Domain | Sales | Prospect Camapign Execution | https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fins-bian-salespce-prc-api-spec/[FINS BIAN Prospect Camapign Execution Process API - Specification^] | https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fins-bian-salespce-prc-api/[FINS BIAN Prospect Camapign Execution Process API - Implementation Template^] -| Customer Domain | Sales | Lead and Opportunity Management | https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fins-bian-saleslom-prc-api-spec/[FINS BIAN Lead and Opportunity Management Process API - Specification^] | https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fins-bian-saleslom-prc-api/[FINS BIAN Lead and Opportunity Management Process API - Implementation Template^] -| Customer Domain | Sales | Party Lifecycle Management | https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fins-bian-salesplm-prc-api-spec/[FINS BIAN Party Lifecycle Management Process API - Specification^] | https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fins-bian-salesplm-prc-api/[FINS BIAN Party Lifecycle Management Process API - Implementation Template^] -| Customer Domain | Sales | Customer Campaign Execution | https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fins-bian-custcampaignexec-prc-api-spec/[FINS BIAN Customer Campaign Execution Process API - Specification^] | https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fins-bian-custcampaignexec-prc-api/[FINS BIAN Customer Campaign Execution Process API - Implementation Template^] -| Customer Domain | Sales | Customer Offer | https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fins-bian-customeroffer-prc-api-spec/[FINS BIAN Customer Offer Process API - Specification^] | https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fins-bian-customeroffer-prc-api/[FINS BIAN Customer Offer Process API - Implementation Template^] -| Customer Domain | Sales | Underwriting | https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fins-bian-underwriting-prc-api-spec/[FINS BIAN Underwriting Process API - Specification^] | https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fins-bian-underwriting-prc-api/[FINS BIAN Underwriting Process API - Implementation Template^] -| Customer Domain | Sales | Commission Agreement | https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fins-bian-salescommagr-prc-api-spec/[FINS BIAN Commission Agreement Process API - Specification^] | https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fins-bian-salescommagr-prc-api/[FINS BIAN Commission Agreement Process API - Implementation Template^] -| Customer Domain | Sales | Commissions | https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fins-bian-commissions-prc-api-spec/[FINS BIAN Commissions Process API - Specification^] | https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fins-bian-commissions-prc-api/[FINS BIAN Commissions Process API - Implementation Template^] -| Customer Domain | Sales | Product Matching | https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fins-bian-productmatching-prc-api-spec/[FINS BIAN Product Matching Process API - Specification^] | https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fins-bian-productmatching-prc-api/[FINS BIAN Product Matching Process API - Implementation Template^] -| Customer Domain | Sales | Product Expert Sales Support | https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fins-bian-productexpertss-prc-api-spec/[FINS BIAN Product Expert Sales Support Process API - Specification^] | https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fins-bian-productexpertss-prc-api/[FINS BIAN Product Expert Sales Support Process API - Implementation Template^] -| Customer Domain | Sales | Product Sales Support | https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fins-bian-productss-prc-api-spec/[FINS BIAN Product Sales Support Process API - Specification^] | https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fins-bian-productss-prc-api/[FINS BIAN Product Sales Support Process API - Implementation Template^] -| Customer Domain | Sales | Sales Product | https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fins-bian-salesproduct-prc-api-spec/[FINS BIAN Sales Product Process API - Specification^] | https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fins-bian-salesproduct-prc-api/[FINS BIAN Sales Product Process API - Implementation Template^] -| Channels | Servicing | Servicing Issue | https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fins-bian-servicingissue-prc-api-spec/[FINS BIAN Servicing Issue Process API - Specification^] | https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fins-bian-servicingissue-prc-api/[FINS BIAN Servicing Issue Process API - Implementation Template^] -| Channels | Servicing | Customer Case Management | https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fins-bian-customercasemgmt-prc-api-spec/[FINS BIAN Customer Case Management Process API - Specification^] | https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fins-bian-customercasemgmt-prc-api/[FINS BIAN Customer Case Management Process API - Implementation Template^] -| Channels | Servicing | Case Root Cause Analysis | https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fins-bian-casertcauseanlys-prc-api-spec/[FINS BIAN Case Root Cause Analysis Process API - Specification^] | https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fins-bian-casertcauseanlys-prc-api/[FINS BIAN Case Root Cause Analysis Process API - Implementation Template^] -| Channels | Servicing | Customer Case | https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fins-bian-customercase-prc-api-spec/[FINS BIAN Customer Case Process API - Specification^] | https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fins-bian-customercase-prc-api/[FINS BIAN Customer Case Process API - Implementation Template^] -| Channels | Servicing | Servicing Order | https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fins-bian-servicingorder-prc-api-spec/[FINS BIAN Servicing Order Process API - Specification^] | https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fins-bian-servicingorder-prc-api/[FINS BIAN Servicing Order Process API - Implementation Template^] -| Channels | Servicing | Servicing Mandate | https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fins-bian-servicingmandate-prc-api-spec/[FINS BIAN Servicing Mandate Process API - Specification^] | https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fins-bian-servicingmandate-prc-api/[FINS BIAN Servicing Mandate Process API - Implementation Template^] -| Channels | Servicing | Payment Execution | https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fins-bian-paymntexecution-prc-api-spec/[FINS BIAN Payment Execution Process API - Specification^] | https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fins-bian-paymntexecution-prc-api/[FINS BIAN Payment Execution Process API - Implementation Template^] -| Channels | Servicing | Payment Initiation | https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fins-bian-paymntinitiation-prc-api-spec/[FINS BIAN Payment Initiation Process API - Specification^] | https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fins-bian-paymntinitiation-prc-api/[FINS BIAN Payment Initiation Process API - Implementation Template^] -| Channels | Servicing | Payment Order | https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fins-bian-paymntorder-prc-api-spec/[FINS BIAN Payment Order Process API - Specification^] | https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fins-bian-paymntorder-prc-api/[FINS BIAN Payment Order Process API - Implementation Template^] -| Sales and Service | Customer Management | Party Reference Data Directory | https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fins-bian-partyrefdatadir-prc-api-spec/[FINS BIAN Party Reference Data Directory Process API - Specification^] | https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fins-bian-partyrefdatadir-prc-api/[FINS BIAN Party Reference Data Directory Process API - Implementation Template^] -| Sales and Service | Cross Channel | Party Authentication | https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fins-bian-partyauth-prc-api-spec/[FINS BIAN Party Authentication Process API - Specification^] | https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fins-bian-partyauth-prc-api/[FINS BIAN Party Authentication Process API - Implementation Template^] -| Sales and Service | Cross Channel | Transaction Authorization | https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fins-bian-transactionauth-prc-api-spec/[FINS BIAN Transaction Authorization Process API - Specification^] | https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fins-bian-transactionauth-prc-api/[FINS BIAN Transaction Authorization Process API - Implementation Template^] -| Sales and Service | Cross Channel | Point of Service | https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fins-bian-pointofservice-prc-api-spec/[FINS BIAN Point of Service Process API - Specification^] | https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fins-bian-pointofservice-prc-api/[FINS BIAN Point of Service Process API - Implementation Template^] -| Sales and Service | Cross Channel | Service Event History | https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fins-bian-svceventhistory-prc-api-spec/[FINS BIAN Service Event History Process API - Specification^] | https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fins-bian-svceventhistory-prc-api/[FINS BIAN Service Event History Process API - Implementation Template^] -| Sales and Service | Cross Channel | Contact Routing | https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fins-bian-contactrouting-prc-api-spec/[FINS BIAN Contact Routing Process API - Specification^] | https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fins-bian-contactrouting-prc-api/[FINS BIAN Contact Routing Process API - Implementation Template^] -| Sales and Service | Cross Channel | Session Dialogue | https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fins-bian-sessiondialogue-prc-api-spec/[FINS BIAN Session Dialogue Process API - Specification^] | https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fins-bian-sessiondialogue-prc-api/[FINS BIAN Session Dialogue Process API - Implementation Template^] -| Sales and Service | Cross Channel | Interactive Help | https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fins-bian-interactivehelp-prc-api-spec/[FINS BIAN Interactive Help Process API - Specification^] | https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fins-bian-interactivehelp-prc-api/[FINS BIAN Interactive Help Process API - Implementation Template^] -| Sales and Service | Cross Channel | Contact Handler | https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fins-bian-contacthandler-prc-api-spec/[FINS BIAN Contact Handler Process API - Specification^] | https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fins-bian-contacthandler-prc-api/[FINS BIAN Contact Handler Process API - Implementation Template^] -| Sales and Service | Cross Channel | Customer Workbench | https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fins-bian-custworkbench-prc-api-spec/[FINS BIAN Customer Workbench Process API - Specification^] | https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fins-bian-custworkbench-prc-api/[FINS BIAN Customer Workbench Process API - Implementation Template^] -| Sales and Service | Cross Channel | Servicing Activity Analysis | https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fins-bian-svcactivityanlys-prc-api-spec/[FINS BIAN Servicing Activity Analysis Process API - Specification^] | https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fins-bian-svcactivityanlys-prc-api/[FINS BIAN Servicing Activity Analysis Process API - Implementation Template^] +| Products Domain | Loans and Deposits | Loan | https://anypoint.mulesoft.com/exchange/org.mule.examples/fins-bian-loan-prc-api-spec/[FINS BIAN Loan Process API - Specification^] | https://anypoint.mulesoft.com/exchange/org.mule.examples/fins-bian-loan-prc-api/[FINS BIAN Loan Process API - Implementation Template^] +| Products Domain | Loans and Deposits | Leasing | https://anypoint.mulesoft.com/exchange/org.mule.examples/fins-bian-leasing-prc-api-spec/[FINS BIAN Leasing Process API - Specification^] | https://anypoint.mulesoft.com/exchange/org.mule.examples/fins-bian-leasing-prc-api/[FINS BIAN Leasing Process API - Implementation Template^] +| Products Domain | Loans and Deposits | Current Account | https://anypoint.mulesoft.com/exchange/org.mule.examples/fins-bian-currentaccount-prc-api-spec/[FINS BIAN Current Account Process API - Specification^] | https://anypoint.mulesoft.com/exchange/org.mule.examples/fins-bian-currentaccount-prc-api/[FINS BIAN Current Account Process API - Implementation Template^] +| Products Domain | Loans and Deposits | Corporate Current Account | https://anypoint.mulesoft.com/exchange/org.mule.examples/fins-bian-corpcuracct-prc-api-spec/[FINS BIAN Corporate Current Account Process API - Specification^] | https://anypoint.mulesoft.com/exchange/org.mule.examples/fins-bian-corpcuracct-prc-api/[FINS BIAN Corporate Current Account Process API - Implementation Template^] +| Products Domain | Loans and Deposits | Consumer Loan | https://anypoint.mulesoft.com/exchange/org.mule.examples/fins-bian-consumerloan-prc-api-spec/[FINS BIAN Consumer Loan Process API - Specification^] | https://anypoint.mulesoft.com/exchange/org.mule.examples/fins-bian-consumerloan-prc-api/[FINS BIAN Consumer Loan Process API - Implementation Template^] +| Products Domain | Loans and Deposits | Corporate Loan | https://anypoint.mulesoft.com/exchange/org.mule.examples/fins-bian-corporateloan-prc-api-spec/[FINS BIAN Corporate Loan Process API - Specification^] | https://anypoint.mulesoft.com/exchange/org.mule.examples/fins-bian-corporateloan-prc-api/[FINS BIAN Corporate Loan Process API - Implementation Template^] +| Products Domain | Loans and Deposits | Term Deposit | https://anypoint.mulesoft.com/exchange/org.mule.examples/fins-bian-termdeposit-prc-api-spec/[FINS BIAN Term Deposit Process API - Specification^] | https://anypoint.mulesoft.com/exchange/org.mule.examples/fins-bian-termdeposit-prc-api/[FINS BIAN Term Deposit Process API - Implementation Template^] +| Products Domain | Loans and Deposits | Corporate Lease | https://anypoint.mulesoft.com/exchange/org.mule.examples/fins-bian-corporatelease-prc-api-spec/[FINS BIAN Corporate Lease Process API - Specification^] | https://anypoint.mulesoft.com/exchange/org.mule.examples/fins-bian-corporatelease-prc-api/[FINS BIAN Corporate Lease Process API - Implementation Template^] +| Products Domain | Loans and Deposits | Merchandising Loan | https://anypoint.mulesoft.com/exchange/org.mule.examples/fins-bian-merchloan-prc-api-spec/[FINS BIAN Merchandising Loan Process API - Specification^] | https://anypoint.mulesoft.com/exchange/org.mule.examples/fins-bian-merchloan-prc-api/[FINS BIAN Merchandising Loan Process API - Implementation Template^] +| Products Domain | Loans and Deposits | Mortgage Loan | https://anypoint.mulesoft.com/exchange/org.mule.examples/fins-bian-mortgageloan-prc-api-spec/[FINS BIAN Mortgage Loan Process API - Specification^] | https://anypoint.mulesoft.com/exchange/org.mule.examples/fins-bian-mortgageloan-prc-api/[FINS BIAN Mortgage Loan Process API - Implementation Template^] +| Products Domain | Loans and Deposits | Fiduciary Agreement | https://anypoint.mulesoft.com/exchange/org.mule.examples/fins-bian-fidagreement-prc-api-spec/[FINS BIAN Fiduciary Agreement Process API - Specification^] | https://anypoint.mulesoft.com/exchange/org.mule.examples/fins-bian-fidagreement-prc-api/[FINS BIAN Fiduciary Agreement Process API - Implementation Template^] +| Products Domain | Loans and Deposits | Savings Account | https://anypoint.mulesoft.com/exchange/org.mule.examples/fins-bian-savingsaccount-prc-api-spec/[FINS BIAN Savings Account Process API - Specification^] | https://anypoint.mulesoft.com/exchange/org.mule.examples/fins-bian-savingsaccount-prc-api/[FINS BIAN Savings Account Process API - Implementation Template^] +| Products Domain | Loans and Deposits | Virtual Account | https://anypoint.mulesoft.com/exchange/org.mule.examples/fins-bian-virtualaccount-prc-api-spec/[FINS BIAN Virtual Account Process API - Specification^] | https://anypoint.mulesoft.com/exchange/org.mule.examples/fins-bian-virtualaccount-prc-api/[FINS BIAN Virtual Account Process API - Implementation Template^] +| Products Domain | Loans and Deposits | Standing Order | https://anypoint.mulesoft.com/exchange/org.mule.examples/fins-bian-standingorder-prc-api-spec/[FINS BIAN Standing Order Process API - Specification^] | https://anypoint.mulesoft.com/exchange/org.mule.examples/fins-bian-standingorder-prc-api/[FINS BIAN Standing Order Process API - Implementation Template^] +| Products Domain | Cards | Credit Card | https://anypoint.mulesoft.com/exchange/org.mule.examples/fins-bian-creditcard-prc-api-spec/[FINS BIAN Credit Card Process API - Specification^] | https://anypoint.mulesoft.com/exchange/org.mule.examples/fins-bian-creditcard-prc-api/[FINS BIAN Credit Card Process API - Implementation Template^] +| Products Domain | Cards | Card Authorization | https://anypoint.mulesoft.com/exchange/org.mule.examples/fins-bian-cardauth-prc-api-spec/[FINS BIAN Card Authorization Process API - Specification^] | https://anypoint.mulesoft.com/exchange/org.mule.examples/fins-bian-cardauth-prc-api/[FINS BIAN Card Authorization Process API - Implementation Template^] +| Products Domain | Cards | Merchant Relations | https://anypoint.mulesoft.com/exchange/org.mule.examples/fins-bian-merchrelations-prc-api-spec/[FINS BIAN Merchant Relations Process API - Specification^] | https://anypoint.mulesoft.com/exchange/org.mule.examples/fins-bian-merchrelations-prc-api/[FINS BIAN Merchant Relations Process API - Implementation Template^] +| Products Domain | Cards | Card Network Partipant Facility | https://anypoint.mulesoft.com/exchange/org.mule.examples/fins-bian-cardnpf-prc-api-spec/[FINS BIAN Card Network Partipant Facility Process API - Specification^] | https://anypoint.mulesoft.com/exchange/org.mule.examples/fins-bian-cardnpf-prc-api/[FINS BIAN Card Network Partipant Facility Process API - Implementation Template^] +| Products Domain | Cards | Merchant Acquiring Facility | https://anypoint.mulesoft.com/exchange/org.mule.examples/fins-bian-cardmaf-prc-api-spec/[FINS BIAN Merchant Acquiring Facility Process API - Specification^] | https://anypoint.mulesoft.com/exchange/org.mule.examples/fins-bian-cardmaf-prc-api/[FINS BIAN Merchant Acquiring Facility Process API - Implementation Template^] +| Products Domain | Cards | Card Capture | https://anypoint.mulesoft.com/exchange/org.mule.examples/fins-bian-cardcapture-prc-api-spec/[FINS BIAN Card Capture Process API - Specification^] | https://anypoint.mulesoft.com/exchange/org.mule.examples/fins-bian-cardcapture-prc-api/[FINS BIAN Card Capture Process API - Implementation Template^] +| Customer Domain | Sales | Prospect Camapign Execution | https://anypoint.mulesoft.com/exchange/org.mule.examples/fins-bian-salespce-prc-api-spec/[FINS BIAN Prospect Camapign Execution Process API - Specification^] | https://anypoint.mulesoft.com/exchange/org.mule.examples/fins-bian-salespce-prc-api/[FINS BIAN Prospect Camapign Execution Process API - Implementation Template^] +| Customer Domain | Sales | Lead and Opportunity Management | https://anypoint.mulesoft.com/exchange/org.mule.examples/fins-bian-saleslom-prc-api-spec/[FINS BIAN Lead and Opportunity Management Process API - Specification^] | https://anypoint.mulesoft.com/exchange/org.mule.examples/fins-bian-saleslom-prc-api/[FINS BIAN Lead and Opportunity Management Process API - Implementation Template^] +| Customer Domain | Sales | Party Lifecycle Management | https://anypoint.mulesoft.com/exchange/org.mule.examples/fins-bian-salesplm-prc-api-spec/[FINS BIAN Party Lifecycle Management Process API - Specification^] | https://anypoint.mulesoft.com/exchange/org.mule.examples/fins-bian-salesplm-prc-api/[FINS BIAN Party Lifecycle Management Process API - Implementation Template^] +| Customer Domain | Sales | Customer Campaign Execution | https://anypoint.mulesoft.com/exchange/org.mule.examples/fins-bian-custcampaignexec-prc-api-spec/[FINS BIAN Customer Campaign Execution Process API - Specification^] | https://anypoint.mulesoft.com/exchange/org.mule.examples/fins-bian-custcampaignexec-prc-api/[FINS BIAN Customer Campaign Execution Process API - Implementation Template^] +| Customer Domain | Sales | Customer Offer | https://anypoint.mulesoft.com/exchange/org.mule.examples/fins-bian-customeroffer-prc-api-spec/[FINS BIAN Customer Offer Process API - Specification^] | https://anypoint.mulesoft.com/exchange/org.mule.examples/fins-bian-customeroffer-prc-api/[FINS BIAN Customer Offer Process API - Implementation Template^] +| Customer Domain | Sales | Underwriting | https://anypoint.mulesoft.com/exchange/org.mule.examples/fins-bian-underwriting-prc-api-spec/[FINS BIAN Underwriting Process API - Specification^] | https://anypoint.mulesoft.com/exchange/org.mule.examples/fins-bian-underwriting-prc-api/[FINS BIAN Underwriting Process API - Implementation Template^] +| Customer Domain | Sales | Commission Agreement | https://anypoint.mulesoft.com/exchange/org.mule.examples/fins-bian-salescommagr-prc-api-spec/[FINS BIAN Commission Agreement Process API - Specification^] | https://anypoint.mulesoft.com/exchange/org.mule.examples/fins-bian-salescommagr-prc-api/[FINS BIAN Commission Agreement Process API - Implementation Template^] +| Customer Domain | Sales | Commissions | https://anypoint.mulesoft.com/exchange/org.mule.examples/fins-bian-commissions-prc-api-spec/[FINS BIAN Commissions Process API - Specification^] | https://anypoint.mulesoft.com/exchange/org.mule.examples/fins-bian-commissions-prc-api/[FINS BIAN Commissions Process API - Implementation Template^] +| Customer Domain | Sales | Product Matching | https://anypoint.mulesoft.com/exchange/org.mule.examples/fins-bian-productmatching-prc-api-spec/[FINS BIAN Product Matching Process API - Specification^] | https://anypoint.mulesoft.com/exchange/org.mule.examples/fins-bian-productmatching-prc-api/[FINS BIAN Product Matching Process API - Implementation Template^] +| Customer Domain | Sales | Product Expert Sales Support | https://anypoint.mulesoft.com/exchange/org.mule.examples/fins-bian-productexpertss-prc-api-spec/[FINS BIAN Product Expert Sales Support Process API - Specification^] | https://anypoint.mulesoft.com/exchange/org.mule.examples/fins-bian-productexpertss-prc-api/[FINS BIAN Product Expert Sales Support Process API - Implementation Template^] +| Customer Domain | Sales | Product Sales Support | https://anypoint.mulesoft.com/exchange/org.mule.examples/fins-bian-productss-prc-api-spec/[FINS BIAN Product Sales Support Process API - Specification^] | https://anypoint.mulesoft.com/exchange/org.mule.examples/fins-bian-productss-prc-api/[FINS BIAN Product Sales Support Process API - Implementation Template^] +| Customer Domain | Sales | Sales Product | https://anypoint.mulesoft.com/exchange/org.mule.examples/fins-bian-salesproduct-prc-api-spec/[FINS BIAN Sales Product Process API - Specification^] | https://anypoint.mulesoft.com/exchange/org.mule.examples/fins-bian-salesproduct-prc-api/[FINS BIAN Sales Product Process API - Implementation Template^] +| Channels | Servicing | Servicing Issue | https://anypoint.mulesoft.com/exchange/org.mule.examples/fins-bian-servicingissue-prc-api-spec/[FINS BIAN Servicing Issue Process API - Specification^] | https://anypoint.mulesoft.com/exchange/org.mule.examples/fins-bian-servicingissue-prc-api/[FINS BIAN Servicing Issue Process API - Implementation Template^] +| Channels | Servicing | Customer Case Management | https://anypoint.mulesoft.com/exchange/org.mule.examples/fins-bian-customercasemgmt-prc-api-spec/[FINS BIAN Customer Case Management Process API - Specification^] | https://anypoint.mulesoft.com/exchange/org.mule.examples/fins-bian-customercasemgmt-prc-api/[FINS BIAN Customer Case Management Process API - Implementation Template^] +| Channels | Servicing | Case Root Cause Analysis | https://anypoint.mulesoft.com/exchange/org.mule.examples/fins-bian-casertcauseanlys-prc-api-spec/[FINS BIAN Case Root Cause Analysis Process API - Specification^] | https://anypoint.mulesoft.com/exchange/org.mule.examples/fins-bian-casertcauseanlys-prc-api/[FINS BIAN Case Root Cause Analysis Process API - Implementation Template^] +| Channels | Servicing | Customer Case | https://anypoint.mulesoft.com/exchange/org.mule.examples/fins-bian-customercase-prc-api-spec/[FINS BIAN Customer Case Process API - Specification^] | https://anypoint.mulesoft.com/exchange/org.mule.examples/fins-bian-customercase-prc-api/[FINS BIAN Customer Case Process API - Implementation Template^] +| Channels | Servicing | Servicing Order | https://anypoint.mulesoft.com/exchange/org.mule.examples/fins-bian-servicingorder-prc-api-spec/[FINS BIAN Servicing Order Process API - Specification^] | https://anypoint.mulesoft.com/exchange/org.mule.examples/fins-bian-servicingorder-prc-api/[FINS BIAN Servicing Order Process API - Implementation Template^] +| Channels | Servicing | Servicing Mandate | https://anypoint.mulesoft.com/exchange/org.mule.examples/fins-bian-servicingmandate-prc-api-spec/[FINS BIAN Servicing Mandate Process API - Specification^] | https://anypoint.mulesoft.com/exchange/org.mule.examples/fins-bian-servicingmandate-prc-api/[FINS BIAN Servicing Mandate Process API - Implementation Template^] +| Channels | Servicing | Payment Execution | https://anypoint.mulesoft.com/exchange/org.mule.examples/fins-bian-paymntexecution-prc-api-spec/[FINS BIAN Payment Execution Process API - Specification^] | https://anypoint.mulesoft.com/exchange/org.mule.examples/fins-bian-paymntexecution-prc-api/[FINS BIAN Payment Execution Process API - Implementation Template^] +| Channels | Servicing | Payment Initiation | https://anypoint.mulesoft.com/exchange/org.mule.examples/fins-bian-paymntinitiation-prc-api-spec/[FINS BIAN Payment Initiation Process API - Specification^] | https://anypoint.mulesoft.com/exchange/org.mule.examples/fins-bian-paymntinitiation-prc-api/[FINS BIAN Payment Initiation Process API - Implementation Template^] +| Channels | Servicing | Payment Order | https://anypoint.mulesoft.com/exchange/org.mule.examples/fins-bian-paymntorder-prc-api-spec/[FINS BIAN Payment Order Process API - Specification^] | https://anypoint.mulesoft.com/exchange/org.mule.examples/fins-bian-paymntorder-prc-api/[FINS BIAN Payment Order Process API - Implementation Template^] +| Sales and Service | Customer Management | Party Reference Data Directory | https://anypoint.mulesoft.com/exchange/org.mule.examples/fins-bian-partyrefdatadir-prc-api-spec/[FINS BIAN Party Reference Data Directory Process API - Specification^] | https://anypoint.mulesoft.com/exchange/org.mule.examples/fins-bian-partyrefdatadir-prc-api/[FINS BIAN Party Reference Data Directory Process API - Implementation Template^] +| Sales and Service | Cross Channel | Party Authentication | https://anypoint.mulesoft.com/exchange/org.mule.examples/fins-bian-partyauth-prc-api-spec/[FINS BIAN Party Authentication Process API - Specification^] | https://anypoint.mulesoft.com/exchange/org.mule.examples/fins-bian-partyauth-prc-api/[FINS BIAN Party Authentication Process API - Implementation Template^] +| Sales and Service | Cross Channel | Transaction Authorization | https://anypoint.mulesoft.com/exchange/org.mule.examples/fins-bian-transactionauth-prc-api-spec/[FINS BIAN Transaction Authorization Process API - Specification^] | https://anypoint.mulesoft.com/exchange/org.mule.examples/fins-bian-transactionauth-prc-api/[FINS BIAN Transaction Authorization Process API - Implementation Template^] +| Sales and Service | Cross Channel | Point of Service | https://anypoint.mulesoft.com/exchange/org.mule.examples/fins-bian-pointofservice-prc-api-spec/[FINS BIAN Point of Service Process API - Specification^] | https://anypoint.mulesoft.com/exchange/org.mule.examples/fins-bian-pointofservice-prc-api/[FINS BIAN Point of Service Process API - Implementation Template^] +| Sales and Service | Cross Channel | Service Event History | https://anypoint.mulesoft.com/exchange/org.mule.examples/fins-bian-svceventhistory-prc-api-spec/[FINS BIAN Service Event History Process API - Specification^] | https://anypoint.mulesoft.com/exchange/org.mule.examples/fins-bian-svceventhistory-prc-api/[FINS BIAN Service Event History Process API - Implementation Template^] +| Sales and Service | Cross Channel | Contact Routing | https://anypoint.mulesoft.com/exchange/org.mule.examples/fins-bian-contactrouting-prc-api-spec/[FINS BIAN Contact Routing Process API - Specification^] | https://anypoint.mulesoft.com/exchange/org.mule.examples/fins-bian-contactrouting-prc-api/[FINS BIAN Contact Routing Process API - Implementation Template^] +| Sales and Service | Cross Channel | Session Dialogue | https://anypoint.mulesoft.com/exchange/org.mule.examples/fins-bian-sessiondialogue-prc-api-spec/[FINS BIAN Session Dialogue Process API - Specification^] | https://anypoint.mulesoft.com/exchange/org.mule.examples/fins-bian-sessiondialogue-prc-api/[FINS BIAN Session Dialogue Process API - Implementation Template^] +| Sales and Service | Cross Channel | Interactive Help | https://anypoint.mulesoft.com/exchange/org.mule.examples/fins-bian-interactivehelp-prc-api-spec/[FINS BIAN Interactive Help Process API - Specification^] | https://anypoint.mulesoft.com/exchange/org.mule.examples/fins-bian-interactivehelp-prc-api/[FINS BIAN Interactive Help Process API - Implementation Template^] +| Sales and Service | Cross Channel | Contact Handler | https://anypoint.mulesoft.com/exchange/org.mule.examples/fins-bian-contacthandler-prc-api-spec/[FINS BIAN Contact Handler Process API - Specification^] | https://anypoint.mulesoft.com/exchange/org.mule.examples/fins-bian-contacthandler-prc-api/[FINS BIAN Contact Handler Process API - Implementation Template^] +| Sales and Service | Cross Channel | Customer Workbench | https://anypoint.mulesoft.com/exchange/org.mule.examples/fins-bian-custworkbench-prc-api-spec/[FINS BIAN Customer Workbench Process API - Specification^] | https://anypoint.mulesoft.com/exchange/org.mule.examples/fins-bian-custworkbench-prc-api/[FINS BIAN Customer Workbench Process API - Implementation Template^] +| Sales and Service | Cross Channel | Servicing Activity Analysis | https://anypoint.mulesoft.com/exchange/org.mule.examples/fins-bian-svcactivityanlys-prc-api-spec/[FINS BIAN Servicing Activity Analysis Process API - Specification^] | https://anypoint.mulesoft.com/exchange/org.mule.examples/fins-bian-svcactivityanlys-prc-api/[FINS BIAN Servicing Activity Analysis Process API - Implementation Template^] |=== == See Also diff --git a/financial-services/1.8/modules/ROOT/pages/fins-assets.adoc b/financial-services/1.8/modules/ROOT/pages/fins-assets.adoc index 0f55e4456..ae9d90416 100644 --- a/financial-services/1.8/modules/ROOT/pages/fins-assets.adoc +++ b/financial-services/1.8/modules/ROOT/pages/fins-assets.adoc @@ -28,10 +28,10 @@ The following shared APIs are are leveraged by this accelerator. [cols="40,30,30"] |=== -| Accelerator Email System API | https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/accelerator-email-sys-api[API Specification^] | https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/accel-email-sys-api[Implementation Template^] -| Accelerator Slack System API | https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/accelerator-slack-sys-api[API Specification^] | https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/accel-slack-sys-api[Implementation Template^] -| Accelerator SMS System API | https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/accelerator-sms-sys-api[API Specification^] | https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/accel-sms-sys-api[Implementation Template^] -| Accelerator Notifications Process API | https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/accelerator-notifications-prc-api[API Specification^] | https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/accel-notifications-prc-api/[Implementation Template^] +| Accelerator Email System API | https://anypoint.mulesoft.com/exchange/org.mule.examples/accelerator-email-sys-api[API Specification^] | https://anypoint.mulesoft.com/exchange/org.mule.examples/accel-email-sys-api[Implementation Template^] +| Accelerator Slack System API | https://anypoint.mulesoft.com/exchange/org.mule.examples/accelerator-slack-sys-api[API Specification^] | https://anypoint.mulesoft.com/exchange/org.mule.examples/accel-slack-sys-api[Implementation Template^] +| Accelerator SMS System API | https://anypoint.mulesoft.com/exchange/org.mule.examples/accelerator-sms-sys-api[API Specification^] | https://anypoint.mulesoft.com/exchange/org.mule.examples/accel-sms-sys-api[Implementation Template^] +| Accelerator Notifications Process API | https://anypoint.mulesoft.com/exchange/org.mule.examples/accelerator-notifications-prc-api[API Specification^] | https://anypoint.mulesoft.com/exchange/org.mule.examples/accel-notifications-prc-api/[Implementation Template^] |=== == Accelerator Shared Components @@ -40,13 +40,13 @@ The following shared components are leveraged by this accelerator. [cols="70,30"] |=== -| Accelerator CIM Global Library | https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/accelerator-cim-global-library[Source^] -| Accelerator CIM Market Library | https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/accelerator-cim-market-library[Source^] -| Accelerator CIM FINS Extension Library | https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/accelerator-cim-fins-ext-library[Source^] -| Accelerator Common Core | https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/accelerator-common-core-src[Source^] -| Accelerator ID Graph Lightning Web Component | https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/accelerator-idgraph-lwc-src[Source^] -| Accelerator Knit Maven Plugin | https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/accelerator-knit-plugin-src[Source^] -| Accelerator POM Parent | https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/accelerator-pom-parent-src[Source^] +| Accelerator CIM Global Library | https://anypoint.mulesoft.com/exchange/org.mule.examples/accelerator-cim-global-library[Source^] +| Accelerator CIM Market Library | https://anypoint.mulesoft.com/exchange/org.mule.examples/accelerator-cim-market-library[Source^] +| Accelerator CIM FINS Extension Library | https://anypoint.mulesoft.com/exchange/org.mule.examples/accelerator-cim-fins-ext-library[Source^] +| Accelerator Common Core | https://anypoint.mulesoft.com/exchange/org.mule.examples/accelerator-common-core-src[Source^] +| Accelerator ID Graph Lightning Web Component | https://anypoint.mulesoft.com/exchange/org.mule.examples/accelerator-idgraph-lwc-src[Source^] +| Accelerator Knit Maven Plugin | https://anypoint.mulesoft.com/exchange/org.mule.examples/accelerator-knit-plugin-src[Source^] +| Accelerator POM Parent | https://anypoint.mulesoft.com/exchange/org.mule.examples/accelerator-pom-parent-src[Source^] |=== == See Also diff --git a/financial-services/1.8/modules/ROOT/pages/index.adoc b/financial-services/1.8/modules/ROOT/pages/index.adoc index a4383bfb5..c46744102 100644 --- a/financial-services/1.8/modules/ROOT/pages/index.adoc +++ b/financial-services/1.8/modules/ROOT/pages/index.adoc @@ -8,42 +8,42 @@ MuleSoft Accelerator for Financial Services simplifies customer 360 initiatives === Core Banking Foundation The Core Banking Foundation use case enables a 360 view of your customers' financial information. There are two variations of this use case: one to jumpstart the unlocking of any core, and one to unlock a specific core. -* https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/mulesoft-accelerator-for-financial-services/minor/{fins-version}/pages/Use%20case%201a%20-%20Unlock%20any%20core/[Unlock any core^] - Unlock and display financial summaries from multiple systems. -* https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/mulesoft-accelerator-for-financial-services/minor/{fins-version}/pages/Use%20case%201b%20-%20Unlock%20Jack%20Henry%20SilverLake%20core/[Unlock Jack Henry SilverLake core^] - Accelerate the delivery of your customer 360 initiatives by unlocking your Jack Henry SilverLake core. +* https://anypoint.mulesoft.com/exchange/org.mule.examples/mulesoft-accelerator-for-financial-services/minor/{fins-version}/pages/Use%20case%201a%20-%20Unlock%20any%20core/[Unlock any core^] - Unlock and display financial summaries from multiple systems. +* https://anypoint.mulesoft.com/exchange/org.mule.examples/mulesoft-accelerator-for-financial-services/minor/{fins-version}/pages/Use%20case%201b%20-%20Unlock%20Jack%20Henry%20SilverLake%20core/[Unlock Jack Henry SilverLake core^] - Accelerate the delivery of your customer 360 initiatives by unlocking your Jack Henry SilverLake core. === Onboarding This use case accelerates the delivery and development of an enhanced onboarding solution to streamline banking loan origination and wealth management client account opening procedures. There are two extensions for this use case: -* https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/mulesoft-accelerator-for-financial-services/minor/{fins-version}/pages/Use%20case%202a%20-%20Customer%20onboarding%20-%20Banking/[Customer Onboarding - Banking^] - Create an easy and straightforward onboarding experience by empowering consumers to apply for a loan via a digital channel. +* https://anypoint.mulesoft.com/exchange/org.mule.examples/mulesoft-accelerator-for-financial-services/minor/{fins-version}/pages/Use%20case%202a%20-%20Customer%20onboarding%20-%20Banking/[Customer Onboarding - Banking^] - Create an easy and straightforward onboarding experience by empowering consumers to apply for a loan via a digital channel. -* https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/mulesoft-accelerator-for-financial-services/minor/{fins-version}/pages/Use%20case%202b%20-%20Client%20onboarding%20-%20Wealth%20management/[Client Onboarding - Wealth management^] - Accelerate the delivery and development of a streamlined and automated client onboarding solution. +* https://anypoint.mulesoft.com/exchange/org.mule.examples/mulesoft-accelerator-for-financial-services/minor/{fins-version}/pages/Use%20case%202b%20-%20Client%20onboarding%20-%20Wealth%20management/[Client Onboarding - Wealth management^] - Accelerate the delivery and development of a streamlined and automated client onboarding solution. === Payments Modernization -The https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/mulesoft-accelerator-for-financial-services/minor/{fins-version}/pages/Use%20case%203%20-%20Payments%20modernization/[Payments Modernization^] use case accelerates the development of modern payment solutions for Financial Institutions. Banks and Credit Unions will be able to deliver a diverse payments landscape that can address multiple types of financial transactions and customer needs. +The https://anypoint.mulesoft.com/exchange/org.mule.examples/mulesoft-accelerator-for-financial-services/minor/{fins-version}/pages/Use%20case%203%20-%20Payments%20modernization/[Payments Modernization^] use case accelerates the development of modern payment solutions for Financial Institutions. Banks and Credit Unions will be able to deliver a diverse payments landscape that can address multiple types of financial transactions and customer needs. === Address Change Orchestration This use case accelerates the delivery and development of a home address validation solution for streamlining downstream processes impacted by postal address changes. There are two extensions for this use case: -* https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/mulesoft-accelerator-for-financial-services/minor/{fins-version}/pages/Use%20case%204a%20-%20Address%20change%20orchestration%20-%20Insurance/[Address Change Orchestration: Insurance^] - Streamline downstream events that result from policyholder or carrier postal address adjustments. +* https://anypoint.mulesoft.com/exchange/org.mule.examples/mulesoft-accelerator-for-financial-services/minor/{fins-version}/pages/Use%20case%204a%20-%20Address%20change%20orchestration%20-%20Insurance/[Address Change Orchestration: Insurance^] - Streamline downstream events that result from policyholder or carrier postal address adjustments. -* https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/mulesoft-accelerator-for-financial-services/minor/{fins-version}/pages/Use%20case%204b%20-%20Address%20change%20orchestration%20-%20Banking/[Address Change Orchestration: Banking^] - Enhance customer service teams to upsell, cross-sell, and service opportunities that result from customer postal code address changes. +* https://anypoint.mulesoft.com/exchange/org.mule.examples/mulesoft-accelerator-for-financial-services/minor/{fins-version}/pages/Use%20case%204b%20-%20Address%20change%20orchestration%20-%20Banking/[Address Change Orchestration: Banking^] - Enhance customer service teams to upsell, cross-sell, and service opportunities that result from customer postal code address changes. === Optimize Customer Experiences -The https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/mulesoft-accelerator-for-financial-services/minor/{fins-version}/pages/Use%20case%205%20-%20Optimize%20customer%20experiences%20with%20CDP/[Optimize Customer Experiences with Salesforce CDP^] use case provides support for ingesting data from multiple sources into Data Cloud and then using the results of Data Cloud activations to optimize customer experiences by providing Customer Service Representatives (CSRs) with marketing insights. +The https://anypoint.mulesoft.com/exchange/org.mule.examples/mulesoft-accelerator-for-financial-services/minor/{fins-version}/pages/Use%20case%205%20-%20Optimize%20customer%20experiences%20with%20CDP/[Optimize Customer Experiences with Salesforce CDP^] use case provides support for ingesting data from multiple sources into Data Cloud and then using the results of Data Cloud activations to optimize customer experiences by providing Customer Service Representatives (CSRs) with marketing insights. === Salesforce Org Sync -The https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/mulesoft-accelerator-for-financial-services/minor/{fins-version}/pages/Use%20case%206%20-%20Salesforce%20org%20sync/[Salesforce Org Sync^] use case enables financial institutions using a multi-org strategy to sync customer data across Salesforce Financial Services Cloud, Sales Cloud, and Service Cloud orgs. +The https://anypoint.mulesoft.com/exchange/org.mule.examples/mulesoft-accelerator-for-financial-services/minor/{fins-version}/pages/Use%20case%206%20-%20Salesforce%20org%20sync/[Salesforce Org Sync^] use case enables financial institutions using a multi-org strategy to sync customer data across Salesforce Financial Services Cloud, Sales Cloud, and Service Cloud orgs. === Additional Assets The following *use-case agnostic* assets are also available: -* https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/mulesoft-accelerator-for-financial-services/minor/{fins-version}/pages/BIAN%20assets/[BIAN assets^] - Jumpstart your BIAN standard implementation using these BIAN-compliant assets, including API specs and implementation templates. +* https://anypoint.mulesoft.com/exchange/org.mule.examples/mulesoft-accelerator-for-financial-services/minor/{fins-version}/pages/BIAN%20assets/[BIAN assets^] - Jumpstart your BIAN standard implementation using these BIAN-compliant assets, including API specs and implementation templates. == See Also @@ -51,4 +51,4 @@ The following *use-case agnostic* assets are also available: * xref:prerequisites.adoc[Prerequisites] * xref:release-notes.adoc[Release Notes] * xref:upgrade-notes.adoc[Upgrade Notes] -* https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/mulesoft-accelerator-for-financial-services/[MuleSoft Accelerator for Financial Services on Exchange^] +* https://anypoint.mulesoft.com/exchange/org.mule.examples/mulesoft-accelerator-for-financial-services/[MuleSoft Accelerator for Financial Services on Exchange^] diff --git a/financial-services/1.8/modules/ROOT/pages/payments-setup-guide.adoc b/financial-services/1.8/modules/ROOT/pages/payments-setup-guide.adoc index e84ae2406..b614ba3b6 100644 --- a/financial-services/1.8/modules/ROOT/pages/payments-setup-guide.adoc +++ b/financial-services/1.8/modules/ROOT/pages/payments-setup-guide.adoc @@ -9,7 +9,7 @@ This guide provides instructions for setting up all the components required to r * Moov.io containers will be used to simulate the processing of ACH and Fedwire messages * A third-party Java library will be used to simulate the processing of SWIFT messages * A custom process will be used to simulate incoming payment confirmations -* A https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fins-payments-frontend-webui-src/[Payments Front-end Web UI^] has been built to demonstrate the functionality implemented by this use case +* A https://anypoint.mulesoft.com/exchange/org.mule.examples/fins-payments-frontend-webui-src/[Payments Front-end Web UI^] has been built to demonstrate the functionality implemented by this use case * MultiChain Wallet Node is used to support processing of BlockChain Transactions == Setup @@ -20,20 +20,20 @@ The following containerized services are deployed on docker. For demo purposes, * moov.io ACH service * moov.io Fedwire service -* https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fins-payments-frontend-webui-src/[Payments Front-end Web UI^] +* https://anypoint.mulesoft.com/exchange/org.mule.examples/fins-payments-frontend-webui-src/[Payments Front-end Web UI^] * Blockchain based on https://www.multichain.com/[MultiChain^] -The https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fins-payments-frontend-webui-src/[Payments Front-end Web UI^] can also be run locally, outside of a container, by following the instructions provided in its README file. +The https://anypoint.mulesoft.com/exchange/org.mule.examples/fins-payments-frontend-webui-src/[Payments Front-end Web UI^] can also be run locally, outside of a container, by following the instructions provided in its README file. *Payments Front-end Web UI recommended setup:* . Install Docker and its dependencies on the server of your choice. -. Configure the https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fins-payments-frontend-webui-src/[Payments Front-end Web UI^] by modifying the following properties in the .env file: - ** `REACT_APP_PAYMENTS_WEBUI_EXP_API_ENDPOINT` should point to an instance of the https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fins-payments-webui-exp-api-spec/[Payments Web UI Experience API^] - ** `REACT_APP_PAYMENTS_WEBUI_EXP_API_WEBSOCKET_ENDPOINT` should point to an instance of the https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fins-payments-webui-exp-api-spec/[Payments Web UI Experience API^] +. Configure the https://anypoint.mulesoft.com/exchange/org.mule.examples/fins-payments-frontend-webui-src/[Payments Front-end Web UI^] by modifying the following properties in the .env file: + ** `REACT_APP_PAYMENTS_WEBUI_EXP_API_ENDPOINT` should point to an instance of the https://anypoint.mulesoft.com/exchange/org.mule.examples/fins-payments-webui-exp-api-spec/[Payments Web UI Experience API^] + ** `REACT_APP_PAYMENTS_WEBUI_EXP_API_WEBSOCKET_ENDPOINT` should point to an instance of the https://anypoint.mulesoft.com/exchange/org.mule.examples/fins-payments-webui-exp-api-spec/[Payments Web UI Experience API^] . Build the docker image by running its docker-build.sh script. . Start the docker container by running the docker-run.sh script on the machine running the Docker server, or use a Docker administration UI to manage the containers. -. Update `https.cors.allow-url` property in the https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fins-payments-webui-exp-api/[Payments Web UI Experience API^] with the Payments Front-end Web UI endpoint to allow CORS. +. Update `https.cors.allow-url` property in the https://anypoint.mulesoft.com/exchange/org.mule.examples/fins-payments-webui-exp-api/[Payments Web UI Experience API^] with the Payments Front-end Web UI endpoint to allow CORS. *Moov.io recommended setup:* @@ -43,7 +43,7 @@ The moov.io images are provided pre-built as-is. They can be started on the Dock To run the MultiChain node as a docker container, perform the following steps: -. Use the Dockerfile from the scripts folder in the https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fins-blockchain-sys-api-spec/[Blockchain System API^] to build the MultiChain image. +. Use the Dockerfile from the scripts folder in the https://anypoint.mulesoft.com/exchange/org.mule.examples/fins-blockchain-sys-api-spec/[Blockchain System API^] to build the MultiChain image. . Run the `docker-run.sh` script to deploy the container and setup network ports. Run `docker-exec.sh` to create MultiChain and configure the json-rpc service to interact with the MultiChain container. == See Also diff --git a/financial-services/1.8/modules/ROOT/pages/release-notes.adoc b/financial-services/1.8/modules/ROOT/pages/release-notes.adoc index 2b5c333d9..67b3a4772 100644 --- a/financial-services/1.8/modules/ROOT/pages/release-notes.adoc +++ b/financial-services/1.8/modules/ROOT/pages/release-notes.adoc @@ -62,8 +62,8 @@ This use case enables a streamlined and automated client onboarding solution. We Introduces the Address change orchestration use case. There are two extensions of this use case: -* https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/mulesoft-accelerator-for-financial-services/minor/{fins-version}/pages/Use%20case%204a%20-%20Address%20change%20orchestration%20-%20Insurance/[Use case 4a - Address change orchestration: Insurance^] -- Streamline downstream events that result from policyholder or carrier postal address adjustments. The address change orchestration use case for insurance delivers a solution for address confirmation, seamless policyholder data updates, and single home policy coverage assessments, resulting in faster policyholder premium updates. -* https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/mulesoft-accelerator-for-financial-services/minor/{fins-version}/pages/Use%20case%202a%20-%20Customer%20onboarding%20-%20Banking/[Use case 4b - Address change orchestration: Banking^] -- Enhance your customer service teams`' upsell, cross-sell, and service opportunities that result from customer postal code address changes. The address change orchestration use case for banking supports faster address validation and increased customer service opportunities, including personalized products and offers. +* https://anypoint.mulesoft.com/exchange/org.mule.examples/mulesoft-accelerator-for-financial-services/minor/{fins-version}/pages/Use%20case%204a%20-%20Address%20change%20orchestration%20-%20Insurance/[Use case 4a - Address change orchestration: Insurance^] -- Streamline downstream events that result from policyholder or carrier postal address adjustments. The address change orchestration use case for insurance delivers a solution for address confirmation, seamless policyholder data updates, and single home policy coverage assessments, resulting in faster policyholder premium updates. +* https://anypoint.mulesoft.com/exchange/org.mule.examples/mulesoft-accelerator-for-financial-services/minor/{fins-version}/pages/Use%20case%202a%20-%20Customer%20onboarding%20-%20Banking/[Use case 4b - Address change orchestration: Banking^] -- Enhance your customer service teams`' upsell, cross-sell, and service opportunities that result from customer postal code address changes. The address change orchestration use case for banking supports faster address validation and increased customer service opportunities, including personalized products and offers. == v1.3 @@ -81,7 +81,7 @@ A few assets were updated to correct minor issues, including: === Payments modernization Use Case -Introduces the https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/mulesoft-accelerator-for-financial-services/minor/{fins-version}/pages/Use%20case%203%20-%20Payments%20modernization/[Payments modernization^] use case, which accelerates the development of modern payment solutions for Financial Institutions. Banks and Credit Unions will be able to deliver a diverse payments landscape that can address multiple types of financial transactions and customer needs. +Introduces the https://anypoint.mulesoft.com/exchange/org.mule.examples/mulesoft-accelerator-for-financial-services/minor/{fins-version}/pages/Use%20case%203%20-%20Payments%20modernization/[Payments modernization^] use case, which accelerates the development of modern payment solutions for Financial Institutions. Banks and Credit Unions will be able to deliver a diverse payments landscape that can address multiple types of financial transactions and customer needs. == v1.2 @@ -103,7 +103,7 @@ See the xref:upgrade-notes.adoc[Upgrade notes] for more information. === Customer onboarding Use Case -Introduces the https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/mulesoft-accelerator-for-financial-services/minor/{fins-version}/pages/Use%20case%202a%20-%20Customer%20onboarding%20-%20Banking/[Customer onboarding - Banking^] use case, which allows leverages Salesforce Financial Services Cloud as the system of engagement, DocuSign as the document management system, and Equifax as the credit analysis system. +Introduces the https://anypoint.mulesoft.com/exchange/org.mule.examples/mulesoft-accelerator-for-financial-services/minor/{fins-version}/pages/Use%20case%202a%20-%20Customer%20onboarding%20-%20Banking/[Customer onboarding - Banking^] use case, which allows leverages Salesforce Financial Services Cloud as the system of engagement, DocuSign as the document management system, and Equifax as the credit analysis system. == v1.0 @@ -113,7 +113,7 @@ Introduces the https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ff This is the first release of the MuleSoft Accelerator for Financial Services. -This accelerator also introduces the https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/mulesoft-accelerator-for-financial-services/minor/{fins-version}/pages/Use%20case%201%20-%20Core%20banking%20foundation/[Core banking foundation^] use case, which allows for the display of a customer's financial summary from multiple systems. The customer and customer service representative (CSR) views are supported in this release. +This accelerator also introduces the https://anypoint.mulesoft.com/exchange/org.mule.examples/mulesoft-accelerator-for-financial-services/minor/{fins-version}/pages/Use%20case%201%20-%20Core%20banking%20foundation/[Core banking foundation^] use case, which allows for the display of a customer's financial summary from multiple systems. The customer and customer service representative (CSR) views are supported in this release. == See Also diff --git a/financial-services/1.8/modules/ROOT/pages/sfdc-data-cloud-setup-guide.adoc b/financial-services/1.8/modules/ROOT/pages/sfdc-data-cloud-setup-guide.adoc index 963031073..404a73bbc 100644 --- a/financial-services/1.8/modules/ROOT/pages/sfdc-data-cloud-setup-guide.adoc +++ b/financial-services/1.8/modules/ROOT/pages/sfdc-data-cloud-setup-guide.adoc @@ -1,7 +1,7 @@ = Salesforce Data Cloud Setup Guide :fins-version: {page-component-version} -The following provides guidance on Salesforce Data Cloud setup required for the https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/mulesoft-accelerator-for-financial-services/minor/{fins-version}/pages/Use%20case%205%20-%20Optimize%20customer%20experiences%20with%20CDP/[Optimize Customer Experiences with Data Cloud^] use case. A few of these steps can be omitted if deploying the https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fins-salesforce-cdp-sys-api[FINS Salesforce Data Cloud System API^] independently of the use case. +The following provides guidance on Salesforce Data Cloud setup required for the https://anypoint.mulesoft.com/exchange/org.mule.examples/mulesoft-accelerator-for-financial-services/minor/{fins-version}/pages/Use%20case%205%20-%20Optimize%20customer%20experiences%20with%20CDP/[Optimize Customer Experiences with Data Cloud^] use case. A few of these steps can be omitted if deploying the https://anypoint.mulesoft.com/exchange/org.mule.examples/fins-salesforce-cdp-sys-api[FINS Salesforce Data Cloud System API^] independently of the use case. == Data Cloud provisioning @@ -13,7 +13,7 @@ If the Data Cloud instance is already provisioned, skip this section. If not fol . Click `Get Started` to provision the Data Cloud Instance and it can take a few minutes. Correct any issues reported and finish the setup. The Data Cloud instance is considered to be successfully set up if there is a green tick mark for all the steps and you do not need to do anything. + + -image:https://www.mulesoft.com/ext/solutions/draft/images/fins-cdp-setup-cdp-provisioning.png[fins-cdp-setup-cdp-provisioning.png,79%] +image:https://www.mulesoft.com/ext/solutions/images/fins-cdp-setup-cdp-provisioning.png[fins-cdp-setup-cdp-provisioning.png,79%] + == Create data connectors @@ -22,7 +22,7 @@ Connectors are specialized data streams that communicate with external sources t === Use case requirements -The https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/mulesoft-accelerator-for-financial-services/minor/{fins-version}/pages/Use%20case%205%20-%20Optimize%20customer%20experiences%20with%20CDP/[Optimize Customer Experiences with CDP^] use case uses the following connectors: +The https://anypoint.mulesoft.com/exchange/org.mule.examples/mulesoft-accelerator-for-financial-services/minor/{fins-version}/pages/Use%20case%205%20-%20Optimize%20customer%20experiences%20with%20CDP/[Optimize Customer Experiences with CDP^] use case uses the following connectors: * Salesforce CRM - to connect data from a Salesforce CRM instance to Data Cloud. * Marketing Cloud - to receive segmentation results for marketing purposes. @@ -48,7 +48,7 @@ In Data Cloud, you can establish a connection to other Salesforce orgs built upo Once the connection is established, the Data Cloud admin can either use bundles that can automatically deploy data or set up their own data streams; we will walk through the latter approach, below. -For the https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/mulesoft-accelerator-for-financial-services/minor/{fins-version}/pages/Use%20case%205%20-%20Optimize%20customer%20experiences%20with%20CDP/[Optimize Customer Experiences with CDP^] use case, hover over the `Connector Name` field of the new connection and click the pencil icon to change the name of the Connector to `Salesforce FSC Banking`. This is the name that will appear under the `Salesforce Org` dropdown while creating a new Data Stream. +For the https://anypoint.mulesoft.com/exchange/org.mule.examples/mulesoft-accelerator-for-financial-services/minor/{fins-version}/pages/Use%20case%205%20-%20Optimize%20customer%20experiences%20with%20CDP/[Optimize Customer Experiences with CDP^] use case, hover over the `Connector Name` field of the new connection and click the pencil icon to change the name of the Connector to `Salesforce FSC Banking`. This is the name that will appear under the `Salesforce Org` dropdown while creating a new Data Stream. === Marketing Cloud Connector @@ -56,7 +56,7 @@ A Marketing Cloud Connector is required in order to use Marketing Cloud as eithe . Select `Marketing Cloud` from the left navigation menu in the `Data Cloud Setup` app. . Enter the Credentials to authenticate your Marketing Cloud account. You can proceed with the next step in the setup only if the authentication is successful. -. Data Source setup - this step is optional, and only needs to be set up if you are planning to ingest data from Marketing Cloud into Data Cloud. This step is not required for the https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/mulesoft-accelerator-for-financial-services/minor/{fins-version}/pages/Use%20case%205%20-%20Optimize%20customer%20experiences%20with%20CDP/[Optimize Customer Experiences with CDP^] use case. +. Data Source setup - this step is optional, and only needs to be set up if you are planning to ingest data from Marketing Cloud into Data Cloud. This step is not required for the https://anypoint.mulesoft.com/exchange/org.mule.examples/mulesoft-accelerator-for-financial-services/minor/{fins-version}/pages/Use%20case%205%20-%20Optimize%20customer%20experiences%20with%20CDP/[Optimize Customer Experiences with CDP^] use case. . Select Business Units to activate - select the business units to publish segments to Marketing Cloud. Ensure all configured items show a green circle before using the connector. @@ -65,7 +65,7 @@ Ensure all configured items show a green circle before using the connector. You can push data from an external system into Data Cloud via the Ingestion API. This RESTful API offers two interaction patterns: bulk and streaming. The streaming pattern accepts incremental updates to a data set as those changes are captured, while the bulk pattern accepts CSV files in cases where data syncs occur periodically. The same data stream can accept data from the streaming and the bulk interaction. -For the https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/mulesoft-accelerator-for-financial-services/minor/{fins-version}/pages/Use%20case%205%20-%20Optimize%20customer%20experiences%20with%20CDP/[Optimize Customer Experiences with CDP^] use case, the external systems Snowflake, Databricks, and Amazon S3 contain data to be pushed to Data Cloud through MuleSoft's Salesforce CDP connector using the Ingestion API. The schema file for the Ingestion API can be found in the https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fins-salesforce-cdp-sys-api/[FINS Salesforce CDP System API^] implementation template. This schema includes definitions for the following objects: +For the https://anypoint.mulesoft.com/exchange/org.mule.examples/mulesoft-accelerator-for-financial-services/minor/{fins-version}/pages/Use%20case%205%20-%20Optimize%20customer%20experiences%20with%20CDP/[Optimize Customer Experiences with CDP^] use case, the external systems Snowflake, Databricks, and Amazon S3 contain data to be pushed to Data Cloud through MuleSoft's Salesforce CDP connector using the Ingestion API. The schema file for the Ingestion API can be found in the https://anypoint.mulesoft.com/exchange/org.mule.examples/fins-salesforce-cdp-sys-api/[FINS Salesforce CDP System API^] implementation template. This schema includes definitions for the following objects: * FinancialAccount * FinancialTransaction @@ -83,7 +83,7 @@ Follow the steps below to setup and configure an ingestion API to push data from . Click `New`, enter a name for the API source (for example, 'FINS_Banking-Data-Connector'), then click `Save`. . On the details page for the new connector, you must upload a schema file in OpenAPI (OAS) format with a `.yaml` file extension. The schema file describes how data transferred via the API is structured. + *Note:* Ingestion API schemas have set requirements - review the schema requirements below if having issues uploading the schema. -. Click `Upload Schema` and navigate to the location of the file you want to use. Select the file and click Open. For the https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/mulesoft-accelerator-for-financial-services/minor/{fins-version}/pages/Use%20case%205%20-%20Optimize%20customer%20experiences%20with%20CDP/[Optimize Customer Experiences with CDP^] use case, the schema file `mule-cdp-connector-schema.yaml` is available under `src/test/resources/cdp-schema` of the https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fins-salesforce-cdp-sys-api/[FINS Salesforce CDP System API^] implementation template. +. Click `Upload Schema` and navigate to the location of the file you want to use. Select the file and click Open. For the https://anypoint.mulesoft.com/exchange/org.mule.examples/mulesoft-accelerator-for-financial-services/minor/{fins-version}/pages/Use%20case%205%20-%20Optimize%20customer%20experiences%20with%20CDP/[Optimize Customer Experiences with CDP^] use case, the schema file `mule-cdp-connector-schema.yaml` is available under `src/test/resources/cdp-schema` of the https://anypoint.mulesoft.com/exchange/org.mule.examples/fins-salesforce-cdp-sys-api/[FINS Salesforce CDP System API^] implementation template. . Preview all the detected objects and their attributes in your schema. . Click `Save`. @@ -108,7 +108,7 @@ Before you can send data into Data Cloud using Ingestion API via Mulesoft's Sale ** `Perform requests on your behalf at any time (refresh_token, offline_access)` . Click `Save` and then `Done` to create the connected app. -After creating the connected app, click the `Manage Consumer Details` button from the app detail page, confirm your identity, and then record the `Consumer Key` and `Consumer Secret` values: you will need these to configure the https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fins-salesforce-cdp-sys-api/[FINS Salesforce CDP System API] implementation template for deployment. This application uses the MuleSoft Connector for Salesforce CDP, which provides customers a pipeline to send data into Data Cloud. Refer to the https://dev-docs-internal.kqa.msap.io/beta-accelerators/salesforce-cdp-connector/1.0/[Salesforce CDP Connector documentation] for additional details on configuration and available operations. +After creating the connected app, click the `Manage Consumer Details` button from the app detail page, confirm your identity, and then record the `Consumer Key` and `Consumer Secret` values: you will need these to configure the https://anypoint.mulesoft.com/exchange/org.mule.examples/fins-salesforce-cdp-sys-api/[FINS Salesforce CDP System API] implementation template for deployment. This application uses the MuleSoft Connector for Salesforce CDP, which provides customers a pipeline to send data into Data Cloud. Refer to the https://docs.mulesoft.com/salesforce-cdp-connector/1.0/[Salesforce CDP Connector documentation] for additional details on configuration and available operations. ==== Schema requirements @@ -150,7 +150,7 @@ To begin the flow of data from a Salesforce CRM data source (such as your Salesf ==== Use case requirements -For the https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/mulesoft-accelerator-for-financial-services/minor/{fins-version}/pages/Use%20case%205%20-%20Optimize%20customer%20experiences%20with%20CDP/[Optimize Customer Experiences with CDP^] use case, a separate data stream for each of the following objects must be created to pull required data from your Salesforce FSC instance: +For the https://anypoint.mulesoft.com/exchange/org.mule.examples/mulesoft-accelerator-for-financial-services/minor/{fins-version}/pages/Use%20case%205%20-%20Optimize%20customer%20experiences%20with%20CDP/[Optimize Customer Experiences with CDP^] use case, a separate data stream for each of the following objects must be created to pull required data from your Salesforce FSC instance: |=== | Object in Salesforce CRM | Name of the DataStream @@ -257,7 +257,7 @@ NOTE: If you are prompted with an error stating those objects cannot be added, y ==== Add formula fields -Once the data streams for standard objects have been created, we need to add a formula field to identify whether or not the associated party represents an Individual. This is required for proper identity resolution and segmentation for the https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/mulesoft-accelerator-for-financial-services/minor/{fins-version}/pages/Use%20case%205%20-%20Optimize%20customer%20experiences%20with%20CDP/[Optimize Customer Experiences with CDP^] use case. Repeat the following steps for both data streams created above: +Once the data streams for standard objects have been created, we need to add a formula field to identify whether or not the associated party represents an Individual. This is required for proper identity resolution and segmentation for the https://anypoint.mulesoft.com/exchange/org.mule.examples/mulesoft-accelerator-for-financial-services/minor/{fins-version}/pages/Use%20case%205%20-%20Optimize%20customer%20experiences%20with%20CDP/[Optimize Customer Experiences with CDP^] use case. Repeat the following steps for both data streams created above: . Click the data stream from the 'Data Streams' list view to bring up the details page. . Select the `New Formula Field` action from the top right action list. You may need to click the 'more' down arrow to find the action. @@ -284,7 +284,7 @@ If you encounter object access errors in Data Cloud when creating data streams, . Enable Read and View All permissions for the object and Read Access for each field. Use the table above for reference. . Click Save. -Repeat these steps for all objects and fields you want to ingest into Data Cloud. For the https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/mulesoft-accelerator-for-financial-services/minor/{fins-version}/pages/Use%20case%205%20-%20Optimize%20customer%20experiences%20with%20CDP/[Optimize Customer Experiences with CDP^] use case, this includes the `Account` and `Contact` objects. +Repeat these steps for all objects and fields you want to ingest into Data Cloud. For the https://anypoint.mulesoft.com/exchange/org.mule.examples/mulesoft-accelerator-for-financial-services/minor/{fins-version}/pages/Use%20case%205%20-%20Optimize%20customer%20experiences%20with%20CDP/[Optimize Customer Experiences with CDP^] use case, this includes the `Account` and `Contact` objects. === Create an Ingestion API data stream @@ -292,7 +292,7 @@ If you have not already done so, < / " : ? | , _ &+` . Click `Save`. -This completes the configuration of Data Cloud required for the https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/mulesoft-accelerator-for-financial-services/minor/{fins-version}/pages/Use%20case%205%20-%20Optimize%20customer%20experiences%20with%20CDP/[Optimize Customer Experiences with CDP^] use case. +This completes the configuration of Data Cloud required for the https://anypoint.mulesoft.com/exchange/org.mule.examples/mulesoft-accelerator-for-financial-services/minor/{fins-version}/pages/Use%20case%205%20-%20Optimize%20customer%20experiences%20with%20CDP/[Optimize Customer Experiences with CDP^] use case. == See Also diff --git a/financial-services/1.8/modules/ROOT/pages/sfdc-fsc-setup-guide.adoc b/financial-services/1.8/modules/ROOT/pages/sfdc-fsc-setup-guide.adoc index d60590e73..3a9693e77 100644 --- a/financial-services/1.8/modules/ROOT/pages/sfdc-fsc-setup-guide.adoc +++ b/financial-services/1.8/modules/ROOT/pages/sfdc-fsc-setup-guide.adoc @@ -429,7 +429,7 @@ The following fields must be created in the corresponding objects. === Create via Apex Script -An Apex class called `CustomFieldUtility` can be used to create custom fields programmatically. The source for this class can be found in the https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fins-common-resources-src[FINS Common Resources^] project. Download this project and follow the steps below. +An Apex class called `CustomFieldUtility` can be used to create custom fields programmatically. The source for this class can be found in the https://anypoint.mulesoft.com/exchange/org.mule.examples/fins-common-resources-src[FINS Common Resources^] project. Download this project and follow the steps below. . Click on Salesforce Setup icon and select `Developer Console` to open a new console window . Go to `+File -> New -> Apex class+` and create a new class named `CustomFieldUtility` @@ -532,7 +532,7 @@ If desired, click the *Currency Setup* button to add support for additional curr == Create Platform Events and Apex Triggers -The following Platform Event Objects and Apex Triggers must be created in order to capture updates from Salesforce. The scripts to create these Apex Triggers and add fields to Platform Event Objects are located in the https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fins-common-resources-src/[FINS Common Resources] project. +The following Platform Event Objects and Apex Triggers must be created in order to capture updates from Salesforce. The scripts to create these Apex Triggers and add fields to Platform Event Objects are located in the https://anypoint.mulesoft.com/exchange/org.mule.examples/fins-common-resources-src/[FINS Common Resources] project. |=== | Salesforce Object | Salesforce Platform Event Object | Salesforce Platform Event API Name | Apex Trigger Name @@ -590,7 +590,7 @@ This implementation requires creation of Platform Events in Salesforce. To creat . Login to Salesforce. . Click Setup to search for Platform Events in Quick Find Box. Platform Events Page under Integrations section appears with list of available Platform Events. . Click *New Platform Event* button to create an Object and enter Platform Information Details fields like Label, Plural Label and Object with Object Name and Event API Names as above table. Click Save. Repeat this step for creating multiple Salesforce Platform Event Objects as mentioned in the above table. -. To add Custom Fields & Relationships to Platform Event Definitions, run the utility scripts (`CreatePlatformEventsCustomFields.txt`) available in the https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fins-common-resources-src/[FINS Common Resources^] under the `/salesforce` folder. +. To add Custom Fields & Relationships to Platform Event Definitions, run the utility scripts (`CreatePlatformEventsCustomFields.txt`) available in the https://anypoint.mulesoft.com/exchange/org.mule.examples/fins-common-resources-src/[FINS Common Resources^] under the `/salesforce` folder. === Create Apex Triggers @@ -600,7 +600,7 @@ Follow the below steps to create the Apex Triggers . Click Setup to search for Object Manager in Quick Find Box. . Search for the Salesforce Object. A page appears with Details of the Object. . Click Triggers unders the Details section to see list of available triggers on the Object. Click New. -. Copy the Trigger Script code searching by Apex Trigger Name (mentioned in the above table for the SalesforceObject) in CreateApexTriggers.txt of https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fins-common-resources-src/[FINS Common Resources] to the script editor. CreateApexTriggers.txt file is available under /salesforce folder. +. Copy the Trigger Script code searching by Apex Trigger Name (mentioned in the above table for the SalesforceObject) in CreateApexTriggers.txt of https://anypoint.mulesoft.com/exchange/org.mule.examples/fins-common-resources-src/[FINS Common Resources] to the script editor. CreateApexTriggers.txt file is available under /salesforce folder. . Obtain the `LastModifiedById` and `RecordTypeId` (if it exists) by running the queries mentioned in the trigger from Developer Console. . Replace the values in the script and Save the trigger. . Click Save and ensure isActive checkbox is ticked. @@ -677,7 +677,7 @@ You now need to copy the `Consumer Key` and `Consumer Secret` values for use in . Verify your identity by entering the verification code that was emailed to you. . Copy the key and secret values and update your `settings.xml` file as described above. -Download the https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fins-common-resources-src[FINS Common Resources project^] for a sample `settings.xml` file that can be used as a starting point. +Download the https://anypoint.mulesoft.com/exchange/org.mule.examples/fins-common-resources-src[FINS Common Resources project^] for a sample `settings.xml` file that can be used as a starting point. == Generating Security Token for Service Account diff --git a/financial-services/1.8/modules/ROOT/pages/sfdc-mc-setup-guide.adoc b/financial-services/1.8/modules/ROOT/pages/sfdc-mc-setup-guide.adoc index be8885537..54d157d0b 100644 --- a/financial-services/1.8/modules/ROOT/pages/sfdc-mc-setup-guide.adoc +++ b/financial-services/1.8/modules/ROOT/pages/sfdc-mc-setup-guide.adoc @@ -1,12 +1,12 @@ = Salesforce Marketing Cloud Setup Guide :fins-version: {page-component-version} -This guide provides the setup instructions for Marketing Cloud for the following use cases that are part of the https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/mulesoft-accelerator-for-financial-services/[MuleSoft Accelerator for Financial Services^]: +This guide provides the setup instructions for Marketing Cloud for the following use cases that are part of the https://anypoint.mulesoft.com/exchange/org.mule.examples/mulesoft-accelerator-for-financial-services/[MuleSoft Accelerator for Financial Services^]: -* https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/mulesoft-accelerator-for-financial-services/minor/{fins-version}/pages/Use%20case%202b%20-%20Client%20onboarding%20-%20Wealth%20management/[Use case 2b - Client onboarding - Wealth management^] -* https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/mulesoft-accelerator-for-financial-services/minor/{fins-version}/pages/Use%20case%204a%20-%20Address%20change%20orchestration%20-%20Insurance/[Use case 4a - Address change orchestration - Insurance^] -* https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/mulesoft-accelerator-for-financial-services/minor/{fins-version}/pages/Use%20case%204b%20-%20Address%20change%20orchestration%20-%20Banking/[Use case 4b - Address change orchestration - Banking^] -* https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/mulesoft-accelerator-for-financial-services/minor/{fins-version}/pages/Use%20case%205%20-%20Optimize%20customer%20experiences%20with%20CDP/[Use case 5 - Optimize customer experiences with CDP^] +* https://anypoint.mulesoft.com/exchange/org.mule.examples/mulesoft-accelerator-for-financial-services/minor/{fins-version}/pages/Use%20case%202b%20-%20Client%20onboarding%20-%20Wealth%20management/[Use case 2b - Client onboarding - Wealth management^] +* https://anypoint.mulesoft.com/exchange/org.mule.examples/mulesoft-accelerator-for-financial-services/minor/{fins-version}/pages/Use%20case%204a%20-%20Address%20change%20orchestration%20-%20Insurance/[Use case 4a - Address change orchestration - Insurance^] +* https://anypoint.mulesoft.com/exchange/org.mule.examples/mulesoft-accelerator-for-financial-services/minor/{fins-version}/pages/Use%20case%204b%20-%20Address%20change%20orchestration%20-%20Banking/[Use case 4b - Address change orchestration - Banking^] +* https://anypoint.mulesoft.com/exchange/org.mule.examples/mulesoft-accelerator-for-financial-services/minor/{fins-version}/pages/Use%20case%205%20-%20Optimize%20customer%20experiences%20with%20CDP/[Use case 5 - Optimize customer experiences with CDP^] == Create Data Extension for Sync Process @@ -101,7 +101,7 @@ Journey Builder is used to trigger emails to a list of email addresses. The foll === Create Online Submission Form -This is the form that the client will submit so that the https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fins-salesforce-wealth-exp-api/[Salesforce Wealth Experience API] will be invoked to create a lead in FSC: +This is the form that the client will submit so that the https://anypoint.mulesoft.com/exchange/org.mule.examples/fins-salesforce-wealth-exp-api/[Salesforce Wealth Experience API] will be invoked to create a lead in FSC: * Navigate to Web Studio and click Cloudpages * Create a Collection diff --git a/financial-services/1.9/modules/ROOT/pages/_partials/custom-components-fragment.adoc b/financial-services/1.9/modules/ROOT/pages/_partials/custom-components-fragment.adoc index 4d7df4589..362076363 100644 --- a/financial-services/1.9/modules/ROOT/pages/_partials/custom-components-fragment.adoc +++ b/financial-services/1.9/modules/ROOT/pages/_partials/custom-components-fragment.adoc @@ -2,9 +2,9 @@ The following non-application components provide additional functionality in sup [cols="70,30",width=100%] |=== -| FINS Common Resources | https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fins-common-resources-src[ Source^] -| FINS Financial Account Sync Lightning Web Component | https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fins-financial-account-sync-lwc-src[ Source^] -| FINS Fraud Analysis Application | https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fins-fraud-analysis-application-src[ Source^] -| FINS Open Banking Library | https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fins-openbanking-library[ Source^] -| FINS Payments Frontend Web UI | https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fins-payments-frontend-webui-src[ Source^] +| FINS Common Resources | https://anypoint.mulesoft.com/exchange/org.mule.examples/fins-common-resources-src[ Source^] +| FINS Financial Account Sync Lightning Web Component | https://anypoint.mulesoft.com/exchange/org.mule.examples/fins-financial-account-sync-lwc-src[ Source^] +| FINS Fraud Analysis Application | https://anypoint.mulesoft.com/exchange/org.mule.examples/fins-fraud-analysis-application-src[ Source^] +| FINS Open Banking Library | https://anypoint.mulesoft.com/exchange/org.mule.examples/fins-openbanking-library[ Source^] +| FINS Payments Frontend Web UI | https://anypoint.mulesoft.com/exchange/org.mule.examples/fins-payments-frontend-webui-src[ Source^] |=== diff --git a/financial-services/1.9/modules/ROOT/pages/_partials/experience-apis-fragment.adoc b/financial-services/1.9/modules/ROOT/pages/_partials/experience-apis-fragment.adoc index 7a68e4bb1..0b302dce0 100644 --- a/financial-services/1.9/modules/ROOT/pages/_partials/experience-apis-fragment.adoc +++ b/financial-services/1.9/modules/ROOT/pages/_partials/experience-apis-fragment.adoc @@ -2,15 +2,15 @@ The following APIs are provided for use by external systems to interact with fun [cols="40,30,30",width=100%] |=== -|FINS DocuSign Experience API | https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fins-docusign-exp-api-spec[API Specification^] | https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fins-docusign-exp-api[Implementation Template^] -|FINS Jack Henry Events Experience API | | https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fins-jackhenry-events-exp-api[Implementation Template^] -|FINS Mobile Experience API | https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fins-mobile-exp-api-spec[API Specification^] | https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fins-mobile-exp-api[Implementation Template^] -|FINS Open Banking Accounts Experience API | https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fins-openbanking-accounts-exp-api-spec[API Specification^] | https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fins-openbanking-accounts-exp-api[Implementation Template^] -|FINS Open Banking ASPSP Experience API | https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fins-openbanking-aspsp-exp-api-spec[API Specification^] | https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fins-openbanking-aspsp-exp-api[Implementation Template^] -|FINS Open Banking PISP Domestic Experience API | https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fins-openbanking-pisp-dom-exp-api-spec[API Specification^] | https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fins-openbanking-pisp-dom-exp-api[Implementation Template^] -|FINS Open Banking PISP International Experience API | https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fins-openbanking-pisp-intl-exp-api-spec[API Specification^] | https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fins-openbanking-pisp-intl-exp-api[Implementation Template^] -|FINS Payments Web UI Experience API | https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fins-payments-webui-exp-api-spec[API Specification^] | https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fins-payments-webui-exp-api[Implementation Template^] -|FINS Salesforce Financial Experience API | https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fins-salesforce-financial-exp-api-spec[API Specification^] | https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fins-salesforce-financial-exp-api[Implementation Template^] -|FINS Salesforce Insurance Experience API | https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fins-salesforce-insurance-exp-api-spec[API Specification^] | https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fins-salesforce-insurance-exp-api[Implementation Template^] -|FINS Salesforce Wealth Experience API | https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fins-salesforce-wealth-exp-api-spec[API Specification^] | https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fins-salesforce-wealth-exp-api[Implementation Template^] +|FINS DocuSign Experience API | https://anypoint.mulesoft.com/exchange/org.mule.examples/fins-docusign-exp-api-spec[API Specification^] | https://anypoint.mulesoft.com/exchange/org.mule.examples/fins-docusign-exp-api[Implementation Template^] +|FINS Jack Henry Events Experience API | | https://anypoint.mulesoft.com/exchange/org.mule.examples/fins-jackhenry-events-exp-api[Implementation Template^] +|FINS Mobile Experience API | https://anypoint.mulesoft.com/exchange/org.mule.examples/fins-mobile-exp-api-spec[API Specification^] | https://anypoint.mulesoft.com/exchange/org.mule.examples/fins-mobile-exp-api[Implementation Template^] +|FINS Open Banking Accounts Experience API | https://anypoint.mulesoft.com/exchange/org.mule.examples/fins-openbanking-accounts-exp-api-spec[API Specification^] | https://anypoint.mulesoft.com/exchange/org.mule.examples/fins-openbanking-accounts-exp-api[Implementation Template^] +|FINS Open Banking ASPSP Experience API | https://anypoint.mulesoft.com/exchange/org.mule.examples/fins-openbanking-aspsp-exp-api-spec[API Specification^] | https://anypoint.mulesoft.com/exchange/org.mule.examples/fins-openbanking-aspsp-exp-api[Implementation Template^] +|FINS Open Banking PISP Domestic Experience API | https://anypoint.mulesoft.com/exchange/org.mule.examples/fins-openbanking-pisp-dom-exp-api-spec[API Specification^] | https://anypoint.mulesoft.com/exchange/org.mule.examples/fins-openbanking-pisp-dom-exp-api[Implementation Template^] +|FINS Open Banking PISP International Experience API | https://anypoint.mulesoft.com/exchange/org.mule.examples/fins-openbanking-pisp-intl-exp-api-spec[API Specification^] | https://anypoint.mulesoft.com/exchange/org.mule.examples/fins-openbanking-pisp-intl-exp-api[Implementation Template^] +|FINS Payments Web UI Experience API | https://anypoint.mulesoft.com/exchange/org.mule.examples/fins-payments-webui-exp-api-spec[API Specification^] | https://anypoint.mulesoft.com/exchange/org.mule.examples/fins-payments-webui-exp-api[Implementation Template^] +|FINS Salesforce Financial Experience API | https://anypoint.mulesoft.com/exchange/org.mule.examples/fins-salesforce-financial-exp-api-spec[API Specification^] | https://anypoint.mulesoft.com/exchange/org.mule.examples/fins-salesforce-financial-exp-api[Implementation Template^] +|FINS Salesforce Insurance Experience API | https://anypoint.mulesoft.com/exchange/org.mule.examples/fins-salesforce-insurance-exp-api-spec[API Specification^] | https://anypoint.mulesoft.com/exchange/org.mule.examples/fins-salesforce-insurance-exp-api[Implementation Template^] +|FINS Salesforce Wealth Experience API | https://anypoint.mulesoft.com/exchange/org.mule.examples/fins-salesforce-wealth-exp-api-spec[API Specification^] | https://anypoint.mulesoft.com/exchange/org.mule.examples/fins-salesforce-wealth-exp-api[Implementation Template^] |=== diff --git a/financial-services/1.9/modules/ROOT/pages/_partials/listeners-fragment.adoc b/financial-services/1.9/modules/ROOT/pages/_partials/listeners-fragment.adoc index ac8366b48..6cf8a79c1 100644 --- a/financial-services/1.9/modules/ROOT/pages/_partials/listeners-fragment.adoc +++ b/financial-services/1.9/modules/ROOT/pages/_partials/listeners-fragment.adoc @@ -2,9 +2,9 @@ The following applications listen for events published by external systems and i [cols="70,30",width=100%] |=== -| FINS Payments ACH Listener | https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fins-payments-ach-listener[Source^] -| FINS Payments Fedwire Listener | https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fins-payments-fedwire-listener[Source^] -| FINS Payments SWIFT Listener | https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fins-payments-swift-listener[Source^] -| FINS Salesforce Marketing Listener | https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fins-salesforce-marketing-listener[Source^] -| FINS Salesforce Topic Listener | https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fins-salesforce-topic-listener[Source^] +| FINS Payments ACH Listener | https://anypoint.mulesoft.com/exchange/org.mule.examples/fins-payments-ach-listener[Source^] +| FINS Payments Fedwire Listener | https://anypoint.mulesoft.com/exchange/org.mule.examples/fins-payments-fedwire-listener[Source^] +| FINS Payments SWIFT Listener | https://anypoint.mulesoft.com/exchange/org.mule.examples/fins-payments-swift-listener[Source^] +| FINS Salesforce Marketing Listener | https://anypoint.mulesoft.com/exchange/org.mule.examples/fins-salesforce-marketing-listener[Source^] +| FINS Salesforce Topic Listener | https://anypoint.mulesoft.com/exchange/org.mule.examples/fins-salesforce-topic-listener[Source^] |=== diff --git a/financial-services/1.9/modules/ROOT/pages/_partials/process-apis-fragment.adoc b/financial-services/1.9/modules/ROOT/pages/_partials/process-apis-fragment.adoc index 74d34e2d0..bc4a0532d 100644 --- a/financial-services/1.9/modules/ROOT/pages/_partials/process-apis-fragment.adoc +++ b/financial-services/1.9/modules/ROOT/pages/_partials/process-apis-fragment.adoc @@ -2,22 +2,22 @@ The following APIs represent the core business processes that orchestrate the FI [cols="40,30,30",width=100%] |=== -| FINS Bank Accounts Process API | https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fins-bank-accounts-prc-api-spec[API Specification^] | https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fins-bank-accounts-prc-api[Implementation Template^] -| FINS Bank Loans Process API | https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fins-bank-loans-prc-api-spec[API Specification^] | https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fins-bank-loans-prc-api[Implementation Template^] -| FINS Core Banking Poller Process API | https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fins-core-banking-poller-prc-api-spec[API Specification^] | https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fins-core-banking-poller-prc-api[Implementation Template^] -| FINS Credit Card Poller Process API | https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fins-creditcard-poller-prc-api-spec[API Specification^] | https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fins-creditcard-poller-prc-api[Implementation Template^] -| FINS Customer Addresses Process API | https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fins-customer-addresses-prc-api-spec[API Specification^] | https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fins-customer-addresses-prc-api[Implementation Template^] -| FINS Customer Leads Process API | https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fins-customer-leads-prc-api-spec[API Specification^] | https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fins-customer-leads-prc-api[Implementation Template^] -| FINS Customers Process API | https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fins-customers-prc-api-spec[API Specification^] | https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fins-customers-prc-api[Implementation Template^] -| FINS Marketing Poller Process API | https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fins-marketing-poller-prc-api-spec[API Specification^] | https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fins-marketing-poller-prc-api[Implementation Template^] -| FINS Payments Initiation Process API | https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fins-bian-paymntinitiation-prc-api-spec[API Specification^] | https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fins-payments-initiation-prc-api[Implementation Template^] -| FINS Payments InterBank International Execution Process API | https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fins-bian-paymntexecution-prc-api-spec[API Specification^] | https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fins-payments-interbank-international-execution-prc-api[Implementation Template^] -| FINS Payments InterBank National Execution Process API | https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fins-bian-paymntexecution-prc-api-spec[API Specification^] | https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fins-payments-interbank-national-execution-prc-api[Implementation Template^] -| FINS Payments IntraBank International Execution Process API | https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fins-bian-paymntexecution-prc-api-spec[API Specification^] | https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fins-payments-intrabank-international-execution-prc-api[Implementation Template^] -| FINS Payments IntraBank National Execution Process API | https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fins-bian-paymntexecution-prc-api-spec[API Specification^] | https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fins-payments-intrabank-national-execution-prc-api[Implementation Template^] -| FINS Payments Order Process API | https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fins-bian-paymntorder-prc-api-spec[API Specification^] | https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fins-payments-order-prc-api[Implementation Template^] -| FINS Payments Remittances Process API | https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fins-bian-paymntexecution-prc-api-spec[API Specification^] | https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fins-payments-remittances-prc-api[Implementation Template^] -| FINS Payments Router Process API | https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fins-payments-router-prc-api-spec[API Specification^] | https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fins-payments-router-prc-api[Implementation Template^] -| FINS Payments Simulator Process API | https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fins-payments-simulator-prc-api-spec[API Specification^] | https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fins-payments-simulator-prc-api[Implementation Template^] -| FINS Reconciliation Process API | https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fins-reconciliation-prc-api-spec[API Specification^] | https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fins-reconciliation-prc-api[Implementation Template^] +| FINS Bank Accounts Process API | https://anypoint.mulesoft.com/exchange/org.mule.examples/fins-bank-accounts-prc-api-spec[API Specification^] | https://anypoint.mulesoft.com/exchange/org.mule.examples/fins-bank-accounts-prc-api[Implementation Template^] +| FINS Bank Loans Process API | https://anypoint.mulesoft.com/exchange/org.mule.examples/fins-bank-loans-prc-api-spec[API Specification^] | https://anypoint.mulesoft.com/exchange/org.mule.examples/fins-bank-loans-prc-api[Implementation Template^] +| FINS Core Banking Poller Process API | https://anypoint.mulesoft.com/exchange/org.mule.examples/fins-core-banking-poller-prc-api-spec[API Specification^] | https://anypoint.mulesoft.com/exchange/org.mule.examples/fins-core-banking-poller-prc-api[Implementation Template^] +| FINS Credit Card Poller Process API | https://anypoint.mulesoft.com/exchange/org.mule.examples/fins-creditcard-poller-prc-api-spec[API Specification^] | https://anypoint.mulesoft.com/exchange/org.mule.examples/fins-creditcard-poller-prc-api[Implementation Template^] +| FINS Customer Addresses Process API | https://anypoint.mulesoft.com/exchange/org.mule.examples/fins-customer-addresses-prc-api-spec[API Specification^] | https://anypoint.mulesoft.com/exchange/org.mule.examples/fins-customer-addresses-prc-api[Implementation Template^] +| FINS Customer Leads Process API | https://anypoint.mulesoft.com/exchange/org.mule.examples/fins-customer-leads-prc-api-spec[API Specification^] | https://anypoint.mulesoft.com/exchange/org.mule.examples/fins-customer-leads-prc-api[Implementation Template^] +| FINS Customers Process API | https://anypoint.mulesoft.com/exchange/org.mule.examples/fins-customers-prc-api-spec[API Specification^] | https://anypoint.mulesoft.com/exchange/org.mule.examples/fins-customers-prc-api[Implementation Template^] +| FINS Marketing Poller Process API | https://anypoint.mulesoft.com/exchange/org.mule.examples/fins-marketing-poller-prc-api-spec[API Specification^] | https://anypoint.mulesoft.com/exchange/org.mule.examples/fins-marketing-poller-prc-api[Implementation Template^] +| FINS Payments Initiation Process API | https://anypoint.mulesoft.com/exchange/org.mule.examples/fins-bian-paymntinitiation-prc-api-spec[API Specification^] | https://anypoint.mulesoft.com/exchange/org.mule.examples/fins-payments-initiation-prc-api[Implementation Template^] +| FINS Payments InterBank International Execution Process API | https://anypoint.mulesoft.com/exchange/org.mule.examples/fins-bian-paymntexecution-prc-api-spec[API Specification^] | https://anypoint.mulesoft.com/exchange/org.mule.examples/fins-payments-interbank-international-execution-prc-api[Implementation Template^] +| FINS Payments InterBank National Execution Process API | https://anypoint.mulesoft.com/exchange/org.mule.examples/fins-bian-paymntexecution-prc-api-spec[API Specification^] | https://anypoint.mulesoft.com/exchange/org.mule.examples/fins-payments-interbank-national-execution-prc-api[Implementation Template^] +| FINS Payments IntraBank International Execution Process API | https://anypoint.mulesoft.com/exchange/org.mule.examples/fins-bian-paymntexecution-prc-api-spec[API Specification^] | https://anypoint.mulesoft.com/exchange/org.mule.examples/fins-payments-intrabank-international-execution-prc-api[Implementation Template^] +| FINS Payments IntraBank National Execution Process API | https://anypoint.mulesoft.com/exchange/org.mule.examples/fins-bian-paymntexecution-prc-api-spec[API Specification^] | https://anypoint.mulesoft.com/exchange/org.mule.examples/fins-payments-intrabank-national-execution-prc-api[Implementation Template^] +| FINS Payments Order Process API | https://anypoint.mulesoft.com/exchange/org.mule.examples/fins-bian-paymntorder-prc-api-spec[API Specification^] | https://anypoint.mulesoft.com/exchange/org.mule.examples/fins-payments-order-prc-api[Implementation Template^] +| FINS Payments Remittances Process API | https://anypoint.mulesoft.com/exchange/org.mule.examples/fins-bian-paymntexecution-prc-api-spec[API Specification^] | https://anypoint.mulesoft.com/exchange/org.mule.examples/fins-payments-remittances-prc-api[Implementation Template^] +| FINS Payments Router Process API | https://anypoint.mulesoft.com/exchange/org.mule.examples/fins-payments-router-prc-api-spec[API Specification^] | https://anypoint.mulesoft.com/exchange/org.mule.examples/fins-payments-router-prc-api[Implementation Template^] +| FINS Payments Simulator Process API | https://anypoint.mulesoft.com/exchange/org.mule.examples/fins-payments-simulator-prc-api-spec[API Specification^] | https://anypoint.mulesoft.com/exchange/org.mule.examples/fins-payments-simulator-prc-api[Implementation Template^] +| FINS Reconciliation Process API | https://anypoint.mulesoft.com/exchange/org.mule.examples/fins-reconciliation-prc-api-spec[API Specification^] | https://anypoint.mulesoft.com/exchange/org.mule.examples/fins-reconciliation-prc-api[Implementation Template^] |=== diff --git a/financial-services/1.9/modules/ROOT/pages/_partials/system-apis-fragment.adoc b/financial-services/1.9/modules/ROOT/pages/_partials/system-apis-fragment.adoc index 3e25513b6..f51eef764 100644 --- a/financial-services/1.9/modules/ROOT/pages/_partials/system-apis-fragment.adoc +++ b/financial-services/1.9/modules/ROOT/pages/_partials/system-apis-fragment.adoc @@ -2,29 +2,29 @@ The following APIs are used to access and manage data in various external system [cols="40,30,30",width=100%] |=== -| FINS Address Validation System API | https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fins-address-validation-sys-api-spec[API Specification^] | https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fins-address-validation-sys-api[Implementation Template^] -| FINS Blockchain System API | https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fins-blockchain-sys-api-spec[API Specification^] | https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fins-blockchain-sys-api[Implementation Template^] -| FINS Core Banking Accounts System API | https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fins-core-banking-accounts-sys-api-spec[API Specification^] | https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fins-core-banking-accounts-sys-api[Implementation Template^] -| FINS Core Banking Customers System API | https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fins-core-banking-customers-sys-api-spec[API Specification^] | https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fins-core-banking-customers-sys-api[Implementation Template^] -| FINS CoreLogic System API | https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fins-corelogic-sys-api-spec[API Specification^] | https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fins-corelogic-sys-api[Implementation Template^] -| FINS Credit Bureau System API | https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fins-credit-bureau-sys-api-spec[API Specification^] | https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fins-credit-bureau-sys-api[Implementation Template^] -| FINS Credit Card System API | https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fins-creditcard-sys-api-spec[API Specification^] | https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fins-creditcard-sys-api[Implementation Template^] -| FINS Databricks Engagements System API | https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fins-engagements-datacloud-sys-api-spec/[API Specification] | https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fins-databricks-engagements-sys-api/[Implementation Template] -| FINS DocuSign System API | https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fins-docusign-sys-api-spec[API Specification^] | https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fins-docusign-sys-api[Implementation Template^] -| FINS Financial Institutions System API | https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fins-financial-institutions-sys-api-spec[API Specification^] | https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fins-financial-institutions-sys-api[Implementation Template^] -| FINS Foreign Exchange System API | https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fins-foreign-exchange-sys-api-spec[API Specification^] | https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fins-foreign-exchange-sys-api[Implementation Template^] -| FINS Fraud Analysis System API | https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fins-fraud-analysis-sys-api-spec[API Specification^] | https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fins-fraud-analysis-sys-api[Implementation Template^] -| FINS Loan Origination System API | https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fins-loan-origination-sys-api-spec[API Specification^] | https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fins-loan-origination-sys-api[Implementation Template^] -| FINS Payments ACH System API | https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fins-payments-ach-sys-api-spec[API Specification^] | https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fins-payments-ach-sys-api[Implementation Template^] -| FINS Payments Fedwire System API | https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fins-payments-fedwire-sys-api-spec[API Specification^] | https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fins-payments-fedwire-sys-api[Implementation Template^] -| FINS Payments SWIFT System API | https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fins-payments-swift-sys-api-spec[API Specification^] | https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fins-payments-swift-sys-api[Implementation Template^] -| Salesforce CDP System API | https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fins-salesforce-cdp-sys-api-spec/[API Specification] | https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fins-salesforce-cdp-sys-api/[Implementation Template] -| FINS Salesforce Customers System API | https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fins-salesforce-customers-sys-api-spec[API Specification^] | https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fins-salesforce-customers-sys-api[Implementation Template^] -| FINS Salesforce Financial System API | https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fins-salesforce-financial-sys-api-spec[API Specification^] | https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fins-salesforce-financial-sys-api[Implementation Template^] -| FINS Salesforce Insurance System API | https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fins-salesforce-insurance-sys-api-spec[API Specification^] | https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fins-salesforce-insurance-sys-api[Implementation Template^] -| FINS Salesforce Marketing System API | https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/rcg-salesforce-marketing-sys-api-spec[API Specification^] | https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fins-salesforce-marketing-sys-api[Implementation Template^] -| SilverLake Accounts System API | https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fins-core-banking-accounts-sys-api-spec/[API Specification] | https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fins-silverlake-accounts-sys-api/[Implementation Template] -| SilverLake Customers System API | https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fins-core-banking-customers-sys-api-spec/[API Specification] | https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fins-silverlake-customers-sys-api/[Implementation Template] -| Snowflake Financial System API | https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fins-financial-datacloud-sys-api-spec/[API Specification] | https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fins-snowflake-financial-sys-api/[Implementation Template] -| Synergy Documents System API | https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fins-core-banking-documents-sys-api-spec/[API Specification] | https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fins-synergy-documents-sys-api/[Implementation Template] +| FINS Address Validation System API | https://anypoint.mulesoft.com/exchange/org.mule.examples/fins-address-validation-sys-api-spec[API Specification^] | https://anypoint.mulesoft.com/exchange/org.mule.examples/fins-address-validation-sys-api[Implementation Template^] +| FINS Blockchain System API | https://anypoint.mulesoft.com/exchange/org.mule.examples/fins-blockchain-sys-api-spec[API Specification^] | https://anypoint.mulesoft.com/exchange/org.mule.examples/fins-blockchain-sys-api[Implementation Template^] +| FINS Core Banking Accounts System API | https://anypoint.mulesoft.com/exchange/org.mule.examples/fins-core-banking-accounts-sys-api-spec[API Specification^] | https://anypoint.mulesoft.com/exchange/org.mule.examples/fins-core-banking-accounts-sys-api[Implementation Template^] +| FINS Core Banking Customers System API | https://anypoint.mulesoft.com/exchange/org.mule.examples/fins-core-banking-customers-sys-api-spec[API Specification^] | https://anypoint.mulesoft.com/exchange/org.mule.examples/fins-core-banking-customers-sys-api[Implementation Template^] +| FINS CoreLogic System API | https://anypoint.mulesoft.com/exchange/org.mule.examples/fins-corelogic-sys-api-spec[API Specification^] | https://anypoint.mulesoft.com/exchange/org.mule.examples/fins-corelogic-sys-api[Implementation Template^] +| FINS Credit Bureau System API | https://anypoint.mulesoft.com/exchange/org.mule.examples/fins-credit-bureau-sys-api-spec[API Specification^] | https://anypoint.mulesoft.com/exchange/org.mule.examples/fins-credit-bureau-sys-api[Implementation Template^] +| FINS Credit Card System API | https://anypoint.mulesoft.com/exchange/org.mule.examples/fins-creditcard-sys-api-spec[API Specification^] | https://anypoint.mulesoft.com/exchange/org.mule.examples/fins-creditcard-sys-api[Implementation Template^] +| FINS Databricks Engagements System API | https://anypoint.mulesoft.com/exchange/org.mule.examples/fins-engagements-datacloud-sys-api-spec/[API Specification] | https://anypoint.mulesoft.com/exchange/org.mule.examples/fins-databricks-engagements-sys-api/[Implementation Template] +| FINS DocuSign System API | https://anypoint.mulesoft.com/exchange/org.mule.examples/fins-docusign-sys-api-spec[API Specification^] | https://anypoint.mulesoft.com/exchange/org.mule.examples/fins-docusign-sys-api[Implementation Template^] +| FINS Financial Institutions System API | https://anypoint.mulesoft.com/exchange/org.mule.examples/fins-financial-institutions-sys-api-spec[API Specification^] | https://anypoint.mulesoft.com/exchange/org.mule.examples/fins-financial-institutions-sys-api[Implementation Template^] +| FINS Foreign Exchange System API | https://anypoint.mulesoft.com/exchange/org.mule.examples/fins-foreign-exchange-sys-api-spec[API Specification^] | https://anypoint.mulesoft.com/exchange/org.mule.examples/fins-foreign-exchange-sys-api[Implementation Template^] +| FINS Fraud Analysis System API | https://anypoint.mulesoft.com/exchange/org.mule.examples/fins-fraud-analysis-sys-api-spec[API Specification^] | https://anypoint.mulesoft.com/exchange/org.mule.examples/fins-fraud-analysis-sys-api[Implementation Template^] +| FINS Loan Origination System API | https://anypoint.mulesoft.com/exchange/org.mule.examples/fins-loan-origination-sys-api-spec[API Specification^] | https://anypoint.mulesoft.com/exchange/org.mule.examples/fins-loan-origination-sys-api[Implementation Template^] +| FINS Payments ACH System API | https://anypoint.mulesoft.com/exchange/org.mule.examples/fins-payments-ach-sys-api-spec[API Specification^] | https://anypoint.mulesoft.com/exchange/org.mule.examples/fins-payments-ach-sys-api[Implementation Template^] +| FINS Payments Fedwire System API | https://anypoint.mulesoft.com/exchange/org.mule.examples/fins-payments-fedwire-sys-api-spec[API Specification^] | https://anypoint.mulesoft.com/exchange/org.mule.examples/fins-payments-fedwire-sys-api[Implementation Template^] +| FINS Payments SWIFT System API | https://anypoint.mulesoft.com/exchange/org.mule.examples/fins-payments-swift-sys-api-spec[API Specification^] | https://anypoint.mulesoft.com/exchange/org.mule.examples/fins-payments-swift-sys-api[Implementation Template^] +| Salesforce CDP System API | https://anypoint.mulesoft.com/exchange/org.mule.examples/fins-salesforce-cdp-sys-api-spec/[API Specification] | https://anypoint.mulesoft.com/exchange/org.mule.examples/fins-salesforce-cdp-sys-api/[Implementation Template] +| FINS Salesforce Customers System API | https://anypoint.mulesoft.com/exchange/org.mule.examples/fins-salesforce-customers-sys-api-spec[API Specification^] | https://anypoint.mulesoft.com/exchange/org.mule.examples/fins-salesforce-customers-sys-api[Implementation Template^] +| FINS Salesforce Financial System API | https://anypoint.mulesoft.com/exchange/org.mule.examples/fins-salesforce-financial-sys-api-spec[API Specification^] | https://anypoint.mulesoft.com/exchange/org.mule.examples/fins-salesforce-financial-sys-api[Implementation Template^] +| FINS Salesforce Insurance System API | https://anypoint.mulesoft.com/exchange/org.mule.examples/fins-salesforce-insurance-sys-api-spec[API Specification^] | https://anypoint.mulesoft.com/exchange/org.mule.examples/fins-salesforce-insurance-sys-api[Implementation Template^] +| FINS Salesforce Marketing System API | https://anypoint.mulesoft.com/exchange/org.mule.examples/rcg-salesforce-marketing-sys-api-spec[API Specification^] | https://anypoint.mulesoft.com/exchange/org.mule.examples/fins-salesforce-marketing-sys-api[Implementation Template^] +| SilverLake Accounts System API | https://anypoint.mulesoft.com/exchange/org.mule.examples/fins-core-banking-accounts-sys-api-spec/[API Specification] | https://anypoint.mulesoft.com/exchange/org.mule.examples/fins-silverlake-accounts-sys-api/[Implementation Template] +| SilverLake Customers System API | https://anypoint.mulesoft.com/exchange/org.mule.examples/fins-core-banking-customers-sys-api-spec/[API Specification] | https://anypoint.mulesoft.com/exchange/org.mule.examples/fins-silverlake-customers-sys-api/[Implementation Template] +| Snowflake Financial System API | https://anypoint.mulesoft.com/exchange/org.mule.examples/fins-financial-datacloud-sys-api-spec/[API Specification] | https://anypoint.mulesoft.com/exchange/org.mule.examples/fins-snowflake-financial-sys-api/[Implementation Template] +| Synergy Documents System API | https://anypoint.mulesoft.com/exchange/org.mule.examples/fins-core-banking-documents-sys-api-spec/[API Specification] | https://anypoint.mulesoft.com/exchange/org.mule.examples/fins-synergy-documents-sys-api/[Implementation Template] |=== diff --git a/financial-services/1.9/modules/ROOT/pages/anypointmq-setup-guide.adoc b/financial-services/1.9/modules/ROOT/pages/anypointmq-setup-guide.adoc index c8b239d96..12e680ff3 100644 --- a/financial-services/1.9/modules/ROOT/pages/anypointmq-setup-guide.adoc +++ b/financial-services/1.9/modules/ROOT/pages/anypointmq-setup-guide.adoc @@ -1,6 +1,6 @@ = Anypoint MQ Setup Guide -The Postman collection `Anypoint-MQ-Configuration` can be used to pre-create all Anypoint MQ destinations required by the accelerator components. This collection can be found in the https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fins-common-resources-src/[FINS Common Resources project^]. +The Postman collection `Anypoint-MQ-Configuration` can be used to pre-create all Anypoint MQ destinations required by the accelerator components. This collection can be found in the https://anypoint.mulesoft.com/exchange/org.mule.examples/fins-common-resources-src/[FINS Common Resources project^]. == Environment Settings diff --git a/financial-services/1.9/modules/ROOT/pages/bian-assets.adoc b/financial-services/1.9/modules/ROOT/pages/bian-assets.adoc index f2cb3951a..d65736179 100644 --- a/financial-services/1.9/modules/ROOT/pages/bian-assets.adoc +++ b/financial-services/1.9/modules/ROOT/pages/bian-assets.adoc @@ -6,63 +6,63 @@ This solution provides a collection of BIAN-compliant assets that allow MuleSoft * BIAN assists banks with improving their architectural maturity and implementing their digital banking initiatives, like Open Banking * BIAN APIs are not required; however, they are available to simplify digital transformation. -The following table lists the BIAN API specifications and implementation template starter assets that are made available as part of the https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/mulesoft-accelerator-for-financial-services[MuleSoft Accelerator for Financial Services^]. +The following table lists the BIAN API specifications and implementation template starter assets that are made available as part of the https://anypoint.mulesoft.com/exchange/org.mule.examples/mulesoft-accelerator-for-financial-services[MuleSoft Accelerator for Financial Services^]. [%header%autowidth.spread^] |=== | Category | Business domain | Service domain | API specification | Implementation template -| Products Domain | Loans and Deposits | Loan | https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fins-bian-loan-prc-api-spec/[FINS BIAN Loan Process API - Specification^] | https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fins-bian-loan-prc-api/[FINS BIAN Loan Process API - Implementation Template^] -| Products Domain | Loans and Deposits | Leasing | https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fins-bian-leasing-prc-api-spec/[FINS BIAN Leasing Process API - Specification^] | https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fins-bian-leasing-prc-api/[FINS BIAN Leasing Process API - Implementation Template^] -| Products Domain | Loans and Deposits | Current Account | https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fins-bian-currentaccount-prc-api-spec/[FINS BIAN Current Account Process API - Specification^] | https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fins-bian-currentaccount-prc-api/[FINS BIAN Current Account Process API - Implementation Template^] -| Products Domain | Loans and Deposits | Corporate Current Account | https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fins-bian-corpcuracct-prc-api-spec/[FINS BIAN Corporate Current Account Process API - Specification^] | https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fins-bian-corpcuracct-prc-api/[FINS BIAN Corporate Current Account Process API - Implementation Template^] -| Products Domain | Loans and Deposits | Consumer Loan | https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fins-bian-consumerloan-prc-api-spec/[FINS BIAN Consumer Loan Process API - Specification^] | https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fins-bian-consumerloan-prc-api/[FINS BIAN Consumer Loan Process API - Implementation Template^] -| Products Domain | Loans and Deposits | Corporate Loan | https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fins-bian-corporateloan-prc-api-spec/[FINS BIAN Corporate Loan Process API - Specification^] | https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fins-bian-corporateloan-prc-api/[FINS BIAN Corporate Loan Process API - Implementation Template^] -| Products Domain | Loans and Deposits | Term Deposit | https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fins-bian-termdeposit-prc-api-spec/[FINS BIAN Term Deposit Process API - Specification^] | https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fins-bian-termdeposit-prc-api/[FINS BIAN Term Deposit Process API - Implementation Template^] -| Products Domain | Loans and Deposits | Corporate Lease | https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fins-bian-corporatelease-prc-api-spec/[FINS BIAN Corporate Lease Process API - Specification^] | https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fins-bian-corporatelease-prc-api/[FINS BIAN Corporate Lease Process API - Implementation Template^] -| Products Domain | Loans and Deposits | Merchandising Loan | https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fins-bian-merchloan-prc-api-spec/[FINS BIAN Merchandising Loan Process API - Specification^] | https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fins-bian-merchloan-prc-api/[FINS BIAN Merchandising Loan Process API - Implementation Template^] -| Products Domain | Loans and Deposits | Mortgage Loan | https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fins-bian-mortgageloan-prc-api-spec/[FINS BIAN Mortgage Loan Process API - Specification^] | https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fins-bian-mortgageloan-prc-api/[FINS BIAN Mortgage Loan Process API - Implementation Template^] -| Products Domain | Loans and Deposits | Fiduciary Agreement | https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fins-bian-fidagreement-prc-api-spec/[FINS BIAN Fiduciary Agreement Process API - Specification^] | https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fins-bian-fidagreement-prc-api/[FINS BIAN Fiduciary Agreement Process API - Implementation Template^] -| Products Domain | Loans and Deposits | Savings Account | https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fins-bian-savingsaccount-prc-api-spec/[FINS BIAN Savings Account Process API - Specification^] | https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fins-bian-savingsaccount-prc-api/[FINS BIAN Savings Account Process API - Implementation Template^] -| Products Domain | Loans and Deposits | Virtual Account | https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fins-bian-virtualaccount-prc-api-spec/[FINS BIAN Virtual Account Process API - Specification^] | https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fins-bian-virtualaccount-prc-api/[FINS BIAN Virtual Account Process API - Implementation Template^] -| Products Domain | Loans and Deposits | Standing Order | https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fins-bian-standingorder-prc-api-spec/[FINS BIAN Standing Order Process API - Specification^] | https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fins-bian-standingorder-prc-api/[FINS BIAN Standing Order Process API - Implementation Template^] -| Products Domain | Cards | Credit Card | https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fins-bian-creditcard-prc-api-spec/[FINS BIAN Credit Card Process API - Specification^] | https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fins-bian-creditcard-prc-api/[FINS BIAN Credit Card Process API - Implementation Template^] -| Products Domain | Cards | Card Authorization | https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fins-bian-cardauth-prc-api-spec/[FINS BIAN Card Authorization Process API - Specification^] | https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fins-bian-cardauth-prc-api/[FINS BIAN Card Authorization Process API - Implementation Template^] -| Products Domain | Cards | Merchant Relations | https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fins-bian-merchrelations-prc-api-spec/[FINS BIAN Merchant Relations Process API - Specification^] | https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fins-bian-merchrelations-prc-api/[FINS BIAN Merchant Relations Process API - Implementation Template^] -| Products Domain | Cards | Card Network Partipant Facility | https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fins-bian-cardnpf-prc-api-spec/[FINS BIAN Card Network Partipant Facility Process API - Specification^] | https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fins-bian-cardnpf-prc-api/[FINS BIAN Card Network Partipant Facility Process API - Implementation Template^] -| Products Domain | Cards | Merchant Acquiring Facility | https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fins-bian-cardmaf-prc-api-spec/[FINS BIAN Merchant Acquiring Facility Process API - Specification^] | https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fins-bian-cardmaf-prc-api/[FINS BIAN Merchant Acquiring Facility Process API - Implementation Template^] -| Products Domain | Cards | Card Capture | https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fins-bian-cardcapture-prc-api-spec/[FINS BIAN Card Capture Process API - Specification^] | https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fins-bian-cardcapture-prc-api/[FINS BIAN Card Capture Process API - Implementation Template^] -| Customer Domain | Sales | Prospect Camapign Execution | https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fins-bian-salespce-prc-api-spec/[FINS BIAN Prospect Camapign Execution Process API - Specification^] | https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fins-bian-salespce-prc-api/[FINS BIAN Prospect Camapign Execution Process API - Implementation Template^] -| Customer Domain | Sales | Lead and Opportunity Management | https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fins-bian-saleslom-prc-api-spec/[FINS BIAN Lead and Opportunity Management Process API - Specification^] | https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fins-bian-saleslom-prc-api/[FINS BIAN Lead and Opportunity Management Process API - Implementation Template^] -| Customer Domain | Sales | Party Lifecycle Management | https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fins-bian-salesplm-prc-api-spec/[FINS BIAN Party Lifecycle Management Process API - Specification^] | https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fins-bian-salesplm-prc-api/[FINS BIAN Party Lifecycle Management Process API - Implementation Template^] -| Customer Domain | Sales | Customer Campaign Execution | https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fins-bian-custcampaignexec-prc-api-spec/[FINS BIAN Customer Campaign Execution Process API - Specification^] | https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fins-bian-custcampaignexec-prc-api/[FINS BIAN Customer Campaign Execution Process API - Implementation Template^] -| Customer Domain | Sales | Customer Offer | https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fins-bian-customeroffer-prc-api-spec/[FINS BIAN Customer Offer Process API - Specification^] | https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fins-bian-customeroffer-prc-api/[FINS BIAN Customer Offer Process API - Implementation Template^] -| Customer Domain | Sales | Underwriting | https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fins-bian-underwriting-prc-api-spec/[FINS BIAN Underwriting Process API - Specification^] | https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fins-bian-underwriting-prc-api/[FINS BIAN Underwriting Process API - Implementation Template^] -| Customer Domain | Sales | Commission Agreement | https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fins-bian-salescommagr-prc-api-spec/[FINS BIAN Commission Agreement Process API - Specification^] | https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fins-bian-salescommagr-prc-api/[FINS BIAN Commission Agreement Process API - Implementation Template^] -| Customer Domain | Sales | Commissions | https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fins-bian-commissions-prc-api-spec/[FINS BIAN Commissions Process API - Specification^] | https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fins-bian-commissions-prc-api/[FINS BIAN Commissions Process API - Implementation Template^] -| Customer Domain | Sales | Product Matching | https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fins-bian-productmatching-prc-api-spec/[FINS BIAN Product Matching Process API - Specification^] | https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fins-bian-productmatching-prc-api/[FINS BIAN Product Matching Process API - Implementation Template^] -| Customer Domain | Sales | Product Expert Sales Support | https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fins-bian-productexpertss-prc-api-spec/[FINS BIAN Product Expert Sales Support Process API - Specification^] | https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fins-bian-productexpertss-prc-api/[FINS BIAN Product Expert Sales Support Process API - Implementation Template^] -| Customer Domain | Sales | Product Sales Support | https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fins-bian-productss-prc-api-spec/[FINS BIAN Product Sales Support Process API - Specification^] | https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fins-bian-productss-prc-api/[FINS BIAN Product Sales Support Process API - Implementation Template^] -| Customer Domain | Sales | Sales Product | https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fins-bian-salesproduct-prc-api-spec/[FINS BIAN Sales Product Process API - Specification^] | https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fins-bian-salesproduct-prc-api/[FINS BIAN Sales Product Process API - Implementation Template^] -| Channels | Servicing | Servicing Issue | https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fins-bian-servicingissue-prc-api-spec/[FINS BIAN Servicing Issue Process API - Specification^] | https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fins-bian-servicingissue-prc-api/[FINS BIAN Servicing Issue Process API - Implementation Template^] -| Channels | Servicing | Customer Case Management | https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fins-bian-customercasemgmt-prc-api-spec/[FINS BIAN Customer Case Management Process API - Specification^] | https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fins-bian-customercasemgmt-prc-api/[FINS BIAN Customer Case Management Process API - Implementation Template^] -| Channels | Servicing | Case Root Cause Analysis | https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fins-bian-casertcauseanlys-prc-api-spec/[FINS BIAN Case Root Cause Analysis Process API - Specification^] | https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fins-bian-casertcauseanlys-prc-api/[FINS BIAN Case Root Cause Analysis Process API - Implementation Template^] -| Channels | Servicing | Customer Case | https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fins-bian-customercase-prc-api-spec/[FINS BIAN Customer Case Process API - Specification^] | https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fins-bian-customercase-prc-api/[FINS BIAN Customer Case Process API - Implementation Template^] -| Channels | Servicing | Servicing Order | https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fins-bian-servicingorder-prc-api-spec/[FINS BIAN Servicing Order Process API - Specification^] | https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fins-bian-servicingorder-prc-api/[FINS BIAN Servicing Order Process API - Implementation Template^] -| Channels | Servicing | Servicing Mandate | https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fins-bian-servicingmandate-prc-api-spec/[FINS BIAN Servicing Mandate Process API - Specification^] | https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fins-bian-servicingmandate-prc-api/[FINS BIAN Servicing Mandate Process API - Implementation Template^] -| Channels | Servicing | Payment Execution | https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fins-bian-paymntexecution-prc-api-spec/[FINS BIAN Payment Execution Process API - Specification^] | https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fins-bian-paymntexecution-prc-api/[FINS BIAN Payment Execution Process API - Implementation Template^] -| Channels | Servicing | Payment Initiation | https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fins-bian-paymntinitiation-prc-api-spec/[FINS BIAN Payment Initiation Process API - Specification^] | https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fins-bian-paymntinitiation-prc-api/[FINS BIAN Payment Initiation Process API - Implementation Template^] -| Channels | Servicing | Payment Order | https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fins-bian-paymntorder-prc-api-spec/[FINS BIAN Payment Order Process API - Specification^] | https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fins-bian-paymntorder-prc-api/[FINS BIAN Payment Order Process API - Implementation Template^] -| Sales and Service | Customer Management | Party Reference Data Directory | https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fins-bian-partyrefdatadir-prc-api-spec/[FINS BIAN Party Reference Data Directory Process API - Specification^] | https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fins-bian-partyrefdatadir-prc-api/[FINS BIAN Party Reference Data Directory Process API - Implementation Template^] -| Sales and Service | Cross Channel | Party Authentication | https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fins-bian-partyauth-prc-api-spec/[FINS BIAN Party Authentication Process API - Specification^] | https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fins-bian-partyauth-prc-api/[FINS BIAN Party Authentication Process API - Implementation Template^] -| Sales and Service | Cross Channel | Transaction Authorization | https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fins-bian-transactionauth-prc-api-spec/[FINS BIAN Transaction Authorization Process API - Specification^] | https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fins-bian-transactionauth-prc-api/[FINS BIAN Transaction Authorization Process API - Implementation Template^] -| Sales and Service | Cross Channel | Point of Service | https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fins-bian-pointofservice-prc-api-spec/[FINS BIAN Point of Service Process API - Specification^] | https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fins-bian-pointofservice-prc-api/[FINS BIAN Point of Service Process API - Implementation Template^] -| Sales and Service | Cross Channel | Service Event History | https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fins-bian-svceventhistory-prc-api-spec/[FINS BIAN Service Event History Process API - Specification^] | https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fins-bian-svceventhistory-prc-api/[FINS BIAN Service Event History Process API - Implementation Template^] -| Sales and Service | Cross Channel | Contact Routing | https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fins-bian-contactrouting-prc-api-spec/[FINS BIAN Contact Routing Process API - Specification^] | https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fins-bian-contactrouting-prc-api/[FINS BIAN Contact Routing Process API - Implementation Template^] -| Sales and Service | Cross Channel | Session Dialogue | https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fins-bian-sessiondialogue-prc-api-spec/[FINS BIAN Session Dialogue Process API - Specification^] | https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fins-bian-sessiondialogue-prc-api/[FINS BIAN Session Dialogue Process API - Implementation Template^] -| Sales and Service | Cross Channel | Interactive Help | https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fins-bian-interactivehelp-prc-api-spec/[FINS BIAN Interactive Help Process API - Specification^] | https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fins-bian-interactivehelp-prc-api/[FINS BIAN Interactive Help Process API - Implementation Template^] -| Sales and Service | Cross Channel | Contact Handler | https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fins-bian-contacthandler-prc-api-spec/[FINS BIAN Contact Handler Process API - Specification^] | https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fins-bian-contacthandler-prc-api/[FINS BIAN Contact Handler Process API - Implementation Template^] -| Sales and Service | Cross Channel | Customer Workbench | https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fins-bian-custworkbench-prc-api-spec/[FINS BIAN Customer Workbench Process API - Specification^] | https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fins-bian-custworkbench-prc-api/[FINS BIAN Customer Workbench Process API - Implementation Template^] -| Sales and Service | Cross Channel | Servicing Activity Analysis | https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fins-bian-svcactivityanlys-prc-api-spec/[FINS BIAN Servicing Activity Analysis Process API - Specification^] | https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fins-bian-svcactivityanlys-prc-api/[FINS BIAN Servicing Activity Analysis Process API - Implementation Template^] +| Products Domain | Loans and Deposits | Loan | https://anypoint.mulesoft.com/exchange/org.mule.examples/fins-bian-loan-prc-api-spec/[FINS BIAN Loan Process API - Specification^] | https://anypoint.mulesoft.com/exchange/org.mule.examples/fins-bian-loan-prc-api/[FINS BIAN Loan Process API - Implementation Template^] +| Products Domain | Loans and Deposits | Leasing | https://anypoint.mulesoft.com/exchange/org.mule.examples/fins-bian-leasing-prc-api-spec/[FINS BIAN Leasing Process API - Specification^] | https://anypoint.mulesoft.com/exchange/org.mule.examples/fins-bian-leasing-prc-api/[FINS BIAN Leasing Process API - Implementation Template^] +| Products Domain | Loans and Deposits | Current Account | https://anypoint.mulesoft.com/exchange/org.mule.examples/fins-bian-currentaccount-prc-api-spec/[FINS BIAN Current Account Process API - Specification^] | https://anypoint.mulesoft.com/exchange/org.mule.examples/fins-bian-currentaccount-prc-api/[FINS BIAN Current Account Process API - Implementation Template^] +| Products Domain | Loans and Deposits | Corporate Current Account | https://anypoint.mulesoft.com/exchange/org.mule.examples/fins-bian-corpcuracct-prc-api-spec/[FINS BIAN Corporate Current Account Process API - Specification^] | https://anypoint.mulesoft.com/exchange/org.mule.examples/fins-bian-corpcuracct-prc-api/[FINS BIAN Corporate Current Account Process API - Implementation Template^] +| Products Domain | Loans and Deposits | Consumer Loan | https://anypoint.mulesoft.com/exchange/org.mule.examples/fins-bian-consumerloan-prc-api-spec/[FINS BIAN Consumer Loan Process API - Specification^] | https://anypoint.mulesoft.com/exchange/org.mule.examples/fins-bian-consumerloan-prc-api/[FINS BIAN Consumer Loan Process API - Implementation Template^] +| Products Domain | Loans and Deposits | Corporate Loan | https://anypoint.mulesoft.com/exchange/org.mule.examples/fins-bian-corporateloan-prc-api-spec/[FINS BIAN Corporate Loan Process API - Specification^] | https://anypoint.mulesoft.com/exchange/org.mule.examples/fins-bian-corporateloan-prc-api/[FINS BIAN Corporate Loan Process API - Implementation Template^] +| Products Domain | Loans and Deposits | Term Deposit | https://anypoint.mulesoft.com/exchange/org.mule.examples/fins-bian-termdeposit-prc-api-spec/[FINS BIAN Term Deposit Process API - Specification^] | https://anypoint.mulesoft.com/exchange/org.mule.examples/fins-bian-termdeposit-prc-api/[FINS BIAN Term Deposit Process API - Implementation Template^] +| Products Domain | Loans and Deposits | Corporate Lease | https://anypoint.mulesoft.com/exchange/org.mule.examples/fins-bian-corporatelease-prc-api-spec/[FINS BIAN Corporate Lease Process API - Specification^] | https://anypoint.mulesoft.com/exchange/org.mule.examples/fins-bian-corporatelease-prc-api/[FINS BIAN Corporate Lease Process API - Implementation Template^] +| Products Domain | Loans and Deposits | Merchandising Loan | https://anypoint.mulesoft.com/exchange/org.mule.examples/fins-bian-merchloan-prc-api-spec/[FINS BIAN Merchandising Loan Process API - Specification^] | https://anypoint.mulesoft.com/exchange/org.mule.examples/fins-bian-merchloan-prc-api/[FINS BIAN Merchandising Loan Process API - Implementation Template^] +| Products Domain | Loans and Deposits | Mortgage Loan | https://anypoint.mulesoft.com/exchange/org.mule.examples/fins-bian-mortgageloan-prc-api-spec/[FINS BIAN Mortgage Loan Process API - Specification^] | https://anypoint.mulesoft.com/exchange/org.mule.examples/fins-bian-mortgageloan-prc-api/[FINS BIAN Mortgage Loan Process API - Implementation Template^] +| Products Domain | Loans and Deposits | Fiduciary Agreement | https://anypoint.mulesoft.com/exchange/org.mule.examples/fins-bian-fidagreement-prc-api-spec/[FINS BIAN Fiduciary Agreement Process API - Specification^] | https://anypoint.mulesoft.com/exchange/org.mule.examples/fins-bian-fidagreement-prc-api/[FINS BIAN Fiduciary Agreement Process API - Implementation Template^] +| Products Domain | Loans and Deposits | Savings Account | https://anypoint.mulesoft.com/exchange/org.mule.examples/fins-bian-savingsaccount-prc-api-spec/[FINS BIAN Savings Account Process API - Specification^] | https://anypoint.mulesoft.com/exchange/org.mule.examples/fins-bian-savingsaccount-prc-api/[FINS BIAN Savings Account Process API - Implementation Template^] +| Products Domain | Loans and Deposits | Virtual Account | https://anypoint.mulesoft.com/exchange/org.mule.examples/fins-bian-virtualaccount-prc-api-spec/[FINS BIAN Virtual Account Process API - Specification^] | https://anypoint.mulesoft.com/exchange/org.mule.examples/fins-bian-virtualaccount-prc-api/[FINS BIAN Virtual Account Process API - Implementation Template^] +| Products Domain | Loans and Deposits | Standing Order | https://anypoint.mulesoft.com/exchange/org.mule.examples/fins-bian-standingorder-prc-api-spec/[FINS BIAN Standing Order Process API - Specification^] | https://anypoint.mulesoft.com/exchange/org.mule.examples/fins-bian-standingorder-prc-api/[FINS BIAN Standing Order Process API - Implementation Template^] +| Products Domain | Cards | Credit Card | https://anypoint.mulesoft.com/exchange/org.mule.examples/fins-bian-creditcard-prc-api-spec/[FINS BIAN Credit Card Process API - Specification^] | https://anypoint.mulesoft.com/exchange/org.mule.examples/fins-bian-creditcard-prc-api/[FINS BIAN Credit Card Process API - Implementation Template^] +| Products Domain | Cards | Card Authorization | https://anypoint.mulesoft.com/exchange/org.mule.examples/fins-bian-cardauth-prc-api-spec/[FINS BIAN Card Authorization Process API - Specification^] | https://anypoint.mulesoft.com/exchange/org.mule.examples/fins-bian-cardauth-prc-api/[FINS BIAN Card Authorization Process API - Implementation Template^] +| Products Domain | Cards | Merchant Relations | https://anypoint.mulesoft.com/exchange/org.mule.examples/fins-bian-merchrelations-prc-api-spec/[FINS BIAN Merchant Relations Process API - Specification^] | https://anypoint.mulesoft.com/exchange/org.mule.examples/fins-bian-merchrelations-prc-api/[FINS BIAN Merchant Relations Process API - Implementation Template^] +| Products Domain | Cards | Card Network Partipant Facility | https://anypoint.mulesoft.com/exchange/org.mule.examples/fins-bian-cardnpf-prc-api-spec/[FINS BIAN Card Network Partipant Facility Process API - Specification^] | https://anypoint.mulesoft.com/exchange/org.mule.examples/fins-bian-cardnpf-prc-api/[FINS BIAN Card Network Partipant Facility Process API - Implementation Template^] +| Products Domain | Cards | Merchant Acquiring Facility | https://anypoint.mulesoft.com/exchange/org.mule.examples/fins-bian-cardmaf-prc-api-spec/[FINS BIAN Merchant Acquiring Facility Process API - Specification^] | https://anypoint.mulesoft.com/exchange/org.mule.examples/fins-bian-cardmaf-prc-api/[FINS BIAN Merchant Acquiring Facility Process API - Implementation Template^] +| Products Domain | Cards | Card Capture | https://anypoint.mulesoft.com/exchange/org.mule.examples/fins-bian-cardcapture-prc-api-spec/[FINS BIAN Card Capture Process API - Specification^] | https://anypoint.mulesoft.com/exchange/org.mule.examples/fins-bian-cardcapture-prc-api/[FINS BIAN Card Capture Process API - Implementation Template^] +| Customer Domain | Sales | Prospect Camapign Execution | https://anypoint.mulesoft.com/exchange/org.mule.examples/fins-bian-salespce-prc-api-spec/[FINS BIAN Prospect Camapign Execution Process API - Specification^] | https://anypoint.mulesoft.com/exchange/org.mule.examples/fins-bian-salespce-prc-api/[FINS BIAN Prospect Camapign Execution Process API - Implementation Template^] +| Customer Domain | Sales | Lead and Opportunity Management | https://anypoint.mulesoft.com/exchange/org.mule.examples/fins-bian-saleslom-prc-api-spec/[FINS BIAN Lead and Opportunity Management Process API - Specification^] | https://anypoint.mulesoft.com/exchange/org.mule.examples/fins-bian-saleslom-prc-api/[FINS BIAN Lead and Opportunity Management Process API - Implementation Template^] +| Customer Domain | Sales | Party Lifecycle Management | https://anypoint.mulesoft.com/exchange/org.mule.examples/fins-bian-salesplm-prc-api-spec/[FINS BIAN Party Lifecycle Management Process API - Specification^] | https://anypoint.mulesoft.com/exchange/org.mule.examples/fins-bian-salesplm-prc-api/[FINS BIAN Party Lifecycle Management Process API - Implementation Template^] +| Customer Domain | Sales | Customer Campaign Execution | https://anypoint.mulesoft.com/exchange/org.mule.examples/fins-bian-custcampaignexec-prc-api-spec/[FINS BIAN Customer Campaign Execution Process API - Specification^] | https://anypoint.mulesoft.com/exchange/org.mule.examples/fins-bian-custcampaignexec-prc-api/[FINS BIAN Customer Campaign Execution Process API - Implementation Template^] +| Customer Domain | Sales | Customer Offer | https://anypoint.mulesoft.com/exchange/org.mule.examples/fins-bian-customeroffer-prc-api-spec/[FINS BIAN Customer Offer Process API - Specification^] | https://anypoint.mulesoft.com/exchange/org.mule.examples/fins-bian-customeroffer-prc-api/[FINS BIAN Customer Offer Process API - Implementation Template^] +| Customer Domain | Sales | Underwriting | https://anypoint.mulesoft.com/exchange/org.mule.examples/fins-bian-underwriting-prc-api-spec/[FINS BIAN Underwriting Process API - Specification^] | https://anypoint.mulesoft.com/exchange/org.mule.examples/fins-bian-underwriting-prc-api/[FINS BIAN Underwriting Process API - Implementation Template^] +| Customer Domain | Sales | Commission Agreement | https://anypoint.mulesoft.com/exchange/org.mule.examples/fins-bian-salescommagr-prc-api-spec/[FINS BIAN Commission Agreement Process API - Specification^] | https://anypoint.mulesoft.com/exchange/org.mule.examples/fins-bian-salescommagr-prc-api/[FINS BIAN Commission Agreement Process API - Implementation Template^] +| Customer Domain | Sales | Commissions | https://anypoint.mulesoft.com/exchange/org.mule.examples/fins-bian-commissions-prc-api-spec/[FINS BIAN Commissions Process API - Specification^] | https://anypoint.mulesoft.com/exchange/org.mule.examples/fins-bian-commissions-prc-api/[FINS BIAN Commissions Process API - Implementation Template^] +| Customer Domain | Sales | Product Matching | https://anypoint.mulesoft.com/exchange/org.mule.examples/fins-bian-productmatching-prc-api-spec/[FINS BIAN Product Matching Process API - Specification^] | https://anypoint.mulesoft.com/exchange/org.mule.examples/fins-bian-productmatching-prc-api/[FINS BIAN Product Matching Process API - Implementation Template^] +| Customer Domain | Sales | Product Expert Sales Support | https://anypoint.mulesoft.com/exchange/org.mule.examples/fins-bian-productexpertss-prc-api-spec/[FINS BIAN Product Expert Sales Support Process API - Specification^] | https://anypoint.mulesoft.com/exchange/org.mule.examples/fins-bian-productexpertss-prc-api/[FINS BIAN Product Expert Sales Support Process API - Implementation Template^] +| Customer Domain | Sales | Product Sales Support | https://anypoint.mulesoft.com/exchange/org.mule.examples/fins-bian-productss-prc-api-spec/[FINS BIAN Product Sales Support Process API - Specification^] | https://anypoint.mulesoft.com/exchange/org.mule.examples/fins-bian-productss-prc-api/[FINS BIAN Product Sales Support Process API - Implementation Template^] +| Customer Domain | Sales | Sales Product | https://anypoint.mulesoft.com/exchange/org.mule.examples/fins-bian-salesproduct-prc-api-spec/[FINS BIAN Sales Product Process API - Specification^] | https://anypoint.mulesoft.com/exchange/org.mule.examples/fins-bian-salesproduct-prc-api/[FINS BIAN Sales Product Process API - Implementation Template^] +| Channels | Servicing | Servicing Issue | https://anypoint.mulesoft.com/exchange/org.mule.examples/fins-bian-servicingissue-prc-api-spec/[FINS BIAN Servicing Issue Process API - Specification^] | https://anypoint.mulesoft.com/exchange/org.mule.examples/fins-bian-servicingissue-prc-api/[FINS BIAN Servicing Issue Process API - Implementation Template^] +| Channels | Servicing | Customer Case Management | https://anypoint.mulesoft.com/exchange/org.mule.examples/fins-bian-customercasemgmt-prc-api-spec/[FINS BIAN Customer Case Management Process API - Specification^] | https://anypoint.mulesoft.com/exchange/org.mule.examples/fins-bian-customercasemgmt-prc-api/[FINS BIAN Customer Case Management Process API - Implementation Template^] +| Channels | Servicing | Case Root Cause Analysis | https://anypoint.mulesoft.com/exchange/org.mule.examples/fins-bian-casertcauseanlys-prc-api-spec/[FINS BIAN Case Root Cause Analysis Process API - Specification^] | https://anypoint.mulesoft.com/exchange/org.mule.examples/fins-bian-casertcauseanlys-prc-api/[FINS BIAN Case Root Cause Analysis Process API - Implementation Template^] +| Channels | Servicing | Customer Case | https://anypoint.mulesoft.com/exchange/org.mule.examples/fins-bian-customercase-prc-api-spec/[FINS BIAN Customer Case Process API - Specification^] | https://anypoint.mulesoft.com/exchange/org.mule.examples/fins-bian-customercase-prc-api/[FINS BIAN Customer Case Process API - Implementation Template^] +| Channels | Servicing | Servicing Order | https://anypoint.mulesoft.com/exchange/org.mule.examples/fins-bian-servicingorder-prc-api-spec/[FINS BIAN Servicing Order Process API - Specification^] | https://anypoint.mulesoft.com/exchange/org.mule.examples/fins-bian-servicingorder-prc-api/[FINS BIAN Servicing Order Process API - Implementation Template^] +| Channels | Servicing | Servicing Mandate | https://anypoint.mulesoft.com/exchange/org.mule.examples/fins-bian-servicingmandate-prc-api-spec/[FINS BIAN Servicing Mandate Process API - Specification^] | https://anypoint.mulesoft.com/exchange/org.mule.examples/fins-bian-servicingmandate-prc-api/[FINS BIAN Servicing Mandate Process API - Implementation Template^] +| Channels | Servicing | Payment Execution | https://anypoint.mulesoft.com/exchange/org.mule.examples/fins-bian-paymntexecution-prc-api-spec/[FINS BIAN Payment Execution Process API - Specification^] | https://anypoint.mulesoft.com/exchange/org.mule.examples/fins-bian-paymntexecution-prc-api/[FINS BIAN Payment Execution Process API - Implementation Template^] +| Channels | Servicing | Payment Initiation | https://anypoint.mulesoft.com/exchange/org.mule.examples/fins-bian-paymntinitiation-prc-api-spec/[FINS BIAN Payment Initiation Process API - Specification^] | https://anypoint.mulesoft.com/exchange/org.mule.examples/fins-bian-paymntinitiation-prc-api/[FINS BIAN Payment Initiation Process API - Implementation Template^] +| Channels | Servicing | Payment Order | https://anypoint.mulesoft.com/exchange/org.mule.examples/fins-bian-paymntorder-prc-api-spec/[FINS BIAN Payment Order Process API - Specification^] | https://anypoint.mulesoft.com/exchange/org.mule.examples/fins-bian-paymntorder-prc-api/[FINS BIAN Payment Order Process API - Implementation Template^] +| Sales and Service | Customer Management | Party Reference Data Directory | https://anypoint.mulesoft.com/exchange/org.mule.examples/fins-bian-partyrefdatadir-prc-api-spec/[FINS BIAN Party Reference Data Directory Process API - Specification^] | https://anypoint.mulesoft.com/exchange/org.mule.examples/fins-bian-partyrefdatadir-prc-api/[FINS BIAN Party Reference Data Directory Process API - Implementation Template^] +| Sales and Service | Cross Channel | Party Authentication | https://anypoint.mulesoft.com/exchange/org.mule.examples/fins-bian-partyauth-prc-api-spec/[FINS BIAN Party Authentication Process API - Specification^] | https://anypoint.mulesoft.com/exchange/org.mule.examples/fins-bian-partyauth-prc-api/[FINS BIAN Party Authentication Process API - Implementation Template^] +| Sales and Service | Cross Channel | Transaction Authorization | https://anypoint.mulesoft.com/exchange/org.mule.examples/fins-bian-transactionauth-prc-api-spec/[FINS BIAN Transaction Authorization Process API - Specification^] | https://anypoint.mulesoft.com/exchange/org.mule.examples/fins-bian-transactionauth-prc-api/[FINS BIAN Transaction Authorization Process API - Implementation Template^] +| Sales and Service | Cross Channel | Point of Service | https://anypoint.mulesoft.com/exchange/org.mule.examples/fins-bian-pointofservice-prc-api-spec/[FINS BIAN Point of Service Process API - Specification^] | https://anypoint.mulesoft.com/exchange/org.mule.examples/fins-bian-pointofservice-prc-api/[FINS BIAN Point of Service Process API - Implementation Template^] +| Sales and Service | Cross Channel | Service Event History | https://anypoint.mulesoft.com/exchange/org.mule.examples/fins-bian-svceventhistory-prc-api-spec/[FINS BIAN Service Event History Process API - Specification^] | https://anypoint.mulesoft.com/exchange/org.mule.examples/fins-bian-svceventhistory-prc-api/[FINS BIAN Service Event History Process API - Implementation Template^] +| Sales and Service | Cross Channel | Contact Routing | https://anypoint.mulesoft.com/exchange/org.mule.examples/fins-bian-contactrouting-prc-api-spec/[FINS BIAN Contact Routing Process API - Specification^] | https://anypoint.mulesoft.com/exchange/org.mule.examples/fins-bian-contactrouting-prc-api/[FINS BIAN Contact Routing Process API - Implementation Template^] +| Sales and Service | Cross Channel | Session Dialogue | https://anypoint.mulesoft.com/exchange/org.mule.examples/fins-bian-sessiondialogue-prc-api-spec/[FINS BIAN Session Dialogue Process API - Specification^] | https://anypoint.mulesoft.com/exchange/org.mule.examples/fins-bian-sessiondialogue-prc-api/[FINS BIAN Session Dialogue Process API - Implementation Template^] +| Sales and Service | Cross Channel | Interactive Help | https://anypoint.mulesoft.com/exchange/org.mule.examples/fins-bian-interactivehelp-prc-api-spec/[FINS BIAN Interactive Help Process API - Specification^] | https://anypoint.mulesoft.com/exchange/org.mule.examples/fins-bian-interactivehelp-prc-api/[FINS BIAN Interactive Help Process API - Implementation Template^] +| Sales and Service | Cross Channel | Contact Handler | https://anypoint.mulesoft.com/exchange/org.mule.examples/fins-bian-contacthandler-prc-api-spec/[FINS BIAN Contact Handler Process API - Specification^] | https://anypoint.mulesoft.com/exchange/org.mule.examples/fins-bian-contacthandler-prc-api/[FINS BIAN Contact Handler Process API - Implementation Template^] +| Sales and Service | Cross Channel | Customer Workbench | https://anypoint.mulesoft.com/exchange/org.mule.examples/fins-bian-custworkbench-prc-api-spec/[FINS BIAN Customer Workbench Process API - Specification^] | https://anypoint.mulesoft.com/exchange/org.mule.examples/fins-bian-custworkbench-prc-api/[FINS BIAN Customer Workbench Process API - Implementation Template^] +| Sales and Service | Cross Channel | Servicing Activity Analysis | https://anypoint.mulesoft.com/exchange/org.mule.examples/fins-bian-svcactivityanlys-prc-api-spec/[FINS BIAN Servicing Activity Analysis Process API - Specification^] | https://anypoint.mulesoft.com/exchange/org.mule.examples/fins-bian-svcactivityanlys-prc-api/[FINS BIAN Servicing Activity Analysis Process API - Implementation Template^] |=== == See Also diff --git a/financial-services/1.9/modules/ROOT/pages/fins-assets.adoc b/financial-services/1.9/modules/ROOT/pages/fins-assets.adoc index 0f55e4456..ae9d90416 100644 --- a/financial-services/1.9/modules/ROOT/pages/fins-assets.adoc +++ b/financial-services/1.9/modules/ROOT/pages/fins-assets.adoc @@ -28,10 +28,10 @@ The following shared APIs are are leveraged by this accelerator. [cols="40,30,30"] |=== -| Accelerator Email System API | https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/accelerator-email-sys-api[API Specification^] | https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/accel-email-sys-api[Implementation Template^] -| Accelerator Slack System API | https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/accelerator-slack-sys-api[API Specification^] | https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/accel-slack-sys-api[Implementation Template^] -| Accelerator SMS System API | https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/accelerator-sms-sys-api[API Specification^] | https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/accel-sms-sys-api[Implementation Template^] -| Accelerator Notifications Process API | https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/accelerator-notifications-prc-api[API Specification^] | https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/accel-notifications-prc-api/[Implementation Template^] +| Accelerator Email System API | https://anypoint.mulesoft.com/exchange/org.mule.examples/accelerator-email-sys-api[API Specification^] | https://anypoint.mulesoft.com/exchange/org.mule.examples/accel-email-sys-api[Implementation Template^] +| Accelerator Slack System API | https://anypoint.mulesoft.com/exchange/org.mule.examples/accelerator-slack-sys-api[API Specification^] | https://anypoint.mulesoft.com/exchange/org.mule.examples/accel-slack-sys-api[Implementation Template^] +| Accelerator SMS System API | https://anypoint.mulesoft.com/exchange/org.mule.examples/accelerator-sms-sys-api[API Specification^] | https://anypoint.mulesoft.com/exchange/org.mule.examples/accel-sms-sys-api[Implementation Template^] +| Accelerator Notifications Process API | https://anypoint.mulesoft.com/exchange/org.mule.examples/accelerator-notifications-prc-api[API Specification^] | https://anypoint.mulesoft.com/exchange/org.mule.examples/accel-notifications-prc-api/[Implementation Template^] |=== == Accelerator Shared Components @@ -40,13 +40,13 @@ The following shared components are leveraged by this accelerator. [cols="70,30"] |=== -| Accelerator CIM Global Library | https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/accelerator-cim-global-library[Source^] -| Accelerator CIM Market Library | https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/accelerator-cim-market-library[Source^] -| Accelerator CIM FINS Extension Library | https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/accelerator-cim-fins-ext-library[Source^] -| Accelerator Common Core | https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/accelerator-common-core-src[Source^] -| Accelerator ID Graph Lightning Web Component | https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/accelerator-idgraph-lwc-src[Source^] -| Accelerator Knit Maven Plugin | https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/accelerator-knit-plugin-src[Source^] -| Accelerator POM Parent | https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/accelerator-pom-parent-src[Source^] +| Accelerator CIM Global Library | https://anypoint.mulesoft.com/exchange/org.mule.examples/accelerator-cim-global-library[Source^] +| Accelerator CIM Market Library | https://anypoint.mulesoft.com/exchange/org.mule.examples/accelerator-cim-market-library[Source^] +| Accelerator CIM FINS Extension Library | https://anypoint.mulesoft.com/exchange/org.mule.examples/accelerator-cim-fins-ext-library[Source^] +| Accelerator Common Core | https://anypoint.mulesoft.com/exchange/org.mule.examples/accelerator-common-core-src[Source^] +| Accelerator ID Graph Lightning Web Component | https://anypoint.mulesoft.com/exchange/org.mule.examples/accelerator-idgraph-lwc-src[Source^] +| Accelerator Knit Maven Plugin | https://anypoint.mulesoft.com/exchange/org.mule.examples/accelerator-knit-plugin-src[Source^] +| Accelerator POM Parent | https://anypoint.mulesoft.com/exchange/org.mule.examples/accelerator-pom-parent-src[Source^] |=== == See Also diff --git a/financial-services/1.9/modules/ROOT/pages/index.adoc b/financial-services/1.9/modules/ROOT/pages/index.adoc index 2e29479ef..926d050d8 100644 --- a/financial-services/1.9/modules/ROOT/pages/index.adoc +++ b/financial-services/1.9/modules/ROOT/pages/index.adoc @@ -8,43 +8,43 @@ MuleSoft Accelerator for Financial Services simplifies customer 360 initiatives === Core Banking Foundation The Core Banking Foundation use case enables a 360 view of your customers' financial information. There are two variations of this use case: one to jumpstart the unlocking of any core, and one to unlock a specific core. -* https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/mulesoft-accelerator-for-financial-services/minor/{fins-version}/pages/Use%20case%201a%20-%20Unlock%20any%20core/[Unlock any core^] - Unlock and display financial summaries from multiple systems. -* https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/mulesoft-accelerator-for-financial-services/minor/{fins-version}/pages/Use%20case%201b%20-%20Unlock%20Jack%20Henry%20SilverLake%20core/[Unlock Jack Henry SilverLake core^] - Accelerate the delivery of your customer 360 initiatives by unlocking your Jack Henry SilverLake core. -* https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/mulesoft-accelerator-for-financial-services/minor/{fins-version}/pages/Use%20case%201c%20-%20Unlock%20Thought%20Machine%20Vault%20Core[Unlock Thought Machine Vault Core] - Accelerate the delivery of your customer 360 initiatives by unlocking your Thought Machine Vault Core. +* https://anypoint.mulesoft.com/exchange/org.mule.examples/mulesoft-accelerator-for-financial-services/minor/{fins-version}/pages/Use%20case%201a%20-%20Unlock%20any%20core/[Unlock any core^] - Unlock and display financial summaries from multiple systems. +* https://anypoint.mulesoft.com/exchange/org.mule.examples/mulesoft-accelerator-for-financial-services/minor/{fins-version}/pages/Use%20case%201b%20-%20Unlock%20Jack%20Henry%20SilverLake%20core/[Unlock Jack Henry SilverLake core^] - Accelerate the delivery of your customer 360 initiatives by unlocking your Jack Henry SilverLake core. +* https://anypoint.mulesoft.com/exchange/org.mule.examples/mulesoft-accelerator-for-financial-services/minor/{fins-version}/pages/Use%20case%201c%20-%20Unlock%20Thought%20Machine%20Vault%20Core[Unlock Thought Machine Vault Core] - Accelerate the delivery of your customer 360 initiatives by unlocking your Thought Machine Vault Core. === Onboarding This use case accelerates the delivery and development of an enhanced onboarding solution to streamline banking loan origination and wealth management client account opening procedures. There are two extensions for this use case: -* https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/mulesoft-accelerator-for-financial-services/minor/{fins-version}/pages/Use%20case%202a%20-%20Customer%20onboarding%20-%20Banking/[Customer Onboarding - Banking^] - Create an easy and straightforward onboarding experience by empowering consumers to apply for a loan via a digital channel. +* https://anypoint.mulesoft.com/exchange/org.mule.examples/mulesoft-accelerator-for-financial-services/minor/{fins-version}/pages/Use%20case%202a%20-%20Customer%20onboarding%20-%20Banking/[Customer Onboarding - Banking^] - Create an easy and straightforward onboarding experience by empowering consumers to apply for a loan via a digital channel. -* https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/mulesoft-accelerator-for-financial-services/minor/{fins-version}/pages/Use%20case%202b%20-%20Client%20onboarding%20-%20Wealth%20management/[Client Onboarding - Wealth management^] - Accelerate the delivery and development of a streamlined and automated client onboarding solution. +* https://anypoint.mulesoft.com/exchange/org.mule.examples/mulesoft-accelerator-for-financial-services/minor/{fins-version}/pages/Use%20case%202b%20-%20Client%20onboarding%20-%20Wealth%20management/[Client Onboarding - Wealth management^] - Accelerate the delivery and development of a streamlined and automated client onboarding solution. === Payments Modernization -The https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/mulesoft-accelerator-for-financial-services/minor/{fins-version}/pages/Use%20case%203%20-%20Payments%20modernization/[Payments Modernization^] use case accelerates the development of modern payment solutions for Financial Institutions. Banks and Credit Unions will be able to deliver a diverse payments landscape that can address multiple types of financial transactions and customer needs. +The https://anypoint.mulesoft.com/exchange/org.mule.examples/mulesoft-accelerator-for-financial-services/minor/{fins-version}/pages/Use%20case%203%20-%20Payments%20modernization/[Payments Modernization^] use case accelerates the development of modern payment solutions for Financial Institutions. Banks and Credit Unions will be able to deliver a diverse payments landscape that can address multiple types of financial transactions and customer needs. === Address Change Orchestration This use case accelerates the delivery and development of a home address validation solution for streamlining downstream processes impacted by postal address changes. There are two extensions for this use case: -* https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/mulesoft-accelerator-for-financial-services/minor/{fins-version}/pages/Use%20case%204a%20-%20Address%20change%20orchestration%20-%20Insurance/[Address Change Orchestration: Insurance^] - Streamline downstream events that result from policyholder or carrier postal address adjustments. +* https://anypoint.mulesoft.com/exchange/org.mule.examples/mulesoft-accelerator-for-financial-services/minor/{fins-version}/pages/Use%20case%204a%20-%20Address%20change%20orchestration%20-%20Insurance/[Address Change Orchestration: Insurance^] - Streamline downstream events that result from policyholder or carrier postal address adjustments. -* https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/mulesoft-accelerator-for-financial-services/minor/{fins-version}/pages/Use%20case%204b%20-%20Address%20change%20orchestration%20-%20Banking/[Address Change Orchestration: Banking^] - Enhance customer service teams to upsell, cross-sell, and service opportunities that result from customer postal code address changes. +* https://anypoint.mulesoft.com/exchange/org.mule.examples/mulesoft-accelerator-for-financial-services/minor/{fins-version}/pages/Use%20case%204b%20-%20Address%20change%20orchestration%20-%20Banking/[Address Change Orchestration: Banking^] - Enhance customer service teams to upsell, cross-sell, and service opportunities that result from customer postal code address changes. === Optimize Customer Experiences -The https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/mulesoft-accelerator-for-financial-services/minor/{fins-version}/pages/Use%20case%205%20-%20Optimize%20customer%20experiences%20with%20CDP/[Optimize Customer Experiences with Salesforce CDP^] use case provides support for ingesting data from multiple sources into Data Cloud and then using the results of Data Cloud activations to optimize customer experiences by providing Customer Service Representatives (CSRs) with marketing insights. +The https://anypoint.mulesoft.com/exchange/org.mule.examples/mulesoft-accelerator-for-financial-services/minor/{fins-version}/pages/Use%20case%205%20-%20Optimize%20customer%20experiences%20with%20CDP/[Optimize Customer Experiences with Salesforce CDP^] use case provides support for ingesting data from multiple sources into Data Cloud and then using the results of Data Cloud activations to optimize customer experiences by providing Customer Service Representatives (CSRs) with marketing insights. === Salesforce Org Sync -The https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/mulesoft-accelerator-for-financial-services/minor/{fins-version}/pages/Use%20case%206%20-%20Salesforce%20org%20sync/[Salesforce Org Sync^] use case enables financial institutions using a multi-org strategy to sync customer data across Salesforce Financial Services Cloud, Sales Cloud, and Service Cloud orgs. +The https://anypoint.mulesoft.com/exchange/org.mule.examples/mulesoft-accelerator-for-financial-services/minor/{fins-version}/pages/Use%20case%206%20-%20Salesforce%20org%20sync/[Salesforce Org Sync^] use case enables financial institutions using a multi-org strategy to sync customer data across Salesforce Financial Services Cloud, Sales Cloud, and Service Cloud orgs. === Additional Assets The following *use-case agnostic* assets are also available: -* https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/mulesoft-accelerator-for-financial-services/minor/{fins-version}/pages/BIAN%20assets/[BIAN assets^] - Jumpstart your BIAN standard implementation using these BIAN-compliant assets, including API specs and implementation templates. +* https://anypoint.mulesoft.com/exchange/org.mule.examples/mulesoft-accelerator-for-financial-services/minor/{fins-version}/pages/BIAN%20assets/[BIAN assets^] - Jumpstart your BIAN standard implementation using these BIAN-compliant assets, including API specs and implementation templates. == See Also @@ -52,4 +52,4 @@ The following *use-case agnostic* assets are also available: * xref:prerequisites.adoc[Prerequisites] * xref:release-notes::accelerators/financial-services/financial-services-release-notes.adoc[Release Notes] * xref:upgrade-notes.adoc[Upgrade Notes] -* https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/mulesoft-accelerator-for-financial-services/[MuleSoft Accelerator for Financial Services on Exchange^] +* https://anypoint.mulesoft.com/exchange/org.mule.examples/mulesoft-accelerator-for-financial-services/[MuleSoft Accelerator for Financial Services on Exchange^] diff --git a/financial-services/1.9/modules/ROOT/pages/payments-setup-guide.adoc b/financial-services/1.9/modules/ROOT/pages/payments-setup-guide.adoc index e84ae2406..b614ba3b6 100644 --- a/financial-services/1.9/modules/ROOT/pages/payments-setup-guide.adoc +++ b/financial-services/1.9/modules/ROOT/pages/payments-setup-guide.adoc @@ -9,7 +9,7 @@ This guide provides instructions for setting up all the components required to r * Moov.io containers will be used to simulate the processing of ACH and Fedwire messages * A third-party Java library will be used to simulate the processing of SWIFT messages * A custom process will be used to simulate incoming payment confirmations -* A https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fins-payments-frontend-webui-src/[Payments Front-end Web UI^] has been built to demonstrate the functionality implemented by this use case +* A https://anypoint.mulesoft.com/exchange/org.mule.examples/fins-payments-frontend-webui-src/[Payments Front-end Web UI^] has been built to demonstrate the functionality implemented by this use case * MultiChain Wallet Node is used to support processing of BlockChain Transactions == Setup @@ -20,20 +20,20 @@ The following containerized services are deployed on docker. For demo purposes, * moov.io ACH service * moov.io Fedwire service -* https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fins-payments-frontend-webui-src/[Payments Front-end Web UI^] +* https://anypoint.mulesoft.com/exchange/org.mule.examples/fins-payments-frontend-webui-src/[Payments Front-end Web UI^] * Blockchain based on https://www.multichain.com/[MultiChain^] -The https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fins-payments-frontend-webui-src/[Payments Front-end Web UI^] can also be run locally, outside of a container, by following the instructions provided in its README file. +The https://anypoint.mulesoft.com/exchange/org.mule.examples/fins-payments-frontend-webui-src/[Payments Front-end Web UI^] can also be run locally, outside of a container, by following the instructions provided in its README file. *Payments Front-end Web UI recommended setup:* . Install Docker and its dependencies on the server of your choice. -. Configure the https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fins-payments-frontend-webui-src/[Payments Front-end Web UI^] by modifying the following properties in the .env file: - ** `REACT_APP_PAYMENTS_WEBUI_EXP_API_ENDPOINT` should point to an instance of the https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fins-payments-webui-exp-api-spec/[Payments Web UI Experience API^] - ** `REACT_APP_PAYMENTS_WEBUI_EXP_API_WEBSOCKET_ENDPOINT` should point to an instance of the https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fins-payments-webui-exp-api-spec/[Payments Web UI Experience API^] +. Configure the https://anypoint.mulesoft.com/exchange/org.mule.examples/fins-payments-frontend-webui-src/[Payments Front-end Web UI^] by modifying the following properties in the .env file: + ** `REACT_APP_PAYMENTS_WEBUI_EXP_API_ENDPOINT` should point to an instance of the https://anypoint.mulesoft.com/exchange/org.mule.examples/fins-payments-webui-exp-api-spec/[Payments Web UI Experience API^] + ** `REACT_APP_PAYMENTS_WEBUI_EXP_API_WEBSOCKET_ENDPOINT` should point to an instance of the https://anypoint.mulesoft.com/exchange/org.mule.examples/fins-payments-webui-exp-api-spec/[Payments Web UI Experience API^] . Build the docker image by running its docker-build.sh script. . Start the docker container by running the docker-run.sh script on the machine running the Docker server, or use a Docker administration UI to manage the containers. -. Update `https.cors.allow-url` property in the https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fins-payments-webui-exp-api/[Payments Web UI Experience API^] with the Payments Front-end Web UI endpoint to allow CORS. +. Update `https.cors.allow-url` property in the https://anypoint.mulesoft.com/exchange/org.mule.examples/fins-payments-webui-exp-api/[Payments Web UI Experience API^] with the Payments Front-end Web UI endpoint to allow CORS. *Moov.io recommended setup:* @@ -43,7 +43,7 @@ The moov.io images are provided pre-built as-is. They can be started on the Dock To run the MultiChain node as a docker container, perform the following steps: -. Use the Dockerfile from the scripts folder in the https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fins-blockchain-sys-api-spec/[Blockchain System API^] to build the MultiChain image. +. Use the Dockerfile from the scripts folder in the https://anypoint.mulesoft.com/exchange/org.mule.examples/fins-blockchain-sys-api-spec/[Blockchain System API^] to build the MultiChain image. . Run the `docker-run.sh` script to deploy the container and setup network ports. Run `docker-exec.sh` to create MultiChain and configure the json-rpc service to interact with the MultiChain container. == See Also diff --git a/financial-services/1.9/modules/ROOT/pages/sfdc-data-cloud-setup-guide.adoc b/financial-services/1.9/modules/ROOT/pages/sfdc-data-cloud-setup-guide.adoc index 963031073..404a73bbc 100644 --- a/financial-services/1.9/modules/ROOT/pages/sfdc-data-cloud-setup-guide.adoc +++ b/financial-services/1.9/modules/ROOT/pages/sfdc-data-cloud-setup-guide.adoc @@ -1,7 +1,7 @@ = Salesforce Data Cloud Setup Guide :fins-version: {page-component-version} -The following provides guidance on Salesforce Data Cloud setup required for the https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/mulesoft-accelerator-for-financial-services/minor/{fins-version}/pages/Use%20case%205%20-%20Optimize%20customer%20experiences%20with%20CDP/[Optimize Customer Experiences with Data Cloud^] use case. A few of these steps can be omitted if deploying the https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fins-salesforce-cdp-sys-api[FINS Salesforce Data Cloud System API^] independently of the use case. +The following provides guidance on Salesforce Data Cloud setup required for the https://anypoint.mulesoft.com/exchange/org.mule.examples/mulesoft-accelerator-for-financial-services/minor/{fins-version}/pages/Use%20case%205%20-%20Optimize%20customer%20experiences%20with%20CDP/[Optimize Customer Experiences with Data Cloud^] use case. A few of these steps can be omitted if deploying the https://anypoint.mulesoft.com/exchange/org.mule.examples/fins-salesforce-cdp-sys-api[FINS Salesforce Data Cloud System API^] independently of the use case. == Data Cloud provisioning @@ -13,7 +13,7 @@ If the Data Cloud instance is already provisioned, skip this section. If not fol . Click `Get Started` to provision the Data Cloud Instance and it can take a few minutes. Correct any issues reported and finish the setup. The Data Cloud instance is considered to be successfully set up if there is a green tick mark for all the steps and you do not need to do anything. + + -image:https://www.mulesoft.com/ext/solutions/draft/images/fins-cdp-setup-cdp-provisioning.png[fins-cdp-setup-cdp-provisioning.png,79%] +image:https://www.mulesoft.com/ext/solutions/images/fins-cdp-setup-cdp-provisioning.png[fins-cdp-setup-cdp-provisioning.png,79%] + == Create data connectors @@ -22,7 +22,7 @@ Connectors are specialized data streams that communicate with external sources t === Use case requirements -The https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/mulesoft-accelerator-for-financial-services/minor/{fins-version}/pages/Use%20case%205%20-%20Optimize%20customer%20experiences%20with%20CDP/[Optimize Customer Experiences with CDP^] use case uses the following connectors: +The https://anypoint.mulesoft.com/exchange/org.mule.examples/mulesoft-accelerator-for-financial-services/minor/{fins-version}/pages/Use%20case%205%20-%20Optimize%20customer%20experiences%20with%20CDP/[Optimize Customer Experiences with CDP^] use case uses the following connectors: * Salesforce CRM - to connect data from a Salesforce CRM instance to Data Cloud. * Marketing Cloud - to receive segmentation results for marketing purposes. @@ -48,7 +48,7 @@ In Data Cloud, you can establish a connection to other Salesforce orgs built upo Once the connection is established, the Data Cloud admin can either use bundles that can automatically deploy data or set up their own data streams; we will walk through the latter approach, below. -For the https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/mulesoft-accelerator-for-financial-services/minor/{fins-version}/pages/Use%20case%205%20-%20Optimize%20customer%20experiences%20with%20CDP/[Optimize Customer Experiences with CDP^] use case, hover over the `Connector Name` field of the new connection and click the pencil icon to change the name of the Connector to `Salesforce FSC Banking`. This is the name that will appear under the `Salesforce Org` dropdown while creating a new Data Stream. +For the https://anypoint.mulesoft.com/exchange/org.mule.examples/mulesoft-accelerator-for-financial-services/minor/{fins-version}/pages/Use%20case%205%20-%20Optimize%20customer%20experiences%20with%20CDP/[Optimize Customer Experiences with CDP^] use case, hover over the `Connector Name` field of the new connection and click the pencil icon to change the name of the Connector to `Salesforce FSC Banking`. This is the name that will appear under the `Salesforce Org` dropdown while creating a new Data Stream. === Marketing Cloud Connector @@ -56,7 +56,7 @@ A Marketing Cloud Connector is required in order to use Marketing Cloud as eithe . Select `Marketing Cloud` from the left navigation menu in the `Data Cloud Setup` app. . Enter the Credentials to authenticate your Marketing Cloud account. You can proceed with the next step in the setup only if the authentication is successful. -. Data Source setup - this step is optional, and only needs to be set up if you are planning to ingest data from Marketing Cloud into Data Cloud. This step is not required for the https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/mulesoft-accelerator-for-financial-services/minor/{fins-version}/pages/Use%20case%205%20-%20Optimize%20customer%20experiences%20with%20CDP/[Optimize Customer Experiences with CDP^] use case. +. Data Source setup - this step is optional, and only needs to be set up if you are planning to ingest data from Marketing Cloud into Data Cloud. This step is not required for the https://anypoint.mulesoft.com/exchange/org.mule.examples/mulesoft-accelerator-for-financial-services/minor/{fins-version}/pages/Use%20case%205%20-%20Optimize%20customer%20experiences%20with%20CDP/[Optimize Customer Experiences with CDP^] use case. . Select Business Units to activate - select the business units to publish segments to Marketing Cloud. Ensure all configured items show a green circle before using the connector. @@ -65,7 +65,7 @@ Ensure all configured items show a green circle before using the connector. You can push data from an external system into Data Cloud via the Ingestion API. This RESTful API offers two interaction patterns: bulk and streaming. The streaming pattern accepts incremental updates to a data set as those changes are captured, while the bulk pattern accepts CSV files in cases where data syncs occur periodically. The same data stream can accept data from the streaming and the bulk interaction. -For the https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/mulesoft-accelerator-for-financial-services/minor/{fins-version}/pages/Use%20case%205%20-%20Optimize%20customer%20experiences%20with%20CDP/[Optimize Customer Experiences with CDP^] use case, the external systems Snowflake, Databricks, and Amazon S3 contain data to be pushed to Data Cloud through MuleSoft's Salesforce CDP connector using the Ingestion API. The schema file for the Ingestion API can be found in the https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fins-salesforce-cdp-sys-api/[FINS Salesforce CDP System API^] implementation template. This schema includes definitions for the following objects: +For the https://anypoint.mulesoft.com/exchange/org.mule.examples/mulesoft-accelerator-for-financial-services/minor/{fins-version}/pages/Use%20case%205%20-%20Optimize%20customer%20experiences%20with%20CDP/[Optimize Customer Experiences with CDP^] use case, the external systems Snowflake, Databricks, and Amazon S3 contain data to be pushed to Data Cloud through MuleSoft's Salesforce CDP connector using the Ingestion API. The schema file for the Ingestion API can be found in the https://anypoint.mulesoft.com/exchange/org.mule.examples/fins-salesforce-cdp-sys-api/[FINS Salesforce CDP System API^] implementation template. This schema includes definitions for the following objects: * FinancialAccount * FinancialTransaction @@ -83,7 +83,7 @@ Follow the steps below to setup and configure an ingestion API to push data from . Click `New`, enter a name for the API source (for example, 'FINS_Banking-Data-Connector'), then click `Save`. . On the details page for the new connector, you must upload a schema file in OpenAPI (OAS) format with a `.yaml` file extension. The schema file describes how data transferred via the API is structured. + *Note:* Ingestion API schemas have set requirements - review the schema requirements below if having issues uploading the schema. -. Click `Upload Schema` and navigate to the location of the file you want to use. Select the file and click Open. For the https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/mulesoft-accelerator-for-financial-services/minor/{fins-version}/pages/Use%20case%205%20-%20Optimize%20customer%20experiences%20with%20CDP/[Optimize Customer Experiences with CDP^] use case, the schema file `mule-cdp-connector-schema.yaml` is available under `src/test/resources/cdp-schema` of the https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fins-salesforce-cdp-sys-api/[FINS Salesforce CDP System API^] implementation template. +. Click `Upload Schema` and navigate to the location of the file you want to use. Select the file and click Open. For the https://anypoint.mulesoft.com/exchange/org.mule.examples/mulesoft-accelerator-for-financial-services/minor/{fins-version}/pages/Use%20case%205%20-%20Optimize%20customer%20experiences%20with%20CDP/[Optimize Customer Experiences with CDP^] use case, the schema file `mule-cdp-connector-schema.yaml` is available under `src/test/resources/cdp-schema` of the https://anypoint.mulesoft.com/exchange/org.mule.examples/fins-salesforce-cdp-sys-api/[FINS Salesforce CDP System API^] implementation template. . Preview all the detected objects and their attributes in your schema. . Click `Save`. @@ -108,7 +108,7 @@ Before you can send data into Data Cloud using Ingestion API via Mulesoft's Sale ** `Perform requests on your behalf at any time (refresh_token, offline_access)` . Click `Save` and then `Done` to create the connected app. -After creating the connected app, click the `Manage Consumer Details` button from the app detail page, confirm your identity, and then record the `Consumer Key` and `Consumer Secret` values: you will need these to configure the https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fins-salesforce-cdp-sys-api/[FINS Salesforce CDP System API] implementation template for deployment. This application uses the MuleSoft Connector for Salesforce CDP, which provides customers a pipeline to send data into Data Cloud. Refer to the https://dev-docs-internal.kqa.msap.io/beta-accelerators/salesforce-cdp-connector/1.0/[Salesforce CDP Connector documentation] for additional details on configuration and available operations. +After creating the connected app, click the `Manage Consumer Details` button from the app detail page, confirm your identity, and then record the `Consumer Key` and `Consumer Secret` values: you will need these to configure the https://anypoint.mulesoft.com/exchange/org.mule.examples/fins-salesforce-cdp-sys-api/[FINS Salesforce CDP System API] implementation template for deployment. This application uses the MuleSoft Connector for Salesforce CDP, which provides customers a pipeline to send data into Data Cloud. Refer to the https://docs.mulesoft.com/salesforce-cdp-connector/1.0/[Salesforce CDP Connector documentation] for additional details on configuration and available operations. ==== Schema requirements @@ -150,7 +150,7 @@ To begin the flow of data from a Salesforce CRM data source (such as your Salesf ==== Use case requirements -For the https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/mulesoft-accelerator-for-financial-services/minor/{fins-version}/pages/Use%20case%205%20-%20Optimize%20customer%20experiences%20with%20CDP/[Optimize Customer Experiences with CDP^] use case, a separate data stream for each of the following objects must be created to pull required data from your Salesforce FSC instance: +For the https://anypoint.mulesoft.com/exchange/org.mule.examples/mulesoft-accelerator-for-financial-services/minor/{fins-version}/pages/Use%20case%205%20-%20Optimize%20customer%20experiences%20with%20CDP/[Optimize Customer Experiences with CDP^] use case, a separate data stream for each of the following objects must be created to pull required data from your Salesforce FSC instance: |=== | Object in Salesforce CRM | Name of the DataStream @@ -257,7 +257,7 @@ NOTE: If you are prompted with an error stating those objects cannot be added, y ==== Add formula fields -Once the data streams for standard objects have been created, we need to add a formula field to identify whether or not the associated party represents an Individual. This is required for proper identity resolution and segmentation for the https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/mulesoft-accelerator-for-financial-services/minor/{fins-version}/pages/Use%20case%205%20-%20Optimize%20customer%20experiences%20with%20CDP/[Optimize Customer Experiences with CDP^] use case. Repeat the following steps for both data streams created above: +Once the data streams for standard objects have been created, we need to add a formula field to identify whether or not the associated party represents an Individual. This is required for proper identity resolution and segmentation for the https://anypoint.mulesoft.com/exchange/org.mule.examples/mulesoft-accelerator-for-financial-services/minor/{fins-version}/pages/Use%20case%205%20-%20Optimize%20customer%20experiences%20with%20CDP/[Optimize Customer Experiences with CDP^] use case. Repeat the following steps for both data streams created above: . Click the data stream from the 'Data Streams' list view to bring up the details page. . Select the `New Formula Field` action from the top right action list. You may need to click the 'more' down arrow to find the action. @@ -284,7 +284,7 @@ If you encounter object access errors in Data Cloud when creating data streams, . Enable Read and View All permissions for the object and Read Access for each field. Use the table above for reference. . Click Save. -Repeat these steps for all objects and fields you want to ingest into Data Cloud. For the https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/mulesoft-accelerator-for-financial-services/minor/{fins-version}/pages/Use%20case%205%20-%20Optimize%20customer%20experiences%20with%20CDP/[Optimize Customer Experiences with CDP^] use case, this includes the `Account` and `Contact` objects. +Repeat these steps for all objects and fields you want to ingest into Data Cloud. For the https://anypoint.mulesoft.com/exchange/org.mule.examples/mulesoft-accelerator-for-financial-services/minor/{fins-version}/pages/Use%20case%205%20-%20Optimize%20customer%20experiences%20with%20CDP/[Optimize Customer Experiences with CDP^] use case, this includes the `Account` and `Contact` objects. === Create an Ingestion API data stream @@ -292,7 +292,7 @@ If you have not already done so, < / " : ? | , _ &+` . Click `Save`. -This completes the configuration of Data Cloud required for the https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/mulesoft-accelerator-for-financial-services/minor/{fins-version}/pages/Use%20case%205%20-%20Optimize%20customer%20experiences%20with%20CDP/[Optimize Customer Experiences with CDP^] use case. +This completes the configuration of Data Cloud required for the https://anypoint.mulesoft.com/exchange/org.mule.examples/mulesoft-accelerator-for-financial-services/minor/{fins-version}/pages/Use%20case%205%20-%20Optimize%20customer%20experiences%20with%20CDP/[Optimize Customer Experiences with CDP^] use case. == See Also diff --git a/financial-services/1.9/modules/ROOT/pages/sfdc-fsc-setup-guide.adoc b/financial-services/1.9/modules/ROOT/pages/sfdc-fsc-setup-guide.adoc index d60590e73..3a9693e77 100644 --- a/financial-services/1.9/modules/ROOT/pages/sfdc-fsc-setup-guide.adoc +++ b/financial-services/1.9/modules/ROOT/pages/sfdc-fsc-setup-guide.adoc @@ -429,7 +429,7 @@ The following fields must be created in the corresponding objects. === Create via Apex Script -An Apex class called `CustomFieldUtility` can be used to create custom fields programmatically. The source for this class can be found in the https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fins-common-resources-src[FINS Common Resources^] project. Download this project and follow the steps below. +An Apex class called `CustomFieldUtility` can be used to create custom fields programmatically. The source for this class can be found in the https://anypoint.mulesoft.com/exchange/org.mule.examples/fins-common-resources-src[FINS Common Resources^] project. Download this project and follow the steps below. . Click on Salesforce Setup icon and select `Developer Console` to open a new console window . Go to `+File -> New -> Apex class+` and create a new class named `CustomFieldUtility` @@ -532,7 +532,7 @@ If desired, click the *Currency Setup* button to add support for additional curr == Create Platform Events and Apex Triggers -The following Platform Event Objects and Apex Triggers must be created in order to capture updates from Salesforce. The scripts to create these Apex Triggers and add fields to Platform Event Objects are located in the https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fins-common-resources-src/[FINS Common Resources] project. +The following Platform Event Objects and Apex Triggers must be created in order to capture updates from Salesforce. The scripts to create these Apex Triggers and add fields to Platform Event Objects are located in the https://anypoint.mulesoft.com/exchange/org.mule.examples/fins-common-resources-src/[FINS Common Resources] project. |=== | Salesforce Object | Salesforce Platform Event Object | Salesforce Platform Event API Name | Apex Trigger Name @@ -590,7 +590,7 @@ This implementation requires creation of Platform Events in Salesforce. To creat . Login to Salesforce. . Click Setup to search for Platform Events in Quick Find Box. Platform Events Page under Integrations section appears with list of available Platform Events. . Click *New Platform Event* button to create an Object and enter Platform Information Details fields like Label, Plural Label and Object with Object Name and Event API Names as above table. Click Save. Repeat this step for creating multiple Salesforce Platform Event Objects as mentioned in the above table. -. To add Custom Fields & Relationships to Platform Event Definitions, run the utility scripts (`CreatePlatformEventsCustomFields.txt`) available in the https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fins-common-resources-src/[FINS Common Resources^] under the `/salesforce` folder. +. To add Custom Fields & Relationships to Platform Event Definitions, run the utility scripts (`CreatePlatformEventsCustomFields.txt`) available in the https://anypoint.mulesoft.com/exchange/org.mule.examples/fins-common-resources-src/[FINS Common Resources^] under the `/salesforce` folder. === Create Apex Triggers @@ -600,7 +600,7 @@ Follow the below steps to create the Apex Triggers . Click Setup to search for Object Manager in Quick Find Box. . Search for the Salesforce Object. A page appears with Details of the Object. . Click Triggers unders the Details section to see list of available triggers on the Object. Click New. -. Copy the Trigger Script code searching by Apex Trigger Name (mentioned in the above table for the SalesforceObject) in CreateApexTriggers.txt of https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fins-common-resources-src/[FINS Common Resources] to the script editor. CreateApexTriggers.txt file is available under /salesforce folder. +. Copy the Trigger Script code searching by Apex Trigger Name (mentioned in the above table for the SalesforceObject) in CreateApexTriggers.txt of https://anypoint.mulesoft.com/exchange/org.mule.examples/fins-common-resources-src/[FINS Common Resources] to the script editor. CreateApexTriggers.txt file is available under /salesforce folder. . Obtain the `LastModifiedById` and `RecordTypeId` (if it exists) by running the queries mentioned in the trigger from Developer Console. . Replace the values in the script and Save the trigger. . Click Save and ensure isActive checkbox is ticked. @@ -677,7 +677,7 @@ You now need to copy the `Consumer Key` and `Consumer Secret` values for use in . Verify your identity by entering the verification code that was emailed to you. . Copy the key and secret values and update your `settings.xml` file as described above. -Download the https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fins-common-resources-src[FINS Common Resources project^] for a sample `settings.xml` file that can be used as a starting point. +Download the https://anypoint.mulesoft.com/exchange/org.mule.examples/fins-common-resources-src[FINS Common Resources project^] for a sample `settings.xml` file that can be used as a starting point. == Generating Security Token for Service Account diff --git a/financial-services/1.9/modules/ROOT/pages/sfdc-mc-setup-guide.adoc b/financial-services/1.9/modules/ROOT/pages/sfdc-mc-setup-guide.adoc index be8885537..54d157d0b 100644 --- a/financial-services/1.9/modules/ROOT/pages/sfdc-mc-setup-guide.adoc +++ b/financial-services/1.9/modules/ROOT/pages/sfdc-mc-setup-guide.adoc @@ -1,12 +1,12 @@ = Salesforce Marketing Cloud Setup Guide :fins-version: {page-component-version} -This guide provides the setup instructions for Marketing Cloud for the following use cases that are part of the https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/mulesoft-accelerator-for-financial-services/[MuleSoft Accelerator for Financial Services^]: +This guide provides the setup instructions for Marketing Cloud for the following use cases that are part of the https://anypoint.mulesoft.com/exchange/org.mule.examples/mulesoft-accelerator-for-financial-services/[MuleSoft Accelerator for Financial Services^]: -* https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/mulesoft-accelerator-for-financial-services/minor/{fins-version}/pages/Use%20case%202b%20-%20Client%20onboarding%20-%20Wealth%20management/[Use case 2b - Client onboarding - Wealth management^] -* https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/mulesoft-accelerator-for-financial-services/minor/{fins-version}/pages/Use%20case%204a%20-%20Address%20change%20orchestration%20-%20Insurance/[Use case 4a - Address change orchestration - Insurance^] -* https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/mulesoft-accelerator-for-financial-services/minor/{fins-version}/pages/Use%20case%204b%20-%20Address%20change%20orchestration%20-%20Banking/[Use case 4b - Address change orchestration - Banking^] -* https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/mulesoft-accelerator-for-financial-services/minor/{fins-version}/pages/Use%20case%205%20-%20Optimize%20customer%20experiences%20with%20CDP/[Use case 5 - Optimize customer experiences with CDP^] +* https://anypoint.mulesoft.com/exchange/org.mule.examples/mulesoft-accelerator-for-financial-services/minor/{fins-version}/pages/Use%20case%202b%20-%20Client%20onboarding%20-%20Wealth%20management/[Use case 2b - Client onboarding - Wealth management^] +* https://anypoint.mulesoft.com/exchange/org.mule.examples/mulesoft-accelerator-for-financial-services/minor/{fins-version}/pages/Use%20case%204a%20-%20Address%20change%20orchestration%20-%20Insurance/[Use case 4a - Address change orchestration - Insurance^] +* https://anypoint.mulesoft.com/exchange/org.mule.examples/mulesoft-accelerator-for-financial-services/minor/{fins-version}/pages/Use%20case%204b%20-%20Address%20change%20orchestration%20-%20Banking/[Use case 4b - Address change orchestration - Banking^] +* https://anypoint.mulesoft.com/exchange/org.mule.examples/mulesoft-accelerator-for-financial-services/minor/{fins-version}/pages/Use%20case%205%20-%20Optimize%20customer%20experiences%20with%20CDP/[Use case 5 - Optimize customer experiences with CDP^] == Create Data Extension for Sync Process @@ -101,7 +101,7 @@ Journey Builder is used to trigger emails to a list of email addresses. The foll === Create Online Submission Form -This is the form that the client will submit so that the https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fins-salesforce-wealth-exp-api/[Salesforce Wealth Experience API] will be invoked to create a lead in FSC: +This is the form that the client will submit so that the https://anypoint.mulesoft.com/exchange/org.mule.examples/fins-salesforce-wealth-exp-api/[Salesforce Wealth Experience API] will be invoked to create a lead in FSC: * Navigate to Web Studio and click Cloudpages * Create a Collection diff --git a/healthcare/2.18/modules/ROOT/pages/ccda-fhir-converter.adoc b/healthcare/2.18/modules/ROOT/pages/ccda-fhir-converter.adoc index 11b76cb60..134619070 100644 --- a/healthcare/2.18/modules/ROOT/pages/ccda-fhir-converter.adoc +++ b/healthcare/2.18/modules/ROOT/pages/ccda-fhir-converter.adoc @@ -1,10 +1,10 @@ = C-CDA to FHIR Converter -The https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/hls-ccda-to-fhir-sys-api/[C-CDA to FHIR converter] comes with a ready to use template for https://www.hl7.org/implement/standards/product_brief.cfm?product_id=496[CDA] to FHIR conversion. This template can be extended or modified to meet specific conversion requirements. +The https://anypoint.mulesoft.com/exchange/org.mule.examples/hls-ccda-to-fhir-sys-api/[C-CDA to FHIR converter] comes with a ready to use template for https://www.hl7.org/implement/standards/product_brief.cfm?product_id=496[CDA] to FHIR conversion. This template can be extended or modified to meet specific conversion requirements. == Functional diagram -image:https://www.mulesoft.com/ext/solutions/draft/images/hls-ccda-fhir-fx-diagram.svg[CDA to FHIR converter functional diagram,900,align="center"] +image:https://www.mulesoft.com/ext/solutions/images/hls-ccda-fhir-fx-diagram.svg[CDA to FHIR converter functional diagram,900,align="center"] == Advantages diff --git a/healthcare/2.18/modules/ROOT/pages/fhir-r4-assets.adoc b/healthcare/2.18/modules/ROOT/pages/fhir-r4-assets.adoc index 134ba48f5..10d431db8 100644 --- a/healthcare/2.18/modules/ROOT/pages/fhir-r4-assets.adoc +++ b/healthcare/2.18/modules/ROOT/pages/fhir-r4-assets.adoc @@ -2,11 +2,11 @@ The following are a collection of assets to support MuleSoft customers who are developing Fast Healthcare Interoperability Resources (FHIR) APIs using MuleSoft. Visit the https://www.hl7.org/fhir/[official HL7 website] for more information. -* https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/hls-fhirjson-to-raml-sys-api-spec/[FHIR RAML auto-generator] - Utility to generate RAML specification(s) for FHIR resources directly from the JSON schema provided by HL7. +* https://anypoint.mulesoft.com/exchange/org.mule.examples/hls-fhirjson-to-raml-sys-api-spec/[FHIR RAML auto-generator] - Utility to generate RAML specification(s) for FHIR resources directly from the JSON schema provided by HL7. * xref:fhir-r4-us-core-profiles.adoc[FHIR R4 US Core Profile Assets] * xref:fhir-r4-resources.adoc[FHIR R4 Resources List] -* https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fhir-error-policy/[FHIR Error API Policy] - Captures error responses and formats them in an FHIR OperationOutcome-compliant format, since Anypoint Platform's out-of-the-box (OOTB) policies do not provide error messages in an FHIR-compliant format. This policy can also be used with other OOTB API policies provided in Anypoint Platform, such as OAuth or JWT. -* https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/hc-accelerator-okta-smartfhir/[Okta SMART on FHIR^] - Implementation template that walks you through how to set up a reference SMART on FHIR implementation on Anypoint Platform using Okta as the identity provider. +* https://anypoint.mulesoft.com/exchange/org.mule.examples/fhir-error-policy/[FHIR Error API Policy] - Captures error responses and formats them in an FHIR OperationOutcome-compliant format, since Anypoint Platform's out-of-the-box (OOTB) policies do not provide error messages in an FHIR-compliant format. This policy can also be used with other OOTB API policies provided in Anypoint Platform, such as OAuth or JWT. +* https://anypoint.mulesoft.com/exchange/org.mule.examples/hc-accelerator-okta-smartfhir/[Okta SMART on FHIR^] - Implementation template that walks you through how to set up a reference SMART on FHIR implementation on Anypoint Platform using Okta as the identity provider. == See Also diff --git a/healthcare/2.18/modules/ROOT/pages/fhir-r4-resources.adoc b/healthcare/2.18/modules/ROOT/pages/fhir-r4-resources.adoc index 062796d38..8414363f1 100644 --- a/healthcare/2.18/modules/ROOT/pages/fhir-r4-resources.adoc +++ b/healthcare/2.18/modules/ROOT/pages/fhir-r4-resources.adoc @@ -2,7 +2,7 @@ The MuleSoft Accelerator for Healthcare provides a library of United States Core Data for Interoperability (USCDI) and FHIR R4 resources to help healthcare developers adhere to interoperability needs and jumpstart the development of healthcare digital transformation initiatives. -You can also use the https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fhir-error-policy/[FHIR Error API Policy] to capture error responses and format them in an FHIR OperationOutcome-compliant format, since Anypoint Platform's out-of-the-box (OOTB) policies do not provide error messages in an FHIR-compliant format. This policy can also be used with other OOTB API policies provided in Anypoint Platform, such as OAuth or JWT. +You can also use the https://anypoint.mulesoft.com/exchange/org.mule.examples/fhir-error-policy/[FHIR Error API Policy] to capture error responses and format them in an FHIR OperationOutcome-compliant format, since Anypoint Platform's out-of-the-box (OOTB) policies do not provide error messages in an FHIR-compliant format. This policy can also be used with other OOTB API policies provided in Anypoint Platform, such as OAuth or JWT. For the list of US core profile assets, please refer to xref:fhir-r4-us-core-profiles.adoc[this link]. @@ -15,339 +15,339 @@ _API specifications, data types, and libraries built to meet compliance with FHI | Category| Library | API Specification .^| Foundation - Confirmance -| https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fhir-r4-capabilitystatement-library/[CapabilityStatement] ^[N]^ + -https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fhir-r4-structuredefinition-library/[StructureDefinition] ^[N]^ + -https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fhir-r4-implementationguide-library/[ImplementationGuide] + -https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fhir-r4-searchparameter-library/[SearchParameter] + -https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fhir-r4-operationdefinition-library/[OperationDefinition] ^[N]^ + -https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fhir-r4-compartmentdefinition-library/[CompartmentDefinition] + -https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fhir-r4-messagedefinition-library/[MessageDefinition] + -https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fhir-r4-structuremap-library/[StructureMap] + -https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fhir-r4-graphdefinition-library/[GraphDefinition] + -https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fhir-r4-examplescenario-library/[ExampleScenario] -| https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fhir-r4-capabilitystatement-api/[CapabilityStatement] ^[N]^ + -https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fhir-r4-structuredefinition-api/[StructureDefinition] ^[N]^ + -https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fhir-r4-implementationguide-api/[ImplementationGuide] + -https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fhir-r4-searchparameter-api/[SearchParameter] + -https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fhir-r4-operationdefinition-api/[OperationDefinition] ^[N]^ + -https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fhir-r4-compartmentdefinition-api/[CompartmentDefinition] + -https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fhir-r4-messagedefinition-api/[MessageDefinition] + -https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fhir-r4-structuremap-api/[StructureMap] + -https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fhir-r4-graphdefinition-api/[GraphDefinition] + -https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fhir-r4-examplescenario-api/[ExampleScenario] +| https://anypoint.mulesoft.com/exchange/org.mule.examples/fhir-r4-capabilitystatement-library/[CapabilityStatement] ^[N]^ + +https://anypoint.mulesoft.com/exchange/org.mule.examples/fhir-r4-structuredefinition-library/[StructureDefinition] ^[N]^ + +https://anypoint.mulesoft.com/exchange/org.mule.examples/fhir-r4-implementationguide-library/[ImplementationGuide] + +https://anypoint.mulesoft.com/exchange/org.mule.examples/fhir-r4-searchparameter-library/[SearchParameter] + +https://anypoint.mulesoft.com/exchange/org.mule.examples/fhir-r4-operationdefinition-library/[OperationDefinition] ^[N]^ + +https://anypoint.mulesoft.com/exchange/org.mule.examples/fhir-r4-compartmentdefinition-library/[CompartmentDefinition] + +https://anypoint.mulesoft.com/exchange/org.mule.examples/fhir-r4-messagedefinition-library/[MessageDefinition] + +https://anypoint.mulesoft.com/exchange/org.mule.examples/fhir-r4-structuremap-library/[StructureMap] + +https://anypoint.mulesoft.com/exchange/org.mule.examples/fhir-r4-graphdefinition-library/[GraphDefinition] + +https://anypoint.mulesoft.com/exchange/org.mule.examples/fhir-r4-examplescenario-library/[ExampleScenario] +| https://anypoint.mulesoft.com/exchange/org.mule.examples/fhir-r4-capabilitystatement-api/[CapabilityStatement] ^[N]^ + +https://anypoint.mulesoft.com/exchange/org.mule.examples/fhir-r4-structuredefinition-api/[StructureDefinition] ^[N]^ + +https://anypoint.mulesoft.com/exchange/org.mule.examples/fhir-r4-implementationguide-api/[ImplementationGuide] + +https://anypoint.mulesoft.com/exchange/org.mule.examples/fhir-r4-searchparameter-api/[SearchParameter] + +https://anypoint.mulesoft.com/exchange/org.mule.examples/fhir-r4-operationdefinition-api/[OperationDefinition] ^[N]^ + +https://anypoint.mulesoft.com/exchange/org.mule.examples/fhir-r4-compartmentdefinition-api/[CompartmentDefinition] + +https://anypoint.mulesoft.com/exchange/org.mule.examples/fhir-r4-messagedefinition-api/[MessageDefinition] + +https://anypoint.mulesoft.com/exchange/org.mule.examples/fhir-r4-structuremap-api/[StructureMap] + +https://anypoint.mulesoft.com/exchange/org.mule.examples/fhir-r4-graphdefinition-api/[GraphDefinition] + +https://anypoint.mulesoft.com/exchange/org.mule.examples/fhir-r4-examplescenario-api/[ExampleScenario] .^| Foundation - Terminology -| https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fhir-r4-codesystem-library/[CodeSystem] ^[N]^ + -https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fhir-r4-valueset-library/[ValueSet] ^[N]^ + -https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fhir-r4-conceptmap-library/[ConceptMap] + -https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fhir-r4-namingsystem-library/[NamingSystem] + -https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fhir-r4-terminologycapabilities-library/[TerminologiesCapabilities] -| https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fhir-r4-codesystem-api/[CodeSystem] ^[N]^ + -https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fhir-r4-valueset-api/[ValueSet] ^[N]^ + -https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fhir-r4-conceptmap-api/[ConceptMap] + -https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fhir-r4-namingsystem-api/[NamingSystem] + -https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fhir-r4-terminologycapabilities-api/[TerminologiesCapabilities] +| https://anypoint.mulesoft.com/exchange/org.mule.examples/fhir-r4-codesystem-library/[CodeSystem] ^[N]^ + +https://anypoint.mulesoft.com/exchange/org.mule.examples/fhir-r4-valueset-library/[ValueSet] ^[N]^ + +https://anypoint.mulesoft.com/exchange/org.mule.examples/fhir-r4-conceptmap-library/[ConceptMap] + +https://anypoint.mulesoft.com/exchange/org.mule.examples/fhir-r4-namingsystem-library/[NamingSystem] + +https://anypoint.mulesoft.com/exchange/org.mule.examples/fhir-r4-terminologycapabilities-library/[TerminologiesCapabilities] +| https://anypoint.mulesoft.com/exchange/org.mule.examples/fhir-r4-codesystem-api/[CodeSystem] ^[N]^ + +https://anypoint.mulesoft.com/exchange/org.mule.examples/fhir-r4-valueset-api/[ValueSet] ^[N]^ + +https://anypoint.mulesoft.com/exchange/org.mule.examples/fhir-r4-conceptmap-api/[ConceptMap] + +https://anypoint.mulesoft.com/exchange/org.mule.examples/fhir-r4-namingsystem-api/[NamingSystem] + +https://anypoint.mulesoft.com/exchange/org.mule.examples/fhir-r4-terminologycapabilities-api/[TerminologiesCapabilities] .^| Foundation - Security -| https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fhir-r4-provenance-library/[Provenance] + -https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fhir-r4-auditevent-library/[AuditEvent] + -https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fhir-r4-consent-library/[Consent] -| https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fhir-r4-provenance-api/[Provenance] + -https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fhir-r4-auditevent-api/[AuditEvent] + -https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fhir-r4-consent-api/[Consent] +| https://anypoint.mulesoft.com/exchange/org.mule.examples/fhir-r4-provenance-library/[Provenance] + +https://anypoint.mulesoft.com/exchange/org.mule.examples/fhir-r4-auditevent-library/[AuditEvent] + +https://anypoint.mulesoft.com/exchange/org.mule.examples/fhir-r4-consent-library/[Consent] +| https://anypoint.mulesoft.com/exchange/org.mule.examples/fhir-r4-provenance-api/[Provenance] + +https://anypoint.mulesoft.com/exchange/org.mule.examples/fhir-r4-auditevent-api/[AuditEvent] + +https://anypoint.mulesoft.com/exchange/org.mule.examples/fhir-r4-consent-api/[Consent] .^| Foundation - Documents -| https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fhir-r4-composition-library/[Composition] + -https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fhir-r4-documentmanifest-library/[DocumentManifest] + -https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fhir-r4-documentreference-library/[DocumentReference] + -https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fhir-r4-catalogentry-library/[CatalogEntry] -| https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fhir-r4-composition-api/[Composition] + -https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fhir-r4-documentmanifest-api/[DocumentManifest] + -https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fhir-r4-documentreference-api/[DocumentReference] + -https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fhir-r4-catalogentry-api/[CatalogEntry] +| https://anypoint.mulesoft.com/exchange/org.mule.examples/fhir-r4-composition-library/[Composition] + +https://anypoint.mulesoft.com/exchange/org.mule.examples/fhir-r4-documentmanifest-library/[DocumentManifest] + +https://anypoint.mulesoft.com/exchange/org.mule.examples/fhir-r4-documentreference-library/[DocumentReference] + +https://anypoint.mulesoft.com/exchange/org.mule.examples/fhir-r4-catalogentry-library/[CatalogEntry] +| https://anypoint.mulesoft.com/exchange/org.mule.examples/fhir-r4-composition-api/[Composition] + +https://anypoint.mulesoft.com/exchange/org.mule.examples/fhir-r4-documentmanifest-api/[DocumentManifest] + +https://anypoint.mulesoft.com/exchange/org.mule.examples/fhir-r4-documentreference-api/[DocumentReference] + +https://anypoint.mulesoft.com/exchange/org.mule.examples/fhir-r4-catalogentry-api/[CatalogEntry] .^| Foundation - Other -| https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fhir-r4-basic-library/[Basic] + -https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fhir-r4-binary-library/[Binary] ^[N]^ + -https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fhir-r4-linkage-library/[Linkage] + -https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fhir-r4-messageheader-library/[MessageHeader] + -https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fhir-r4-parameters-library/[Parameters] ^[N]^ + -https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fhir-r4-subscription-library/[Subscription] + +| https://anypoint.mulesoft.com/exchange/org.mule.examples/fhir-r4-basic-library/[Basic] + +https://anypoint.mulesoft.com/exchange/org.mule.examples/fhir-r4-binary-library/[Binary] ^[N]^ + +https://anypoint.mulesoft.com/exchange/org.mule.examples/fhir-r4-linkage-library/[Linkage] + +https://anypoint.mulesoft.com/exchange/org.mule.examples/fhir-r4-messageheader-library/[MessageHeader] + +https://anypoint.mulesoft.com/exchange/org.mule.examples/fhir-r4-parameters-library/[Parameters] ^[N]^ + +https://anypoint.mulesoft.com/exchange/org.mule.examples/fhir-r4-subscription-library/[Subscription] + ++++++ -| https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fhir-r4-basic-api/[Basic] + -https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fhir-r4-binary-api/[Binary] ^[N]^ + -https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fhir-r4-linkage-api/[Linkage] + -https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fhir-r4-messageheader-api/[MessageHeader] + -https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fhir-r4-parameters-api/[Parameters] ^[N]^ + -https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fhir-r4-subscription-api/[Subscription] +| https://anypoint.mulesoft.com/exchange/org.mule.examples/fhir-r4-basic-api/[Basic] + +https://anypoint.mulesoft.com/exchange/org.mule.examples/fhir-r4-binary-api/[Binary] ^[N]^ + +https://anypoint.mulesoft.com/exchange/org.mule.examples/fhir-r4-linkage-api/[Linkage] + +https://anypoint.mulesoft.com/exchange/org.mule.examples/fhir-r4-messageheader-api/[MessageHeader] + +https://anypoint.mulesoft.com/exchange/org.mule.examples/fhir-r4-parameters-api/[Parameters] ^[N]^ + +https://anypoint.mulesoft.com/exchange/org.mule.examples/fhir-r4-subscription-api/[Subscription] .^| Base - Individuals -| https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fhir-r4-patient-library/[Patient] ^[N]^ + -https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fhir-r4-practitioner-library/[Practitioner] + -https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fhir-r4-practitionerrole-library/[PractitionerRole] + -https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fhir-r4-relatedperson-library/[RelatedPerson] + -https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fhir-r4-person-library/[Person] + -https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fhir-r4-group-library/[Group] + +| https://anypoint.mulesoft.com/exchange/org.mule.examples/fhir-r4-patient-library/[Patient] ^[N]^ + +https://anypoint.mulesoft.com/exchange/org.mule.examples/fhir-r4-practitioner-library/[Practitioner] + +https://anypoint.mulesoft.com/exchange/org.mule.examples/fhir-r4-practitionerrole-library/[PractitionerRole] + +https://anypoint.mulesoft.com/exchange/org.mule.examples/fhir-r4-relatedperson-library/[RelatedPerson] + +https://anypoint.mulesoft.com/exchange/org.mule.examples/fhir-r4-person-library/[Person] + +https://anypoint.mulesoft.com/exchange/org.mule.examples/fhir-r4-group-library/[Group] + ++++++ -| https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fhir-r4-patient-api/[Patient] ^[N]^ + -https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fhir-r4-practitioner-api/[Practitioner] + -https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fhir-r4-practitionerrole-api/[PractitionerRole] + -https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fhir-r4-relatedperson-api/[RelatedPerson] + -https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fhir-r4-person-api/[Person] + -https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fhir-r4-group-api/[Group] +| https://anypoint.mulesoft.com/exchange/org.mule.examples/fhir-r4-patient-api/[Patient] ^[N]^ + +https://anypoint.mulesoft.com/exchange/org.mule.examples/fhir-r4-practitioner-api/[Practitioner] + +https://anypoint.mulesoft.com/exchange/org.mule.examples/fhir-r4-practitionerrole-api/[PractitionerRole] + +https://anypoint.mulesoft.com/exchange/org.mule.examples/fhir-r4-relatedperson-api/[RelatedPerson] + +https://anypoint.mulesoft.com/exchange/org.mule.examples/fhir-r4-person-api/[Person] + +https://anypoint.mulesoft.com/exchange/org.mule.examples/fhir-r4-group-api/[Group] .^| Base - Entities #1 -| https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fhir-r4-organization-library/[Organization] + -https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fhir-r4-organizationaffiliation-library/[OrganizationAffiliation] + -https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fhir-r4-healthcareservice-library/[HealthcareService] + -https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fhir-r4-endpoint-library/[Endpoint] + -https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fhir-r4-location-library/[Location] + +| https://anypoint.mulesoft.com/exchange/org.mule.examples/fhir-r4-organization-library/[Organization] + +https://anypoint.mulesoft.com/exchange/org.mule.examples/fhir-r4-organizationaffiliation-library/[OrganizationAffiliation] + +https://anypoint.mulesoft.com/exchange/org.mule.examples/fhir-r4-healthcareservice-library/[HealthcareService] + +https://anypoint.mulesoft.com/exchange/org.mule.examples/fhir-r4-endpoint-library/[Endpoint] + +https://anypoint.mulesoft.com/exchange/org.mule.examples/fhir-r4-location-library/[Location] + ++++++ -| https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fhir-r4-organization-api/[Organization] + -https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fhir-r4-organizationaffiliation-api/[OrganizationAffiliation] + -https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fhir-r4-healthcareservice-api/[HealthcareService] + -https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fhir-r4-endpoint-api/[Endpoint] + -https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fhir-r4-location-api/[Location] +| https://anypoint.mulesoft.com/exchange/org.mule.examples/fhir-r4-organization-api/[Organization] + +https://anypoint.mulesoft.com/exchange/org.mule.examples/fhir-r4-organizationaffiliation-api/[OrganizationAffiliation] + +https://anypoint.mulesoft.com/exchange/org.mule.examples/fhir-r4-healthcareservice-api/[HealthcareService] + +https://anypoint.mulesoft.com/exchange/org.mule.examples/fhir-r4-endpoint-api/[Endpoint] + +https://anypoint.mulesoft.com/exchange/org.mule.examples/fhir-r4-location-api/[Location] .^| Base - Entities #2 -| https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fhir-r4-substance-library/[Substance] + -https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fhir-r4-biologicallyderivedproduct-library/[BiologicallyDerivedProduct #] + -https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fhir-r4-device-library/[Device] + -https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fhir-r4-devicemetric-library/[DeviceMetric] + +| https://anypoint.mulesoft.com/exchange/org.mule.examples/fhir-r4-substance-library/[Substance] + +https://anypoint.mulesoft.com/exchange/org.mule.examples/fhir-r4-biologicallyderivedproduct-library/[BiologicallyDerivedProduct #] + +https://anypoint.mulesoft.com/exchange/org.mule.examples/fhir-r4-device-library/[Device] + +https://anypoint.mulesoft.com/exchange/org.mule.examples/fhir-r4-devicemetric-library/[DeviceMetric] + ++++++ -| https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fhir-r4-substance-api/[Substance] + -https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fhir-r4-biologicallyderivedproduct-api/[BiologicallyDerivedProduct #] + -https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fhir-r4-device-api/[Device] + -https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fhir-r4-devicemetric-api/[DeviceMetric] +| https://anypoint.mulesoft.com/exchange/org.mule.examples/fhir-r4-substance-api/[Substance] + +https://anypoint.mulesoft.com/exchange/org.mule.examples/fhir-r4-biologicallyderivedproduct-api/[BiologicallyDerivedProduct #] + +https://anypoint.mulesoft.com/exchange/org.mule.examples/fhir-r4-device-api/[Device] + +https://anypoint.mulesoft.com/exchange/org.mule.examples/fhir-r4-devicemetric-api/[DeviceMetric] .^| Base - Workflow -| https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fhir-r4-task-library/[Task] + -https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fhir-r4-appointment-library/[Appointment] + -https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fhir-r4-appointmentresponse-library/[AppointmentResponse] + -https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fhir-r4-schedule-library/[Schedule] + -https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fhir-r4-slot-library/[Slot] + -https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fhir-r4-verificationresult-library/[VerificationResult] -| https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fhir-r4-task-api/[Task] + -https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fhir-r4-appointment-api/[Appointment] + -https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fhir-r4-appointmentresponse-api/[AppointmentResponse] + -https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fhir-r4-schedule-api/[Schedule] + -https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fhir-r4-slot-api/[Slot] + -https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fhir-r4-verificationresult-api/[VerificationResult] +| https://anypoint.mulesoft.com/exchange/org.mule.examples/fhir-r4-task-library/[Task] + +https://anypoint.mulesoft.com/exchange/org.mule.examples/fhir-r4-appointment-library/[Appointment] + +https://anypoint.mulesoft.com/exchange/org.mule.examples/fhir-r4-appointmentresponse-library/[AppointmentResponse] + +https://anypoint.mulesoft.com/exchange/org.mule.examples/fhir-r4-schedule-library/[Schedule] + +https://anypoint.mulesoft.com/exchange/org.mule.examples/fhir-r4-slot-library/[Slot] + +https://anypoint.mulesoft.com/exchange/org.mule.examples/fhir-r4-verificationresult-library/[VerificationResult] +| https://anypoint.mulesoft.com/exchange/org.mule.examples/fhir-r4-task-api/[Task] + +https://anypoint.mulesoft.com/exchange/org.mule.examples/fhir-r4-appointment-api/[Appointment] + +https://anypoint.mulesoft.com/exchange/org.mule.examples/fhir-r4-appointmentresponse-api/[AppointmentResponse] + +https://anypoint.mulesoft.com/exchange/org.mule.examples/fhir-r4-schedule-api/[Schedule] + +https://anypoint.mulesoft.com/exchange/org.mule.examples/fhir-r4-slot-api/[Slot] + +https://anypoint.mulesoft.com/exchange/org.mule.examples/fhir-r4-verificationresult-api/[VerificationResult] .^| Base - Management -| https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fhir-r4-encounter-library/[Encounter] + -https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fhir-r4-episodeofcare-library/[EpisodeOfCare] + -https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fhir-r4-flag-library/[Flag] + -https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fhir-r4-list-library/[List] + -https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fhir-r4-library-library/[Library] -| https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fhir-r4-encounter-api/[Encounter] + -https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fhir-r4-episodeofcare-api/[EpisodeOfCare] + -https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fhir-r4-flag-api/[Flag] + -https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fhir-r4-list-api/[List] + -https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fhir-r4-library-api/[Library] +| https://anypoint.mulesoft.com/exchange/org.mule.examples/fhir-r4-encounter-library/[Encounter] + +https://anypoint.mulesoft.com/exchange/org.mule.examples/fhir-r4-episodeofcare-library/[EpisodeOfCare] + +https://anypoint.mulesoft.com/exchange/org.mule.examples/fhir-r4-flag-library/[Flag] + +https://anypoint.mulesoft.com/exchange/org.mule.examples/fhir-r4-list-library/[List] + +https://anypoint.mulesoft.com/exchange/org.mule.examples/fhir-r4-library-library/[Library] +| https://anypoint.mulesoft.com/exchange/org.mule.examples/fhir-r4-encounter-api/[Encounter] + +https://anypoint.mulesoft.com/exchange/org.mule.examples/fhir-r4-episodeofcare-api/[EpisodeOfCare] + +https://anypoint.mulesoft.com/exchange/org.mule.examples/fhir-r4-flag-api/[Flag] + +https://anypoint.mulesoft.com/exchange/org.mule.examples/fhir-r4-list-api/[List] + +https://anypoint.mulesoft.com/exchange/org.mule.examples/fhir-r4-library-api/[Library] .^| Clinical - Summary -| https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fhir-r4-allergyintolerance-library/[AllergyIntolerance] + -https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fhir-r4-adverseevent-library/[AdverseEvent] + -https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fhir-r4-condition-library/[Condition(Problem)] + -https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fhir-r4-procedure-library/[Procedure] + -https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fhir-r4-familymemberhistory-library/[FamilyMemberHistory] + -https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fhir-r4-clinicalimpression-library/[ClinicalImpression #] + -https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fhir-r4-clinicalimpression-library/[Note] + -https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fhir-r4-detectedissue-library/[DetectedIssue] -| https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fhir-r4-allergyintolerance-api/[AllergyIntolerance] + -https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fhir-r4-adverseevent-api/[AdverseEvent] + -https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fhir-r4-condition-api/[Condition(Problem)] + -https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fhir-r4-procedure-api/[Procedure] + -https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fhir-r4-familymemberhistory-api/[FamilyMemberHistory] + -https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fhir-r4-clinicalimpression-api/[ClinicalImpression #] + -https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fhir-r4-clinicalimpression-api/[Note] + -https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fhir-r4-detectedissue-api/[DetectedIssue] +| https://anypoint.mulesoft.com/exchange/org.mule.examples/fhir-r4-allergyintolerance-library/[AllergyIntolerance] + +https://anypoint.mulesoft.com/exchange/org.mule.examples/fhir-r4-adverseevent-library/[AdverseEvent] + +https://anypoint.mulesoft.com/exchange/org.mule.examples/fhir-r4-condition-library/[Condition(Problem)] + +https://anypoint.mulesoft.com/exchange/org.mule.examples/fhir-r4-procedure-library/[Procedure] + +https://anypoint.mulesoft.com/exchange/org.mule.examples/fhir-r4-familymemberhistory-library/[FamilyMemberHistory] + +https://anypoint.mulesoft.com/exchange/org.mule.examples/fhir-r4-clinicalimpression-library/[ClinicalImpression #] + +https://anypoint.mulesoft.com/exchange/org.mule.examples/fhir-r4-clinicalimpression-library/[Note] + +https://anypoint.mulesoft.com/exchange/org.mule.examples/fhir-r4-detectedissue-library/[DetectedIssue] +| https://anypoint.mulesoft.com/exchange/org.mule.examples/fhir-r4-allergyintolerance-api/[AllergyIntolerance] + +https://anypoint.mulesoft.com/exchange/org.mule.examples/fhir-r4-adverseevent-api/[AdverseEvent] + +https://anypoint.mulesoft.com/exchange/org.mule.examples/fhir-r4-condition-api/[Condition(Problem)] + +https://anypoint.mulesoft.com/exchange/org.mule.examples/fhir-r4-procedure-api/[Procedure] + +https://anypoint.mulesoft.com/exchange/org.mule.examples/fhir-r4-familymemberhistory-api/[FamilyMemberHistory] + +https://anypoint.mulesoft.com/exchange/org.mule.examples/fhir-r4-clinicalimpression-api/[ClinicalImpression #] + +https://anypoint.mulesoft.com/exchange/org.mule.examples/fhir-r4-clinicalimpression-api/[Note] + +https://anypoint.mulesoft.com/exchange/org.mule.examples/fhir-r4-detectedissue-api/[DetectedIssue] .^| Clinical - Diagnostics -| https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fhir-r4-observation-library/[Observation] ^[N]^ + -https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fhir-r4-media-library/[Media] ^[u]^ + -https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fhir-r4-diagnosticreport-library/[DiagnosticReport] + -https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fhir-r4-specimen-library/[Specimen] + -https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fhir-r4-bodystructure-library/[BodyStructure] + -https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fhir-r4-imagingstudy-library/[ImagingStudy] + -https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fhir-r4-questionnaireresponse-library/[QuestionnaireResponse ] + -https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fhir-r4-molecularsequence-library/[MolecularSequence] -| https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fhir-r4-observation-api/[Observation] ^[N]^ + -https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fhir-r4-media-api/[Media] ^[u]^ + -https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fhir-r4-diagnosticreport-api/[DiagnosticReport] + -https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fhir-r4-specimen-api/[Specimen] + -https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fhir-r4-bodystructure-api/[BodyStructure] + -https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fhir-r4-imagingstudy-api/[ImagingStudy] + -https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fhir-r4-questionnaireresponse-api/[QuestionnaireResponse ] + -https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fhir-r4-molecularsequence-api/[MolecularSequence] +| https://anypoint.mulesoft.com/exchange/org.mule.examples/fhir-r4-observation-library/[Observation] ^[N]^ + +https://anypoint.mulesoft.com/exchange/org.mule.examples/fhir-r4-media-library/[Media] ^[u]^ + +https://anypoint.mulesoft.com/exchange/org.mule.examples/fhir-r4-diagnosticreport-library/[DiagnosticReport] + +https://anypoint.mulesoft.com/exchange/org.mule.examples/fhir-r4-specimen-library/[Specimen] + +https://anypoint.mulesoft.com/exchange/org.mule.examples/fhir-r4-bodystructure-library/[BodyStructure] + +https://anypoint.mulesoft.com/exchange/org.mule.examples/fhir-r4-imagingstudy-library/[ImagingStudy] + +https://anypoint.mulesoft.com/exchange/org.mule.examples/fhir-r4-questionnaireresponse-library/[QuestionnaireResponse ] + +https://anypoint.mulesoft.com/exchange/org.mule.examples/fhir-r4-molecularsequence-library/[MolecularSequence] +| https://anypoint.mulesoft.com/exchange/org.mule.examples/fhir-r4-observation-api/[Observation] ^[N]^ + +https://anypoint.mulesoft.com/exchange/org.mule.examples/fhir-r4-media-api/[Media] ^[u]^ + +https://anypoint.mulesoft.com/exchange/org.mule.examples/fhir-r4-diagnosticreport-api/[DiagnosticReport] + +https://anypoint.mulesoft.com/exchange/org.mule.examples/fhir-r4-specimen-api/[Specimen] + +https://anypoint.mulesoft.com/exchange/org.mule.examples/fhir-r4-bodystructure-api/[BodyStructure] + +https://anypoint.mulesoft.com/exchange/org.mule.examples/fhir-r4-imagingstudy-api/[ImagingStudy] + +https://anypoint.mulesoft.com/exchange/org.mule.examples/fhir-r4-questionnaireresponse-api/[QuestionnaireResponse ] + +https://anypoint.mulesoft.com/exchange/org.mule.examples/fhir-r4-molecularsequence-api/[MolecularSequence] .^| Clinical - Medications -| https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fhir-r4-medicationrequest-library/[MedicationRequest] + -https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fhir-r4-medicationadministration-library/[MedicationAdministration] + -https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fhir-r4-medicationdispense-library/[MedicationDispense] + -https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fhir-r4-medicationstatement-library/[MedicationStatement] + -https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fhir-r4-medication-library/[Medication] + -https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fhir-r4-medicationknowledge-library/[MedicationKnowledge] + -https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fhir-r4-immunization-library/[Immunization] + -https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fhir-r4-immunizationevaluation-library/[ImmunizationEvaluation] + -https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fhir-r4-immunizationrecommendation-library/[ImmunizationRecommendation] -| https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fhir-r4-medicationrequest-api/[MedicationRequest] + -https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fhir-r4-medicationadministration-api/[MedicationAdministration] + -https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fhir-r4-medicationdispense-api/[MedicationDispense] + -https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fhir-r4-medicationstatement-api/[MedicationStatement] + -https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fhir-r4-medication-api/[Medication] + -https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fhir-r4-medicationknowledge-api/[MedicationKnowledge] + -https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fhir-r4-immunization-api/[Immunization] + -https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fhir-r4-immunizationevaluation-api/[ImmunizationEvaluation] + -https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fhir-r4-immunizationrecommendation-api/[ImmunizationRecommendation] +| https://anypoint.mulesoft.com/exchange/org.mule.examples/fhir-r4-medicationrequest-library/[MedicationRequest] + +https://anypoint.mulesoft.com/exchange/org.mule.examples/fhir-r4-medicationadministration-library/[MedicationAdministration] + +https://anypoint.mulesoft.com/exchange/org.mule.examples/fhir-r4-medicationdispense-library/[MedicationDispense] + +https://anypoint.mulesoft.com/exchange/org.mule.examples/fhir-r4-medicationstatement-library/[MedicationStatement] + +https://anypoint.mulesoft.com/exchange/org.mule.examples/fhir-r4-medication-library/[Medication] + +https://anypoint.mulesoft.com/exchange/org.mule.examples/fhir-r4-medicationknowledge-library/[MedicationKnowledge] + +https://anypoint.mulesoft.com/exchange/org.mule.examples/fhir-r4-immunization-library/[Immunization] + +https://anypoint.mulesoft.com/exchange/org.mule.examples/fhir-r4-immunizationevaluation-library/[ImmunizationEvaluation] + +https://anypoint.mulesoft.com/exchange/org.mule.examples/fhir-r4-immunizationrecommendation-library/[ImmunizationRecommendation] +| https://anypoint.mulesoft.com/exchange/org.mule.examples/fhir-r4-medicationrequest-api/[MedicationRequest] + +https://anypoint.mulesoft.com/exchange/org.mule.examples/fhir-r4-medicationadministration-api/[MedicationAdministration] + +https://anypoint.mulesoft.com/exchange/org.mule.examples/fhir-r4-medicationdispense-api/[MedicationDispense] + +https://anypoint.mulesoft.com/exchange/org.mule.examples/fhir-r4-medicationstatement-api/[MedicationStatement] + +https://anypoint.mulesoft.com/exchange/org.mule.examples/fhir-r4-medication-api/[Medication] + +https://anypoint.mulesoft.com/exchange/org.mule.examples/fhir-r4-medicationknowledge-api/[MedicationKnowledge] + +https://anypoint.mulesoft.com/exchange/org.mule.examples/fhir-r4-immunization-api/[Immunization] + +https://anypoint.mulesoft.com/exchange/org.mule.examples/fhir-r4-immunizationevaluation-api/[ImmunizationEvaluation] + +https://anypoint.mulesoft.com/exchange/org.mule.examples/fhir-r4-immunizationrecommendation-api/[ImmunizationRecommendation] .^| Clinical - Care Provision -| https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fhir-r4-careplan-library/[CarePlan] + -https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fhir-r4-careteam-library/[CareTeam] + -https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fhir-r4-goal-library/[Goal] + -https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fhir-r4-servicerequest-library/[ServiceRequest] + -https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fhir-r4-nutritionorder-library/[NutritionOrder] + -https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fhir-r4-visionprescription-library/[VisionPrescription] + -https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fhir-r4-riskassessment-library/[RiskAssessment] + -https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fhir-r4-requestgroup-library/[RequestGroup] -| https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fhir-r4-careplan-api/[CarePlan] + -https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fhir-r4-careteam-api/[CareTeam] + -https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fhir-r4-goal-api/[Goal] + -https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fhir-r4-servicerequest-api/[ServiceRequest] + -https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fhir-r4-nutritionorder-api/[NutritionOrder] + -https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fhir-r4-visionprescription-api/[VisionPrescription] + -https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fhir-r4-riskassessment-api/[RiskAssessment] + -https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fhir-r4-requestgroup-api/[RequestGroup] +| https://anypoint.mulesoft.com/exchange/org.mule.examples/fhir-r4-careplan-library/[CarePlan] + +https://anypoint.mulesoft.com/exchange/org.mule.examples/fhir-r4-careteam-library/[CareTeam] + +https://anypoint.mulesoft.com/exchange/org.mule.examples/fhir-r4-goal-library/[Goal] + +https://anypoint.mulesoft.com/exchange/org.mule.examples/fhir-r4-servicerequest-library/[ServiceRequest] + +https://anypoint.mulesoft.com/exchange/org.mule.examples/fhir-r4-nutritionorder-library/[NutritionOrder] + +https://anypoint.mulesoft.com/exchange/org.mule.examples/fhir-r4-visionprescription-library/[VisionPrescription] + +https://anypoint.mulesoft.com/exchange/org.mule.examples/fhir-r4-riskassessment-library/[RiskAssessment] + +https://anypoint.mulesoft.com/exchange/org.mule.examples/fhir-r4-requestgroup-library/[RequestGroup] +| https://anypoint.mulesoft.com/exchange/org.mule.examples/fhir-r4-careplan-api/[CarePlan] + +https://anypoint.mulesoft.com/exchange/org.mule.examples/fhir-r4-careteam-api/[CareTeam] + +https://anypoint.mulesoft.com/exchange/org.mule.examples/fhir-r4-goal-api/[Goal] + +https://anypoint.mulesoft.com/exchange/org.mule.examples/fhir-r4-servicerequest-api/[ServiceRequest] + +https://anypoint.mulesoft.com/exchange/org.mule.examples/fhir-r4-nutritionorder-api/[NutritionOrder] + +https://anypoint.mulesoft.com/exchange/org.mule.examples/fhir-r4-visionprescription-api/[VisionPrescription] + +https://anypoint.mulesoft.com/exchange/org.mule.examples/fhir-r4-riskassessment-api/[RiskAssessment] + +https://anypoint.mulesoft.com/exchange/org.mule.examples/fhir-r4-requestgroup-api/[RequestGroup] .^| Clinical - Request & Response -| https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fhir-r4-communication-library/[Communication] + -https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fhir-r4-communicationrequest-library/[CommunicationRequest] + -https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fhir-r4-devicerequest-library/[DeviceRequest #] + -https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fhir-r4-deviceusestatement-library/[DeviceUseStatement] ^[u]^ + -https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fhir-r4-guidanceresponse-library/[GuidanceResponse] + -https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fhir-r4-supplyrequest-library/[SupplyRequest #] + -https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fhir-r4-supplydelivery-library/[SupplyDelivery] -| https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fhir-r4-communication-api/[Communication] + -https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fhir-r4-communicationrequest-api/[CommunicationRequest] + -https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fhir-r4-devicerequest-api/[DeviceRequest #] + -https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fhir-r4-deviceusestatement-api/[DeviceUseStatement] ^[u]^ + -https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fhir-r4-guidanceresponse-api/[GuidanceResponse] + -https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fhir-r4-supplyrequest-api/[SupplyRequest #] + -https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fhir-r4-supplydelivery-api/[SupplyDelivery] +| https://anypoint.mulesoft.com/exchange/org.mule.examples/fhir-r4-communication-library/[Communication] + +https://anypoint.mulesoft.com/exchange/org.mule.examples/fhir-r4-communicationrequest-library/[CommunicationRequest] + +https://anypoint.mulesoft.com/exchange/org.mule.examples/fhir-r4-devicerequest-library/[DeviceRequest #] + +https://anypoint.mulesoft.com/exchange/org.mule.examples/fhir-r4-deviceusestatement-library/[DeviceUseStatement] ^[u]^ + +https://anypoint.mulesoft.com/exchange/org.mule.examples/fhir-r4-guidanceresponse-library/[GuidanceResponse] + +https://anypoint.mulesoft.com/exchange/org.mule.examples/fhir-r4-supplyrequest-library/[SupplyRequest #] + +https://anypoint.mulesoft.com/exchange/org.mule.examples/fhir-r4-supplydelivery-library/[SupplyDelivery] +| https://anypoint.mulesoft.com/exchange/org.mule.examples/fhir-r4-communication-api/[Communication] + +https://anypoint.mulesoft.com/exchange/org.mule.examples/fhir-r4-communicationrequest-api/[CommunicationRequest] + +https://anypoint.mulesoft.com/exchange/org.mule.examples/fhir-r4-devicerequest-api/[DeviceRequest #] + +https://anypoint.mulesoft.com/exchange/org.mule.examples/fhir-r4-deviceusestatement-api/[DeviceUseStatement] ^[u]^ + +https://anypoint.mulesoft.com/exchange/org.mule.examples/fhir-r4-guidanceresponse-api/[GuidanceResponse] + +https://anypoint.mulesoft.com/exchange/org.mule.examples/fhir-r4-supplyrequest-api/[SupplyRequest #] + +https://anypoint.mulesoft.com/exchange/org.mule.examples/fhir-r4-supplydelivery-api/[SupplyDelivery] .^| Financial - Support -| https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fhir-r4-coverage-library/[Coverage] + -https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fhir-r4-coverageeligibilityrequest-library/[CoverageEligibilityRequest] + -https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fhir-r4-coverageeligibilityresponse-library/[CoverageEligibilityResponse] + -https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fhir-r4-enrollmentrequest-library/[EnrollmentRequest] ^[u]^ + -https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fhir-r4-enrollmentresponse-library/[EnrollmentResponse] ^[u]^ -| https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fhir-r4-coverage-api/[Coverage] + -https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fhir-r4-coverageeligibilityrequest-api/[CoverageEligibilityRequest] + -https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fhir-r4-coverageeligibilityresponse-api/[CoverageEligibilityResponse] + -https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fhir-r4-enrollmentrequest-api/[EnrollmentRequest] ^[u]^ + -https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fhir-r4-enrollmentresponse-api/[EnrollmentResponse] ^[u]^ +| https://anypoint.mulesoft.com/exchange/org.mule.examples/fhir-r4-coverage-library/[Coverage] + +https://anypoint.mulesoft.com/exchange/org.mule.examples/fhir-r4-coverageeligibilityrequest-library/[CoverageEligibilityRequest] + +https://anypoint.mulesoft.com/exchange/org.mule.examples/fhir-r4-coverageeligibilityresponse-library/[CoverageEligibilityResponse] + +https://anypoint.mulesoft.com/exchange/org.mule.examples/fhir-r4-enrollmentrequest-library/[EnrollmentRequest] ^[u]^ + +https://anypoint.mulesoft.com/exchange/org.mule.examples/fhir-r4-enrollmentresponse-library/[EnrollmentResponse] ^[u]^ +| https://anypoint.mulesoft.com/exchange/org.mule.examples/fhir-r4-coverage-api/[Coverage] + +https://anypoint.mulesoft.com/exchange/org.mule.examples/fhir-r4-coverageeligibilityrequest-api/[CoverageEligibilityRequest] + +https://anypoint.mulesoft.com/exchange/org.mule.examples/fhir-r4-coverageeligibilityresponse-api/[CoverageEligibilityResponse] + +https://anypoint.mulesoft.com/exchange/org.mule.examples/fhir-r4-enrollmentrequest-api/[EnrollmentRequest] ^[u]^ + +https://anypoint.mulesoft.com/exchange/org.mule.examples/fhir-r4-enrollmentresponse-api/[EnrollmentResponse] ^[u]^ .^| Financial - Billing -| https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fhir-r4-claim-library/[Claim] + -https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fhir-r4-claimresponse-library/[ClaimResponse] + -https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fhir-r4-invoice-library/[Invoice] -| https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fhir-r4-claim-api/[Claim] + -https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fhir-r4-claimresponse-api/[ClaimResponse] + -https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fhir-r4-invoice-api/[Invoice] - -.^| Financial - Payment | https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fhir-r4-paymentnotice-library/[PaymentNotice] + -https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fhir-r4-paymentreconciliation-library/[PaymentReconcilliation] -| https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fhir-r4-paymentnotice-api/[PaymentNotice] + -https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fhir-r4-paymentreconciliation-api/[PaymentReconcilliation] - -.^| Financial - General | https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fhir-r4-account-library/[Account] + -https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fhir-r4-chargeitem-library/[ChargeItem] + -https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fhir-r4-chargeitemdefinition-library/[ChargeItemDefinition] + -https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fhir-r4-contract-library/[Contract] + -https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fhir-r4-explanationofbenefit-library/[ExplanationOfBenefit] + -https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fhir-r4-insuranceplan-library/[InsurancePlan] -| https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fhir-r4-account-api/[Account] + -https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fhir-r4-chargeitem-api/[ChargeItem] + -https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fhir-r4-chargeitemdefinition-api/[ChargeItemDefinition] + -https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fhir-r4-contract-api/[Contract] + -https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fhir-r4-explanationofbenefit-api/[ExplanationOfBenefit] + -https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fhir-r4-insuranceplan-api/[InsurancePlan] - -.^| Specialized - Public Health & Research | https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fhir-r4-researchstudy-library/[ResearchStudy] + -https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fhir-r4-researchsubject-library/[ResearchSubject] -| https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fhir-r4-researchstudy-api/[ResearchStudy] + -https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fhir-r4-researchsubject-api/[ResearchSubject] - -.^| Specialized - Definitional Artifacts | https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fhir-r4-activitydefinition-library/[ActivityDefinition] + -https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fhir-r4-devicedefinition-library/[DeviceDefinition] + -https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fhir-r4-eventdefinition-library/[EventDefinition] + -https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fhir-r4-observationdefinition-library/[ObservationDefinition] ^[u]^ + -https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fhir-r4-plandefinition-library/[PlanDefinition] + -https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fhir-r4-questionnaire-library/[Questionnaire] + -https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fhir-r4-specimendefinition-library/[SpecimenDefinition] -| https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fhir-r4-activitydefinition-api/[ActivityDefinition] + -https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fhir-r4-devicedefinition-api/[DeviceDefinition] + -https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fhir-r4-eventdefinition-api/[EventDefinition] + -https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fhir-r4-observationdefinition-api/[ObservationDefinition] ^[u]^ + -https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fhir-r4-plandefinition-api/[PlanDefinition] + -https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fhir-r4-questionnaire-api/[Questionnaire] + -https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fhir-r4-specimendefinition-api/[SpecimenDefinition] - -.^| Specialized - Evidence Based Medicine | https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fhir-r4-researchdefinition-library/[ResearchDefinition] + -https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fhir-r4-researchelementdefinition-library/[ResearchElementDefinition] + -https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fhir-r4-evidence-library/[Evidence] + -https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fhir-r4-evidencevariable-library/[EvidenceVariable] + -https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fhir-r4-effectevidencesynthesis-library/[EffectEvidenceSynthesis] + -https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fhir-r4-riskevidencesynthesis-library/[RiskEvidenceSynthesis] -| https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fhir-r4-researchdefinition-api/[ResearchDefinition] + -https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fhir-r4-researchelementdefinition-api/[ResearchElementDefinition] + -https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fhir-r4-evidence-api/[Evidence] + -https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fhir-r4-evidencevariable-api/[EvidenceVariable] + -https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fhir-r4-effectevidencesynthesis-api/[EffectEvidenceSynthesis] + -https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fhir-r4-riskevidencesynthesis-api/[RiskEvidenceSynthesis] - -.^| Specialized - Quality Reporting & Testing | https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fhir-r4-measure-library/[Measure] + -https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fhir-r4-measurereport-library/[MeasureReport] + -https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fhir-r4-testscript-library/[TestScript] + -https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fhir-r4-testreport-library/[TestReport] -| https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fhir-r4-measure-api/[Measure] + -https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fhir-r4-measurereport-api/[MeasureReport] + -https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fhir-r4-testscript-api/[TestScript] + -https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fhir-r4-testreport-api/[TestReport] - -.^| Specialized - Medication Definition | https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fhir-r4-medicinalproduct-library/[MedicinalProduct] ^[u]^ + -https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fhir-r4-medicinalproductauthorization-library/[MedicinalProductAuthorization] ^[u]^ + -https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fhir-r4-medicinalproductcontraindication-library/[MedicinalProductContraindication] + -https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fhir-r4-medicinalproductindication-library/[MedicinalProductIndication] + -https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fhir-r4-medicinalproductingredient-library/[MedicinalProductIngredient] ^[u]^ + -https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fhir-r4-medicinalproductinteraction-library/[MedicinalProductInteraction] + -https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fhir-r4-medicinalproductmanufactured-library/[MedicinalProductManufactured] + -https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fhir-r4-medicinalproductpackaged-library/[MedicinalProductPackaged] ^[u]^ + -https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fhir-r4-medicinalproductpharmaceutical-library/[MedicinalProductPharmaceutical] ^[u]^ + -https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fhir-r4-medicinalproductundesirableeffect-library/[MedicinalProductUndesirableEffect] + -https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fhir-r4-substancenucleicacid-library/[SubstanceNucleicAcid] + -https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fhir-r4-substancepolymer-library/[SubstancePolymer] ^[u]^ + -https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fhir-r4-substanceprotein-library/[SubstanceProtein] + -https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fhir-r4-substancereferenceinformation-library/[SubstanceReferenceInformation] ^[u]^ + -https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fhir-r4-substancespecification-library/[SubstanceSpecification] ^[u]^ + -https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fhir-r4-substancesourcematerial-library/[SubstanceSourceMaterial] -| https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fhir-r4-medicinalproduct-api/[MedicinalProduct] ^[u]^ + -https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fhir-r4-medicinalproductauthorization-api/[MedicinalProductAuthorization] ^[u]^ + -https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fhir-r4-medicinalproductcontraindication-api/[MedicinalProductContraindication] + -https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fhir-r4-medicinalproductindication-api/[MedicinalProductIndication] + -https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fhir-r4-medicinalproductingredient-api/[MedicinalProductIngredient] ^[u]^ + -https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fhir-r4-medicinalproductinteraction-api/[MedicinalProductInteraction] + -https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fhir-r4-medicinalproductmanufactured-api/[MedicinalProductManufactured] + -https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fhir-r4-medicinalproductpackaged-api/[MedicinalProductPackaged] ^[u]^ + -https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fhir-r4-medicinalproductpharmaceutical-api/[MedicinalProductPharmaceutical] ^[u]^ + -https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fhir-r4-medicinalproductundesirableeffect-api/[MedicinalProductUndesirableEffect] + -https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fhir-r4-substancenucleicacid-api/[SubstanceNucleicAcid] + -https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fhir-r4-substancepolymer-api/[SubstancePolymer] ^[u]^ + -https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fhir-r4-substanceprotein-api/[SubstanceProtein] + -https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fhir-r4-substancereferenceinformation-api/[SubstanceReferenceInformation] ^[u]^ + -https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fhir-r4-substancespecification-api/[SubstanceSpecification] ^[u]^ + -https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fhir-r4-substancesourcematerial-api/[SubstanceSourceMaterial] +| https://anypoint.mulesoft.com/exchange/org.mule.examples/fhir-r4-claim-library/[Claim] + +https://anypoint.mulesoft.com/exchange/org.mule.examples/fhir-r4-claimresponse-library/[ClaimResponse] + +https://anypoint.mulesoft.com/exchange/org.mule.examples/fhir-r4-invoice-library/[Invoice] +| https://anypoint.mulesoft.com/exchange/org.mule.examples/fhir-r4-claim-api/[Claim] + +https://anypoint.mulesoft.com/exchange/org.mule.examples/fhir-r4-claimresponse-api/[ClaimResponse] + +https://anypoint.mulesoft.com/exchange/org.mule.examples/fhir-r4-invoice-api/[Invoice] + +.^| Financial - Payment | https://anypoint.mulesoft.com/exchange/org.mule.examples/fhir-r4-paymentnotice-library/[PaymentNotice] + +https://anypoint.mulesoft.com/exchange/org.mule.examples/fhir-r4-paymentreconciliation-library/[PaymentReconcilliation] +| https://anypoint.mulesoft.com/exchange/org.mule.examples/fhir-r4-paymentnotice-api/[PaymentNotice] + +https://anypoint.mulesoft.com/exchange/org.mule.examples/fhir-r4-paymentreconciliation-api/[PaymentReconcilliation] + +.^| Financial - General | https://anypoint.mulesoft.com/exchange/org.mule.examples/fhir-r4-account-library/[Account] + +https://anypoint.mulesoft.com/exchange/org.mule.examples/fhir-r4-chargeitem-library/[ChargeItem] + +https://anypoint.mulesoft.com/exchange/org.mule.examples/fhir-r4-chargeitemdefinition-library/[ChargeItemDefinition] + +https://anypoint.mulesoft.com/exchange/org.mule.examples/fhir-r4-contract-library/[Contract] + +https://anypoint.mulesoft.com/exchange/org.mule.examples/fhir-r4-explanationofbenefit-library/[ExplanationOfBenefit] + +https://anypoint.mulesoft.com/exchange/org.mule.examples/fhir-r4-insuranceplan-library/[InsurancePlan] +| https://anypoint.mulesoft.com/exchange/org.mule.examples/fhir-r4-account-api/[Account] + +https://anypoint.mulesoft.com/exchange/org.mule.examples/fhir-r4-chargeitem-api/[ChargeItem] + +https://anypoint.mulesoft.com/exchange/org.mule.examples/fhir-r4-chargeitemdefinition-api/[ChargeItemDefinition] + +https://anypoint.mulesoft.com/exchange/org.mule.examples/fhir-r4-contract-api/[Contract] + +https://anypoint.mulesoft.com/exchange/org.mule.examples/fhir-r4-explanationofbenefit-api/[ExplanationOfBenefit] + +https://anypoint.mulesoft.com/exchange/org.mule.examples/fhir-r4-insuranceplan-api/[InsurancePlan] + +.^| Specialized - Public Health & Research | https://anypoint.mulesoft.com/exchange/org.mule.examples/fhir-r4-researchstudy-library/[ResearchStudy] + +https://anypoint.mulesoft.com/exchange/org.mule.examples/fhir-r4-researchsubject-library/[ResearchSubject] +| https://anypoint.mulesoft.com/exchange/org.mule.examples/fhir-r4-researchstudy-api/[ResearchStudy] + +https://anypoint.mulesoft.com/exchange/org.mule.examples/fhir-r4-researchsubject-api/[ResearchSubject] + +.^| Specialized - Definitional Artifacts | https://anypoint.mulesoft.com/exchange/org.mule.examples/fhir-r4-activitydefinition-library/[ActivityDefinition] + +https://anypoint.mulesoft.com/exchange/org.mule.examples/fhir-r4-devicedefinition-library/[DeviceDefinition] + +https://anypoint.mulesoft.com/exchange/org.mule.examples/fhir-r4-eventdefinition-library/[EventDefinition] + +https://anypoint.mulesoft.com/exchange/org.mule.examples/fhir-r4-observationdefinition-library/[ObservationDefinition] ^[u]^ + +https://anypoint.mulesoft.com/exchange/org.mule.examples/fhir-r4-plandefinition-library/[PlanDefinition] + +https://anypoint.mulesoft.com/exchange/org.mule.examples/fhir-r4-questionnaire-library/[Questionnaire] + +https://anypoint.mulesoft.com/exchange/org.mule.examples/fhir-r4-specimendefinition-library/[SpecimenDefinition] +| https://anypoint.mulesoft.com/exchange/org.mule.examples/fhir-r4-activitydefinition-api/[ActivityDefinition] + +https://anypoint.mulesoft.com/exchange/org.mule.examples/fhir-r4-devicedefinition-api/[DeviceDefinition] + +https://anypoint.mulesoft.com/exchange/org.mule.examples/fhir-r4-eventdefinition-api/[EventDefinition] + +https://anypoint.mulesoft.com/exchange/org.mule.examples/fhir-r4-observationdefinition-api/[ObservationDefinition] ^[u]^ + +https://anypoint.mulesoft.com/exchange/org.mule.examples/fhir-r4-plandefinition-api/[PlanDefinition] + +https://anypoint.mulesoft.com/exchange/org.mule.examples/fhir-r4-questionnaire-api/[Questionnaire] + +https://anypoint.mulesoft.com/exchange/org.mule.examples/fhir-r4-specimendefinition-api/[SpecimenDefinition] + +.^| Specialized - Evidence Based Medicine | https://anypoint.mulesoft.com/exchange/org.mule.examples/fhir-r4-researchdefinition-library/[ResearchDefinition] + +https://anypoint.mulesoft.com/exchange/org.mule.examples/fhir-r4-researchelementdefinition-library/[ResearchElementDefinition] + +https://anypoint.mulesoft.com/exchange/org.mule.examples/fhir-r4-evidence-library/[Evidence] + +https://anypoint.mulesoft.com/exchange/org.mule.examples/fhir-r4-evidencevariable-library/[EvidenceVariable] + +https://anypoint.mulesoft.com/exchange/org.mule.examples/fhir-r4-effectevidencesynthesis-library/[EffectEvidenceSynthesis] + +https://anypoint.mulesoft.com/exchange/org.mule.examples/fhir-r4-riskevidencesynthesis-library/[RiskEvidenceSynthesis] +| https://anypoint.mulesoft.com/exchange/org.mule.examples/fhir-r4-researchdefinition-api/[ResearchDefinition] + +https://anypoint.mulesoft.com/exchange/org.mule.examples/fhir-r4-researchelementdefinition-api/[ResearchElementDefinition] + +https://anypoint.mulesoft.com/exchange/org.mule.examples/fhir-r4-evidence-api/[Evidence] + +https://anypoint.mulesoft.com/exchange/org.mule.examples/fhir-r4-evidencevariable-api/[EvidenceVariable] + +https://anypoint.mulesoft.com/exchange/org.mule.examples/fhir-r4-effectevidencesynthesis-api/[EffectEvidenceSynthesis] + +https://anypoint.mulesoft.com/exchange/org.mule.examples/fhir-r4-riskevidencesynthesis-api/[RiskEvidenceSynthesis] + +.^| Specialized - Quality Reporting & Testing | https://anypoint.mulesoft.com/exchange/org.mule.examples/fhir-r4-measure-library/[Measure] + +https://anypoint.mulesoft.com/exchange/org.mule.examples/fhir-r4-measurereport-library/[MeasureReport] + +https://anypoint.mulesoft.com/exchange/org.mule.examples/fhir-r4-testscript-library/[TestScript] + +https://anypoint.mulesoft.com/exchange/org.mule.examples/fhir-r4-testreport-library/[TestReport] +| https://anypoint.mulesoft.com/exchange/org.mule.examples/fhir-r4-measure-api/[Measure] + +https://anypoint.mulesoft.com/exchange/org.mule.examples/fhir-r4-measurereport-api/[MeasureReport] + +https://anypoint.mulesoft.com/exchange/org.mule.examples/fhir-r4-testscript-api/[TestScript] + +https://anypoint.mulesoft.com/exchange/org.mule.examples/fhir-r4-testreport-api/[TestReport] + +.^| Specialized - Medication Definition | https://anypoint.mulesoft.com/exchange/org.mule.examples/fhir-r4-medicinalproduct-library/[MedicinalProduct] ^[u]^ + +https://anypoint.mulesoft.com/exchange/org.mule.examples/fhir-r4-medicinalproductauthorization-library/[MedicinalProductAuthorization] ^[u]^ + +https://anypoint.mulesoft.com/exchange/org.mule.examples/fhir-r4-medicinalproductcontraindication-library/[MedicinalProductContraindication] + +https://anypoint.mulesoft.com/exchange/org.mule.examples/fhir-r4-medicinalproductindication-library/[MedicinalProductIndication] + +https://anypoint.mulesoft.com/exchange/org.mule.examples/fhir-r4-medicinalproductingredient-library/[MedicinalProductIngredient] ^[u]^ + +https://anypoint.mulesoft.com/exchange/org.mule.examples/fhir-r4-medicinalproductinteraction-library/[MedicinalProductInteraction] + +https://anypoint.mulesoft.com/exchange/org.mule.examples/fhir-r4-medicinalproductmanufactured-library/[MedicinalProductManufactured] + +https://anypoint.mulesoft.com/exchange/org.mule.examples/fhir-r4-medicinalproductpackaged-library/[MedicinalProductPackaged] ^[u]^ + +https://anypoint.mulesoft.com/exchange/org.mule.examples/fhir-r4-medicinalproductpharmaceutical-library/[MedicinalProductPharmaceutical] ^[u]^ + +https://anypoint.mulesoft.com/exchange/org.mule.examples/fhir-r4-medicinalproductundesirableeffect-library/[MedicinalProductUndesirableEffect] + +https://anypoint.mulesoft.com/exchange/org.mule.examples/fhir-r4-substancenucleicacid-library/[SubstanceNucleicAcid] + +https://anypoint.mulesoft.com/exchange/org.mule.examples/fhir-r4-substancepolymer-library/[SubstancePolymer] ^[u]^ + +https://anypoint.mulesoft.com/exchange/org.mule.examples/fhir-r4-substanceprotein-library/[SubstanceProtein] + +https://anypoint.mulesoft.com/exchange/org.mule.examples/fhir-r4-substancereferenceinformation-library/[SubstanceReferenceInformation] ^[u]^ + +https://anypoint.mulesoft.com/exchange/org.mule.examples/fhir-r4-substancespecification-library/[SubstanceSpecification] ^[u]^ + +https://anypoint.mulesoft.com/exchange/org.mule.examples/fhir-r4-substancesourcematerial-library/[SubstanceSourceMaterial] +| https://anypoint.mulesoft.com/exchange/org.mule.examples/fhir-r4-medicinalproduct-api/[MedicinalProduct] ^[u]^ + +https://anypoint.mulesoft.com/exchange/org.mule.examples/fhir-r4-medicinalproductauthorization-api/[MedicinalProductAuthorization] ^[u]^ + +https://anypoint.mulesoft.com/exchange/org.mule.examples/fhir-r4-medicinalproductcontraindication-api/[MedicinalProductContraindication] + +https://anypoint.mulesoft.com/exchange/org.mule.examples/fhir-r4-medicinalproductindication-api/[MedicinalProductIndication] + +https://anypoint.mulesoft.com/exchange/org.mule.examples/fhir-r4-medicinalproductingredient-api/[MedicinalProductIngredient] ^[u]^ + +https://anypoint.mulesoft.com/exchange/org.mule.examples/fhir-r4-medicinalproductinteraction-api/[MedicinalProductInteraction] + +https://anypoint.mulesoft.com/exchange/org.mule.examples/fhir-r4-medicinalproductmanufactured-api/[MedicinalProductManufactured] + +https://anypoint.mulesoft.com/exchange/org.mule.examples/fhir-r4-medicinalproductpackaged-api/[MedicinalProductPackaged] ^[u]^ + +https://anypoint.mulesoft.com/exchange/org.mule.examples/fhir-r4-medicinalproductpharmaceutical-api/[MedicinalProductPharmaceutical] ^[u]^ + +https://anypoint.mulesoft.com/exchange/org.mule.examples/fhir-r4-medicinalproductundesirableeffect-api/[MedicinalProductUndesirableEffect] + +https://anypoint.mulesoft.com/exchange/org.mule.examples/fhir-r4-substancenucleicacid-api/[SubstanceNucleicAcid] + +https://anypoint.mulesoft.com/exchange/org.mule.examples/fhir-r4-substancepolymer-api/[SubstancePolymer] ^[u]^ + +https://anypoint.mulesoft.com/exchange/org.mule.examples/fhir-r4-substanceprotein-api/[SubstanceProtein] + +https://anypoint.mulesoft.com/exchange/org.mule.examples/fhir-r4-substancereferenceinformation-api/[SubstanceReferenceInformation] ^[u]^ + +https://anypoint.mulesoft.com/exchange/org.mule.examples/fhir-r4-substancespecification-api/[SubstanceSpecification] ^[u]^ + +https://anypoint.mulesoft.com/exchange/org.mule.examples/fhir-r4-substancesourcematerial-api/[SubstanceSourceMaterial] |=== NOTE: @@ -364,7 +364,7 @@ This FHIR Error API policy can be used to capture error responses and format the See the following page to learn more about the FHIR Error API Policy: -* https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fhir-error-policy/[FHIR Error API Policy] +* https://anypoint.mulesoft.com/exchange/org.mule.examples/fhir-error-policy/[FHIR Error API Policy] == See Also diff --git a/healthcare/2.18/modules/ROOT/pages/fhir-r4-us-core-profiles.adoc b/healthcare/2.18/modules/ROOT/pages/fhir-r4-us-core-profiles.adoc index bd9f34445..22b48f675 100644 --- a/healthcare/2.18/modules/ROOT/pages/fhir-r4-us-core-profiles.adoc +++ b/healthcare/2.18/modules/ROOT/pages/fhir-r4-us-core-profiles.adoc @@ -2,7 +2,7 @@ The MuleSoft Accelerator for Healthcare provides a library of United States Core Data for Interoperability (USCDI) and FHIR R4 resources to help healthcare developers adhere to interoperability needs and jumpstart the development of healthcare digital transformation initiatives. -You can also use the https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fhir-error-policy/[FHIR Error API Policy] to capture error responses and format them in an FHIR OperationOutcome-compliant format, since Anypoint Platform's out-of-the-box (OOTB) policies do not provide error messages in an FHIR-compliant format. This policy can also be used with other OOTB API policies provided in Anypoint Platform, such as OAuth or JWT. +You can also use the https://anypoint.mulesoft.com/exchange/org.mule.examples/fhir-error-policy/[FHIR Error API Policy] to capture error responses and format them in an FHIR OperationOutcome-compliant format, since Anypoint Platform's out-of-the-box (OOTB) policies do not provide error messages in an FHIR-compliant format. This policy can also be used with other OOTB API policies provided in Anypoint Platform, such as OAuth or JWT. For the list of all FHIR R4 assets, please refer to xref:fhir-r4-resources.adoc[this link]. @@ -15,68 +15,68 @@ _API specifications, data types, and libraries built to meet compliance with FHI | Module | Library | API specification | Data Types -| https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fhir-r4-commons-library/[FHIR R4 Common Library] + -https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fhir-r4-resource-types-library/[Resource Types Library] + +| https://anypoint.mulesoft.com/exchange/org.mule.examples/fhir-r4-commons-library/[FHIR R4 Common Library] + +https://anypoint.mulesoft.com/exchange/org.mule.examples/fhir-r4-resource-types-library/[Resource Types Library] + | NA | Foundation -| https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fhir-r4-documentreference-library/[DocumentReference Library] -| https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fhir-r4-documentreference-api/[DocumentReference API] +| https://anypoint.mulesoft.com/exchange/org.mule.examples/fhir-r4-documentreference-library/[DocumentReference Library] +| https://anypoint.mulesoft.com/exchange/org.mule.examples/fhir-r4-documentreference-api/[DocumentReference API] | Security -| https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fhir-r4-provenance-library/[Provenance Library] -| https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fhir-r4-provenance-api/[Provenance API] +| https://anypoint.mulesoft.com/exchange/org.mule.examples/fhir-r4-provenance-library/[Provenance Library] +| https://anypoint.mulesoft.com/exchange/org.mule.examples/fhir-r4-provenance-api/[Provenance API] | Conformance -| https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fhir-r4-capabilitystatement-library/[CapabilityStatement Library] -| https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fhir-r4-capabilitystatement-api/[CapabilityStatement API] +| https://anypoint.mulesoft.com/exchange/org.mule.examples/fhir-r4-capabilitystatement-library/[CapabilityStatement Library] +| https://anypoint.mulesoft.com/exchange/org.mule.examples/fhir-r4-capabilitystatement-api/[CapabilityStatement API] | Administration -| https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fhir-r4-us-core-patient-library/[Patient Library] + -https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fhir-r4-practitioner-library/[Practitioner Library] + -https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fhir-r4-practitionerrole-library/[PractitionerRole Library] + -https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fhir-r4-device-library/[Device Library] + -https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fhir-r4-organization-library/[Organization Library] + -https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fhir-r4-location-library/[Location Library] + -https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fhir-r4-careteam-library/[CareTeam Library] + -https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fhir-r4-encounter-library/[Encounter Library] + - -| https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fhir-r4-us-core-patient-api/[Patient API*] + -https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fhir-r4-practitioner-api/[Practitioner API] + -https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fhir-r4-practitionerrole-api/[PractitionerRole API] + -https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fhir-r4-device-api/[Device API] + -https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fhir-r4-organization-api/[Organization API] + -https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fhir-r4-location-api/[Location API] + -https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fhir-r4-careteam-api/[CareTeam API] + -https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fhir-r4-encounter-api/[Encounter API] +| https://anypoint.mulesoft.com/exchange/org.mule.examples/fhir-r4-us-core-patient-library/[Patient Library] + +https://anypoint.mulesoft.com/exchange/org.mule.examples/fhir-r4-practitioner-library/[Practitioner Library] + +https://anypoint.mulesoft.com/exchange/org.mule.examples/fhir-r4-practitionerrole-library/[PractitionerRole Library] + +https://anypoint.mulesoft.com/exchange/org.mule.examples/fhir-r4-device-library/[Device Library] + +https://anypoint.mulesoft.com/exchange/org.mule.examples/fhir-r4-organization-library/[Organization Library] + +https://anypoint.mulesoft.com/exchange/org.mule.examples/fhir-r4-location-library/[Location Library] + +https://anypoint.mulesoft.com/exchange/org.mule.examples/fhir-r4-careteam-library/[CareTeam Library] + +https://anypoint.mulesoft.com/exchange/org.mule.examples/fhir-r4-encounter-library/[Encounter Library] + + +| https://anypoint.mulesoft.com/exchange/org.mule.examples/fhir-r4-us-core-patient-api/[Patient API*] + +https://anypoint.mulesoft.com/exchange/org.mule.examples/fhir-r4-practitioner-api/[Practitioner API] + +https://anypoint.mulesoft.com/exchange/org.mule.examples/fhir-r4-practitionerrole-api/[PractitionerRole API] + +https://anypoint.mulesoft.com/exchange/org.mule.examples/fhir-r4-device-api/[Device API] + +https://anypoint.mulesoft.com/exchange/org.mule.examples/fhir-r4-organization-api/[Organization API] + +https://anypoint.mulesoft.com/exchange/org.mule.examples/fhir-r4-location-api/[Location API] + +https://anypoint.mulesoft.com/exchange/org.mule.examples/fhir-r4-careteam-api/[CareTeam API] + +https://anypoint.mulesoft.com/exchange/org.mule.examples/fhir-r4-encounter-api/[Encounter API] | Clinical -| https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fhir-r4-us-core-allergyintolerance-library/[AllergyIntolerance Library] + -https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fhir-r4-careplan-library/[CarePlan Library] + -https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fhir-r4-goal-library/[Goal Library] + -https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fhir-r4-procedure-library/[Procedure Library] + -https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fhir-r4-us-core-condition-library/[Condition Library] + - -| https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fhir-r4-us-core-allergyintolerance-api/[AllergyIntolerance API*] + -https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fhir-r4-careplan-api/[CarePlan API] + -https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fhir-r4-goal-api/[Goal API] + -https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fhir-r4-procedure-api/[Procedure API] + -https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fhir-r4-us-core-condition-api/[Condition API] +| https://anypoint.mulesoft.com/exchange/org.mule.examples/fhir-r4-us-core-allergyintolerance-library/[AllergyIntolerance Library] + +https://anypoint.mulesoft.com/exchange/org.mule.examples/fhir-r4-careplan-library/[CarePlan Library] + +https://anypoint.mulesoft.com/exchange/org.mule.examples/fhir-r4-goal-library/[Goal Library] + +https://anypoint.mulesoft.com/exchange/org.mule.examples/fhir-r4-procedure-library/[Procedure Library] + +https://anypoint.mulesoft.com/exchange/org.mule.examples/fhir-r4-us-core-condition-library/[Condition Library] + + +| https://anypoint.mulesoft.com/exchange/org.mule.examples/fhir-r4-us-core-allergyintolerance-api/[AllergyIntolerance API*] + +https://anypoint.mulesoft.com/exchange/org.mule.examples/fhir-r4-careplan-api/[CarePlan API] + +https://anypoint.mulesoft.com/exchange/org.mule.examples/fhir-r4-goal-api/[Goal API] + +https://anypoint.mulesoft.com/exchange/org.mule.examples/fhir-r4-procedure-api/[Procedure API] + +https://anypoint.mulesoft.com/exchange/org.mule.examples/fhir-r4-us-core-condition-api/[Condition API] | Diagnostics -| https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fhir-r4-us-core-observation-library/[Observation Library] + -https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fhir-r4-diagnosticreport-library/[DiagnosticReport Library] -| https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fhir-r4-us-core-observation-api/[Observation API*] + -https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fhir-r4-diagnosticreport-api/[DiagnosticReport API] +| https://anypoint.mulesoft.com/exchange/org.mule.examples/fhir-r4-us-core-observation-library/[Observation Library] + +https://anypoint.mulesoft.com/exchange/org.mule.examples/fhir-r4-diagnosticreport-library/[DiagnosticReport Library] +| https://anypoint.mulesoft.com/exchange/org.mule.examples/fhir-r4-us-core-observation-api/[Observation API*] + +https://anypoint.mulesoft.com/exchange/org.mule.examples/fhir-r4-diagnosticreport-api/[DiagnosticReport API] | Medications -| https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fhir-r4-immunization-library/[Immunization Library] + -https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fhir-r4-medication-library/[Medication Library] + -https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fhir-r4-medicationrequest-library/[MedicationRequest Library] -| https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fhir-r4-immunization-api/[Immunization API] + -https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fhir-r4-medication-api/[Medication API] + -https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fhir-r4-medicationrequest-api/[MedicationRequest API] +| https://anypoint.mulesoft.com/exchange/org.mule.examples/fhir-r4-immunization-library/[Immunization Library] + +https://anypoint.mulesoft.com/exchange/org.mule.examples/fhir-r4-medication-library/[Medication Library] + +https://anypoint.mulesoft.com/exchange/org.mule.examples/fhir-r4-medicationrequest-library/[MedicationRequest Library] +| https://anypoint.mulesoft.com/exchange/org.mule.examples/fhir-r4-immunization-api/[Immunization API] + +https://anypoint.mulesoft.com/exchange/org.mule.examples/fhir-r4-medication-api/[Medication API] + +https://anypoint.mulesoft.com/exchange/org.mule.examples/fhir-r4-medicationrequest-api/[MedicationRequest API] |=== _APIs marked with `*` have both FHIR R4 and US Core-specific Library and API specification available._ diff --git a/healthcare/2.18/modules/ROOT/pages/hl7-v2-fhir-converter.adoc b/healthcare/2.18/modules/ROOT/pages/hl7-v2-fhir-converter.adoc index 737ae28d6..d750bb00e 100644 --- a/healthcare/2.18/modules/ROOT/pages/hl7-v2-fhir-converter.adoc +++ b/healthcare/2.18/modules/ROOT/pages/hl7-v2-fhir-converter.adoc @@ -1,10 +1,10 @@ = HL7 v2 to FHIR Converter -The https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/hc-accelerator-hl7v2-to-fhir-sys-api[HL7 v2 to FHIR converter] comes with a ready to use template for HL7 v2 to FHIR conversion, which is based on the guidance provided by the https://build.fhir.org/ig/HL7/v2-to-fhir[HL7 v2 to FHIR Implementation Guide]. This template can be extended or modified to meet specific conversion requirements. +The https://anypoint.mulesoft.com/exchange/org.mule.examples/hc-accelerator-hl7v2-to-fhir-sys-api[HL7 v2 to FHIR converter] comes with a ready to use template for HL7 v2 to FHIR conversion, which is based on the guidance provided by the https://build.fhir.org/ig/HL7/v2-to-fhir[HL7 v2 to FHIR Implementation Guide]. This template can be extended or modified to meet specific conversion requirements. == Functional diagram -image:https://www.mulesoft.com/ext/solutions/draft/images/hc-hl7v2-to-fhir-usecase-diagram.png[hc-hl7v2-to-fhir-usecase-diagram.png,799,align="center"] +image:https://www.mulesoft.com/ext/solutions/images/hc-hl7v2-to-fhir-usecase-diagram.png[hc-hl7v2-to-fhir-usecase-diagram.png,799,align="center"] == Advantages diff --git a/healthcare/2.18/modules/ROOT/pages/index.adoc b/healthcare/2.18/modules/ROOT/pages/index.adoc index 171fea4bc..2eeb33916 100644 --- a/healthcare/2.18/modules/ROOT/pages/index.adoc +++ b/healthcare/2.18/modules/ROOT/pages/index.adoc @@ -9,13 +9,13 @@ For solutions related to life sciences, the xref:life-sciences::index.adoc[MuleS The following describes the use cases supported by the MuleSoft Accelerator for Healthcare: -* https://www.anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/mulesoft-accelerator-for-healthcare/minor/{hls-version}/pages/Use%20case%201%20-%20Patient%20360/[Patient 360^] — Includes two options (HL7 v2 and FHIR R4) for surfacing patient demographics and clinical data from an EHR into Salesforce Health Cloud. Assets can be used for a variety of use cases and provide customers with a reference implementation to integrate with common EHRs such as Epic and Cerner via API. -* https://www.anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/mulesoft-accelerator-for-healthcare/minor/{hls-version}/pages/Use%20case%202%20-%20CMS%20Interoperability/[CMS Interoperability^] — Includes assets to accelerate your API development efforts to meet https://www.cms.gov/Regulations-and-Guidance/Guidance/Interoperability/index[CMS Interoperability and Patient Access final rule]. -* https://www.anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/mulesoft-accelerator-for-healthcare/minor/{hls-version}/pages/Use%20case%203%20-%20Labs%20integration/[Labs integration^] — Includes an asset to accelerate the transmission of laboratory results that identify a notifiable condition to public health agencies, such as the California Department of Public Health. -* https://www.anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/mulesoft-accelerator-for-healthcare/minor/{hls-version}/pages/Use%20case%204%20-%20Appointment%20scheduling/[Appointment scheduling^] — Includes assets to enable scheduling, updating and canceling appointments in EHRs via APIs from patient engagement platforms like Salesforce Health Cloud, mobile apps and patient portals. -* https://www.anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/mulesoft-accelerator-for-healthcare/minor/{hls-version}/pages/Use%20case%205%20-%20Benefits%20and%20eligibility%20verification/[Benefits and eligibility verification^] — Includes assets to perform real-time benefits and eligibility verification to allow organizations to electronically verify a patient's insurance coverage for medical treatment directly within Salesforce Health Cloud. -* https://www.anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/mulesoft-accelerator-for-healthcare/minor/{hls-version}/pages/Use%20case%206%20-%20Prior%20Authorization/[Prior Authorization^] — Includes assets to accelerate development of CRD, DTR, and PAS APIs to enable API-based prior authorizations between healthcare providers and payers to reduce administrative burden and drive better patient outcomes. -* https://www.anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/mulesoft-accelerator-for-healthcare/minor/{hls-version}/pages/Use%20case%207%20-%20Population%20health%20management/[Population health management^] - Includes assets to convert and ingest valuable patient information into platforms like Amazon HealthLake and Salesforce Data Cloud to power population health initiatives. +* https://www.anypoint.mulesoft.com/exchange/org.mule.examples/mulesoft-accelerator-for-healthcare/minor/{hls-version}/pages/Use%20case%201%20-%20Patient%20360/[Patient 360^] — Includes two options (HL7 v2 and FHIR R4) for surfacing patient demographics and clinical data from an EHR into Salesforce Health Cloud. Assets can be used for a variety of use cases and provide customers with a reference implementation to integrate with common EHRs such as Epic and Cerner via API. +* https://www.anypoint.mulesoft.com/exchange/org.mule.examples/mulesoft-accelerator-for-healthcare/minor/{hls-version}/pages/Use%20case%202%20-%20CMS%20Interoperability/[CMS Interoperability^] — Includes assets to accelerate your API development efforts to meet https://www.cms.gov/Regulations-and-Guidance/Guidance/Interoperability/index[CMS Interoperability and Patient Access final rule]. +* https://www.anypoint.mulesoft.com/exchange/org.mule.examples/mulesoft-accelerator-for-healthcare/minor/{hls-version}/pages/Use%20case%203%20-%20Labs%20integration/[Labs integration^] — Includes an asset to accelerate the transmission of laboratory results that identify a notifiable condition to public health agencies, such as the California Department of Public Health. +* https://www.anypoint.mulesoft.com/exchange/org.mule.examples/mulesoft-accelerator-for-healthcare/minor/{hls-version}/pages/Use%20case%204%20-%20Appointment%20scheduling/[Appointment scheduling^] — Includes assets to enable scheduling, updating and canceling appointments in EHRs via APIs from patient engagement platforms like Salesforce Health Cloud, mobile apps and patient portals. +* https://www.anypoint.mulesoft.com/exchange/org.mule.examples/mulesoft-accelerator-for-healthcare/minor/{hls-version}/pages/Use%20case%205%20-%20Benefits%20and%20eligibility%20verification/[Benefits and eligibility verification^] — Includes assets to perform real-time benefits and eligibility verification to allow organizations to electronically verify a patient's insurance coverage for medical treatment directly within Salesforce Health Cloud. +* https://www.anypoint.mulesoft.com/exchange/org.mule.examples/mulesoft-accelerator-for-healthcare/minor/{hls-version}/pages/Use%20case%206%20-%20Prior%20Authorization/[Prior Authorization^] — Includes assets to accelerate development of CRD, DTR, and PAS APIs to enable API-based prior authorizations between healthcare providers and payers to reduce administrative burden and drive better patient outcomes. +* https://www.anypoint.mulesoft.com/exchange/org.mule.examples/mulesoft-accelerator-for-healthcare/minor/{hls-version}/pages/Use%20case%207%20-%20Population%20health%20management/[Population health management^] - Includes assets to convert and ingest valuable patient information into platforms like Amazon HealthLake and Salesforce Data Cloud to power population health initiatives. === Use Case Agnostic Assets @@ -32,4 +32,4 @@ The following use-case agnostic assets are also available: * xref:prerequisites.adoc[Prerequisites] * xref:fhir-r4-assets.adoc[Available Assets] * xref:release-notes.adoc[Release Notes] -* https://www.anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/mulesoft-accelerator-for-healthcare/[MuleSoft Accelerator for Healthcare on Exchange^] +* https://www.anypoint.mulesoft.com/exchange/org.mule.examples/mulesoft-accelerator-for-healthcare/[MuleSoft Accelerator for Healthcare on Exchange^] diff --git a/healthcare/2.18/modules/ROOT/pages/release-notes.adoc b/healthcare/2.18/modules/ROOT/pages/release-notes.adoc index 465a41022..396ea289b 100644 --- a/healthcare/2.18/modules/ROOT/pages/release-notes.adoc +++ b/healthcare/2.18/modules/ROOT/pages/release-notes.adoc @@ -5,19 +5,19 @@ 13 December 2022 -This release extends the solution provided for https://www.anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/mulesoft-accelerator-for-healthcare/minor/{hls-version}/pages/Use%20case%207%20-%20Population%20health%20management/[Population health management] to enable organizations to surface valuable population health data from EHR systems into Amazon HealthLake and Salesforce Customer Data Platform to improve clinical outcomes. +This release extends the solution provided for https://www.anypoint.mulesoft.com/exchange/org.mule.examples/mulesoft-accelerator-for-healthcare/minor/{hls-version}/pages/Use%20case%207%20-%20Population%20health%20management/[Population health management] to enable organizations to surface valuable population health data from EHR systems into Amazon HealthLake and Salesforce Customer Data Platform to improve clinical outcomes. -* FHIR Bulk Export System API | https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/hls-fhir-bulk-export-sys-api-spec[API Specification] | https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/hls-fhir-bulk-export-sys-api[Implementation Template] -* Population Health Management Process API | https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/hls-population-health-mgmt-prc-api/[Implementation Template] -* Salesforce CDP System API | https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/hls-salesforce-cdp-sys-api-spec[API Specification] | https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/hls-salesforce-cdp-sys-api[Implementation Template] -* Azure Web Engagement System API | https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/hls-engagements-sys-api-spec[API Specification] | https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/hls-azure-patient-engmt-sys-api[Implementation Template] -* Patient Segmentation Process API | https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/hls-patient-segmentation-prc-api/[Implementation Template] +* FHIR Bulk Export System API | https://anypoint.mulesoft.com/exchange/org.mule.examples/hls-fhir-bulk-export-sys-api-spec[API Specification] | https://anypoint.mulesoft.com/exchange/org.mule.examples/hls-fhir-bulk-export-sys-api[Implementation Template] +* Population Health Management Process API | https://anypoint.mulesoft.com/exchange/org.mule.examples/hls-population-health-mgmt-prc-api/[Implementation Template] +* Salesforce CDP System API | https://anypoint.mulesoft.com/exchange/org.mule.examples/hls-salesforce-cdp-sys-api-spec[API Specification] | https://anypoint.mulesoft.com/exchange/org.mule.examples/hls-salesforce-cdp-sys-api[Implementation Template] +* Azure Web Engagement System API | https://anypoint.mulesoft.com/exchange/org.mule.examples/hls-engagements-sys-api-spec[API Specification] | https://anypoint.mulesoft.com/exchange/org.mule.examples/hls-azure-patient-engmt-sys-api[Implementation Template] +* Patient Segmentation Process API | https://anypoint.mulesoft.com/exchange/org.mule.examples/hls-patient-segmentation-prc-api/[Implementation Template] == v2.17 20 October 2022 -This release provides a solution for https://www.anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/mulesoft-accelerator-for-healthcare/minor/{hls-version}/pages/Use%20case%207%20-%20Population%20health%20management/[Population health management] to enable organizations to convert and surface valuable population health data into Amazon HealthLake to improve clinical outcomes. +This release provides a solution for https://www.anypoint.mulesoft.com/exchange/org.mule.examples/mulesoft-accelerator-for-healthcare/minor/{hls-version}/pages/Use%20case%207%20-%20Population%20health%20management/[Population health management] to enable organizations to convert and surface valuable population health data into Amazon HealthLake to improve clinical outcomes. As part of this release, existing assets used to convert from HL7 v2, C-CDA and X12 formats to FHIR R4 were enhanced to fix defects and enable use with Amazon HealthLake. @@ -33,8 +33,8 @@ This release provides a support to additional CDA document types in xref:ccda-fh This release provides Healthcare organizations with a reference implementations to xref:fhir-r4-assets.adoc[convert FHIR R4 resources from HL7 FHIR JSON format to RAML specification] and xref:ccda-fhir-converter.adoc[convert C-CDA messages to FHIR]. -* FHIR RAML auto-generator | https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/hls-fhirjson-to-raml-sys-api-spec/[API specification] | https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/hls-fhirjson-to-raml-sys-api/[Implementation Template] -* C-CDA to FHIR System API | https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/hls-ccda-to-fhir-sys-api-spec/[API specification] | https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/hls-ccda-to-fhir-sys-api/[Implementation Template] +* FHIR RAML auto-generator | https://anypoint.mulesoft.com/exchange/org.mule.examples/hls-fhirjson-to-raml-sys-api-spec/[API specification] | https://anypoint.mulesoft.com/exchange/org.mule.examples/hls-fhirjson-to-raml-sys-api/[Implementation Template] +* C-CDA to FHIR System API | https://anypoint.mulesoft.com/exchange/org.mule.examples/hls-ccda-to-fhir-sys-api-spec/[API specification] | https://anypoint.mulesoft.com/exchange/org.mule.examples/hls-ccda-to-fhir-sys-api/[Implementation Template] == v2.14.1 @@ -42,29 +42,29 @@ This release provides Healthcare organizations with a reference implementations This minor release includes an upgrade to the dependencies on the assets that perform FHIR resource validation. -* Health Cloud Administration System API | https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/hc-accelerator-sfdc-us-core-administration-sys-api/[Implementation Template] -* Health Cloud Clinical System API | https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/hc-accelerator-sfdc-us-core-clinical-sys-api/[Implementation Template] -* Health Cloud Diagnostics System API | https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/hc-accelerator-sfdc-us-core-diagnostics-sys-api/[Implementation Template] -* Health Cloud Medications System API | https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/hc-accelerator-sfdc-us-core-medications-sys-api/[Implementation Template] -* Health Cloud Financial System API | https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/hc-accelerator-sfdc-financial-sys-api/[Implementation Template] -* Cerner Administration System API | https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/hc-accelerator-cerner-us-core-administration-sys-api/[Implementation Template] -* Cerner Clinical System API | https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/hc-accelerator-cerner-us-core-clinical-sys-api/[Implementation Template] -* Cerner Diagnostics System API | https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/hc-accelerator-cerner-us-core-diagnostics-sys-api/[Implementation Template] -* Cerner Medications System API | https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/hc-accelerator-cerner-us-core-medications-sys-api/[Implementation Template] -* Cerner Workflow System API | https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/hc-accelerator-cerner-workflow-sys-api/[Implementation Template] -* Cerner Financial System API | https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/hc-accelerator-cerner-financial-sys-api/[Implementation Template] -* Epic Administration System API | https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/hc-accelerator-epic-us-core-administration-sys-api/[Implementation Template] -* Epic Clinical System API | https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/hc-accelerator-epic-us-core-clinical-sys-api/[Implementation Template] -* Epic Diagnostics System API | https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/hc-accelerator-epic-us-core-diagnostics-sys-api/[Implementation Template] -* Epic Medications System API | https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/hc-accelerator-epic-us-core-medications-sys-api/[Implementation Template] -* Epic Financial System API | https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/hc-accelerator-epic-financial-sys-api/[Implementation Template] -* Benefits Verification Process API | https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/hc-accelerator-benefits-verification-prc-api/[Implementation Template] -* Benefits Eligibility Verification System API | https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/hc-accelerator-availity-financial-sys-api/[Implementation Template] -* CRD Clinical Decision Support System API | https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/hc-accelerator-cds-services-sys-api/[Implementation Template] -* DTR System API | https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/hc-accelerator-davinci-dtr-sys-api/[Implementation Template] -* Prior Authorization System API | https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/hc-accelerator-prior-authorization-sys-api[Implementation Template] -* HL7 V2 to FHIR System API | https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/hc-accelerator-hl7v2-to-fhir-sys-api/[Implementation Template] -* X12 to FHIR System API | https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/hls-fhir-to-x12-sys-api/[Implementation Template] +* Health Cloud Administration System API | https://anypoint.mulesoft.com/exchange/org.mule.examples/hc-accelerator-sfdc-us-core-administration-sys-api/[Implementation Template] +* Health Cloud Clinical System API | https://anypoint.mulesoft.com/exchange/org.mule.examples/hc-accelerator-sfdc-us-core-clinical-sys-api/[Implementation Template] +* Health Cloud Diagnostics System API | https://anypoint.mulesoft.com/exchange/org.mule.examples/hc-accelerator-sfdc-us-core-diagnostics-sys-api/[Implementation Template] +* Health Cloud Medications System API | https://anypoint.mulesoft.com/exchange/org.mule.examples/hc-accelerator-sfdc-us-core-medications-sys-api/[Implementation Template] +* Health Cloud Financial System API | https://anypoint.mulesoft.com/exchange/org.mule.examples/hc-accelerator-sfdc-financial-sys-api/[Implementation Template] +* Cerner Administration System API | https://anypoint.mulesoft.com/exchange/org.mule.examples/hc-accelerator-cerner-us-core-administration-sys-api/[Implementation Template] +* Cerner Clinical System API | https://anypoint.mulesoft.com/exchange/org.mule.examples/hc-accelerator-cerner-us-core-clinical-sys-api/[Implementation Template] +* Cerner Diagnostics System API | https://anypoint.mulesoft.com/exchange/org.mule.examples/hc-accelerator-cerner-us-core-diagnostics-sys-api/[Implementation Template] +* Cerner Medications System API | https://anypoint.mulesoft.com/exchange/org.mule.examples/hc-accelerator-cerner-us-core-medications-sys-api/[Implementation Template] +* Cerner Workflow System API | https://anypoint.mulesoft.com/exchange/org.mule.examples/hc-accelerator-cerner-workflow-sys-api/[Implementation Template] +* Cerner Financial System API | https://anypoint.mulesoft.com/exchange/org.mule.examples/hc-accelerator-cerner-financial-sys-api/[Implementation Template] +* Epic Administration System API | https://anypoint.mulesoft.com/exchange/org.mule.examples/hc-accelerator-epic-us-core-administration-sys-api/[Implementation Template] +* Epic Clinical System API | https://anypoint.mulesoft.com/exchange/org.mule.examples/hc-accelerator-epic-us-core-clinical-sys-api/[Implementation Template] +* Epic Diagnostics System API | https://anypoint.mulesoft.com/exchange/org.mule.examples/hc-accelerator-epic-us-core-diagnostics-sys-api/[Implementation Template] +* Epic Medications System API | https://anypoint.mulesoft.com/exchange/org.mule.examples/hc-accelerator-epic-us-core-medications-sys-api/[Implementation Template] +* Epic Financial System API | https://anypoint.mulesoft.com/exchange/org.mule.examples/hc-accelerator-epic-financial-sys-api/[Implementation Template] +* Benefits Verification Process API | https://anypoint.mulesoft.com/exchange/org.mule.examples/hc-accelerator-benefits-verification-prc-api/[Implementation Template] +* Benefits Eligibility Verification System API | https://anypoint.mulesoft.com/exchange/org.mule.examples/hc-accelerator-availity-financial-sys-api/[Implementation Template] +* CRD Clinical Decision Support System API | https://anypoint.mulesoft.com/exchange/org.mule.examples/hc-accelerator-cds-services-sys-api/[Implementation Template] +* DTR System API | https://anypoint.mulesoft.com/exchange/org.mule.examples/hc-accelerator-davinci-dtr-sys-api/[Implementation Template] +* Prior Authorization System API | https://anypoint.mulesoft.com/exchange/org.mule.examples/hc-accelerator-prior-authorization-sys-api[Implementation Template] +* HL7 V2 to FHIR System API | https://anypoint.mulesoft.com/exchange/org.mule.examples/hc-accelerator-hl7v2-to-fhir-sys-api/[Implementation Template] +* X12 to FHIR System API | https://anypoint.mulesoft.com/exchange/org.mule.examples/hls-fhir-to-x12-sys-api/[Implementation Template] == v2.14 @@ -72,7 +72,7 @@ This minor release includes an upgrade to the dependencies on the assets that pe This release provides Healthcare organizations with a reference implementation to xref:x12-fhir-converter.adoc[convert X12 messages to FHIR]. -* https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/hls-fhir-r4-to-x12-sys-api-spec/[API specification] and https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/hls-fhir-to-x12-sys-api/[implementation template] for the X12 to FHIR System API. +* https://anypoint.mulesoft.com/exchange/org.mule.examples/hls-fhir-r4-to-x12-sys-api-spec/[API specification] and https://anypoint.mulesoft.com/exchange/org.mule.examples/hls-fhir-to-x12-sys-api/[implementation template] for the X12 to FHIR System API. == v2.13 @@ -80,9 +80,9 @@ This release provides Healthcare organizations with a reference implementation t This release provides an end-to-end solution for prior authorization, which includes CRD, DTR, and PAS API specifications and implementation templates to automate the prior authorization process for more immediate authorizations: -* CRD Clinical Decision Support System API | https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/hls-cds-services-sys-api-spec/[API Specification] | https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/hc-accelerator-cds-services-sys-api/[Implementation Template] -* DTR System API | https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fhir-r4-davinci-dtr-api/[API Specification] | https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/hc-accelerator-davinci-dtr-sys-api/[Implementation Template] -* Prior Authorization System API | https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fhir-r4-prior-authorization-api[API Specification] | https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/hc-accelerator-prior-authorization-sys-api[Implementation Template] +* CRD Clinical Decision Support System API | https://anypoint.mulesoft.com/exchange/org.mule.examples/hls-cds-services-sys-api-spec/[API Specification] | https://anypoint.mulesoft.com/exchange/org.mule.examples/hc-accelerator-cds-services-sys-api/[Implementation Template] +* DTR System API | https://anypoint.mulesoft.com/exchange/org.mule.examples/fhir-r4-davinci-dtr-api/[API Specification] | https://anypoint.mulesoft.com/exchange/org.mule.examples/hc-accelerator-davinci-dtr-sys-api/[Implementation Template] +* Prior Authorization System API | https://anypoint.mulesoft.com/exchange/org.mule.examples/fhir-r4-prior-authorization-api[API Specification] | https://anypoint.mulesoft.com/exchange/org.mule.examples/hc-accelerator-prior-authorization-sys-api[Implementation Template] == v2.12.1 @@ -90,7 +90,7 @@ This release provides an end-to-end solution for prior authorization, which incl This minor release includes an upgrade to the assets to be EMR agnostic, which allows customers to choose any EMR as a System of Record: -* Patient Sync Process API | https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/patient-sync-prc-api/[API Specification] | https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/hc-accelerator-patient-sync-prc-api/[Implementation Template] +* Patient Sync Process API | https://anypoint.mulesoft.com/exchange/org.mule.examples/patient-sync-prc-api/[API Specification] | https://anypoint.mulesoft.com/exchange/org.mule.examples/hc-accelerator-patient-sync-prc-api/[Implementation Template] == v2.12 @@ -98,8 +98,8 @@ This minor release includes an upgrade to the assets to be EMR agnostic, which a This release provides an end-to-end solution for prior authorization support, which automates the prior authorization process for more immediate authorizations. The following assets are also available: -* Prior Authorization System API | https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fhir-r4-prior-authorization-api[API Specification] | https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/hc-accelerator-prior-authorization-sys-api[Implementation Template] -* Aidbox Administration System API | https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fhir-r4-administration-api/[API Specification] | https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/hc-accelerator-aidbox-us-core-administration-sys-api/[Implementation Template] +* Prior Authorization System API | https://anypoint.mulesoft.com/exchange/org.mule.examples/fhir-r4-prior-authorization-api[API Specification] | https://anypoint.mulesoft.com/exchange/org.mule.examples/hc-accelerator-prior-authorization-sys-api[Implementation Template] +* Aidbox Administration System API | https://anypoint.mulesoft.com/exchange/org.mule.examples/fhir-r4-administration-api/[API Specification] | https://anypoint.mulesoft.com/exchange/org.mule.examples/hc-accelerator-aidbox-us-core-administration-sys-api/[Implementation Template] == v2.11 @@ -107,12 +107,12 @@ This release provides an end-to-end solution for prior authorization support, wh This release provides an end-to-end solution for benefits and eligibility verification using Health Cloud, Epic, and Cerner as the reference backend systems: -* Benefits Verification Process API | https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/benefits-verification-prc-api/[API Specification] | https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/hc-accelerator-benefits-verification-prc-api/[Implementation Template] -* Cerner Financial System API | https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/cerner-fhir-r4-financial-api/[API Specification] | https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/hc-accelerator-cerner-financial-sys-api/[Implementation Template] -* Epic Financial System API | https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/epic-fhir-r4-financial-api/[API Specification] | https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/hc-accelerator-epic-financial-sys-api/[Implementation Template] -* Benefits Eligibility Verification System API | https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/availity-fhir-r4-financial-api/[API Specification] | https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/hc-accelerator-availity-financial-sys-api/[Implementation Template] -* Health Cloud Financial System API | https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fhir-r4-financial-api/[API Specification] | https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/hc-accelerator-sfdc-financial-sys-api/[Implementation Template] -* Health Cloud Benefits Verification Lightning Web Component | https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/hc-accelerator-benefits-verification-lwc-src/[Source] +* Benefits Verification Process API | https://anypoint.mulesoft.com/exchange/org.mule.examples/benefits-verification-prc-api/[API Specification] | https://anypoint.mulesoft.com/exchange/org.mule.examples/hc-accelerator-benefits-verification-prc-api/[Implementation Template] +* Cerner Financial System API | https://anypoint.mulesoft.com/exchange/org.mule.examples/cerner-fhir-r4-financial-api/[API Specification] | https://anypoint.mulesoft.com/exchange/org.mule.examples/hc-accelerator-cerner-financial-sys-api/[Implementation Template] +* Epic Financial System API | https://anypoint.mulesoft.com/exchange/org.mule.examples/epic-fhir-r4-financial-api/[API Specification] | https://anypoint.mulesoft.com/exchange/org.mule.examples/hc-accelerator-epic-financial-sys-api/[Implementation Template] +* Benefits Eligibility Verification System API | https://anypoint.mulesoft.com/exchange/org.mule.examples/availity-fhir-r4-financial-api/[API Specification] | https://anypoint.mulesoft.com/exchange/org.mule.examples/hc-accelerator-availity-financial-sys-api/[Implementation Template] +* Health Cloud Financial System API | https://anypoint.mulesoft.com/exchange/org.mule.examples/fhir-r4-financial-api/[API Specification] | https://anypoint.mulesoft.com/exchange/org.mule.examples/hc-accelerator-sfdc-financial-sys-api/[Implementation Template] +* Health Cloud Benefits Verification Lightning Web Component | https://anypoint.mulesoft.com/exchange/org.mule.examples/hc-accelerator-benefits-verification-lwc-src/[Source] == v2.10 @@ -120,37 +120,37 @@ This release provides an end-to-end solution for benefits and eligibility verifi The focus of the 2.10 release is to provide assets for the patient sync capabilities: -* Patient sync Lightning Web Component | https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/hc-accelerator-sfdc-patient-sync-lwc-src/[Source] -* Patient Sync Process API | https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/patient-sync-prc-api/[API Specification] | https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/hc-accelerator-patient-sync-prc-api/[Implementation Template] +* Patient sync Lightning Web Component | https://anypoint.mulesoft.com/exchange/org.mule.examples/hc-accelerator-sfdc-patient-sync-lwc-src/[Source] +* Patient Sync Process API | https://anypoint.mulesoft.com/exchange/org.mule.examples/patient-sync-prc-api/[API Specification] | https://anypoint.mulesoft.com/exchange/org.mule.examples/hc-accelerator-patient-sync-prc-api/[Implementation Template] The following assets were also enhanced and improved for this release: -* FHIR R4 Location Library | https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fhir-r4-location-library/[API Specification Fragment] -* FHIR R4 Procedure Library | https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fhir-r4-procedure-library/[API Specification Fragment] -* FHIR R4 Administration API | https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fhir-r4-administration-api/[API Specification] -* FHIR R4 Clinical API | https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fhir-r4-clinical-api/[API Specification] -* Epic FHIR R4 Administration API | https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/epic-fhir-r4-administration-api/[API Specification] -* Epic FHIR R4 Clinical API | https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/epic-fhir-r4-clinical-api/[API Specification] -* Epic FHIR R4 Medications API | https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/epic-fhir-r4-medications-api/[API Specification] -* Cerner FHIR R4 Administration API | https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/cerner-fhir-r4-administration-api/[API Specification] -* Cerner Administration System API | https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/hc-accelerator-cerner-us-core-administration-sys-api/[Implementation Template] -* Health Cloud Clinical System API | https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/hc-accelerator-sfdc-us-core-clinical-sys-api/[Implementation Template] -* Health Cloud Diagnostics System API | https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/hc-accelerator-sfdc-us-core-diagnostics-sys-api/[Implementation Template] -* Health Cloud Medications System API | https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/hc-accelerator-sfdc-us-core-medications-sys-api/[Implementation Template] -* Health Cloud Administration System API | https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/hc-accelerator-sfdc-us-core-administration-sys-api/[Implementation Template] +* FHIR R4 Location Library | https://anypoint.mulesoft.com/exchange/org.mule.examples/fhir-r4-location-library/[API Specification Fragment] +* FHIR R4 Procedure Library | https://anypoint.mulesoft.com/exchange/org.mule.examples/fhir-r4-procedure-library/[API Specification Fragment] +* FHIR R4 Administration API | https://anypoint.mulesoft.com/exchange/org.mule.examples/fhir-r4-administration-api/[API Specification] +* FHIR R4 Clinical API | https://anypoint.mulesoft.com/exchange/org.mule.examples/fhir-r4-clinical-api/[API Specification] +* Epic FHIR R4 Administration API | https://anypoint.mulesoft.com/exchange/org.mule.examples/epic-fhir-r4-administration-api/[API Specification] +* Epic FHIR R4 Clinical API | https://anypoint.mulesoft.com/exchange/org.mule.examples/epic-fhir-r4-clinical-api/[API Specification] +* Epic FHIR R4 Medications API | https://anypoint.mulesoft.com/exchange/org.mule.examples/epic-fhir-r4-medications-api/[API Specification] +* Cerner FHIR R4 Administration API | https://anypoint.mulesoft.com/exchange/org.mule.examples/cerner-fhir-r4-administration-api/[API Specification] +* Cerner Administration System API | https://anypoint.mulesoft.com/exchange/org.mule.examples/hc-accelerator-cerner-us-core-administration-sys-api/[Implementation Template] +* Health Cloud Clinical System API | https://anypoint.mulesoft.com/exchange/org.mule.examples/hc-accelerator-sfdc-us-core-clinical-sys-api/[Implementation Template] +* Health Cloud Diagnostics System API | https://anypoint.mulesoft.com/exchange/org.mule.examples/hc-accelerator-sfdc-us-core-diagnostics-sys-api/[Implementation Template] +* Health Cloud Medications System API | https://anypoint.mulesoft.com/exchange/org.mule.examples/hc-accelerator-sfdc-us-core-medications-sys-api/[Implementation Template] +* Health Cloud Administration System API | https://anypoint.mulesoft.com/exchange/org.mule.examples/hc-accelerator-sfdc-us-core-administration-sys-api/[Implementation Template] The following assets are modified to support XML format for existing Epic System APIs: -* Epic Clinical System API | https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/hc-accelerator-epic-us-core-clinical-sys-api/[Implementation Template] -* Epic Diagnostics System API | https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/hc-accelerator-epic-us-core-diagnostics-sys-api/[Implementation Template] -* Epic Medications System API | https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/hc-accelerator-epic-us-core-medications-sys-api/[Implementation Template] -* Epic Administration System API | https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/hc-accelerator-epic-us-core-administration-sys-api/[Implementation Template] +* Epic Clinical System API | https://anypoint.mulesoft.com/exchange/org.mule.examples/hc-accelerator-epic-us-core-clinical-sys-api/[Implementation Template] +* Epic Diagnostics System API | https://anypoint.mulesoft.com/exchange/org.mule.examples/hc-accelerator-epic-us-core-diagnostics-sys-api/[Implementation Template] +* Epic Medications System API | https://anypoint.mulesoft.com/exchange/org.mule.examples/hc-accelerator-epic-us-core-medications-sys-api/[Implementation Template] +* Epic Administration System API | https://anypoint.mulesoft.com/exchange/org.mule.examples/hc-accelerator-epic-us-core-administration-sys-api/[Implementation Template] The following assets are modified to support updated API specifications for existing Cerner System APIs: -* Cerner Administration System API | https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/hc-accelerator-cerner-us-core-administration-sys-api/[Implementation Template] -* Cerner Clinical System API | https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/hc-accelerator-cerner-us-core-clinical-sys-api/[Implementation Template] -* Cerner Medications System API | https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/hc-accelerator-cerner-us-core-medications-sys-api/[Implementation Template] +* Cerner Administration System API | https://anypoint.mulesoft.com/exchange/org.mule.examples/hc-accelerator-cerner-us-core-administration-sys-api/[Implementation Template] +* Cerner Clinical System API | https://anypoint.mulesoft.com/exchange/org.mule.examples/hc-accelerator-cerner-us-core-clinical-sys-api/[Implementation Template] +* Cerner Medications System API | https://anypoint.mulesoft.com/exchange/org.mule.examples/hc-accelerator-cerner-us-core-medications-sys-api/[Implementation Template] == v2.9 @@ -158,30 +158,30 @@ The following assets are modified to support updated API specifications for exis This release provides API specifications and implementation templates for the Appointment Scheduling use case described https://www.hl7.org/fhir/workflow-module.html[here]: -* Appointment Scheduling Process API | https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fhir-r4-appointment-scheduling-api/[API Specification] | https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/hc-accelerator-appointment-scheduling-prc-api/[Implementation Template] -* Cerner Workflow System API | https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/cerner-fhir-r4-workflow-api/[API Specification] | https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/hc-accelerator-cerner-workflow-sys-api/[Implementation Template] -* Epic Workflow System API | https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/epic-fhir-r4-workflow-api/[API Specification] | https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/hc-accelerator-epic-workflow-sys-api/[Implementation Template] +* Appointment Scheduling Process API | https://anypoint.mulesoft.com/exchange/org.mule.examples/fhir-r4-appointment-scheduling-api/[API Specification] | https://anypoint.mulesoft.com/exchange/org.mule.examples/hc-accelerator-appointment-scheduling-prc-api/[Implementation Template] +* Cerner Workflow System API | https://anypoint.mulesoft.com/exchange/org.mule.examples/cerner-fhir-r4-workflow-api/[API Specification] | https://anypoint.mulesoft.com/exchange/org.mule.examples/hc-accelerator-cerner-workflow-sys-api/[Implementation Template] +* Epic Workflow System API | https://anypoint.mulesoft.com/exchange/org.mule.examples/epic-fhir-r4-workflow-api/[API Specification] | https://anypoint.mulesoft.com/exchange/org.mule.examples/hc-accelerator-epic-workflow-sys-api/[Implementation Template] It also includes the following Cerner assets for Patient 360: -* Cerner Administration System API | https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/cerner-fhir-r4-administration-api/[API Specification] | https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/hc-accelerator-cerner-us-core-administration-sys-api/[Implementation Template] -* Cerner Clinical System API | https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/cerner-fhir-r4-clinical-api/[API Specification] | https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/hc-accelerator-cerner-us-core-clinical-sys-api/[Implementation Template] -* Cerner Diagnostics System API | https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/cerner-fhir-r4-diagnostics-api/[API Specification] | https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/hc-accelerator-cerner-us-core-diagnostics-sys-api/[Implementation Template] -* Cerner Medications System API | https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/cerner-fhir-r4-medications-api/[API Specification] | https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/hc-accelerator-cerner-us-core-medications-sys-api/[Implementation Template] +* Cerner Administration System API | https://anypoint.mulesoft.com/exchange/org.mule.examples/cerner-fhir-r4-administration-api/[API Specification] | https://anypoint.mulesoft.com/exchange/org.mule.examples/hc-accelerator-cerner-us-core-administration-sys-api/[Implementation Template] +* Cerner Clinical System API | https://anypoint.mulesoft.com/exchange/org.mule.examples/cerner-fhir-r4-clinical-api/[API Specification] | https://anypoint.mulesoft.com/exchange/org.mule.examples/hc-accelerator-cerner-us-core-clinical-sys-api/[Implementation Template] +* Cerner Diagnostics System API | https://anypoint.mulesoft.com/exchange/org.mule.examples/cerner-fhir-r4-diagnostics-api/[API Specification] | https://anypoint.mulesoft.com/exchange/org.mule.examples/hc-accelerator-cerner-us-core-diagnostics-sys-api/[Implementation Template] +* Cerner Medications System API | https://anypoint.mulesoft.com/exchange/org.mule.examples/cerner-fhir-r4-medications-api/[API Specification] | https://anypoint.mulesoft.com/exchange/org.mule.examples/hc-accelerator-cerner-us-core-medications-sys-api/[Implementation Template] The following assets were also enhanced and improved for this release: -* Epic Administration System API | https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/epic-fhir-r4-administration-api/[API Specification] | https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/hc-accelerator-epic-us-core-administration-sys-api/[Implementation Template] -* Epic Clinical System API | https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/epic-fhir-r4-clinical-api/[API Specification] | https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/hc-accelerator-epic-us-core-clinical-sys-api/[Implementation Template] -* Epic Diagnostics System API | https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/epic-fhir-r4-diagnostics-api[API Specification] | https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/hc-accelerator-epic-us-core-diagnostics-sys-api/[Implementation Template] -* Epic Medications System API | https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/epic-fhir-r4-medications-api/[API Specification] | https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/hc-accelerator-epic-us-core-medications-sys-api/[Implementation Template] -* FHIR R4 Administration API | https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fhir-r4-administration-api/[API Specification] -* FHIR R4 Clinical API | https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fhir-r4-clinical-api/[API Specification] -* FHIR R4 Diagnostics API | https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fhir-r4-diagnostics-api/[API Specification] -* FHIR R4 Medications API | https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fhir-r4-medications-api/[API Specification] -* FHIR R4 Workflow API | https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fhir-r4-workflow-api/[API Specification] -* https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/hc-accelerator-sfdc-adt-api/[HL7 V2 ADT Process API] -* https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/hc-accelerator-sfdc-oru-api/[HL7 V2 ORU Process API] +* Epic Administration System API | https://anypoint.mulesoft.com/exchange/org.mule.examples/epic-fhir-r4-administration-api/[API Specification] | https://anypoint.mulesoft.com/exchange/org.mule.examples/hc-accelerator-epic-us-core-administration-sys-api/[Implementation Template] +* Epic Clinical System API | https://anypoint.mulesoft.com/exchange/org.mule.examples/epic-fhir-r4-clinical-api/[API Specification] | https://anypoint.mulesoft.com/exchange/org.mule.examples/hc-accelerator-epic-us-core-clinical-sys-api/[Implementation Template] +* Epic Diagnostics System API | https://anypoint.mulesoft.com/exchange/org.mule.examples/epic-fhir-r4-diagnostics-api[API Specification] | https://anypoint.mulesoft.com/exchange/org.mule.examples/hc-accelerator-epic-us-core-diagnostics-sys-api/[Implementation Template] +* Epic Medications System API | https://anypoint.mulesoft.com/exchange/org.mule.examples/epic-fhir-r4-medications-api/[API Specification] | https://anypoint.mulesoft.com/exchange/org.mule.examples/hc-accelerator-epic-us-core-medications-sys-api/[Implementation Template] +* FHIR R4 Administration API | https://anypoint.mulesoft.com/exchange/org.mule.examples/fhir-r4-administration-api/[API Specification] +* FHIR R4 Clinical API | https://anypoint.mulesoft.com/exchange/org.mule.examples/fhir-r4-clinical-api/[API Specification] +* FHIR R4 Diagnostics API | https://anypoint.mulesoft.com/exchange/org.mule.examples/fhir-r4-diagnostics-api/[API Specification] +* FHIR R4 Medications API | https://anypoint.mulesoft.com/exchange/org.mule.examples/fhir-r4-medications-api/[API Specification] +* FHIR R4 Workflow API | https://anypoint.mulesoft.com/exchange/org.mule.examples/fhir-r4-workflow-api/[API Specification] +* https://anypoint.mulesoft.com/exchange/org.mule.examples/hc-accelerator-sfdc-adt-api/[HL7 V2 ADT Process API] +* https://anypoint.mulesoft.com/exchange/org.mule.examples/hc-accelerator-sfdc-oru-api/[HL7 V2 ORU Process API] == v2.8 @@ -190,24 +190,24 @@ The following assets were also enhanced and improved for this release: This release includes: * Implementation templates added for the following Health Cloud and Epic APIs for Patient 360: - ** https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/hc-accelerator-epic-us-core-clinical-sys-api/[Epic Clinical System API] - ** https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/hc-accelerator-epic-us-core-diagnostics-sys-api/[Epic Diagnostics System API] - ** https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/hc-accelerator-epic-us-core-medications-sys-api/[Epic Medications System API] - ** https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/hc-accelerator-sfdc-us-core-clinical-sys-api/[Health Cloud Clinical System API] - ** https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/hc-accelerator-sfdc-us-core-diagnostics-sys-api/[Health Cloud Diagnostics System API] - ** https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/hc-accelerator-sfdc-us-core-medications-sys-api/[Health Cloud Medications System API] + ** https://anypoint.mulesoft.com/exchange/org.mule.examples/hc-accelerator-epic-us-core-clinical-sys-api/[Epic Clinical System API] + ** https://anypoint.mulesoft.com/exchange/org.mule.examples/hc-accelerator-epic-us-core-diagnostics-sys-api/[Epic Diagnostics System API] + ** https://anypoint.mulesoft.com/exchange/org.mule.examples/hc-accelerator-epic-us-core-medications-sys-api/[Epic Medications System API] + ** https://anypoint.mulesoft.com/exchange/org.mule.examples/hc-accelerator-sfdc-us-core-clinical-sys-api/[Health Cloud Clinical System API] + ** https://anypoint.mulesoft.com/exchange/org.mule.examples/hc-accelerator-sfdc-us-core-diagnostics-sys-api/[Health Cloud Diagnostics System API] + ** https://anypoint.mulesoft.com/exchange/org.mule.examples/hc-accelerator-sfdc-us-core-medications-sys-api/[Health Cloud Medications System API] * Enhancements and improvements made to the following templates: - ** https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/hc-accelerator-epic-us-core-administration-sys-api/[Epic Administration System API] - ** https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/hc-accelerator-sfdc-us-core-administration-sys-api/[Health Cloud Administration System API] + ** https://anypoint.mulesoft.com/exchange/org.mule.examples/hc-accelerator-epic-us-core-administration-sys-api/[Epic Administration System API] + ** https://anypoint.mulesoft.com/exchange/org.mule.examples/hc-accelerator-sfdc-us-core-administration-sys-api/[Health Cloud Administration System API] * Updated the following templates to support the Spring 2021 release of the Health Cloud data model: - ** https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/hc-accelerator-sfdc-adt-api/[HL7 V2 ADT Process API] - ** https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/hc-accelerator-sfdc-oru-api/[HL7 V2 ORU Process API] + ** https://anypoint.mulesoft.com/exchange/org.mule.examples/hc-accelerator-sfdc-adt-api/[HL7 V2 ADT Process API] + ** https://anypoint.mulesoft.com/exchange/org.mule.examples/hc-accelerator-sfdc-oru-api/[HL7 V2 ORU Process API] * Additional updates and improvements: - ** https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/hc-accelerator-hl7v2-to-fhir-sys-api/[HL7 V2 to FHIR System API] - ** https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fhir-r4-capabilitystatement-api/[FHIR R4 Capability Statement API] + ** https://anypoint.mulesoft.com/exchange/org.mule.examples/hc-accelerator-hl7v2-to-fhir-sys-api/[HL7 V2 to FHIR System API] + ** https://anypoint.mulesoft.com/exchange/org.mule.examples/fhir-r4-capabilitystatement-api/[FHIR R4 Capability Statement API] == v2.7 @@ -216,9 +216,9 @@ This release includes: This release includes: * Implementation templates for the Administration API for Patient 360: - * https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/hc-accelerator-sfdc-us-core-administration-sys-api/[Health Cloud Administration System API] - Supports the Spring 2021 release of the Health Cloud data model. - * https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/hc-accelerator-epic-us-core-administration-sys-api/[EPIC Administration System API] - Supports the Patient resource currently. Additional resources will be supported in the next release. -* Reference implementation for https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/hc-accelerator-okta-smartfhir/[SMART on FHIR with Okta]. + * https://anypoint.mulesoft.com/exchange/org.mule.examples/hc-accelerator-sfdc-us-core-administration-sys-api/[Health Cloud Administration System API] - Supports the Spring 2021 release of the Health Cloud data model. + * https://anypoint.mulesoft.com/exchange/org.mule.examples/hc-accelerator-epic-us-core-administration-sys-api/[EPIC Administration System API] - Supports the Patient resource currently. Additional resources will be supported in the next release. +* Reference implementation for https://anypoint.mulesoft.com/exchange/org.mule.examples/hc-accelerator-okta-smartfhir/[SMART on FHIR with Okta]. == v2.6 @@ -227,7 +227,7 @@ This release includes: This release includes: * API specifications for Patient 360 to support the Spring 2021 release of the Health Cloud data model. -* Added support for the ORU message type in the https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/hc-accelerator-hl7v2-to-fhir-sys-api/[HL7 v2 to FHIR converter]. +* Added support for the ORU message type in the https://anypoint.mulesoft.com/exchange/org.mule.examples/hc-accelerator-hl7v2-to-fhir-sys-api/[HL7 v2 to FHIR converter]. == v2.5 @@ -235,7 +235,7 @@ This release includes: This release provides Healthcare organizations with a reference implementation to convert HL7 v2 messages to FHIR to integrate with different systems using the https://build.fhir.org/ig/HL7/v2-to-fhir/mapping_guidelines.html[guidelines] provided by the https://build.fhir.org/ig/HL7/v2-to-fhir/[HL7 v2 to FHIR Implementation Guide]. -* https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fhir-r4-convert-api/[API specification] and https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/hc-accelerator-hl7v2-to-fhir-sys-api/[implementation template] for HL7 v2 to FHIR System API +* https://anypoint.mulesoft.com/exchange/org.mule.examples/fhir-r4-convert-api/[API specification] and https://anypoint.mulesoft.com/exchange/org.mule.examples/hc-accelerator-hl7v2-to-fhir-sys-api/[implementation template] for HL7 v2 to FHIR System API == v2.4 @@ -243,8 +243,8 @@ This release provides Healthcare organizations with a reference implementation t The focus of release 2.4 is on providing the API specifications and implementation templates for https://www.cms.gov/Regulations-and-Guidance/Guidance/Interoperability/index[CMS Interoperability and Patient Access final rule]. The release contains the following assets: -* https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fhir-r4-patient-access-clinical-exp-api/[API specification] and https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/hc-accelerator-sfdc-us-core-patientaccessclinicaldata-exp-api/[implementation template] for Patient Access API - Clinical Data as per the https://www.hl7.org/fhir/us/core/[US Core Implementation Guide]. -* https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fhir-r4-patient-access-claims-encounter-exp-api/[API specification] and https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/hc-accelerator-carin-patientclaimsencounterdata-exp-api/[implementation template] for Patient Access API - Claims and Encounter Data as per the https://build.fhir.org/ig/HL7/carin-bb/index.html[CARIN Implementation Guide for Blue Button]. +* https://anypoint.mulesoft.com/exchange/org.mule.examples/fhir-r4-patient-access-clinical-exp-api/[API specification] and https://anypoint.mulesoft.com/exchange/org.mule.examples/hc-accelerator-sfdc-us-core-patientaccessclinicaldata-exp-api/[implementation template] for Patient Access API - Clinical Data as per the https://www.hl7.org/fhir/us/core/[US Core Implementation Guide]. +* https://anypoint.mulesoft.com/exchange/org.mule.examples/fhir-r4-patient-access-claims-encounter-exp-api/[API specification] and https://anypoint.mulesoft.com/exchange/org.mule.examples/hc-accelerator-carin-patientclaimsencounterdata-exp-api/[implementation template] for Patient Access API - Claims and Encounter Data as per the https://build.fhir.org/ig/HL7/carin-bb/index.html[CARIN Implementation Guide for Blue Button]. * Minor bug fixes. == v2.3 @@ -253,8 +253,8 @@ The focus of release 2.4 is on providing the API specifications and implementati The focus of release 2.3 is on providing the API specifications and implementation templates for https://www.cms.gov/Regulations-and-Guidance/Guidance/Interoperability/index[CMS Interoperability and Patient Access final rule]. The release contains the following assets: -* https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fhir-r4-pdex-formulary-api/[API specification] and https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/hc-accelerator-pdex-formulary-exp-api/[implementation template] for Formulary API as per the http://build.fhir.org/ig/HL7/davinci-pdex-formulary/index.html[DaVinci PDEX US Drug Formulary Implementation Guide]. -* https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fhir-r4-plannet-providerdirectory-api/[API specification] and https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/hc-accelerator-plannet-providerdirectory-exp-api/[implementation template] for Provider Directory API as per the https://build.fhir.org/ig/HL7/davinci-pdex-plan-net/index.html[DaVinci PDEX Plan Net Implementation Guide]. +* https://anypoint.mulesoft.com/exchange/org.mule.examples/fhir-r4-pdex-formulary-api/[API specification] and https://anypoint.mulesoft.com/exchange/org.mule.examples/hc-accelerator-pdex-formulary-exp-api/[implementation template] for Formulary API as per the http://build.fhir.org/ig/HL7/davinci-pdex-formulary/index.html[DaVinci PDEX US Drug Formulary Implementation Guide]. +* https://anypoint.mulesoft.com/exchange/org.mule.examples/fhir-r4-plannet-providerdirectory-api/[API specification] and https://anypoint.mulesoft.com/exchange/org.mule.examples/hc-accelerator-plannet-providerdirectory-exp-api/[implementation template] for Provider Directory API as per the https://build.fhir.org/ig/HL7/davinci-pdex-plan-net/index.html[DaVinci PDEX Plan Net Implementation Guide]. * Minor bug fixes. == v2.2 @@ -263,8 +263,8 @@ The focus of release 2.3 is on providing the API specifications and implementati The focus of release 2.2 is on providing the implementation template for Electronic Laboratory Reporting to CalREDIE. The release contains the following assets: -* Implementation template for https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/hc-accelerator-lblims-calredie-process-bapi/[Electronic Laboratory Reporting], which is the notifiable condition to CalREDIE. -* API policy to return https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fhir-error-policy/[FHIR compliant OperationOutcome response]. +* Implementation template for https://anypoint.mulesoft.com/exchange/org.mule.examples/hc-accelerator-lblims-calredie-process-bapi/[Electronic Laboratory Reporting], which is the notifiable condition to CalREDIE. +* API policy to return https://anypoint.mulesoft.com/exchange/org.mule.examples/fhir-error-policy/[FHIR compliant OperationOutcome response]. * Minor bug fixes. == v2.1.1 diff --git a/healthcare/2.18/modules/ROOT/pages/sfdc-data-cloud-setup-guide.adoc b/healthcare/2.18/modules/ROOT/pages/sfdc-data-cloud-setup-guide.adoc index c688a003a..127fa2b67 100644 --- a/healthcare/2.18/modules/ROOT/pages/sfdc-data-cloud-setup-guide.adoc +++ b/healthcare/2.18/modules/ROOT/pages/sfdc-data-cloud-setup-guide.adoc @@ -1,7 +1,7 @@ = Salesforce Data Cloud Setup Guide :hls-version: 2.18 -The following provides guidance on Salesforce Data Cloud setup required for the https://www.anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/mulesoft-accelerator-for-healthcare/minor/{hls-version}/pages/Use%20case%207%20-%20Population%20health%20management/[Population Health Management] use case. +The following provides guidance on Salesforce Data Cloud setup required for the https://www.anypoint.mulesoft.com/exchange/org.mule.examples/mulesoft-accelerator-for-healthcare/minor/{hls-version}/pages/Use%20case%207%20-%20Population%20health%20management/[Population Health Management] use case. * <> * <> @@ -25,7 +25,7 @@ Connectors are specialized data streams that communicate with external sources t Customer Data Platform has connectors for: Marketing Cloud Email Studio, MobileConnect, MobilePush, Marketing Cloud Data Extensions, for Salesforce CRM, Ingestion API, Interaction Studio, and for data outside Salesforce via cloud storage providers. -The https://www.anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/mulesoft-accelerator-for-healthcare/minor/{hls-version}/pages/Use%20case%207%20-%20Population%20health%20management/[Population Health Management] use case uses the following connectors to ingest data into cdp: +The https://www.anypoint.mulesoft.com/exchange/org.mule.examples/mulesoft-accelerator-for-healthcare/minor/{hls-version}/pages/Use%20case%207%20-%20Population%20health%20management/[Population Health Management] use case uses the following connectors to ingest data into cdp: * Salesforce CRM - to connect data from a Salesforce Health Cloud instance to Data Cloud * Ingestion API - to connect data from external source systems like Azure, Epic, Cerner, and other EHR systems via MuleSoft's CDP connector. @@ -50,7 +50,7 @@ Follow the below steps to create connection to your Salesforce Health Cloud org. After you create your Customer Data Platform instance and set up your Salesforce Health Cloud connection, you can install standard data bundles that are powered by data kits to deploy data within Customer Data Platform. -For the https://www.anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/mulesoft-accelerator-for-healthcare/minor/{hls-version}/pages/Use%20case%207%20-%20Population%20health%20management/[Population Health Management] use case, Service Cloud bundle is installed. Refer https://help.salesforce.com/s/articleView?id=sf.c360_a_install_standard_data_bundles_powered_by_data_kits.htm&type=5[link] to install the bundle. +For the https://www.anypoint.mulesoft.com/exchange/org.mule.examples/mulesoft-accelerator-for-healthcare/minor/{hls-version}/pages/Use%20case%207%20-%20Population%20health%20management/[Population Health Management] use case, Service Cloud bundle is installed. Refer https://help.salesforce.com/s/articleView?id=sf.c360_a_install_standard_data_bundles_powered_by_data_kits.htm&type=5[link] to install the bundle. === Ingestion API @@ -63,14 +63,14 @@ Follow the steps in each section below to setup and configure ingestion API to p . In Data Cloud, select Data Cloud Setup. . Click Ingestion API. . Click New, enter a name for the API source, then click Save. On the details page for the new connector, you must upload a schema file in OpenAPI (OAS) format with a `.yaml` file extension. The schema file describes how data transferred via the API is structured. *Note:* Ingestion API schemas have set requirements - review the schema requirements before ingestion. -. Click Upload Schema and navigate to the location of the file you want to use. Select the file and click Open. For the https://www.anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/mulesoft-accelerator-for-healthcare/minor/{hls-version}/pages/Use%20case%207%20-%20Population%20health%20management/[Population Health Management] use case the schema file `mule-hls-cdp-connector-schema.yaml` is available under `/src/test/resources` of the Implementation Template https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/hls-salesforce-cdp-sys-api[HLS CDP System API]. +. Click Upload Schema and navigate to the location of the file you want to use. Select the file and click Open. For the https://www.anypoint.mulesoft.com/exchange/org.mule.examples/mulesoft-accelerator-for-healthcare/minor/{hls-version}/pages/Use%20case%207%20-%20Population%20health%20management/[Population Health Management] use case the schema file `mule-hls-cdp-connector-schema.yaml` is available under `/src/test/resources` of the Implementation Template https://anypoint.mulesoft.com/exchange/org.mule.examples/hls-salesforce-cdp-sys-api[HLS CDP System API]. . Preview all the detected objects and their attributes in your schema. . Click Save. The connector page reflects the updated status. . After the schema file is uploaded, you can create data streams to begin sending data from your source system. -For the https://www.anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/mulesoft-accelerator-for-healthcare/minor/{hls-version}/pages/Use%20case%207%20-%20Population%20health%20management/[Population Health Management] use case, the external systems Azure, Epic, Cerner, and other EHR systems contain data to be pushed to Data Cloud through MuleSoft's CDP connector using the Ingestion API. The name of the Connector used will appear under `Ingestion API` drop down while creating a new Data Stream. +For the https://www.anypoint.mulesoft.com/exchange/org.mule.examples/mulesoft-accelerator-for-healthcare/minor/{hls-version}/pages/Use%20case%207%20-%20Population%20health%20management/[Population Health Management] use case, the external systems Azure, Epic, Cerner, and other EHR systems contain data to be pushed to Data Cloud through MuleSoft's CDP connector using the Ingestion API. The name of the Connector used will appear under `Ingestion API` drop down while creating a new Data Stream. -The schema used for the https://www.anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/mulesoft-accelerator-for-healthcare/minor/{hls-version}/pages/Use%20case%207%20-%20Population%20health%20management/[Population Health Management] use case can be found in the implementation template. The following objects are added for this use case: +The schema used for the https://www.anypoint.mulesoft.com/exchange/org.mule.examples/mulesoft-accelerator-for-healthcare/minor/{hls-version}/pages/Use%20case%207%20-%20Population%20health%20management/[Population Health Management] use case can be found in the implementation template. The following objects are added for this use case: * condition * immunization @@ -116,7 +116,7 @@ To create data streams from Salesforce CRM starter bundle: Refer this https://help.salesforce.com/s/articleView?id=sf.c360_a_create_crm_starter_bundle.htm&type=5[link] to create data streams using starter bundle to begin the flow of data from a Salesforce Health Cloud data source. -For the https://www.anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/mulesoft-accelerator-for-healthcare/minor/{hls-version}/pages/Use%20case%207%20-%20Population%20health%20management/[Population Health Management] use case, data streams for Salesforce Health Cloud Account and Contact objects are created using Salesforce CRM Service bundle. +For the https://www.anypoint.mulesoft.com/exchange/org.mule.examples/mulesoft-accelerator-for-healthcare/minor/{hls-version}/pages/Use%20case%207%20-%20Population%20health%20management/[Population Health Management] use case, data streams for Salesforce Health Cloud Account and Contact objects are created using Salesforce CRM Service bundle. To create data streams from Salesforce Health Cloud data source: @@ -134,11 +134,11 @@ To add permissions for objects and their fields: Repeat these steps for all objects and fields you want to ingest into Data Cloud. Now, create data streams for the required objects by following the steps in this https://help.salesforce.com/s/articleView?id=sf.c360_a_create_crm_data_stream.htm&type=5&language=en_US[link]. -For the https://www.anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/mulesoft-accelerator-for-healthcare/minor/{hls-version}/pages/Use%20case%207%20-%20Population%20health%20management/[Population Health Management] use case, data streams for Contact Point Objects, Identifier, and ContactContactRelation are created. +For the https://www.anypoint.mulesoft.com/exchange/org.mule.examples/mulesoft-accelerator-for-healthcare/minor/{hls-version}/pages/Use%20case%207%20-%20Population%20health%20management/[Population Health Management] use case, data streams for Contact Point Objects, Identifier, and ContactContactRelation are created. === Create an Ingestion API data stream -After uploading the schema file for Ingestion API Connector, create a data stream from your source objects. For the https://www.anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/mulesoft-accelerator-for-healthcare/minor/{hls-version}/pages/Use%20case%207%20-%20Population%20health%20management/[Population Health Management] use case, data streams for condition, immunization and webEngagement are created. +After uploading the schema file for Ingestion API Connector, create a data stream from your source objects. For the https://www.anypoint.mulesoft.com/exchange/org.mule.examples/mulesoft-accelerator-for-healthcare/minor/{hls-version}/pages/Use%20case%207%20-%20Population%20health%20management/[Population Health Management] use case, data streams for condition, immunization and webEngagement are created. . In Data Cloud, select Data Streams. . In recently viewed data streams, click New. @@ -147,7 +147,7 @@ After uploading the schema file for Ingestion API Connector, create a data strea . Check the objects found in the schema you want to use and click Next. . At the New Data Stream dialog box, configure the following: ** Primary Key: A true Primary Key needs to be leveraged for Data Cloud. If one does not exist, you will need to create a Formula Field for the Primary Key. - ** Category: Choose between Profile, Engagement or Other. *Note:* For the https://www.anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/mulesoft-accelerator-for-healthcare/minor/{hls-version}/pages/Use%20case%207%20-%20Population%20health%20management/[Population Health Management] use case, the category for all the objects in the schema are Other. + ** Category: Choose between Profile, Engagement or Other. *Note:* For the https://www.anypoint.mulesoft.com/exchange/org.mule.examples/mulesoft-accelerator-for-healthcare/minor/{hls-version}/pages/Use%20case%207%20-%20Population%20health%20management/[Population Health Management] use case, the category for all the objects in the schema are Other. ** Record Modified Date: To order Profile modifications, use the Record Modified Date. *Note:* A record modified field that indicates when each incoming record was last modified is required for Engagement object types. While the field requirement is optional for Profile and Other objects, it is encouraged to provide the record modified field to ensure incoming records are processed in the right order. ** Date Time Field: Used to represent when Engagement from an external source occurred at ingestion. ** Click the `New Formula Field` (Optional). @@ -156,7 +156,7 @@ After uploading the schema file for Ingestion API Connector, create a data strea . Click Deploy. If you have only created one data stream, the data stream's record page appears. If you've created multiple data streams, the view refreshes to show all recently viewed data streams. . Wait up to one hour for your data to appear in your data stream. Map your data stream to data model objects to start using your data. -For the https://www.anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/mulesoft-accelerator-for-healthcare/minor/{hls-version}/pages/Use%20case%207%20-%20Population%20health%20management/[Population Health Management] use case, data stream is created for the objects added in schema by following the steps above. At step 6, click `New Formula field` with `Field Label` as `uniqueId` with `Formula Return` Type as `Text`. Under `Transformation Formula`, the formula is created as below for each of the object. +For the https://www.anypoint.mulesoft.com/exchange/org.mule.examples/mulesoft-accelerator-for-healthcare/minor/{hls-version}/pages/Use%20case%207%20-%20Population%20health%20management/[Population Health Management] use case, data stream is created for the objects added in schema by following the steps above. At step 6, click `New Formula field` with `Field Label` as `uniqueId` with `Formula Return` Type as `Text`. Under `Transformation Formula`, the formula is created as below for each of the object. * condition: `CONCAT(sourceField['patientMrn'],"~",sourceField['conditionCode'])` * immunization: `CONCAT(sourceField['patientMrn'],"~",sourceField['vaccineCode'],"~",sourceField['vaccineStatus'],"~",sourceField['vaccineDate'])` @@ -178,9 +178,9 @@ As part of your Connected App set up for Ingestion API, you must select the foll The MuleSoft Connector for CDP provides customers a pipeline to send data into Data Cloud. This connector works with the Data Cloud Bulk and Streaming API, depending on the operation you configure. Each API call uses a request/response pattern over an HTTPS connection. All required request headers, error handling, and HTTPS connection configurations are built into the connector. -Refer to the https://dev-docs-internal.kqa.msap.io/beta-accelerators/salesforce-cdp-connector/1.1/[CDP Connector documentation] for additional details on configuration and available operations. +Refer to the https://docs.mulesoft.com/salesforce-cdp-connector/1.1/[CDP Connector documentation] for additional details on configuration and available operations. -For the https://www.anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/mulesoft-accelerator-for-healthcare/minor/{hls-version}/pages/Use%20case%207%20-%20Population%20health%20management/[Population Health Management] use case, refer to the https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/hls-salesforce-cdp-sys-api-spec/[HLS CDP System API] specification and https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/hls-salesforce-cdp-sys-api[HLS CDP System API] implementation template assets. +For the https://www.anypoint.mulesoft.com/exchange/org.mule.examples/mulesoft-accelerator-for-healthcare/minor/{hls-version}/pages/Use%20case%207%20-%20Population%20health%20management/[Population Health Management] use case, refer to the https://anypoint.mulesoft.com/exchange/org.mule.examples/hls-salesforce-cdp-sys-api-spec/[HLS CDP System API] specification and https://anypoint.mulesoft.com/exchange/org.mule.examples/hls-salesforce-cdp-sys-api[HLS CDP System API] implementation template assets. == Data modeling and data mapping @@ -220,7 +220,7 @@ Objects in the data model created by the customer for Data Cloud implementation When mapping your party area data, complete the required fields and relationships to successfully use Identity Resolution, Segmentation, and Activation. -Default mapping exists for Account and Contact Objects if service Bundle is used to create data streams. For the https://www.anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/mulesoft-accelerator-for-healthcare/minor/{hls-version}/pages/Use%20case%207%20-%20Population%20health%20management/[Population Health Management] use case, the default mapping from Account and Contact DSOs to Contact Point DMOs are removed. Data Streams to Data Model Objects (DMO) are mapped as per the below table. +Default mapping exists for Account and Contact Objects if service Bundle is used to create data streams. For the https://www.anypoint.mulesoft.com/exchange/org.mule.examples/mulesoft-accelerator-for-healthcare/minor/{hls-version}/pages/Use%20case%207%20-%20Population%20health%20management/[Population Health Management] use case, the default mapping from Account and Contact DSOs to Contact Point DMOs are removed. Data Streams to Data Model Objects (DMO) are mapped as per the below table. |=== | Data Stream Name (DSO) | Custom Data Model Object (DMO) | Standard Data Model Object (DMO) @@ -250,7 +250,7 @@ Default mapping exists for Account and Contact Objects if service Bundle is used | |=== -For the https://www.anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/mulesoft-accelerator-for-healthcare/minor/{hls-version}/pages/Use%20case%207%20-%20Population%20health%20management/[Population Health Management] use case, below Data Mappings are created between Data Streams and DMOs/custom DMOs. +For the https://www.anypoint.mulesoft.com/exchange/org.mule.examples/mulesoft-accelerator-for-healthcare/minor/{hls-version}/pages/Use%20case%207%20-%20Population%20health%20management/[Population Health Management] use case, below Data Mappings are created between Data Streams and DMOs/custom DMOs. *Data Mappings of Account Data Stream to Account DMO* @@ -490,7 +490,7 @@ Some of the mappings are added by default from Bundle. Mapping needs to be chang | userId |=== -For the https://www.anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/mulesoft-accelerator-for-healthcare/minor/{hls-version}/pages/Use%20case%207%20-%20Population%20health%20management/[Population Health Management] use case, below DMOs and relationships needs to be maintained when Data mappings are done between Data Stream and DMOs. +For the https://www.anypoint.mulesoft.com/exchange/org.mule.examples/mulesoft-accelerator-for-healthcare/minor/{hls-version}/pages/Use%20case%207%20-%20Population%20health%20management/[Population Health Management] use case, below DMOs and relationships needs to be maintained when Data mappings are done between Data Stream and DMOs. *Data Relationships between DMOs* @@ -542,7 +542,7 @@ For the https://www.anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10 == Identity Resolution -NOTE: For the https://www.anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/mulesoft-accelerator-for-healthcare/minor/{hls-version}/pages/Use%20case%207%20-%20Population%20health%20management/[Population Health Management] use case, identity resolution rulesets were not required. +NOTE: For the https://www.anypoint.mulesoft.com/exchange/org.mule.examples/mulesoft-accelerator-for-healthcare/minor/{hls-version}/pages/Use%20case%207%20-%20Population%20health%20management/[Population Health Management] use case, identity resolution rulesets were not required. Use identity resolution to consolidate data from difference sources into a comprehensive view of your customer called a unified profile. Identity resolution uses matching and reconciliation rules to link data about people into unified profiles. Each unified profile contains all the unique contact point values from all sources. @@ -550,7 +550,7 @@ Set up identity resolution rulesets after mapping source data to data model obje == Calculated Insights -NOTE: For the https://www.anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/mulesoft-accelerator-for-healthcare/minor/{hls-version}/pages/Use%20case%207%20-%20Population%20health%20management/[Population Health Management] use case, Calculated Insights were not required. +NOTE: For the https://www.anypoint.mulesoft.com/exchange/org.mule.examples/mulesoft-accelerator-for-healthcare/minor/{hls-version}/pages/Use%20case%207%20-%20Population%20health%20management/[Population Health Management] use case, Calculated Insights were not required. The Calculated Insights feature lets you define and calculate multidimensional metrics on your entire digital state stored in Salesforce Customer Data Platform. @@ -577,7 +577,7 @@ TIP: Leave the Publish Schedule as *Don't Refresh for now*, and then fill it in Segment On: Segment On defines the target entity (object) used to build your segment. For example, you can build a segment on Unified Individual or Account or Individual. You can choose any entity marked as type Profile during ingestion. -For the https://www.anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/mulesoft-accelerator-for-healthcare/minor/{hls-version}/pages/Use%20case%207%20-%20Population%20health%20management/[Population Health Management] use case, create Segments on Individual. +For the https://www.anypoint.mulesoft.com/exchange/org.mule.examples/mulesoft-accelerator-for-healthcare/minor/{hls-version}/pages/Use%20case%207%20-%20Population%20health%20management/[Population Health Management] use case, create Segments on Individual. Example segment: @@ -615,7 +615,7 @@ For the Publish Schedule, we update it to reflect a Publish Schedule of every 12 Create activation targets to build, and activate data segments with Data Cloud. -For the https://www.anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/mulesoft-accelerator-for-healthcare/minor/{hls-version}/pages/Use%20case%207%20-%20Population%20health%20management/[Population Health Management] use case, create a Marketing Cloud Activation Target. +For the https://www.anypoint.mulesoft.com/exchange/org.mule.examples/mulesoft-accelerator-for-healthcare/minor/{hls-version}/pages/Use%20case%207%20-%20Population%20health%20management/[Population Health Management] use case, create a Marketing Cloud Activation Target. *Activation Target - Marketing Cloud:* @@ -624,8 +624,8 @@ Before creating an activation target, configure the Marketing Cloud connector in . Click Setup gear icon and then Data Cloud Setup. . Select Marketing Cloud. . Enter the Credentials to authenticate your Marketing Cloud account. You can proceed with the next step in the setup only if the authentication is successful. -. Data Source setup - this step is optional. This needs to be set up if you are planning to ingest data from Marketing Cloud into Data Cloud. *Note:* For the https://www.anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/mulesoft-accelerator-for-healthcare/minor/{hls-version}/pages/Use%20case%207%20-%20Population%20health%20management/[Population Health Management] use case, this step is skipped. -. Select Business Units to activate - this step is optional. To add or remove business units (BU), click the arrows between the two columns. *Note:* For the https://www.anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/mulesoft-accelerator-for-healthcare/minor/{hls-version}/pages/Use%20case%207%20-%20Population%20health%20management/[Population Health Management] use case, select business units to publish segments to Marketing Cloud. +. Data Source setup - this step is optional. This needs to be set up if you are planning to ingest data from Marketing Cloud into Data Cloud. *Note:* For the https://www.anypoint.mulesoft.com/exchange/org.mule.examples/mulesoft-accelerator-for-healthcare/minor/{hls-version}/pages/Use%20case%207%20-%20Population%20health%20management/[Population Health Management] use case, this step is skipped. +. Select Business Units to activate - this step is optional. To add or remove business units (BU), click the arrows between the two columns. *Note:* For the https://www.anypoint.mulesoft.com/exchange/org.mule.examples/mulesoft-accelerator-for-healthcare/minor/{hls-version}/pages/Use%20case%207%20-%20Population%20health%20management/[Population Health Management] use case, select business units to publish segments to Marketing Cloud. Create an activation target in Data Cloud to publish segments to Marketing Cloud business units. diff --git a/healthcare/2.18/modules/ROOT/pages/sfdc-health-cloud-setup-guide.adoc b/healthcare/2.18/modules/ROOT/pages/sfdc-health-cloud-setup-guide.adoc index a4876f44d..b7bac4b99 100644 --- a/healthcare/2.18/modules/ROOT/pages/sfdc-health-cloud-setup-guide.adoc +++ b/healthcare/2.18/modules/ROOT/pages/sfdc-health-cloud-setup-guide.adoc @@ -41,13 +41,13 @@ This accelerator uses MuleSoft's HL7 Connector. If you're required to use custom * Modify the message structure schema file (for example, ADT_A31.esl) to include your custom segment (or modify an existing segment to fit your needs). * Modify the basedefs.esl file to include the changes for segment definitions. -The https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/hc-accelerator-sfdc-adt-api/[implementation template^] for storing ADT messages in Salesforce Health Cloud shows an example of custom segment processing. Please check the src/main/resources/config/hl7/v2_2 folder in the implementation template. This folder has the necessary changes required to process custom segment `ZG1`. +The https://anypoint.mulesoft.com/exchange/org.mule.examples/hc-accelerator-sfdc-adt-api/[implementation template^] for storing ADT messages in Salesforce Health Cloud shows an example of custom segment processing. Please check the src/main/resources/config/hl7/v2_2 folder in the implementation template. This folder has the necessary changes required to process custom segment `ZG1`. -For additional details on HL7 Connector, please refer to the https://dev-docs-internal.kqa.msap.io/beta-accelerators/connectors/hl7/hl7-connector[documentation^]. +For additional details on HL7 Connector, please refer to the https://docs.mulesoft.com/connectors/hl7/hl7-connector[documentation^]. == Maven POM Parent -In addition to some global settings and repository references, the Maven https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/accelerator-pom-parent-src/[POM parent^] config also defines the versions of all MuleSoft connectors and modules used by applications. Refer to the https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/accelerator-pom-parent-src/[Exchange documentation^] for information on how to make changes to the POM parent file. +In addition to some global settings and repository references, the Maven https://anypoint.mulesoft.com/exchange/org.mule.examples/accelerator-pom-parent-src/[POM parent^] config also defines the versions of all MuleSoft connectors and modules used by applications. Refer to the https://anypoint.mulesoft.com/exchange/org.mule.examples/accelerator-pom-parent-src/[Exchange documentation^] for information on how to make changes to the POM parent file. == See Also diff --git a/healthcare/2.18/modules/ROOT/pages/smart-fhir-okta.adoc b/healthcare/2.18/modules/ROOT/pages/smart-fhir-okta.adoc index 293f4ce13..809023dd4 100644 --- a/healthcare/2.18/modules/ROOT/pages/smart-fhir-okta.adoc +++ b/healthcare/2.18/modules/ROOT/pages/smart-fhir-okta.adoc @@ -1,6 +1,6 @@ = SMART on FHIR with Okta -See the https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/hc-accelerator-okta-smartfhir/[Okta SMART on FHIR - Implementation Template^] asset, which walks you through how to set up a reference SMART on FHIR implementation on Anypoint Platform using Okta as the identity provider. +See the https://anypoint.mulesoft.com/exchange/org.mule.examples/hc-accelerator-okta-smartfhir/[Okta SMART on FHIR - Implementation Template^] asset, which walks you through how to set up a reference SMART on FHIR implementation on Anypoint Platform using Okta as the identity provider. The **S**ubstitutable **M**edical **A**pplications and **R**eusable **T**echnology (SMART) is a web/mobile app, which is typically embedded in EHR but can also serve as a standalone smartphone app. SMART on FHIR provides a consistent approach to security and data requirements for health applications. It also provides a workflow to securely request access to data, receive the data, and use the data. @@ -20,13 +20,13 @@ SMART on FHIR addresses the following three key aspects: Anypoint platform supports SMART on FHIR in the following ways: * Identity and access management -** Provisioning third-party https://dev-docs-internal.kqa.msap.io/beta-accelerators/access-management/configure-client-management-openid-task[OIDC client provider^] like Okta for identity management -** Out-of-the-box https://dev-docs-internal.kqa.msap.io/beta-accelerators/api-manager/2.x/policy-openid-connect[OpenID Connect token enforcement policy^] +** Provisioning third-party https://docs.mulesoft.com/access-management/configure-client-management-openid-task[OIDC client provider^] like Okta for identity management +** Out-of-the-box https://docs.mulesoft.com/api-manager/2.x/policy-openid-connect[OpenID Connect token enforcement policy^] ** Leverage OAuth provider information in the `authentication` object for custom policy * Access to the data using FHIR based APIs ** MuleSoft Accelerator for Healthcare provides FHIR R4 specifications for all the FHIR resources -** Out-of-the-box https://dev-docs-internal.kqa.msap.io/beta-accelerators/api-manager/2.x/cors-policy[cross origin resource sharing (CORS) policy^] enables cross origin data exchange. +** Out-of-the-box https://docs.mulesoft.com/api-manager/2.x/cors-policy[cross origin resource sharing (CORS) policy^] enables cross origin data exchange. == See Also diff --git a/healthcare/2.18/modules/ROOT/pages/x12-fhir-converter.adoc b/healthcare/2.18/modules/ROOT/pages/x12-fhir-converter.adoc index 354475b59..69f9d3caa 100644 --- a/healthcare/2.18/modules/ROOT/pages/x12-fhir-converter.adoc +++ b/healthcare/2.18/modules/ROOT/pages/x12-fhir-converter.adoc @@ -1,10 +1,10 @@ = X12 to FHIR Converter -The https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/hls-fhir-to-x12-sys-api/[X12 to FHIR converter^] comes with a ready to use template for https://x12.org/[X12^] to FHIR conversion. This template can be extended or modified to meet specific conversion requirements. The converter converts FHIR R4 to X12 formats and its responses from X12 to FHIR R4. +The https://anypoint.mulesoft.com/exchange/org.mule.examples/hls-fhir-to-x12-sys-api/[X12 to FHIR converter^] comes with a ready to use template for https://x12.org/[X12^] to FHIR conversion. This template can be extended or modified to meet specific conversion requirements. The converter converts FHIR R4 to X12 formats and its responses from X12 to FHIR R4. == Functional Diagram -image:https://www.mulesoft.com/ext/solutions/draft/images/hls-x12-fhir-fx-diagram.svg[X12 to FHIR converter functional diagram,900,align="center"] +image:https://www.mulesoft.com/ext/solutions/images/hls-x12-fhir-fx-diagram.svg[X12 to FHIR converter functional diagram,900,align="center"] == Advantages diff --git a/healthcare/2.19/modules/ROOT/pages/ccda-fhir-converter.adoc b/healthcare/2.19/modules/ROOT/pages/ccda-fhir-converter.adoc index 11b76cb60..134619070 100644 --- a/healthcare/2.19/modules/ROOT/pages/ccda-fhir-converter.adoc +++ b/healthcare/2.19/modules/ROOT/pages/ccda-fhir-converter.adoc @@ -1,10 +1,10 @@ = C-CDA to FHIR Converter -The https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/hls-ccda-to-fhir-sys-api/[C-CDA to FHIR converter] comes with a ready to use template for https://www.hl7.org/implement/standards/product_brief.cfm?product_id=496[CDA] to FHIR conversion. This template can be extended or modified to meet specific conversion requirements. +The https://anypoint.mulesoft.com/exchange/org.mule.examples/hls-ccda-to-fhir-sys-api/[C-CDA to FHIR converter] comes with a ready to use template for https://www.hl7.org/implement/standards/product_brief.cfm?product_id=496[CDA] to FHIR conversion. This template can be extended or modified to meet specific conversion requirements. == Functional diagram -image:https://www.mulesoft.com/ext/solutions/draft/images/hls-ccda-fhir-fx-diagram.svg[CDA to FHIR converter functional diagram,900,align="center"] +image:https://www.mulesoft.com/ext/solutions/images/hls-ccda-fhir-fx-diagram.svg[CDA to FHIR converter functional diagram,900,align="center"] == Advantages diff --git a/healthcare/2.19/modules/ROOT/pages/fhir-r4-assets.adoc b/healthcare/2.19/modules/ROOT/pages/fhir-r4-assets.adoc index 134ba48f5..10d431db8 100644 --- a/healthcare/2.19/modules/ROOT/pages/fhir-r4-assets.adoc +++ b/healthcare/2.19/modules/ROOT/pages/fhir-r4-assets.adoc @@ -2,11 +2,11 @@ The following are a collection of assets to support MuleSoft customers who are developing Fast Healthcare Interoperability Resources (FHIR) APIs using MuleSoft. Visit the https://www.hl7.org/fhir/[official HL7 website] for more information. -* https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/hls-fhirjson-to-raml-sys-api-spec/[FHIR RAML auto-generator] - Utility to generate RAML specification(s) for FHIR resources directly from the JSON schema provided by HL7. +* https://anypoint.mulesoft.com/exchange/org.mule.examples/hls-fhirjson-to-raml-sys-api-spec/[FHIR RAML auto-generator] - Utility to generate RAML specification(s) for FHIR resources directly from the JSON schema provided by HL7. * xref:fhir-r4-us-core-profiles.adoc[FHIR R4 US Core Profile Assets] * xref:fhir-r4-resources.adoc[FHIR R4 Resources List] -* https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fhir-error-policy/[FHIR Error API Policy] - Captures error responses and formats them in an FHIR OperationOutcome-compliant format, since Anypoint Platform's out-of-the-box (OOTB) policies do not provide error messages in an FHIR-compliant format. This policy can also be used with other OOTB API policies provided in Anypoint Platform, such as OAuth or JWT. -* https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/hc-accelerator-okta-smartfhir/[Okta SMART on FHIR^] - Implementation template that walks you through how to set up a reference SMART on FHIR implementation on Anypoint Platform using Okta as the identity provider. +* https://anypoint.mulesoft.com/exchange/org.mule.examples/fhir-error-policy/[FHIR Error API Policy] - Captures error responses and formats them in an FHIR OperationOutcome-compliant format, since Anypoint Platform's out-of-the-box (OOTB) policies do not provide error messages in an FHIR-compliant format. This policy can also be used with other OOTB API policies provided in Anypoint Platform, such as OAuth or JWT. +* https://anypoint.mulesoft.com/exchange/org.mule.examples/hc-accelerator-okta-smartfhir/[Okta SMART on FHIR^] - Implementation template that walks you through how to set up a reference SMART on FHIR implementation on Anypoint Platform using Okta as the identity provider. == See Also diff --git a/healthcare/2.19/modules/ROOT/pages/fhir-r4-resources.adoc b/healthcare/2.19/modules/ROOT/pages/fhir-r4-resources.adoc index 062796d38..8414363f1 100644 --- a/healthcare/2.19/modules/ROOT/pages/fhir-r4-resources.adoc +++ b/healthcare/2.19/modules/ROOT/pages/fhir-r4-resources.adoc @@ -2,7 +2,7 @@ The MuleSoft Accelerator for Healthcare provides a library of United States Core Data for Interoperability (USCDI) and FHIR R4 resources to help healthcare developers adhere to interoperability needs and jumpstart the development of healthcare digital transformation initiatives. -You can also use the https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fhir-error-policy/[FHIR Error API Policy] to capture error responses and format them in an FHIR OperationOutcome-compliant format, since Anypoint Platform's out-of-the-box (OOTB) policies do not provide error messages in an FHIR-compliant format. This policy can also be used with other OOTB API policies provided in Anypoint Platform, such as OAuth or JWT. +You can also use the https://anypoint.mulesoft.com/exchange/org.mule.examples/fhir-error-policy/[FHIR Error API Policy] to capture error responses and format them in an FHIR OperationOutcome-compliant format, since Anypoint Platform's out-of-the-box (OOTB) policies do not provide error messages in an FHIR-compliant format. This policy can also be used with other OOTB API policies provided in Anypoint Platform, such as OAuth or JWT. For the list of US core profile assets, please refer to xref:fhir-r4-us-core-profiles.adoc[this link]. @@ -15,339 +15,339 @@ _API specifications, data types, and libraries built to meet compliance with FHI | Category| Library | API Specification .^| Foundation - Confirmance -| https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fhir-r4-capabilitystatement-library/[CapabilityStatement] ^[N]^ + -https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fhir-r4-structuredefinition-library/[StructureDefinition] ^[N]^ + -https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fhir-r4-implementationguide-library/[ImplementationGuide] + -https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fhir-r4-searchparameter-library/[SearchParameter] + -https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fhir-r4-operationdefinition-library/[OperationDefinition] ^[N]^ + -https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fhir-r4-compartmentdefinition-library/[CompartmentDefinition] + -https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fhir-r4-messagedefinition-library/[MessageDefinition] + -https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fhir-r4-structuremap-library/[StructureMap] + -https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fhir-r4-graphdefinition-library/[GraphDefinition] + -https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fhir-r4-examplescenario-library/[ExampleScenario] -| https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fhir-r4-capabilitystatement-api/[CapabilityStatement] ^[N]^ + -https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fhir-r4-structuredefinition-api/[StructureDefinition] ^[N]^ + -https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fhir-r4-implementationguide-api/[ImplementationGuide] + -https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fhir-r4-searchparameter-api/[SearchParameter] + -https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fhir-r4-operationdefinition-api/[OperationDefinition] ^[N]^ + -https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fhir-r4-compartmentdefinition-api/[CompartmentDefinition] + -https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fhir-r4-messagedefinition-api/[MessageDefinition] + -https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fhir-r4-structuremap-api/[StructureMap] + -https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fhir-r4-graphdefinition-api/[GraphDefinition] + -https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fhir-r4-examplescenario-api/[ExampleScenario] +| https://anypoint.mulesoft.com/exchange/org.mule.examples/fhir-r4-capabilitystatement-library/[CapabilityStatement] ^[N]^ + +https://anypoint.mulesoft.com/exchange/org.mule.examples/fhir-r4-structuredefinition-library/[StructureDefinition] ^[N]^ + +https://anypoint.mulesoft.com/exchange/org.mule.examples/fhir-r4-implementationguide-library/[ImplementationGuide] + +https://anypoint.mulesoft.com/exchange/org.mule.examples/fhir-r4-searchparameter-library/[SearchParameter] + +https://anypoint.mulesoft.com/exchange/org.mule.examples/fhir-r4-operationdefinition-library/[OperationDefinition] ^[N]^ + +https://anypoint.mulesoft.com/exchange/org.mule.examples/fhir-r4-compartmentdefinition-library/[CompartmentDefinition] + +https://anypoint.mulesoft.com/exchange/org.mule.examples/fhir-r4-messagedefinition-library/[MessageDefinition] + +https://anypoint.mulesoft.com/exchange/org.mule.examples/fhir-r4-structuremap-library/[StructureMap] + +https://anypoint.mulesoft.com/exchange/org.mule.examples/fhir-r4-graphdefinition-library/[GraphDefinition] + +https://anypoint.mulesoft.com/exchange/org.mule.examples/fhir-r4-examplescenario-library/[ExampleScenario] +| https://anypoint.mulesoft.com/exchange/org.mule.examples/fhir-r4-capabilitystatement-api/[CapabilityStatement] ^[N]^ + +https://anypoint.mulesoft.com/exchange/org.mule.examples/fhir-r4-structuredefinition-api/[StructureDefinition] ^[N]^ + +https://anypoint.mulesoft.com/exchange/org.mule.examples/fhir-r4-implementationguide-api/[ImplementationGuide] + +https://anypoint.mulesoft.com/exchange/org.mule.examples/fhir-r4-searchparameter-api/[SearchParameter] + +https://anypoint.mulesoft.com/exchange/org.mule.examples/fhir-r4-operationdefinition-api/[OperationDefinition] ^[N]^ + +https://anypoint.mulesoft.com/exchange/org.mule.examples/fhir-r4-compartmentdefinition-api/[CompartmentDefinition] + +https://anypoint.mulesoft.com/exchange/org.mule.examples/fhir-r4-messagedefinition-api/[MessageDefinition] + +https://anypoint.mulesoft.com/exchange/org.mule.examples/fhir-r4-structuremap-api/[StructureMap] + +https://anypoint.mulesoft.com/exchange/org.mule.examples/fhir-r4-graphdefinition-api/[GraphDefinition] + +https://anypoint.mulesoft.com/exchange/org.mule.examples/fhir-r4-examplescenario-api/[ExampleScenario] .^| Foundation - Terminology -| https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fhir-r4-codesystem-library/[CodeSystem] ^[N]^ + -https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fhir-r4-valueset-library/[ValueSet] ^[N]^ + -https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fhir-r4-conceptmap-library/[ConceptMap] + -https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fhir-r4-namingsystem-library/[NamingSystem] + -https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fhir-r4-terminologycapabilities-library/[TerminologiesCapabilities] -| https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fhir-r4-codesystem-api/[CodeSystem] ^[N]^ + -https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fhir-r4-valueset-api/[ValueSet] ^[N]^ + -https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fhir-r4-conceptmap-api/[ConceptMap] + -https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fhir-r4-namingsystem-api/[NamingSystem] + -https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fhir-r4-terminologycapabilities-api/[TerminologiesCapabilities] +| https://anypoint.mulesoft.com/exchange/org.mule.examples/fhir-r4-codesystem-library/[CodeSystem] ^[N]^ + +https://anypoint.mulesoft.com/exchange/org.mule.examples/fhir-r4-valueset-library/[ValueSet] ^[N]^ + +https://anypoint.mulesoft.com/exchange/org.mule.examples/fhir-r4-conceptmap-library/[ConceptMap] + +https://anypoint.mulesoft.com/exchange/org.mule.examples/fhir-r4-namingsystem-library/[NamingSystem] + +https://anypoint.mulesoft.com/exchange/org.mule.examples/fhir-r4-terminologycapabilities-library/[TerminologiesCapabilities] +| https://anypoint.mulesoft.com/exchange/org.mule.examples/fhir-r4-codesystem-api/[CodeSystem] ^[N]^ + +https://anypoint.mulesoft.com/exchange/org.mule.examples/fhir-r4-valueset-api/[ValueSet] ^[N]^ + +https://anypoint.mulesoft.com/exchange/org.mule.examples/fhir-r4-conceptmap-api/[ConceptMap] + +https://anypoint.mulesoft.com/exchange/org.mule.examples/fhir-r4-namingsystem-api/[NamingSystem] + +https://anypoint.mulesoft.com/exchange/org.mule.examples/fhir-r4-terminologycapabilities-api/[TerminologiesCapabilities] .^| Foundation - Security -| https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fhir-r4-provenance-library/[Provenance] + -https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fhir-r4-auditevent-library/[AuditEvent] + -https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fhir-r4-consent-library/[Consent] -| https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fhir-r4-provenance-api/[Provenance] + -https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fhir-r4-auditevent-api/[AuditEvent] + -https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fhir-r4-consent-api/[Consent] +| https://anypoint.mulesoft.com/exchange/org.mule.examples/fhir-r4-provenance-library/[Provenance] + +https://anypoint.mulesoft.com/exchange/org.mule.examples/fhir-r4-auditevent-library/[AuditEvent] + +https://anypoint.mulesoft.com/exchange/org.mule.examples/fhir-r4-consent-library/[Consent] +| https://anypoint.mulesoft.com/exchange/org.mule.examples/fhir-r4-provenance-api/[Provenance] + +https://anypoint.mulesoft.com/exchange/org.mule.examples/fhir-r4-auditevent-api/[AuditEvent] + +https://anypoint.mulesoft.com/exchange/org.mule.examples/fhir-r4-consent-api/[Consent] .^| Foundation - Documents -| https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fhir-r4-composition-library/[Composition] + -https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fhir-r4-documentmanifest-library/[DocumentManifest] + -https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fhir-r4-documentreference-library/[DocumentReference] + -https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fhir-r4-catalogentry-library/[CatalogEntry] -| https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fhir-r4-composition-api/[Composition] + -https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fhir-r4-documentmanifest-api/[DocumentManifest] + -https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fhir-r4-documentreference-api/[DocumentReference] + -https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fhir-r4-catalogentry-api/[CatalogEntry] +| https://anypoint.mulesoft.com/exchange/org.mule.examples/fhir-r4-composition-library/[Composition] + +https://anypoint.mulesoft.com/exchange/org.mule.examples/fhir-r4-documentmanifest-library/[DocumentManifest] + +https://anypoint.mulesoft.com/exchange/org.mule.examples/fhir-r4-documentreference-library/[DocumentReference] + +https://anypoint.mulesoft.com/exchange/org.mule.examples/fhir-r4-catalogentry-library/[CatalogEntry] +| https://anypoint.mulesoft.com/exchange/org.mule.examples/fhir-r4-composition-api/[Composition] + +https://anypoint.mulesoft.com/exchange/org.mule.examples/fhir-r4-documentmanifest-api/[DocumentManifest] + +https://anypoint.mulesoft.com/exchange/org.mule.examples/fhir-r4-documentreference-api/[DocumentReference] + +https://anypoint.mulesoft.com/exchange/org.mule.examples/fhir-r4-catalogentry-api/[CatalogEntry] .^| Foundation - Other -| https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fhir-r4-basic-library/[Basic] + -https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fhir-r4-binary-library/[Binary] ^[N]^ + -https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fhir-r4-linkage-library/[Linkage] + -https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fhir-r4-messageheader-library/[MessageHeader] + -https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fhir-r4-parameters-library/[Parameters] ^[N]^ + -https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fhir-r4-subscription-library/[Subscription] + +| https://anypoint.mulesoft.com/exchange/org.mule.examples/fhir-r4-basic-library/[Basic] + +https://anypoint.mulesoft.com/exchange/org.mule.examples/fhir-r4-binary-library/[Binary] ^[N]^ + +https://anypoint.mulesoft.com/exchange/org.mule.examples/fhir-r4-linkage-library/[Linkage] + +https://anypoint.mulesoft.com/exchange/org.mule.examples/fhir-r4-messageheader-library/[MessageHeader] + +https://anypoint.mulesoft.com/exchange/org.mule.examples/fhir-r4-parameters-library/[Parameters] ^[N]^ + +https://anypoint.mulesoft.com/exchange/org.mule.examples/fhir-r4-subscription-library/[Subscription] + ++++++ -| https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fhir-r4-basic-api/[Basic] + -https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fhir-r4-binary-api/[Binary] ^[N]^ + -https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fhir-r4-linkage-api/[Linkage] + -https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fhir-r4-messageheader-api/[MessageHeader] + -https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fhir-r4-parameters-api/[Parameters] ^[N]^ + -https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fhir-r4-subscription-api/[Subscription] +| https://anypoint.mulesoft.com/exchange/org.mule.examples/fhir-r4-basic-api/[Basic] + +https://anypoint.mulesoft.com/exchange/org.mule.examples/fhir-r4-binary-api/[Binary] ^[N]^ + +https://anypoint.mulesoft.com/exchange/org.mule.examples/fhir-r4-linkage-api/[Linkage] + +https://anypoint.mulesoft.com/exchange/org.mule.examples/fhir-r4-messageheader-api/[MessageHeader] + +https://anypoint.mulesoft.com/exchange/org.mule.examples/fhir-r4-parameters-api/[Parameters] ^[N]^ + +https://anypoint.mulesoft.com/exchange/org.mule.examples/fhir-r4-subscription-api/[Subscription] .^| Base - Individuals -| https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fhir-r4-patient-library/[Patient] ^[N]^ + -https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fhir-r4-practitioner-library/[Practitioner] + -https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fhir-r4-practitionerrole-library/[PractitionerRole] + -https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fhir-r4-relatedperson-library/[RelatedPerson] + -https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fhir-r4-person-library/[Person] + -https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fhir-r4-group-library/[Group] + +| https://anypoint.mulesoft.com/exchange/org.mule.examples/fhir-r4-patient-library/[Patient] ^[N]^ + +https://anypoint.mulesoft.com/exchange/org.mule.examples/fhir-r4-practitioner-library/[Practitioner] + +https://anypoint.mulesoft.com/exchange/org.mule.examples/fhir-r4-practitionerrole-library/[PractitionerRole] + +https://anypoint.mulesoft.com/exchange/org.mule.examples/fhir-r4-relatedperson-library/[RelatedPerson] + +https://anypoint.mulesoft.com/exchange/org.mule.examples/fhir-r4-person-library/[Person] + +https://anypoint.mulesoft.com/exchange/org.mule.examples/fhir-r4-group-library/[Group] + ++++++ -| https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fhir-r4-patient-api/[Patient] ^[N]^ + -https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fhir-r4-practitioner-api/[Practitioner] + -https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fhir-r4-practitionerrole-api/[PractitionerRole] + -https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fhir-r4-relatedperson-api/[RelatedPerson] + -https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fhir-r4-person-api/[Person] + -https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fhir-r4-group-api/[Group] +| https://anypoint.mulesoft.com/exchange/org.mule.examples/fhir-r4-patient-api/[Patient] ^[N]^ + +https://anypoint.mulesoft.com/exchange/org.mule.examples/fhir-r4-practitioner-api/[Practitioner] + +https://anypoint.mulesoft.com/exchange/org.mule.examples/fhir-r4-practitionerrole-api/[PractitionerRole] + +https://anypoint.mulesoft.com/exchange/org.mule.examples/fhir-r4-relatedperson-api/[RelatedPerson] + +https://anypoint.mulesoft.com/exchange/org.mule.examples/fhir-r4-person-api/[Person] + +https://anypoint.mulesoft.com/exchange/org.mule.examples/fhir-r4-group-api/[Group] .^| Base - Entities #1 -| https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fhir-r4-organization-library/[Organization] + -https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fhir-r4-organizationaffiliation-library/[OrganizationAffiliation] + -https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fhir-r4-healthcareservice-library/[HealthcareService] + -https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fhir-r4-endpoint-library/[Endpoint] + -https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fhir-r4-location-library/[Location] + +| https://anypoint.mulesoft.com/exchange/org.mule.examples/fhir-r4-organization-library/[Organization] + +https://anypoint.mulesoft.com/exchange/org.mule.examples/fhir-r4-organizationaffiliation-library/[OrganizationAffiliation] + +https://anypoint.mulesoft.com/exchange/org.mule.examples/fhir-r4-healthcareservice-library/[HealthcareService] + +https://anypoint.mulesoft.com/exchange/org.mule.examples/fhir-r4-endpoint-library/[Endpoint] + +https://anypoint.mulesoft.com/exchange/org.mule.examples/fhir-r4-location-library/[Location] + ++++++ -| https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fhir-r4-organization-api/[Organization] + -https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fhir-r4-organizationaffiliation-api/[OrganizationAffiliation] + -https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fhir-r4-healthcareservice-api/[HealthcareService] + -https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fhir-r4-endpoint-api/[Endpoint] + -https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fhir-r4-location-api/[Location] +| https://anypoint.mulesoft.com/exchange/org.mule.examples/fhir-r4-organization-api/[Organization] + +https://anypoint.mulesoft.com/exchange/org.mule.examples/fhir-r4-organizationaffiliation-api/[OrganizationAffiliation] + +https://anypoint.mulesoft.com/exchange/org.mule.examples/fhir-r4-healthcareservice-api/[HealthcareService] + +https://anypoint.mulesoft.com/exchange/org.mule.examples/fhir-r4-endpoint-api/[Endpoint] + +https://anypoint.mulesoft.com/exchange/org.mule.examples/fhir-r4-location-api/[Location] .^| Base - Entities #2 -| https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fhir-r4-substance-library/[Substance] + -https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fhir-r4-biologicallyderivedproduct-library/[BiologicallyDerivedProduct #] + -https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fhir-r4-device-library/[Device] + -https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fhir-r4-devicemetric-library/[DeviceMetric] + +| https://anypoint.mulesoft.com/exchange/org.mule.examples/fhir-r4-substance-library/[Substance] + +https://anypoint.mulesoft.com/exchange/org.mule.examples/fhir-r4-biologicallyderivedproduct-library/[BiologicallyDerivedProduct #] + +https://anypoint.mulesoft.com/exchange/org.mule.examples/fhir-r4-device-library/[Device] + +https://anypoint.mulesoft.com/exchange/org.mule.examples/fhir-r4-devicemetric-library/[DeviceMetric] + ++++++ -| https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fhir-r4-substance-api/[Substance] + -https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fhir-r4-biologicallyderivedproduct-api/[BiologicallyDerivedProduct #] + -https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fhir-r4-device-api/[Device] + -https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fhir-r4-devicemetric-api/[DeviceMetric] +| https://anypoint.mulesoft.com/exchange/org.mule.examples/fhir-r4-substance-api/[Substance] + +https://anypoint.mulesoft.com/exchange/org.mule.examples/fhir-r4-biologicallyderivedproduct-api/[BiologicallyDerivedProduct #] + +https://anypoint.mulesoft.com/exchange/org.mule.examples/fhir-r4-device-api/[Device] + +https://anypoint.mulesoft.com/exchange/org.mule.examples/fhir-r4-devicemetric-api/[DeviceMetric] .^| Base - Workflow -| https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fhir-r4-task-library/[Task] + -https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fhir-r4-appointment-library/[Appointment] + -https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fhir-r4-appointmentresponse-library/[AppointmentResponse] + -https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fhir-r4-schedule-library/[Schedule] + -https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fhir-r4-slot-library/[Slot] + -https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fhir-r4-verificationresult-library/[VerificationResult] -| https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fhir-r4-task-api/[Task] + -https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fhir-r4-appointment-api/[Appointment] + -https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fhir-r4-appointmentresponse-api/[AppointmentResponse] + -https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fhir-r4-schedule-api/[Schedule] + -https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fhir-r4-slot-api/[Slot] + -https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fhir-r4-verificationresult-api/[VerificationResult] +| https://anypoint.mulesoft.com/exchange/org.mule.examples/fhir-r4-task-library/[Task] + +https://anypoint.mulesoft.com/exchange/org.mule.examples/fhir-r4-appointment-library/[Appointment] + +https://anypoint.mulesoft.com/exchange/org.mule.examples/fhir-r4-appointmentresponse-library/[AppointmentResponse] + +https://anypoint.mulesoft.com/exchange/org.mule.examples/fhir-r4-schedule-library/[Schedule] + +https://anypoint.mulesoft.com/exchange/org.mule.examples/fhir-r4-slot-library/[Slot] + +https://anypoint.mulesoft.com/exchange/org.mule.examples/fhir-r4-verificationresult-library/[VerificationResult] +| https://anypoint.mulesoft.com/exchange/org.mule.examples/fhir-r4-task-api/[Task] + +https://anypoint.mulesoft.com/exchange/org.mule.examples/fhir-r4-appointment-api/[Appointment] + +https://anypoint.mulesoft.com/exchange/org.mule.examples/fhir-r4-appointmentresponse-api/[AppointmentResponse] + +https://anypoint.mulesoft.com/exchange/org.mule.examples/fhir-r4-schedule-api/[Schedule] + +https://anypoint.mulesoft.com/exchange/org.mule.examples/fhir-r4-slot-api/[Slot] + +https://anypoint.mulesoft.com/exchange/org.mule.examples/fhir-r4-verificationresult-api/[VerificationResult] .^| Base - Management -| https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fhir-r4-encounter-library/[Encounter] + -https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fhir-r4-episodeofcare-library/[EpisodeOfCare] + -https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fhir-r4-flag-library/[Flag] + -https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fhir-r4-list-library/[List] + -https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fhir-r4-library-library/[Library] -| https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fhir-r4-encounter-api/[Encounter] + -https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fhir-r4-episodeofcare-api/[EpisodeOfCare] + -https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fhir-r4-flag-api/[Flag] + -https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fhir-r4-list-api/[List] + -https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fhir-r4-library-api/[Library] +| https://anypoint.mulesoft.com/exchange/org.mule.examples/fhir-r4-encounter-library/[Encounter] + +https://anypoint.mulesoft.com/exchange/org.mule.examples/fhir-r4-episodeofcare-library/[EpisodeOfCare] + +https://anypoint.mulesoft.com/exchange/org.mule.examples/fhir-r4-flag-library/[Flag] + +https://anypoint.mulesoft.com/exchange/org.mule.examples/fhir-r4-list-library/[List] + +https://anypoint.mulesoft.com/exchange/org.mule.examples/fhir-r4-library-library/[Library] +| https://anypoint.mulesoft.com/exchange/org.mule.examples/fhir-r4-encounter-api/[Encounter] + +https://anypoint.mulesoft.com/exchange/org.mule.examples/fhir-r4-episodeofcare-api/[EpisodeOfCare] + +https://anypoint.mulesoft.com/exchange/org.mule.examples/fhir-r4-flag-api/[Flag] + +https://anypoint.mulesoft.com/exchange/org.mule.examples/fhir-r4-list-api/[List] + +https://anypoint.mulesoft.com/exchange/org.mule.examples/fhir-r4-library-api/[Library] .^| Clinical - Summary -| https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fhir-r4-allergyintolerance-library/[AllergyIntolerance] + -https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fhir-r4-adverseevent-library/[AdverseEvent] + -https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fhir-r4-condition-library/[Condition(Problem)] + -https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fhir-r4-procedure-library/[Procedure] + -https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fhir-r4-familymemberhistory-library/[FamilyMemberHistory] + -https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fhir-r4-clinicalimpression-library/[ClinicalImpression #] + -https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fhir-r4-clinicalimpression-library/[Note] + -https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fhir-r4-detectedissue-library/[DetectedIssue] -| https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fhir-r4-allergyintolerance-api/[AllergyIntolerance] + -https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fhir-r4-adverseevent-api/[AdverseEvent] + -https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fhir-r4-condition-api/[Condition(Problem)] + -https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fhir-r4-procedure-api/[Procedure] + -https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fhir-r4-familymemberhistory-api/[FamilyMemberHistory] + -https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fhir-r4-clinicalimpression-api/[ClinicalImpression #] + -https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fhir-r4-clinicalimpression-api/[Note] + -https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fhir-r4-detectedissue-api/[DetectedIssue] +| https://anypoint.mulesoft.com/exchange/org.mule.examples/fhir-r4-allergyintolerance-library/[AllergyIntolerance] + +https://anypoint.mulesoft.com/exchange/org.mule.examples/fhir-r4-adverseevent-library/[AdverseEvent] + +https://anypoint.mulesoft.com/exchange/org.mule.examples/fhir-r4-condition-library/[Condition(Problem)] + +https://anypoint.mulesoft.com/exchange/org.mule.examples/fhir-r4-procedure-library/[Procedure] + +https://anypoint.mulesoft.com/exchange/org.mule.examples/fhir-r4-familymemberhistory-library/[FamilyMemberHistory] + +https://anypoint.mulesoft.com/exchange/org.mule.examples/fhir-r4-clinicalimpression-library/[ClinicalImpression #] + +https://anypoint.mulesoft.com/exchange/org.mule.examples/fhir-r4-clinicalimpression-library/[Note] + +https://anypoint.mulesoft.com/exchange/org.mule.examples/fhir-r4-detectedissue-library/[DetectedIssue] +| https://anypoint.mulesoft.com/exchange/org.mule.examples/fhir-r4-allergyintolerance-api/[AllergyIntolerance] + +https://anypoint.mulesoft.com/exchange/org.mule.examples/fhir-r4-adverseevent-api/[AdverseEvent] + +https://anypoint.mulesoft.com/exchange/org.mule.examples/fhir-r4-condition-api/[Condition(Problem)] + +https://anypoint.mulesoft.com/exchange/org.mule.examples/fhir-r4-procedure-api/[Procedure] + +https://anypoint.mulesoft.com/exchange/org.mule.examples/fhir-r4-familymemberhistory-api/[FamilyMemberHistory] + +https://anypoint.mulesoft.com/exchange/org.mule.examples/fhir-r4-clinicalimpression-api/[ClinicalImpression #] + +https://anypoint.mulesoft.com/exchange/org.mule.examples/fhir-r4-clinicalimpression-api/[Note] + +https://anypoint.mulesoft.com/exchange/org.mule.examples/fhir-r4-detectedissue-api/[DetectedIssue] .^| Clinical - Diagnostics -| https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fhir-r4-observation-library/[Observation] ^[N]^ + -https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fhir-r4-media-library/[Media] ^[u]^ + -https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fhir-r4-diagnosticreport-library/[DiagnosticReport] + -https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fhir-r4-specimen-library/[Specimen] + -https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fhir-r4-bodystructure-library/[BodyStructure] + -https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fhir-r4-imagingstudy-library/[ImagingStudy] + -https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fhir-r4-questionnaireresponse-library/[QuestionnaireResponse ] + -https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fhir-r4-molecularsequence-library/[MolecularSequence] -| https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fhir-r4-observation-api/[Observation] ^[N]^ + -https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fhir-r4-media-api/[Media] ^[u]^ + -https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fhir-r4-diagnosticreport-api/[DiagnosticReport] + -https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fhir-r4-specimen-api/[Specimen] + -https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fhir-r4-bodystructure-api/[BodyStructure] + -https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fhir-r4-imagingstudy-api/[ImagingStudy] + -https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fhir-r4-questionnaireresponse-api/[QuestionnaireResponse ] + -https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fhir-r4-molecularsequence-api/[MolecularSequence] +| https://anypoint.mulesoft.com/exchange/org.mule.examples/fhir-r4-observation-library/[Observation] ^[N]^ + +https://anypoint.mulesoft.com/exchange/org.mule.examples/fhir-r4-media-library/[Media] ^[u]^ + +https://anypoint.mulesoft.com/exchange/org.mule.examples/fhir-r4-diagnosticreport-library/[DiagnosticReport] + +https://anypoint.mulesoft.com/exchange/org.mule.examples/fhir-r4-specimen-library/[Specimen] + +https://anypoint.mulesoft.com/exchange/org.mule.examples/fhir-r4-bodystructure-library/[BodyStructure] + +https://anypoint.mulesoft.com/exchange/org.mule.examples/fhir-r4-imagingstudy-library/[ImagingStudy] + +https://anypoint.mulesoft.com/exchange/org.mule.examples/fhir-r4-questionnaireresponse-library/[QuestionnaireResponse ] + +https://anypoint.mulesoft.com/exchange/org.mule.examples/fhir-r4-molecularsequence-library/[MolecularSequence] +| https://anypoint.mulesoft.com/exchange/org.mule.examples/fhir-r4-observation-api/[Observation] ^[N]^ + +https://anypoint.mulesoft.com/exchange/org.mule.examples/fhir-r4-media-api/[Media] ^[u]^ + +https://anypoint.mulesoft.com/exchange/org.mule.examples/fhir-r4-diagnosticreport-api/[DiagnosticReport] + +https://anypoint.mulesoft.com/exchange/org.mule.examples/fhir-r4-specimen-api/[Specimen] + +https://anypoint.mulesoft.com/exchange/org.mule.examples/fhir-r4-bodystructure-api/[BodyStructure] + +https://anypoint.mulesoft.com/exchange/org.mule.examples/fhir-r4-imagingstudy-api/[ImagingStudy] + +https://anypoint.mulesoft.com/exchange/org.mule.examples/fhir-r4-questionnaireresponse-api/[QuestionnaireResponse ] + +https://anypoint.mulesoft.com/exchange/org.mule.examples/fhir-r4-molecularsequence-api/[MolecularSequence] .^| Clinical - Medications -| https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fhir-r4-medicationrequest-library/[MedicationRequest] + -https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fhir-r4-medicationadministration-library/[MedicationAdministration] + -https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fhir-r4-medicationdispense-library/[MedicationDispense] + -https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fhir-r4-medicationstatement-library/[MedicationStatement] + -https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fhir-r4-medication-library/[Medication] + -https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fhir-r4-medicationknowledge-library/[MedicationKnowledge] + -https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fhir-r4-immunization-library/[Immunization] + -https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fhir-r4-immunizationevaluation-library/[ImmunizationEvaluation] + -https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fhir-r4-immunizationrecommendation-library/[ImmunizationRecommendation] -| https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fhir-r4-medicationrequest-api/[MedicationRequest] + -https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fhir-r4-medicationadministration-api/[MedicationAdministration] + -https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fhir-r4-medicationdispense-api/[MedicationDispense] + -https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fhir-r4-medicationstatement-api/[MedicationStatement] + -https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fhir-r4-medication-api/[Medication] + -https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fhir-r4-medicationknowledge-api/[MedicationKnowledge] + -https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fhir-r4-immunization-api/[Immunization] + -https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fhir-r4-immunizationevaluation-api/[ImmunizationEvaluation] + -https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fhir-r4-immunizationrecommendation-api/[ImmunizationRecommendation] +| https://anypoint.mulesoft.com/exchange/org.mule.examples/fhir-r4-medicationrequest-library/[MedicationRequest] + +https://anypoint.mulesoft.com/exchange/org.mule.examples/fhir-r4-medicationadministration-library/[MedicationAdministration] + +https://anypoint.mulesoft.com/exchange/org.mule.examples/fhir-r4-medicationdispense-library/[MedicationDispense] + +https://anypoint.mulesoft.com/exchange/org.mule.examples/fhir-r4-medicationstatement-library/[MedicationStatement] + +https://anypoint.mulesoft.com/exchange/org.mule.examples/fhir-r4-medication-library/[Medication] + +https://anypoint.mulesoft.com/exchange/org.mule.examples/fhir-r4-medicationknowledge-library/[MedicationKnowledge] + +https://anypoint.mulesoft.com/exchange/org.mule.examples/fhir-r4-immunization-library/[Immunization] + +https://anypoint.mulesoft.com/exchange/org.mule.examples/fhir-r4-immunizationevaluation-library/[ImmunizationEvaluation] + +https://anypoint.mulesoft.com/exchange/org.mule.examples/fhir-r4-immunizationrecommendation-library/[ImmunizationRecommendation] +| https://anypoint.mulesoft.com/exchange/org.mule.examples/fhir-r4-medicationrequest-api/[MedicationRequest] + +https://anypoint.mulesoft.com/exchange/org.mule.examples/fhir-r4-medicationadministration-api/[MedicationAdministration] + +https://anypoint.mulesoft.com/exchange/org.mule.examples/fhir-r4-medicationdispense-api/[MedicationDispense] + +https://anypoint.mulesoft.com/exchange/org.mule.examples/fhir-r4-medicationstatement-api/[MedicationStatement] + +https://anypoint.mulesoft.com/exchange/org.mule.examples/fhir-r4-medication-api/[Medication] + +https://anypoint.mulesoft.com/exchange/org.mule.examples/fhir-r4-medicationknowledge-api/[MedicationKnowledge] + +https://anypoint.mulesoft.com/exchange/org.mule.examples/fhir-r4-immunization-api/[Immunization] + +https://anypoint.mulesoft.com/exchange/org.mule.examples/fhir-r4-immunizationevaluation-api/[ImmunizationEvaluation] + +https://anypoint.mulesoft.com/exchange/org.mule.examples/fhir-r4-immunizationrecommendation-api/[ImmunizationRecommendation] .^| Clinical - Care Provision -| https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fhir-r4-careplan-library/[CarePlan] + -https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fhir-r4-careteam-library/[CareTeam] + -https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fhir-r4-goal-library/[Goal] + -https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fhir-r4-servicerequest-library/[ServiceRequest] + -https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fhir-r4-nutritionorder-library/[NutritionOrder] + -https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fhir-r4-visionprescription-library/[VisionPrescription] + -https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fhir-r4-riskassessment-library/[RiskAssessment] + -https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fhir-r4-requestgroup-library/[RequestGroup] -| https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fhir-r4-careplan-api/[CarePlan] + -https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fhir-r4-careteam-api/[CareTeam] + -https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fhir-r4-goal-api/[Goal] + -https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fhir-r4-servicerequest-api/[ServiceRequest] + -https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fhir-r4-nutritionorder-api/[NutritionOrder] + -https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fhir-r4-visionprescription-api/[VisionPrescription] + -https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fhir-r4-riskassessment-api/[RiskAssessment] + -https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fhir-r4-requestgroup-api/[RequestGroup] +| https://anypoint.mulesoft.com/exchange/org.mule.examples/fhir-r4-careplan-library/[CarePlan] + +https://anypoint.mulesoft.com/exchange/org.mule.examples/fhir-r4-careteam-library/[CareTeam] + +https://anypoint.mulesoft.com/exchange/org.mule.examples/fhir-r4-goal-library/[Goal] + +https://anypoint.mulesoft.com/exchange/org.mule.examples/fhir-r4-servicerequest-library/[ServiceRequest] + +https://anypoint.mulesoft.com/exchange/org.mule.examples/fhir-r4-nutritionorder-library/[NutritionOrder] + +https://anypoint.mulesoft.com/exchange/org.mule.examples/fhir-r4-visionprescription-library/[VisionPrescription] + +https://anypoint.mulesoft.com/exchange/org.mule.examples/fhir-r4-riskassessment-library/[RiskAssessment] + +https://anypoint.mulesoft.com/exchange/org.mule.examples/fhir-r4-requestgroup-library/[RequestGroup] +| https://anypoint.mulesoft.com/exchange/org.mule.examples/fhir-r4-careplan-api/[CarePlan] + +https://anypoint.mulesoft.com/exchange/org.mule.examples/fhir-r4-careteam-api/[CareTeam] + +https://anypoint.mulesoft.com/exchange/org.mule.examples/fhir-r4-goal-api/[Goal] + +https://anypoint.mulesoft.com/exchange/org.mule.examples/fhir-r4-servicerequest-api/[ServiceRequest] + +https://anypoint.mulesoft.com/exchange/org.mule.examples/fhir-r4-nutritionorder-api/[NutritionOrder] + +https://anypoint.mulesoft.com/exchange/org.mule.examples/fhir-r4-visionprescription-api/[VisionPrescription] + +https://anypoint.mulesoft.com/exchange/org.mule.examples/fhir-r4-riskassessment-api/[RiskAssessment] + +https://anypoint.mulesoft.com/exchange/org.mule.examples/fhir-r4-requestgroup-api/[RequestGroup] .^| Clinical - Request & Response -| https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fhir-r4-communication-library/[Communication] + -https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fhir-r4-communicationrequest-library/[CommunicationRequest] + -https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fhir-r4-devicerequest-library/[DeviceRequest #] + -https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fhir-r4-deviceusestatement-library/[DeviceUseStatement] ^[u]^ + -https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fhir-r4-guidanceresponse-library/[GuidanceResponse] + -https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fhir-r4-supplyrequest-library/[SupplyRequest #] + -https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fhir-r4-supplydelivery-library/[SupplyDelivery] -| https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fhir-r4-communication-api/[Communication] + -https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fhir-r4-communicationrequest-api/[CommunicationRequest] + -https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fhir-r4-devicerequest-api/[DeviceRequest #] + -https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fhir-r4-deviceusestatement-api/[DeviceUseStatement] ^[u]^ + -https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fhir-r4-guidanceresponse-api/[GuidanceResponse] + -https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fhir-r4-supplyrequest-api/[SupplyRequest #] + -https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fhir-r4-supplydelivery-api/[SupplyDelivery] +| https://anypoint.mulesoft.com/exchange/org.mule.examples/fhir-r4-communication-library/[Communication] + +https://anypoint.mulesoft.com/exchange/org.mule.examples/fhir-r4-communicationrequest-library/[CommunicationRequest] + +https://anypoint.mulesoft.com/exchange/org.mule.examples/fhir-r4-devicerequest-library/[DeviceRequest #] + +https://anypoint.mulesoft.com/exchange/org.mule.examples/fhir-r4-deviceusestatement-library/[DeviceUseStatement] ^[u]^ + +https://anypoint.mulesoft.com/exchange/org.mule.examples/fhir-r4-guidanceresponse-library/[GuidanceResponse] + +https://anypoint.mulesoft.com/exchange/org.mule.examples/fhir-r4-supplyrequest-library/[SupplyRequest #] + +https://anypoint.mulesoft.com/exchange/org.mule.examples/fhir-r4-supplydelivery-library/[SupplyDelivery] +| https://anypoint.mulesoft.com/exchange/org.mule.examples/fhir-r4-communication-api/[Communication] + +https://anypoint.mulesoft.com/exchange/org.mule.examples/fhir-r4-communicationrequest-api/[CommunicationRequest] + +https://anypoint.mulesoft.com/exchange/org.mule.examples/fhir-r4-devicerequest-api/[DeviceRequest #] + +https://anypoint.mulesoft.com/exchange/org.mule.examples/fhir-r4-deviceusestatement-api/[DeviceUseStatement] ^[u]^ + +https://anypoint.mulesoft.com/exchange/org.mule.examples/fhir-r4-guidanceresponse-api/[GuidanceResponse] + +https://anypoint.mulesoft.com/exchange/org.mule.examples/fhir-r4-supplyrequest-api/[SupplyRequest #] + +https://anypoint.mulesoft.com/exchange/org.mule.examples/fhir-r4-supplydelivery-api/[SupplyDelivery] .^| Financial - Support -| https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fhir-r4-coverage-library/[Coverage] + -https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fhir-r4-coverageeligibilityrequest-library/[CoverageEligibilityRequest] + -https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fhir-r4-coverageeligibilityresponse-library/[CoverageEligibilityResponse] + -https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fhir-r4-enrollmentrequest-library/[EnrollmentRequest] ^[u]^ + -https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fhir-r4-enrollmentresponse-library/[EnrollmentResponse] ^[u]^ -| https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fhir-r4-coverage-api/[Coverage] + -https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fhir-r4-coverageeligibilityrequest-api/[CoverageEligibilityRequest] + -https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fhir-r4-coverageeligibilityresponse-api/[CoverageEligibilityResponse] + -https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fhir-r4-enrollmentrequest-api/[EnrollmentRequest] ^[u]^ + -https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fhir-r4-enrollmentresponse-api/[EnrollmentResponse] ^[u]^ +| https://anypoint.mulesoft.com/exchange/org.mule.examples/fhir-r4-coverage-library/[Coverage] + +https://anypoint.mulesoft.com/exchange/org.mule.examples/fhir-r4-coverageeligibilityrequest-library/[CoverageEligibilityRequest] + +https://anypoint.mulesoft.com/exchange/org.mule.examples/fhir-r4-coverageeligibilityresponse-library/[CoverageEligibilityResponse] + +https://anypoint.mulesoft.com/exchange/org.mule.examples/fhir-r4-enrollmentrequest-library/[EnrollmentRequest] ^[u]^ + +https://anypoint.mulesoft.com/exchange/org.mule.examples/fhir-r4-enrollmentresponse-library/[EnrollmentResponse] ^[u]^ +| https://anypoint.mulesoft.com/exchange/org.mule.examples/fhir-r4-coverage-api/[Coverage] + +https://anypoint.mulesoft.com/exchange/org.mule.examples/fhir-r4-coverageeligibilityrequest-api/[CoverageEligibilityRequest] + +https://anypoint.mulesoft.com/exchange/org.mule.examples/fhir-r4-coverageeligibilityresponse-api/[CoverageEligibilityResponse] + +https://anypoint.mulesoft.com/exchange/org.mule.examples/fhir-r4-enrollmentrequest-api/[EnrollmentRequest] ^[u]^ + +https://anypoint.mulesoft.com/exchange/org.mule.examples/fhir-r4-enrollmentresponse-api/[EnrollmentResponse] ^[u]^ .^| Financial - Billing -| https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fhir-r4-claim-library/[Claim] + -https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fhir-r4-claimresponse-library/[ClaimResponse] + -https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fhir-r4-invoice-library/[Invoice] -| https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fhir-r4-claim-api/[Claim] + -https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fhir-r4-claimresponse-api/[ClaimResponse] + -https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fhir-r4-invoice-api/[Invoice] - -.^| Financial - Payment | https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fhir-r4-paymentnotice-library/[PaymentNotice] + -https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fhir-r4-paymentreconciliation-library/[PaymentReconcilliation] -| https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fhir-r4-paymentnotice-api/[PaymentNotice] + -https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fhir-r4-paymentreconciliation-api/[PaymentReconcilliation] - -.^| Financial - General | https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fhir-r4-account-library/[Account] + -https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fhir-r4-chargeitem-library/[ChargeItem] + -https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fhir-r4-chargeitemdefinition-library/[ChargeItemDefinition] + -https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fhir-r4-contract-library/[Contract] + -https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fhir-r4-explanationofbenefit-library/[ExplanationOfBenefit] + -https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fhir-r4-insuranceplan-library/[InsurancePlan] -| https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fhir-r4-account-api/[Account] + -https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fhir-r4-chargeitem-api/[ChargeItem] + -https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fhir-r4-chargeitemdefinition-api/[ChargeItemDefinition] + -https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fhir-r4-contract-api/[Contract] + -https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fhir-r4-explanationofbenefit-api/[ExplanationOfBenefit] + -https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fhir-r4-insuranceplan-api/[InsurancePlan] - -.^| Specialized - Public Health & Research | https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fhir-r4-researchstudy-library/[ResearchStudy] + -https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fhir-r4-researchsubject-library/[ResearchSubject] -| https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fhir-r4-researchstudy-api/[ResearchStudy] + -https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fhir-r4-researchsubject-api/[ResearchSubject] - -.^| Specialized - Definitional Artifacts | https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fhir-r4-activitydefinition-library/[ActivityDefinition] + -https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fhir-r4-devicedefinition-library/[DeviceDefinition] + -https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fhir-r4-eventdefinition-library/[EventDefinition] + -https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fhir-r4-observationdefinition-library/[ObservationDefinition] ^[u]^ + -https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fhir-r4-plandefinition-library/[PlanDefinition] + -https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fhir-r4-questionnaire-library/[Questionnaire] + -https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fhir-r4-specimendefinition-library/[SpecimenDefinition] -| https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fhir-r4-activitydefinition-api/[ActivityDefinition] + -https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fhir-r4-devicedefinition-api/[DeviceDefinition] + -https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fhir-r4-eventdefinition-api/[EventDefinition] + -https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fhir-r4-observationdefinition-api/[ObservationDefinition] ^[u]^ + -https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fhir-r4-plandefinition-api/[PlanDefinition] + -https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fhir-r4-questionnaire-api/[Questionnaire] + -https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fhir-r4-specimendefinition-api/[SpecimenDefinition] - -.^| Specialized - Evidence Based Medicine | https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fhir-r4-researchdefinition-library/[ResearchDefinition] + -https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fhir-r4-researchelementdefinition-library/[ResearchElementDefinition] + -https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fhir-r4-evidence-library/[Evidence] + -https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fhir-r4-evidencevariable-library/[EvidenceVariable] + -https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fhir-r4-effectevidencesynthesis-library/[EffectEvidenceSynthesis] + -https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fhir-r4-riskevidencesynthesis-library/[RiskEvidenceSynthesis] -| https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fhir-r4-researchdefinition-api/[ResearchDefinition] + -https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fhir-r4-researchelementdefinition-api/[ResearchElementDefinition] + -https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fhir-r4-evidence-api/[Evidence] + -https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fhir-r4-evidencevariable-api/[EvidenceVariable] + -https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fhir-r4-effectevidencesynthesis-api/[EffectEvidenceSynthesis] + -https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fhir-r4-riskevidencesynthesis-api/[RiskEvidenceSynthesis] - -.^| Specialized - Quality Reporting & Testing | https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fhir-r4-measure-library/[Measure] + -https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fhir-r4-measurereport-library/[MeasureReport] + -https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fhir-r4-testscript-library/[TestScript] + -https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fhir-r4-testreport-library/[TestReport] -| https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fhir-r4-measure-api/[Measure] + -https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fhir-r4-measurereport-api/[MeasureReport] + -https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fhir-r4-testscript-api/[TestScript] + -https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fhir-r4-testreport-api/[TestReport] - -.^| Specialized - Medication Definition | https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fhir-r4-medicinalproduct-library/[MedicinalProduct] ^[u]^ + -https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fhir-r4-medicinalproductauthorization-library/[MedicinalProductAuthorization] ^[u]^ + -https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fhir-r4-medicinalproductcontraindication-library/[MedicinalProductContraindication] + -https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fhir-r4-medicinalproductindication-library/[MedicinalProductIndication] + -https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fhir-r4-medicinalproductingredient-library/[MedicinalProductIngredient] ^[u]^ + -https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fhir-r4-medicinalproductinteraction-library/[MedicinalProductInteraction] + -https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fhir-r4-medicinalproductmanufactured-library/[MedicinalProductManufactured] + -https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fhir-r4-medicinalproductpackaged-library/[MedicinalProductPackaged] ^[u]^ + -https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fhir-r4-medicinalproductpharmaceutical-library/[MedicinalProductPharmaceutical] ^[u]^ + -https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fhir-r4-medicinalproductundesirableeffect-library/[MedicinalProductUndesirableEffect] + -https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fhir-r4-substancenucleicacid-library/[SubstanceNucleicAcid] + -https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fhir-r4-substancepolymer-library/[SubstancePolymer] ^[u]^ + -https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fhir-r4-substanceprotein-library/[SubstanceProtein] + -https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fhir-r4-substancereferenceinformation-library/[SubstanceReferenceInformation] ^[u]^ + -https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fhir-r4-substancespecification-library/[SubstanceSpecification] ^[u]^ + -https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fhir-r4-substancesourcematerial-library/[SubstanceSourceMaterial] -| https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fhir-r4-medicinalproduct-api/[MedicinalProduct] ^[u]^ + -https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fhir-r4-medicinalproductauthorization-api/[MedicinalProductAuthorization] ^[u]^ + -https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fhir-r4-medicinalproductcontraindication-api/[MedicinalProductContraindication] + -https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fhir-r4-medicinalproductindication-api/[MedicinalProductIndication] + -https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fhir-r4-medicinalproductingredient-api/[MedicinalProductIngredient] ^[u]^ + -https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fhir-r4-medicinalproductinteraction-api/[MedicinalProductInteraction] + -https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fhir-r4-medicinalproductmanufactured-api/[MedicinalProductManufactured] + -https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fhir-r4-medicinalproductpackaged-api/[MedicinalProductPackaged] ^[u]^ + -https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fhir-r4-medicinalproductpharmaceutical-api/[MedicinalProductPharmaceutical] ^[u]^ + -https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fhir-r4-medicinalproductundesirableeffect-api/[MedicinalProductUndesirableEffect] + -https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fhir-r4-substancenucleicacid-api/[SubstanceNucleicAcid] + -https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fhir-r4-substancepolymer-api/[SubstancePolymer] ^[u]^ + -https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fhir-r4-substanceprotein-api/[SubstanceProtein] + -https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fhir-r4-substancereferenceinformation-api/[SubstanceReferenceInformation] ^[u]^ + -https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fhir-r4-substancespecification-api/[SubstanceSpecification] ^[u]^ + -https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fhir-r4-substancesourcematerial-api/[SubstanceSourceMaterial] +| https://anypoint.mulesoft.com/exchange/org.mule.examples/fhir-r4-claim-library/[Claim] + +https://anypoint.mulesoft.com/exchange/org.mule.examples/fhir-r4-claimresponse-library/[ClaimResponse] + +https://anypoint.mulesoft.com/exchange/org.mule.examples/fhir-r4-invoice-library/[Invoice] +| https://anypoint.mulesoft.com/exchange/org.mule.examples/fhir-r4-claim-api/[Claim] + +https://anypoint.mulesoft.com/exchange/org.mule.examples/fhir-r4-claimresponse-api/[ClaimResponse] + +https://anypoint.mulesoft.com/exchange/org.mule.examples/fhir-r4-invoice-api/[Invoice] + +.^| Financial - Payment | https://anypoint.mulesoft.com/exchange/org.mule.examples/fhir-r4-paymentnotice-library/[PaymentNotice] + +https://anypoint.mulesoft.com/exchange/org.mule.examples/fhir-r4-paymentreconciliation-library/[PaymentReconcilliation] +| https://anypoint.mulesoft.com/exchange/org.mule.examples/fhir-r4-paymentnotice-api/[PaymentNotice] + +https://anypoint.mulesoft.com/exchange/org.mule.examples/fhir-r4-paymentreconciliation-api/[PaymentReconcilliation] + +.^| Financial - General | https://anypoint.mulesoft.com/exchange/org.mule.examples/fhir-r4-account-library/[Account] + +https://anypoint.mulesoft.com/exchange/org.mule.examples/fhir-r4-chargeitem-library/[ChargeItem] + +https://anypoint.mulesoft.com/exchange/org.mule.examples/fhir-r4-chargeitemdefinition-library/[ChargeItemDefinition] + +https://anypoint.mulesoft.com/exchange/org.mule.examples/fhir-r4-contract-library/[Contract] + +https://anypoint.mulesoft.com/exchange/org.mule.examples/fhir-r4-explanationofbenefit-library/[ExplanationOfBenefit] + +https://anypoint.mulesoft.com/exchange/org.mule.examples/fhir-r4-insuranceplan-library/[InsurancePlan] +| https://anypoint.mulesoft.com/exchange/org.mule.examples/fhir-r4-account-api/[Account] + +https://anypoint.mulesoft.com/exchange/org.mule.examples/fhir-r4-chargeitem-api/[ChargeItem] + +https://anypoint.mulesoft.com/exchange/org.mule.examples/fhir-r4-chargeitemdefinition-api/[ChargeItemDefinition] + +https://anypoint.mulesoft.com/exchange/org.mule.examples/fhir-r4-contract-api/[Contract] + +https://anypoint.mulesoft.com/exchange/org.mule.examples/fhir-r4-explanationofbenefit-api/[ExplanationOfBenefit] + +https://anypoint.mulesoft.com/exchange/org.mule.examples/fhir-r4-insuranceplan-api/[InsurancePlan] + +.^| Specialized - Public Health & Research | https://anypoint.mulesoft.com/exchange/org.mule.examples/fhir-r4-researchstudy-library/[ResearchStudy] + +https://anypoint.mulesoft.com/exchange/org.mule.examples/fhir-r4-researchsubject-library/[ResearchSubject] +| https://anypoint.mulesoft.com/exchange/org.mule.examples/fhir-r4-researchstudy-api/[ResearchStudy] + +https://anypoint.mulesoft.com/exchange/org.mule.examples/fhir-r4-researchsubject-api/[ResearchSubject] + +.^| Specialized - Definitional Artifacts | https://anypoint.mulesoft.com/exchange/org.mule.examples/fhir-r4-activitydefinition-library/[ActivityDefinition] + +https://anypoint.mulesoft.com/exchange/org.mule.examples/fhir-r4-devicedefinition-library/[DeviceDefinition] + +https://anypoint.mulesoft.com/exchange/org.mule.examples/fhir-r4-eventdefinition-library/[EventDefinition] + +https://anypoint.mulesoft.com/exchange/org.mule.examples/fhir-r4-observationdefinition-library/[ObservationDefinition] ^[u]^ + +https://anypoint.mulesoft.com/exchange/org.mule.examples/fhir-r4-plandefinition-library/[PlanDefinition] + +https://anypoint.mulesoft.com/exchange/org.mule.examples/fhir-r4-questionnaire-library/[Questionnaire] + +https://anypoint.mulesoft.com/exchange/org.mule.examples/fhir-r4-specimendefinition-library/[SpecimenDefinition] +| https://anypoint.mulesoft.com/exchange/org.mule.examples/fhir-r4-activitydefinition-api/[ActivityDefinition] + +https://anypoint.mulesoft.com/exchange/org.mule.examples/fhir-r4-devicedefinition-api/[DeviceDefinition] + +https://anypoint.mulesoft.com/exchange/org.mule.examples/fhir-r4-eventdefinition-api/[EventDefinition] + +https://anypoint.mulesoft.com/exchange/org.mule.examples/fhir-r4-observationdefinition-api/[ObservationDefinition] ^[u]^ + +https://anypoint.mulesoft.com/exchange/org.mule.examples/fhir-r4-plandefinition-api/[PlanDefinition] + +https://anypoint.mulesoft.com/exchange/org.mule.examples/fhir-r4-questionnaire-api/[Questionnaire] + +https://anypoint.mulesoft.com/exchange/org.mule.examples/fhir-r4-specimendefinition-api/[SpecimenDefinition] + +.^| Specialized - Evidence Based Medicine | https://anypoint.mulesoft.com/exchange/org.mule.examples/fhir-r4-researchdefinition-library/[ResearchDefinition] + +https://anypoint.mulesoft.com/exchange/org.mule.examples/fhir-r4-researchelementdefinition-library/[ResearchElementDefinition] + +https://anypoint.mulesoft.com/exchange/org.mule.examples/fhir-r4-evidence-library/[Evidence] + +https://anypoint.mulesoft.com/exchange/org.mule.examples/fhir-r4-evidencevariable-library/[EvidenceVariable] + +https://anypoint.mulesoft.com/exchange/org.mule.examples/fhir-r4-effectevidencesynthesis-library/[EffectEvidenceSynthesis] + +https://anypoint.mulesoft.com/exchange/org.mule.examples/fhir-r4-riskevidencesynthesis-library/[RiskEvidenceSynthesis] +| https://anypoint.mulesoft.com/exchange/org.mule.examples/fhir-r4-researchdefinition-api/[ResearchDefinition] + +https://anypoint.mulesoft.com/exchange/org.mule.examples/fhir-r4-researchelementdefinition-api/[ResearchElementDefinition] + +https://anypoint.mulesoft.com/exchange/org.mule.examples/fhir-r4-evidence-api/[Evidence] + +https://anypoint.mulesoft.com/exchange/org.mule.examples/fhir-r4-evidencevariable-api/[EvidenceVariable] + +https://anypoint.mulesoft.com/exchange/org.mule.examples/fhir-r4-effectevidencesynthesis-api/[EffectEvidenceSynthesis] + +https://anypoint.mulesoft.com/exchange/org.mule.examples/fhir-r4-riskevidencesynthesis-api/[RiskEvidenceSynthesis] + +.^| Specialized - Quality Reporting & Testing | https://anypoint.mulesoft.com/exchange/org.mule.examples/fhir-r4-measure-library/[Measure] + +https://anypoint.mulesoft.com/exchange/org.mule.examples/fhir-r4-measurereport-library/[MeasureReport] + +https://anypoint.mulesoft.com/exchange/org.mule.examples/fhir-r4-testscript-library/[TestScript] + +https://anypoint.mulesoft.com/exchange/org.mule.examples/fhir-r4-testreport-library/[TestReport] +| https://anypoint.mulesoft.com/exchange/org.mule.examples/fhir-r4-measure-api/[Measure] + +https://anypoint.mulesoft.com/exchange/org.mule.examples/fhir-r4-measurereport-api/[MeasureReport] + +https://anypoint.mulesoft.com/exchange/org.mule.examples/fhir-r4-testscript-api/[TestScript] + +https://anypoint.mulesoft.com/exchange/org.mule.examples/fhir-r4-testreport-api/[TestReport] + +.^| Specialized - Medication Definition | https://anypoint.mulesoft.com/exchange/org.mule.examples/fhir-r4-medicinalproduct-library/[MedicinalProduct] ^[u]^ + +https://anypoint.mulesoft.com/exchange/org.mule.examples/fhir-r4-medicinalproductauthorization-library/[MedicinalProductAuthorization] ^[u]^ + +https://anypoint.mulesoft.com/exchange/org.mule.examples/fhir-r4-medicinalproductcontraindication-library/[MedicinalProductContraindication] + +https://anypoint.mulesoft.com/exchange/org.mule.examples/fhir-r4-medicinalproductindication-library/[MedicinalProductIndication] + +https://anypoint.mulesoft.com/exchange/org.mule.examples/fhir-r4-medicinalproductingredient-library/[MedicinalProductIngredient] ^[u]^ + +https://anypoint.mulesoft.com/exchange/org.mule.examples/fhir-r4-medicinalproductinteraction-library/[MedicinalProductInteraction] + +https://anypoint.mulesoft.com/exchange/org.mule.examples/fhir-r4-medicinalproductmanufactured-library/[MedicinalProductManufactured] + +https://anypoint.mulesoft.com/exchange/org.mule.examples/fhir-r4-medicinalproductpackaged-library/[MedicinalProductPackaged] ^[u]^ + +https://anypoint.mulesoft.com/exchange/org.mule.examples/fhir-r4-medicinalproductpharmaceutical-library/[MedicinalProductPharmaceutical] ^[u]^ + +https://anypoint.mulesoft.com/exchange/org.mule.examples/fhir-r4-medicinalproductundesirableeffect-library/[MedicinalProductUndesirableEffect] + +https://anypoint.mulesoft.com/exchange/org.mule.examples/fhir-r4-substancenucleicacid-library/[SubstanceNucleicAcid] + +https://anypoint.mulesoft.com/exchange/org.mule.examples/fhir-r4-substancepolymer-library/[SubstancePolymer] ^[u]^ + +https://anypoint.mulesoft.com/exchange/org.mule.examples/fhir-r4-substanceprotein-library/[SubstanceProtein] + +https://anypoint.mulesoft.com/exchange/org.mule.examples/fhir-r4-substancereferenceinformation-library/[SubstanceReferenceInformation] ^[u]^ + +https://anypoint.mulesoft.com/exchange/org.mule.examples/fhir-r4-substancespecification-library/[SubstanceSpecification] ^[u]^ + +https://anypoint.mulesoft.com/exchange/org.mule.examples/fhir-r4-substancesourcematerial-library/[SubstanceSourceMaterial] +| https://anypoint.mulesoft.com/exchange/org.mule.examples/fhir-r4-medicinalproduct-api/[MedicinalProduct] ^[u]^ + +https://anypoint.mulesoft.com/exchange/org.mule.examples/fhir-r4-medicinalproductauthorization-api/[MedicinalProductAuthorization] ^[u]^ + +https://anypoint.mulesoft.com/exchange/org.mule.examples/fhir-r4-medicinalproductcontraindication-api/[MedicinalProductContraindication] + +https://anypoint.mulesoft.com/exchange/org.mule.examples/fhir-r4-medicinalproductindication-api/[MedicinalProductIndication] + +https://anypoint.mulesoft.com/exchange/org.mule.examples/fhir-r4-medicinalproductingredient-api/[MedicinalProductIngredient] ^[u]^ + +https://anypoint.mulesoft.com/exchange/org.mule.examples/fhir-r4-medicinalproductinteraction-api/[MedicinalProductInteraction] + +https://anypoint.mulesoft.com/exchange/org.mule.examples/fhir-r4-medicinalproductmanufactured-api/[MedicinalProductManufactured] + +https://anypoint.mulesoft.com/exchange/org.mule.examples/fhir-r4-medicinalproductpackaged-api/[MedicinalProductPackaged] ^[u]^ + +https://anypoint.mulesoft.com/exchange/org.mule.examples/fhir-r4-medicinalproductpharmaceutical-api/[MedicinalProductPharmaceutical] ^[u]^ + +https://anypoint.mulesoft.com/exchange/org.mule.examples/fhir-r4-medicinalproductundesirableeffect-api/[MedicinalProductUndesirableEffect] + +https://anypoint.mulesoft.com/exchange/org.mule.examples/fhir-r4-substancenucleicacid-api/[SubstanceNucleicAcid] + +https://anypoint.mulesoft.com/exchange/org.mule.examples/fhir-r4-substancepolymer-api/[SubstancePolymer] ^[u]^ + +https://anypoint.mulesoft.com/exchange/org.mule.examples/fhir-r4-substanceprotein-api/[SubstanceProtein] + +https://anypoint.mulesoft.com/exchange/org.mule.examples/fhir-r4-substancereferenceinformation-api/[SubstanceReferenceInformation] ^[u]^ + +https://anypoint.mulesoft.com/exchange/org.mule.examples/fhir-r4-substancespecification-api/[SubstanceSpecification] ^[u]^ + +https://anypoint.mulesoft.com/exchange/org.mule.examples/fhir-r4-substancesourcematerial-api/[SubstanceSourceMaterial] |=== NOTE: @@ -364,7 +364,7 @@ This FHIR Error API policy can be used to capture error responses and format the See the following page to learn more about the FHIR Error API Policy: -* https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fhir-error-policy/[FHIR Error API Policy] +* https://anypoint.mulesoft.com/exchange/org.mule.examples/fhir-error-policy/[FHIR Error API Policy] == See Also diff --git a/healthcare/2.19/modules/ROOT/pages/fhir-r4-us-core-profiles.adoc b/healthcare/2.19/modules/ROOT/pages/fhir-r4-us-core-profiles.adoc index bd9f34445..22b48f675 100644 --- a/healthcare/2.19/modules/ROOT/pages/fhir-r4-us-core-profiles.adoc +++ b/healthcare/2.19/modules/ROOT/pages/fhir-r4-us-core-profiles.adoc @@ -2,7 +2,7 @@ The MuleSoft Accelerator for Healthcare provides a library of United States Core Data for Interoperability (USCDI) and FHIR R4 resources to help healthcare developers adhere to interoperability needs and jumpstart the development of healthcare digital transformation initiatives. -You can also use the https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fhir-error-policy/[FHIR Error API Policy] to capture error responses and format them in an FHIR OperationOutcome-compliant format, since Anypoint Platform's out-of-the-box (OOTB) policies do not provide error messages in an FHIR-compliant format. This policy can also be used with other OOTB API policies provided in Anypoint Platform, such as OAuth or JWT. +You can also use the https://anypoint.mulesoft.com/exchange/org.mule.examples/fhir-error-policy/[FHIR Error API Policy] to capture error responses and format them in an FHIR OperationOutcome-compliant format, since Anypoint Platform's out-of-the-box (OOTB) policies do not provide error messages in an FHIR-compliant format. This policy can also be used with other OOTB API policies provided in Anypoint Platform, such as OAuth or JWT. For the list of all FHIR R4 assets, please refer to xref:fhir-r4-resources.adoc[this link]. @@ -15,68 +15,68 @@ _API specifications, data types, and libraries built to meet compliance with FHI | Module | Library | API specification | Data Types -| https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fhir-r4-commons-library/[FHIR R4 Common Library] + -https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fhir-r4-resource-types-library/[Resource Types Library] + +| https://anypoint.mulesoft.com/exchange/org.mule.examples/fhir-r4-commons-library/[FHIR R4 Common Library] + +https://anypoint.mulesoft.com/exchange/org.mule.examples/fhir-r4-resource-types-library/[Resource Types Library] + | NA | Foundation -| https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fhir-r4-documentreference-library/[DocumentReference Library] -| https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fhir-r4-documentreference-api/[DocumentReference API] +| https://anypoint.mulesoft.com/exchange/org.mule.examples/fhir-r4-documentreference-library/[DocumentReference Library] +| https://anypoint.mulesoft.com/exchange/org.mule.examples/fhir-r4-documentreference-api/[DocumentReference API] | Security -| https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fhir-r4-provenance-library/[Provenance Library] -| https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fhir-r4-provenance-api/[Provenance API] +| https://anypoint.mulesoft.com/exchange/org.mule.examples/fhir-r4-provenance-library/[Provenance Library] +| https://anypoint.mulesoft.com/exchange/org.mule.examples/fhir-r4-provenance-api/[Provenance API] | Conformance -| https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fhir-r4-capabilitystatement-library/[CapabilityStatement Library] -| https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fhir-r4-capabilitystatement-api/[CapabilityStatement API] +| https://anypoint.mulesoft.com/exchange/org.mule.examples/fhir-r4-capabilitystatement-library/[CapabilityStatement Library] +| https://anypoint.mulesoft.com/exchange/org.mule.examples/fhir-r4-capabilitystatement-api/[CapabilityStatement API] | Administration -| https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fhir-r4-us-core-patient-library/[Patient Library] + -https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fhir-r4-practitioner-library/[Practitioner Library] + -https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fhir-r4-practitionerrole-library/[PractitionerRole Library] + -https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fhir-r4-device-library/[Device Library] + -https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fhir-r4-organization-library/[Organization Library] + -https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fhir-r4-location-library/[Location Library] + -https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fhir-r4-careteam-library/[CareTeam Library] + -https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fhir-r4-encounter-library/[Encounter Library] + - -| https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fhir-r4-us-core-patient-api/[Patient API*] + -https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fhir-r4-practitioner-api/[Practitioner API] + -https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fhir-r4-practitionerrole-api/[PractitionerRole API] + -https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fhir-r4-device-api/[Device API] + -https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fhir-r4-organization-api/[Organization API] + -https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fhir-r4-location-api/[Location API] + -https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fhir-r4-careteam-api/[CareTeam API] + -https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fhir-r4-encounter-api/[Encounter API] +| https://anypoint.mulesoft.com/exchange/org.mule.examples/fhir-r4-us-core-patient-library/[Patient Library] + +https://anypoint.mulesoft.com/exchange/org.mule.examples/fhir-r4-practitioner-library/[Practitioner Library] + +https://anypoint.mulesoft.com/exchange/org.mule.examples/fhir-r4-practitionerrole-library/[PractitionerRole Library] + +https://anypoint.mulesoft.com/exchange/org.mule.examples/fhir-r4-device-library/[Device Library] + +https://anypoint.mulesoft.com/exchange/org.mule.examples/fhir-r4-organization-library/[Organization Library] + +https://anypoint.mulesoft.com/exchange/org.mule.examples/fhir-r4-location-library/[Location Library] + +https://anypoint.mulesoft.com/exchange/org.mule.examples/fhir-r4-careteam-library/[CareTeam Library] + +https://anypoint.mulesoft.com/exchange/org.mule.examples/fhir-r4-encounter-library/[Encounter Library] + + +| https://anypoint.mulesoft.com/exchange/org.mule.examples/fhir-r4-us-core-patient-api/[Patient API*] + +https://anypoint.mulesoft.com/exchange/org.mule.examples/fhir-r4-practitioner-api/[Practitioner API] + +https://anypoint.mulesoft.com/exchange/org.mule.examples/fhir-r4-practitionerrole-api/[PractitionerRole API] + +https://anypoint.mulesoft.com/exchange/org.mule.examples/fhir-r4-device-api/[Device API] + +https://anypoint.mulesoft.com/exchange/org.mule.examples/fhir-r4-organization-api/[Organization API] + +https://anypoint.mulesoft.com/exchange/org.mule.examples/fhir-r4-location-api/[Location API] + +https://anypoint.mulesoft.com/exchange/org.mule.examples/fhir-r4-careteam-api/[CareTeam API] + +https://anypoint.mulesoft.com/exchange/org.mule.examples/fhir-r4-encounter-api/[Encounter API] | Clinical -| https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fhir-r4-us-core-allergyintolerance-library/[AllergyIntolerance Library] + -https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fhir-r4-careplan-library/[CarePlan Library] + -https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fhir-r4-goal-library/[Goal Library] + -https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fhir-r4-procedure-library/[Procedure Library] + -https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fhir-r4-us-core-condition-library/[Condition Library] + - -| https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fhir-r4-us-core-allergyintolerance-api/[AllergyIntolerance API*] + -https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fhir-r4-careplan-api/[CarePlan API] + -https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fhir-r4-goal-api/[Goal API] + -https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fhir-r4-procedure-api/[Procedure API] + -https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fhir-r4-us-core-condition-api/[Condition API] +| https://anypoint.mulesoft.com/exchange/org.mule.examples/fhir-r4-us-core-allergyintolerance-library/[AllergyIntolerance Library] + +https://anypoint.mulesoft.com/exchange/org.mule.examples/fhir-r4-careplan-library/[CarePlan Library] + +https://anypoint.mulesoft.com/exchange/org.mule.examples/fhir-r4-goal-library/[Goal Library] + +https://anypoint.mulesoft.com/exchange/org.mule.examples/fhir-r4-procedure-library/[Procedure Library] + +https://anypoint.mulesoft.com/exchange/org.mule.examples/fhir-r4-us-core-condition-library/[Condition Library] + + +| https://anypoint.mulesoft.com/exchange/org.mule.examples/fhir-r4-us-core-allergyintolerance-api/[AllergyIntolerance API*] + +https://anypoint.mulesoft.com/exchange/org.mule.examples/fhir-r4-careplan-api/[CarePlan API] + +https://anypoint.mulesoft.com/exchange/org.mule.examples/fhir-r4-goal-api/[Goal API] + +https://anypoint.mulesoft.com/exchange/org.mule.examples/fhir-r4-procedure-api/[Procedure API] + +https://anypoint.mulesoft.com/exchange/org.mule.examples/fhir-r4-us-core-condition-api/[Condition API] | Diagnostics -| https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fhir-r4-us-core-observation-library/[Observation Library] + -https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fhir-r4-diagnosticreport-library/[DiagnosticReport Library] -| https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fhir-r4-us-core-observation-api/[Observation API*] + -https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fhir-r4-diagnosticreport-api/[DiagnosticReport API] +| https://anypoint.mulesoft.com/exchange/org.mule.examples/fhir-r4-us-core-observation-library/[Observation Library] + +https://anypoint.mulesoft.com/exchange/org.mule.examples/fhir-r4-diagnosticreport-library/[DiagnosticReport Library] +| https://anypoint.mulesoft.com/exchange/org.mule.examples/fhir-r4-us-core-observation-api/[Observation API*] + +https://anypoint.mulesoft.com/exchange/org.mule.examples/fhir-r4-diagnosticreport-api/[DiagnosticReport API] | Medications -| https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fhir-r4-immunization-library/[Immunization Library] + -https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fhir-r4-medication-library/[Medication Library] + -https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fhir-r4-medicationrequest-library/[MedicationRequest Library] -| https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fhir-r4-immunization-api/[Immunization API] + -https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fhir-r4-medication-api/[Medication API] + -https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fhir-r4-medicationrequest-api/[MedicationRequest API] +| https://anypoint.mulesoft.com/exchange/org.mule.examples/fhir-r4-immunization-library/[Immunization Library] + +https://anypoint.mulesoft.com/exchange/org.mule.examples/fhir-r4-medication-library/[Medication Library] + +https://anypoint.mulesoft.com/exchange/org.mule.examples/fhir-r4-medicationrequest-library/[MedicationRequest Library] +| https://anypoint.mulesoft.com/exchange/org.mule.examples/fhir-r4-immunization-api/[Immunization API] + +https://anypoint.mulesoft.com/exchange/org.mule.examples/fhir-r4-medication-api/[Medication API] + +https://anypoint.mulesoft.com/exchange/org.mule.examples/fhir-r4-medicationrequest-api/[MedicationRequest API] |=== _APIs marked with `*` have both FHIR R4 and US Core-specific Library and API specification available._ diff --git a/healthcare/2.19/modules/ROOT/pages/hl7-v2-fhir-converter.adoc b/healthcare/2.19/modules/ROOT/pages/hl7-v2-fhir-converter.adoc index 737ae28d6..d750bb00e 100644 --- a/healthcare/2.19/modules/ROOT/pages/hl7-v2-fhir-converter.adoc +++ b/healthcare/2.19/modules/ROOT/pages/hl7-v2-fhir-converter.adoc @@ -1,10 +1,10 @@ = HL7 v2 to FHIR Converter -The https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/hc-accelerator-hl7v2-to-fhir-sys-api[HL7 v2 to FHIR converter] comes with a ready to use template for HL7 v2 to FHIR conversion, which is based on the guidance provided by the https://build.fhir.org/ig/HL7/v2-to-fhir[HL7 v2 to FHIR Implementation Guide]. This template can be extended or modified to meet specific conversion requirements. +The https://anypoint.mulesoft.com/exchange/org.mule.examples/hc-accelerator-hl7v2-to-fhir-sys-api[HL7 v2 to FHIR converter] comes with a ready to use template for HL7 v2 to FHIR conversion, which is based on the guidance provided by the https://build.fhir.org/ig/HL7/v2-to-fhir[HL7 v2 to FHIR Implementation Guide]. This template can be extended or modified to meet specific conversion requirements. == Functional diagram -image:https://www.mulesoft.com/ext/solutions/draft/images/hc-hl7v2-to-fhir-usecase-diagram.png[hc-hl7v2-to-fhir-usecase-diagram.png,799,align="center"] +image:https://www.mulesoft.com/ext/solutions/images/hc-hl7v2-to-fhir-usecase-diagram.png[hc-hl7v2-to-fhir-usecase-diagram.png,799,align="center"] == Advantages diff --git a/healthcare/2.19/modules/ROOT/pages/index.adoc b/healthcare/2.19/modules/ROOT/pages/index.adoc index 7fa784de2..366f4c508 100644 --- a/healthcare/2.19/modules/ROOT/pages/index.adoc +++ b/healthcare/2.19/modules/ROOT/pages/index.adoc @@ -9,13 +9,13 @@ For solutions related to life sciences, the xref:life-sciences::index.adoc[MuleS The following describes the use cases supported by the MuleSoft Accelerator for Healthcare: -* https://www.anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/mulesoft-accelerator-for-healthcare/minor/{hls-version}/pages/Use%20case%201%20-%20Patient%20360/[Patient 360^] — This use case accelerates Patient 360 efforts by providing pre-built APIs and implementation templates to integrate critical data from EHRs with other emerging technologies and applications. This solution provides both HL7 v2 and FHIR-based capabilities to allow organizations to support a variety of use cases and realize value regardless of the industry standard that is present in their organization's ecosystem. -* https://www.anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/mulesoft-accelerator-for-healthcare/minor/{hls-version}/pages/Use%20case%202%20-%20CMS%20Interoperability/[CMS Interoperability^] — Includes assets to help you meet CMS Interoperability and Patient Access final rule. -* https://www.anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/mulesoft-accelerator-for-healthcare/minor/{hls-version}/pages/Use%20case%203%20-%20Labs%20integration/[Labs integration^] — Includes the The Electronic Laboratory Reporting (ELR) to CalREDIE implementation template, which helps you transmit laboratory reports that identify a notifiable condition to public health agencies (for example, California Department of Public Health). -* https://www.anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/mulesoft-accelerator-for-healthcare/minor/{hls-version}/pages/Use%20case%204%20-%20Appointment%20scheduling/[Appointment scheduling^] — Includes the Appointment Scheduling Process API for both Cerner and Epic, which enables call center agents to schedule, update, and cancel appointments on behalf of the patient. See the implementation template for more information. -* https://www.anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/mulesoft-accelerator-for-healthcare/minor/{hls-version}/pages/Use%20case%205%20-%20Benefits%20and%20eligibility%20verification/[Benefits and eligibility verification^] — Enables call center agents and care staff to perform real-time benefits and eligibility verification. Providers can electronically verify a patient's insurance coverage in real-time for medical treatment directly within Salesforce Health Cloud. -* https://www.anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/mulesoft-accelerator-for-healthcare/minor/{hls-version}/pages/Use%20case%206%20-%20Prior%20Authorization/[Prior Authorization^] — Includes CRD, DTR, and PAS API specifications and implementation templates to automate the prior authorization process for more immediate authorizations, leading to better outcomes and increased satisfaction for patients, providers, and payers. -* https://www.anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/mulesoft-accelerator-for-healthcare/minor/{hls-version}/pages/Use%20case%207%20-%20Population%20health%20management/[Population health management^] - Convert and surface valuable population health data into Amazon HealthLake to improve clinical outcomes. +* https://www.anypoint.mulesoft.com/exchange/org.mule.examples/mulesoft-accelerator-for-healthcare/minor/{hls-version}/pages/Use%20case%201%20-%20Patient%20360/[Patient 360^] — This use case accelerates Patient 360 efforts by providing pre-built APIs and implementation templates to integrate critical data from EHRs with other emerging technologies and applications. This solution provides both HL7 v2 and FHIR-based capabilities to allow organizations to support a variety of use cases and realize value regardless of the industry standard that is present in their organization's ecosystem. +* https://www.anypoint.mulesoft.com/exchange/org.mule.examples/mulesoft-accelerator-for-healthcare/minor/{hls-version}/pages/Use%20case%202%20-%20CMS%20Interoperability/[CMS Interoperability^] — Includes assets to help you meet CMS Interoperability and Patient Access final rule. +* https://www.anypoint.mulesoft.com/exchange/org.mule.examples/mulesoft-accelerator-for-healthcare/minor/{hls-version}/pages/Use%20case%203%20-%20Labs%20integration/[Labs integration^] — Includes the The Electronic Laboratory Reporting (ELR) to CalREDIE implementation template, which helps you transmit laboratory reports that identify a notifiable condition to public health agencies (for example, California Department of Public Health). +* https://www.anypoint.mulesoft.com/exchange/org.mule.examples/mulesoft-accelerator-for-healthcare/minor/{hls-version}/pages/Use%20case%204%20-%20Appointment%20scheduling/[Appointment scheduling^] — Includes the Appointment Scheduling Process API for both Cerner and Epic, which enables call center agents to schedule, update, and cancel appointments on behalf of the patient. See the implementation template for more information. +* https://www.anypoint.mulesoft.com/exchange/org.mule.examples/mulesoft-accelerator-for-healthcare/minor/{hls-version}/pages/Use%20case%205%20-%20Benefits%20and%20eligibility%20verification/[Benefits and eligibility verification^] — Enables call center agents and care staff to perform real-time benefits and eligibility verification. Providers can electronically verify a patient's insurance coverage in real-time for medical treatment directly within Salesforce Health Cloud. +* https://www.anypoint.mulesoft.com/exchange/org.mule.examples/mulesoft-accelerator-for-healthcare/minor/{hls-version}/pages/Use%20case%206%20-%20Prior%20Authorization/[Prior Authorization^] — Includes CRD, DTR, and PAS API specifications and implementation templates to automate the prior authorization process for more immediate authorizations, leading to better outcomes and increased satisfaction for patients, providers, and payers. +* https://www.anypoint.mulesoft.com/exchange/org.mule.examples/mulesoft-accelerator-for-healthcare/minor/{hls-version}/pages/Use%20case%207%20-%20Population%20health%20management/[Population health management^] - Convert and surface valuable population health data into Amazon HealthLake to improve clinical outcomes. === Use Case Agnostic Assets @@ -32,4 +32,4 @@ The following use-case agnostic assets are also available: * xref:prerequisites.adoc[Prerequisites] * xref:fhir-r4-assets.adoc[Available Assets] * xref:release-notes.adoc[Release Notes] -* https://www.anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/mulesoft-accelerator-for-healthcare/[MuleSoft Accelerator for Healthcare on Exchange^] +* https://www.anypoint.mulesoft.com/exchange/org.mule.examples/mulesoft-accelerator-for-healthcare/[MuleSoft Accelerator for Healthcare on Exchange^] diff --git a/healthcare/2.19/modules/ROOT/pages/release-notes.adoc b/healthcare/2.19/modules/ROOT/pages/release-notes.adoc index 6861b4a16..ffa38915c 100644 --- a/healthcare/2.19/modules/ROOT/pages/release-notes.adoc +++ b/healthcare/2.19/modules/ROOT/pages/release-notes.adoc @@ -5,7 +5,7 @@ *May 30, 2023* -This release includes the following enhancements to the https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/mulesoft-accelerator-for-healthcare/minor/{hls-version}/pages/Use%20case%201%20-%20Patient%20360/[Patient 360 use case] and https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/mulesoft-accelerator-for-healthcare/minor/2.19/pages/dkv-pq7/FHIR%20API%20assets%20and%20converters%20(HL7%20v2%2C%20CDA%20and%20X12)/[FHIR API assets and converters]: +This release includes the following enhancements to the https://anypoint.mulesoft.com/exchange/org.mule.examples/mulesoft-accelerator-for-healthcare/minor/{hls-version}/pages/Use%20case%201%20-%20Patient%20360/[Patient 360 use case] and https://anypoint.mulesoft.com/exchange/org.mule.examples/mulesoft-accelerator-for-healthcare/minor/2.19/pages/dkv-pq7/FHIR%20API%20assets%20and%20converters%20(HL7%20v2%2C%20CDA%20and%20X12)/[FHIR API assets and converters]: * Expanded the library of assets to allow organizations to more easily ingest critical information from clinical systems into Salesforce Health Cloud, which enables users to view the information included in the supported HL7 v2 events natively in their Salesforce console. ** Added support for ADT^A02, ADT^A03, ADT^A04, ADT^A05, SIU^S12, SIU^S13, SIU^S14, and SIU^S15. @@ -18,19 +18,19 @@ This release includes the following enhancements to the https://anypoint.mulesof 13 December 2022 -This release extends the solution provided for https://www.anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/mulesoft-accelerator-for-healthcare/minor/{hls-version}/pages/Use%20case%207%20-%20Population%20health%20management/[Population health management] to enable organizations to surface valuable population health data from EHR systems into Amazon HealthLake and Salesforce Customer Data Platform to improve clinical outcomes. +This release extends the solution provided for https://www.anypoint.mulesoft.com/exchange/org.mule.examples/mulesoft-accelerator-for-healthcare/minor/{hls-version}/pages/Use%20case%207%20-%20Population%20health%20management/[Population health management] to enable organizations to surface valuable population health data from EHR systems into Amazon HealthLake and Salesforce Customer Data Platform to improve clinical outcomes. -* FHIR Bulk Export System API | https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/hls-fhir-bulk-export-sys-api-spec[API Specification] | https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/hls-fhir-bulk-export-sys-api[Implementation Template] -* Population Health Management Process API | https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/hls-population-health-mgmt-prc-api/[Implementation Template] -* Salesforce CDP System API | https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/hls-salesforce-cdp-sys-api-spec[API Specification] | https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/hls-salesforce-cdp-sys-api[Implementation Template] -* Azure Web Engagement System API | https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/hls-engagements-sys-api-spec[API Specification] | https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/hls-azure-patient-engmt-sys-api[Implementation Template] -* Patient Segmentation Process API | https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/hls-patient-segmentation-prc-api/[Implementation Template] +* FHIR Bulk Export System API | https://anypoint.mulesoft.com/exchange/org.mule.examples/hls-fhir-bulk-export-sys-api-spec[API Specification] | https://anypoint.mulesoft.com/exchange/org.mule.examples/hls-fhir-bulk-export-sys-api[Implementation Template] +* Population Health Management Process API | https://anypoint.mulesoft.com/exchange/org.mule.examples/hls-population-health-mgmt-prc-api/[Implementation Template] +* Salesforce CDP System API | https://anypoint.mulesoft.com/exchange/org.mule.examples/hls-salesforce-cdp-sys-api-spec[API Specification] | https://anypoint.mulesoft.com/exchange/org.mule.examples/hls-salesforce-cdp-sys-api[Implementation Template] +* Azure Web Engagement System API | https://anypoint.mulesoft.com/exchange/org.mule.examples/hls-engagements-sys-api-spec[API Specification] | https://anypoint.mulesoft.com/exchange/org.mule.examples/hls-azure-patient-engmt-sys-api[Implementation Template] +* Patient Segmentation Process API | https://anypoint.mulesoft.com/exchange/org.mule.examples/hls-patient-segmentation-prc-api/[Implementation Template] == v2.17 20 October 2022 -This release provides a solution for https://www.anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/mulesoft-accelerator-for-healthcare/minor/{hls-version}/pages/Use%20case%207%20-%20Population%20health%20management/[Population health management] to enable organizations to convert and surface valuable population health data into Amazon HealthLake to improve clinical outcomes. +This release provides a solution for https://www.anypoint.mulesoft.com/exchange/org.mule.examples/mulesoft-accelerator-for-healthcare/minor/{hls-version}/pages/Use%20case%207%20-%20Population%20health%20management/[Population health management] to enable organizations to convert and surface valuable population health data into Amazon HealthLake to improve clinical outcomes. As part of this release, existing assets used to convert from HL7 v2, C-CDA and X12 formats to FHIR R4 were enhanced to fix defects and enable use with Amazon HealthLake. @@ -46,8 +46,8 @@ This release provides a support to additional CDA document types in xref:ccda-fh This release provides Healthcare organizations with a reference implementations to xref:fhir-r4-assets.adoc[convert FHIR R4 resources from HL7 FHIR JSON format to RAML specification] and xref:ccda-fhir-converter.adoc[convert C-CDA messages to FHIR]. -* FHIR RAML auto-generator | https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/hls-fhirjson-to-raml-sys-api-spec/[API specification] | https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/hls-fhirjson-to-raml-sys-api/[Implementation Template] -* C-CDA to FHIR System API | https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/hls-ccda-to-fhir-sys-api-spec/[API specification] | https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/hls-ccda-to-fhir-sys-api/[Implementation Template] +* FHIR RAML auto-generator | https://anypoint.mulesoft.com/exchange/org.mule.examples/hls-fhirjson-to-raml-sys-api-spec/[API specification] | https://anypoint.mulesoft.com/exchange/org.mule.examples/hls-fhirjson-to-raml-sys-api/[Implementation Template] +* C-CDA to FHIR System API | https://anypoint.mulesoft.com/exchange/org.mule.examples/hls-ccda-to-fhir-sys-api-spec/[API specification] | https://anypoint.mulesoft.com/exchange/org.mule.examples/hls-ccda-to-fhir-sys-api/[Implementation Template] == v2.14.1 @@ -55,29 +55,29 @@ This release provides Healthcare organizations with a reference implementations This minor release includes an upgrade to the dependencies on the assets that perform FHIR resource validation. -* Health Cloud Administration System API | https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/hc-accelerator-sfdc-us-core-administration-sys-api/[Implementation Template] -* Health Cloud Clinical System API | https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/hc-accelerator-sfdc-us-core-clinical-sys-api/[Implementation Template] -* Health Cloud Diagnostics System API | https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/hc-accelerator-sfdc-us-core-diagnostics-sys-api/[Implementation Template] -* Health Cloud Medications System API | https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/hc-accelerator-sfdc-us-core-medications-sys-api/[Implementation Template] -* Health Cloud Financial System API | https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/hc-accelerator-sfdc-financial-sys-api/[Implementation Template] -* Cerner Administration System API | https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/hc-accelerator-cerner-us-core-administration-sys-api/[Implementation Template] -* Cerner Clinical System API | https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/hc-accelerator-cerner-us-core-clinical-sys-api/[Implementation Template] -* Cerner Diagnostics System API | https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/hc-accelerator-cerner-us-core-diagnostics-sys-api/[Implementation Template] -* Cerner Medications System API | https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/hc-accelerator-cerner-us-core-medications-sys-api/[Implementation Template] -* Cerner Workflow System API | https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/hc-accelerator-cerner-workflow-sys-api/[Implementation Template] -* Cerner Financial System API | https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/hc-accelerator-cerner-financial-sys-api/[Implementation Template] -* Epic Administration System API | https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/hc-accelerator-epic-us-core-administration-sys-api/[Implementation Template] -* Epic Clinical System API | https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/hc-accelerator-epic-us-core-clinical-sys-api/[Implementation Template] -* Epic Diagnostics System API | https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/hc-accelerator-epic-us-core-diagnostics-sys-api/[Implementation Template] -* Epic Medications System API | https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/hc-accelerator-epic-us-core-medications-sys-api/[Implementation Template] -* Epic Financial System API | https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/hc-accelerator-epic-financial-sys-api/[Implementation Template] -* Benefits Verification Process API | https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/hc-accelerator-benefits-verification-prc-api/[Implementation Template] -* Benefits Eligibility Verification System API | https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/hc-accelerator-availity-financial-sys-api/[Implementation Template] -* CRD Clinical Decision Support System API | https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/hc-accelerator-cds-services-sys-api/[Implementation Template] -* DTR System API | https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/hc-accelerator-davinci-dtr-sys-api/[Implementation Template] -* Prior Authorization System API | https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/hc-accelerator-prior-authorization-sys-api[Implementation Template] -* HL7 V2 to FHIR System API | https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/hc-accelerator-hl7v2-to-fhir-sys-api/[Implementation Template] -* X12 to FHIR System API | https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/hls-fhir-to-x12-sys-api/[Implementation Template] +* Health Cloud Administration System API | https://anypoint.mulesoft.com/exchange/org.mule.examples/hc-accelerator-sfdc-us-core-administration-sys-api/[Implementation Template] +* Health Cloud Clinical System API | https://anypoint.mulesoft.com/exchange/org.mule.examples/hc-accelerator-sfdc-us-core-clinical-sys-api/[Implementation Template] +* Health Cloud Diagnostics System API | https://anypoint.mulesoft.com/exchange/org.mule.examples/hc-accelerator-sfdc-us-core-diagnostics-sys-api/[Implementation Template] +* Health Cloud Medications System API | https://anypoint.mulesoft.com/exchange/org.mule.examples/hc-accelerator-sfdc-us-core-medications-sys-api/[Implementation Template] +* Health Cloud Financial System API | https://anypoint.mulesoft.com/exchange/org.mule.examples/hc-accelerator-sfdc-financial-sys-api/[Implementation Template] +* Cerner Administration System API | https://anypoint.mulesoft.com/exchange/org.mule.examples/hc-accelerator-cerner-us-core-administration-sys-api/[Implementation Template] +* Cerner Clinical System API | https://anypoint.mulesoft.com/exchange/org.mule.examples/hc-accelerator-cerner-us-core-clinical-sys-api/[Implementation Template] +* Cerner Diagnostics System API | https://anypoint.mulesoft.com/exchange/org.mule.examples/hc-accelerator-cerner-us-core-diagnostics-sys-api/[Implementation Template] +* Cerner Medications System API | https://anypoint.mulesoft.com/exchange/org.mule.examples/hc-accelerator-cerner-us-core-medications-sys-api/[Implementation Template] +* Cerner Workflow System API | https://anypoint.mulesoft.com/exchange/org.mule.examples/hc-accelerator-cerner-workflow-sys-api/[Implementation Template] +* Cerner Financial System API | https://anypoint.mulesoft.com/exchange/org.mule.examples/hc-accelerator-cerner-financial-sys-api/[Implementation Template] +* Epic Administration System API | https://anypoint.mulesoft.com/exchange/org.mule.examples/hc-accelerator-epic-us-core-administration-sys-api/[Implementation Template] +* Epic Clinical System API | https://anypoint.mulesoft.com/exchange/org.mule.examples/hc-accelerator-epic-us-core-clinical-sys-api/[Implementation Template] +* Epic Diagnostics System API | https://anypoint.mulesoft.com/exchange/org.mule.examples/hc-accelerator-epic-us-core-diagnostics-sys-api/[Implementation Template] +* Epic Medications System API | https://anypoint.mulesoft.com/exchange/org.mule.examples/hc-accelerator-epic-us-core-medications-sys-api/[Implementation Template] +* Epic Financial System API | https://anypoint.mulesoft.com/exchange/org.mule.examples/hc-accelerator-epic-financial-sys-api/[Implementation Template] +* Benefits Verification Process API | https://anypoint.mulesoft.com/exchange/org.mule.examples/hc-accelerator-benefits-verification-prc-api/[Implementation Template] +* Benefits Eligibility Verification System API | https://anypoint.mulesoft.com/exchange/org.mule.examples/hc-accelerator-availity-financial-sys-api/[Implementation Template] +* CRD Clinical Decision Support System API | https://anypoint.mulesoft.com/exchange/org.mule.examples/hc-accelerator-cds-services-sys-api/[Implementation Template] +* DTR System API | https://anypoint.mulesoft.com/exchange/org.mule.examples/hc-accelerator-davinci-dtr-sys-api/[Implementation Template] +* Prior Authorization System API | https://anypoint.mulesoft.com/exchange/org.mule.examples/hc-accelerator-prior-authorization-sys-api[Implementation Template] +* HL7 V2 to FHIR System API | https://anypoint.mulesoft.com/exchange/org.mule.examples/hc-accelerator-hl7v2-to-fhir-sys-api/[Implementation Template] +* X12 to FHIR System API | https://anypoint.mulesoft.com/exchange/org.mule.examples/hls-fhir-to-x12-sys-api/[Implementation Template] == v2.14 @@ -85,7 +85,7 @@ This minor release includes an upgrade to the dependencies on the assets that pe This release provides Healthcare organizations with a reference implementation to xref:x12-fhir-converter.adoc[convert X12 messages to FHIR]. -* https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/hls-fhir-r4-to-x12-sys-api-spec/[API specification] and https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/hls-fhir-to-x12-sys-api/[implementation template] for the X12 to FHIR System API. +* https://anypoint.mulesoft.com/exchange/org.mule.examples/hls-fhir-r4-to-x12-sys-api-spec/[API specification] and https://anypoint.mulesoft.com/exchange/org.mule.examples/hls-fhir-to-x12-sys-api/[implementation template] for the X12 to FHIR System API. == v2.13 @@ -93,9 +93,9 @@ This release provides Healthcare organizations with a reference implementation t This release provides an end-to-end solution for prior authorization, which includes CRD, DTR, and PAS API specifications and implementation templates to automate the prior authorization process for more immediate authorizations: -* CRD Clinical Decision Support System API | https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/hls-cds-services-sys-api-spec/[API Specification] | https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/hc-accelerator-cds-services-sys-api/[Implementation Template] -* DTR System API | https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fhir-r4-davinci-dtr-api/[API Specification] | https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/hc-accelerator-davinci-dtr-sys-api/[Implementation Template] -* Prior Authorization System API | https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fhir-r4-prior-authorization-api[API Specification] | https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/hc-accelerator-prior-authorization-sys-api[Implementation Template] +* CRD Clinical Decision Support System API | https://anypoint.mulesoft.com/exchange/org.mule.examples/hls-cds-services-sys-api-spec/[API Specification] | https://anypoint.mulesoft.com/exchange/org.mule.examples/hc-accelerator-cds-services-sys-api/[Implementation Template] +* DTR System API | https://anypoint.mulesoft.com/exchange/org.mule.examples/fhir-r4-davinci-dtr-api/[API Specification] | https://anypoint.mulesoft.com/exchange/org.mule.examples/hc-accelerator-davinci-dtr-sys-api/[Implementation Template] +* Prior Authorization System API | https://anypoint.mulesoft.com/exchange/org.mule.examples/fhir-r4-prior-authorization-api[API Specification] | https://anypoint.mulesoft.com/exchange/org.mule.examples/hc-accelerator-prior-authorization-sys-api[Implementation Template] == v2.12.1 @@ -103,7 +103,7 @@ This release provides an end-to-end solution for prior authorization, which incl This minor release includes an upgrade to the assets to be EMR agnostic, which allows customers to choose any EMR as a System of Record: -* Patient Sync Process API | https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/patient-sync-prc-api/[API Specification] | https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/hc-accelerator-patient-sync-prc-api/[Implementation Template] +* Patient Sync Process API | https://anypoint.mulesoft.com/exchange/org.mule.examples/patient-sync-prc-api/[API Specification] | https://anypoint.mulesoft.com/exchange/org.mule.examples/hc-accelerator-patient-sync-prc-api/[Implementation Template] == v2.12 @@ -111,8 +111,8 @@ This minor release includes an upgrade to the assets to be EMR agnostic, which a This release provides an end-to-end solution for prior authorization support, which automates the prior authorization process for more immediate authorizations. The following assets are also available: -* Prior Authorization System API | https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fhir-r4-prior-authorization-api[API Specification] | https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/hc-accelerator-prior-authorization-sys-api[Implementation Template] -* Aidbox Administration System API | https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fhir-r4-administration-api/[API Specification] | https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/hc-accelerator-aidbox-us-core-administration-sys-api/[Implementation Template] +* Prior Authorization System API | https://anypoint.mulesoft.com/exchange/org.mule.examples/fhir-r4-prior-authorization-api[API Specification] | https://anypoint.mulesoft.com/exchange/org.mule.examples/hc-accelerator-prior-authorization-sys-api[Implementation Template] +* Aidbox Administration System API | https://anypoint.mulesoft.com/exchange/org.mule.examples/fhir-r4-administration-api/[API Specification] | https://anypoint.mulesoft.com/exchange/org.mule.examples/hc-accelerator-aidbox-us-core-administration-sys-api/[Implementation Template] == v2.11 @@ -120,12 +120,12 @@ This release provides an end-to-end solution for prior authorization support, wh This release provides an end-to-end solution for benefits and eligibility verification using Health Cloud, Epic, and Cerner as the reference backend systems: -* Benefits Verification Process API | https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/benefits-verification-prc-api/[API Specification] | https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/hc-accelerator-benefits-verification-prc-api/[Implementation Template] -* Cerner Financial System API | https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/cerner-fhir-r4-financial-api/[API Specification] | https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/hc-accelerator-cerner-financial-sys-api/[Implementation Template] -* Epic Financial System API | https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/epic-fhir-r4-financial-api/[API Specification] | https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/hc-accelerator-epic-financial-sys-api/[Implementation Template] -* Benefits Eligibility Verification System API | https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/availity-fhir-r4-financial-api/[API Specification] | https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/hc-accelerator-availity-financial-sys-api/[Implementation Template] -* Health Cloud Financial System API | https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fhir-r4-financial-api/[API Specification] | https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/hc-accelerator-sfdc-financial-sys-api/[Implementation Template] -* Health Cloud Benefits Verification Lightning Web Component | https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/hc-accelerator-benefits-verification-lwc-src/[Source] +* Benefits Verification Process API | https://anypoint.mulesoft.com/exchange/org.mule.examples/benefits-verification-prc-api/[API Specification] | https://anypoint.mulesoft.com/exchange/org.mule.examples/hc-accelerator-benefits-verification-prc-api/[Implementation Template] +* Cerner Financial System API | https://anypoint.mulesoft.com/exchange/org.mule.examples/cerner-fhir-r4-financial-api/[API Specification] | https://anypoint.mulesoft.com/exchange/org.mule.examples/hc-accelerator-cerner-financial-sys-api/[Implementation Template] +* Epic Financial System API | https://anypoint.mulesoft.com/exchange/org.mule.examples/epic-fhir-r4-financial-api/[API Specification] | https://anypoint.mulesoft.com/exchange/org.mule.examples/hc-accelerator-epic-financial-sys-api/[Implementation Template] +* Benefits Eligibility Verification System API | https://anypoint.mulesoft.com/exchange/org.mule.examples/availity-fhir-r4-financial-api/[API Specification] | https://anypoint.mulesoft.com/exchange/org.mule.examples/hc-accelerator-availity-financial-sys-api/[Implementation Template] +* Health Cloud Financial System API | https://anypoint.mulesoft.com/exchange/org.mule.examples/fhir-r4-financial-api/[API Specification] | https://anypoint.mulesoft.com/exchange/org.mule.examples/hc-accelerator-sfdc-financial-sys-api/[Implementation Template] +* Health Cloud Benefits Verification Lightning Web Component | https://anypoint.mulesoft.com/exchange/org.mule.examples/hc-accelerator-benefits-verification-lwc-src/[Source] == v2.10 @@ -133,37 +133,37 @@ This release provides an end-to-end solution for benefits and eligibility verifi The focus of the 2.10 release is to provide assets for the patient sync capabilities: -* Patient sync Lightning Web Component | https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/hc-accelerator-sfdc-patient-sync-lwc-src/[Source] -* Patient Sync Process API | https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/patient-sync-prc-api/[API Specification] | https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/hc-accelerator-patient-sync-prc-api/[Implementation Template] +* Patient sync Lightning Web Component | https://anypoint.mulesoft.com/exchange/org.mule.examples/hc-accelerator-sfdc-patient-sync-lwc-src/[Source] +* Patient Sync Process API | https://anypoint.mulesoft.com/exchange/org.mule.examples/patient-sync-prc-api/[API Specification] | https://anypoint.mulesoft.com/exchange/org.mule.examples/hc-accelerator-patient-sync-prc-api/[Implementation Template] The following assets were also enhanced and improved for this release: -* FHIR R4 Location Library | https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fhir-r4-location-library/[API Specification Fragment] -* FHIR R4 Procedure Library | https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fhir-r4-procedure-library/[API Specification Fragment] -* FHIR R4 Administration API | https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fhir-r4-administration-api/[API Specification] -* FHIR R4 Clinical API | https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fhir-r4-clinical-api/[API Specification] -* Epic FHIR R4 Administration API | https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/epic-fhir-r4-administration-api/[API Specification] -* Epic FHIR R4 Clinical API | https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/epic-fhir-r4-clinical-api/[API Specification] -* Epic FHIR R4 Medications API | https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/epic-fhir-r4-medications-api/[API Specification] -* Cerner FHIR R4 Administration API | https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/cerner-fhir-r4-administration-api/[API Specification] -* Cerner Administration System API | https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/hc-accelerator-cerner-us-core-administration-sys-api/[Implementation Template] -* Health Cloud Clinical System API | https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/hc-accelerator-sfdc-us-core-clinical-sys-api/[Implementation Template] -* Health Cloud Diagnostics System API | https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/hc-accelerator-sfdc-us-core-diagnostics-sys-api/[Implementation Template] -* Health Cloud Medications System API | https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/hc-accelerator-sfdc-us-core-medications-sys-api/[Implementation Template] -* Health Cloud Administration System API | https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/hc-accelerator-sfdc-us-core-administration-sys-api/[Implementation Template] +* FHIR R4 Location Library | https://anypoint.mulesoft.com/exchange/org.mule.examples/fhir-r4-location-library/[API Specification Fragment] +* FHIR R4 Procedure Library | https://anypoint.mulesoft.com/exchange/org.mule.examples/fhir-r4-procedure-library/[API Specification Fragment] +* FHIR R4 Administration API | https://anypoint.mulesoft.com/exchange/org.mule.examples/fhir-r4-administration-api/[API Specification] +* FHIR R4 Clinical API | https://anypoint.mulesoft.com/exchange/org.mule.examples/fhir-r4-clinical-api/[API Specification] +* Epic FHIR R4 Administration API | https://anypoint.mulesoft.com/exchange/org.mule.examples/epic-fhir-r4-administration-api/[API Specification] +* Epic FHIR R4 Clinical API | https://anypoint.mulesoft.com/exchange/org.mule.examples/epic-fhir-r4-clinical-api/[API Specification] +* Epic FHIR R4 Medications API | https://anypoint.mulesoft.com/exchange/org.mule.examples/epic-fhir-r4-medications-api/[API Specification] +* Cerner FHIR R4 Administration API | https://anypoint.mulesoft.com/exchange/org.mule.examples/cerner-fhir-r4-administration-api/[API Specification] +* Cerner Administration System API | https://anypoint.mulesoft.com/exchange/org.mule.examples/hc-accelerator-cerner-us-core-administration-sys-api/[Implementation Template] +* Health Cloud Clinical System API | https://anypoint.mulesoft.com/exchange/org.mule.examples/hc-accelerator-sfdc-us-core-clinical-sys-api/[Implementation Template] +* Health Cloud Diagnostics System API | https://anypoint.mulesoft.com/exchange/org.mule.examples/hc-accelerator-sfdc-us-core-diagnostics-sys-api/[Implementation Template] +* Health Cloud Medications System API | https://anypoint.mulesoft.com/exchange/org.mule.examples/hc-accelerator-sfdc-us-core-medications-sys-api/[Implementation Template] +* Health Cloud Administration System API | https://anypoint.mulesoft.com/exchange/org.mule.examples/hc-accelerator-sfdc-us-core-administration-sys-api/[Implementation Template] The following assets are modified to support XML format for existing Epic System APIs: -* Epic Clinical System API | https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/hc-accelerator-epic-us-core-clinical-sys-api/[Implementation Template] -* Epic Diagnostics System API | https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/hc-accelerator-epic-us-core-diagnostics-sys-api/[Implementation Template] -* Epic Medications System API | https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/hc-accelerator-epic-us-core-medications-sys-api/[Implementation Template] -* Epic Administration System API | https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/hc-accelerator-epic-us-core-administration-sys-api/[Implementation Template] +* Epic Clinical System API | https://anypoint.mulesoft.com/exchange/org.mule.examples/hc-accelerator-epic-us-core-clinical-sys-api/[Implementation Template] +* Epic Diagnostics System API | https://anypoint.mulesoft.com/exchange/org.mule.examples/hc-accelerator-epic-us-core-diagnostics-sys-api/[Implementation Template] +* Epic Medications System API | https://anypoint.mulesoft.com/exchange/org.mule.examples/hc-accelerator-epic-us-core-medications-sys-api/[Implementation Template] +* Epic Administration System API | https://anypoint.mulesoft.com/exchange/org.mule.examples/hc-accelerator-epic-us-core-administration-sys-api/[Implementation Template] The following assets are modified to support updated API specifications for existing Cerner System APIs: -* Cerner Administration System API | https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/hc-accelerator-cerner-us-core-administration-sys-api/[Implementation Template] -* Cerner Clinical System API | https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/hc-accelerator-cerner-us-core-clinical-sys-api/[Implementation Template] -* Cerner Medications System API | https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/hc-accelerator-cerner-us-core-medications-sys-api/[Implementation Template] +* Cerner Administration System API | https://anypoint.mulesoft.com/exchange/org.mule.examples/hc-accelerator-cerner-us-core-administration-sys-api/[Implementation Template] +* Cerner Clinical System API | https://anypoint.mulesoft.com/exchange/org.mule.examples/hc-accelerator-cerner-us-core-clinical-sys-api/[Implementation Template] +* Cerner Medications System API | https://anypoint.mulesoft.com/exchange/org.mule.examples/hc-accelerator-cerner-us-core-medications-sys-api/[Implementation Template] == v2.9 @@ -171,30 +171,30 @@ The following assets are modified to support updated API specifications for exis This release provides API specifications and implementation templates for the Appointment Scheduling use case described https://www.hl7.org/fhir/workflow-module.html[here]: -* Appointment Scheduling Process API | https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fhir-r4-appointment-scheduling-api/[API Specification] | https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/hc-accelerator-appointment-scheduling-prc-api/[Implementation Template] -* Cerner Workflow System API | https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/cerner-fhir-r4-workflow-api/[API Specification] | https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/hc-accelerator-cerner-workflow-sys-api/[Implementation Template] -* Epic Workflow System API | https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/epic-fhir-r4-workflow-api/[API Specification] | https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/hc-accelerator-epic-workflow-sys-api/[Implementation Template] +* Appointment Scheduling Process API | https://anypoint.mulesoft.com/exchange/org.mule.examples/fhir-r4-appointment-scheduling-api/[API Specification] | https://anypoint.mulesoft.com/exchange/org.mule.examples/hc-accelerator-appointment-scheduling-prc-api/[Implementation Template] +* Cerner Workflow System API | https://anypoint.mulesoft.com/exchange/org.mule.examples/cerner-fhir-r4-workflow-api/[API Specification] | https://anypoint.mulesoft.com/exchange/org.mule.examples/hc-accelerator-cerner-workflow-sys-api/[Implementation Template] +* Epic Workflow System API | https://anypoint.mulesoft.com/exchange/org.mule.examples/epic-fhir-r4-workflow-api/[API Specification] | https://anypoint.mulesoft.com/exchange/org.mule.examples/hc-accelerator-epic-workflow-sys-api/[Implementation Template] It also includes the following Cerner assets for Patient 360: -* Cerner Administration System API | https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/cerner-fhir-r4-administration-api/[API Specification] | https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/hc-accelerator-cerner-us-core-administration-sys-api/[Implementation Template] -* Cerner Clinical System API | https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/cerner-fhir-r4-clinical-api/[API Specification] | https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/hc-accelerator-cerner-us-core-clinical-sys-api/[Implementation Template] -* Cerner Diagnostics System API | https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/cerner-fhir-r4-diagnostics-api/[API Specification] | https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/hc-accelerator-cerner-us-core-diagnostics-sys-api/[Implementation Template] -* Cerner Medications System API | https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/cerner-fhir-r4-medications-api/[API Specification] | https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/hc-accelerator-cerner-us-core-medications-sys-api/[Implementation Template] +* Cerner Administration System API | https://anypoint.mulesoft.com/exchange/org.mule.examples/cerner-fhir-r4-administration-api/[API Specification] | https://anypoint.mulesoft.com/exchange/org.mule.examples/hc-accelerator-cerner-us-core-administration-sys-api/[Implementation Template] +* Cerner Clinical System API | https://anypoint.mulesoft.com/exchange/org.mule.examples/cerner-fhir-r4-clinical-api/[API Specification] | https://anypoint.mulesoft.com/exchange/org.mule.examples/hc-accelerator-cerner-us-core-clinical-sys-api/[Implementation Template] +* Cerner Diagnostics System API | https://anypoint.mulesoft.com/exchange/org.mule.examples/cerner-fhir-r4-diagnostics-api/[API Specification] | https://anypoint.mulesoft.com/exchange/org.mule.examples/hc-accelerator-cerner-us-core-diagnostics-sys-api/[Implementation Template] +* Cerner Medications System API | https://anypoint.mulesoft.com/exchange/org.mule.examples/cerner-fhir-r4-medications-api/[API Specification] | https://anypoint.mulesoft.com/exchange/org.mule.examples/hc-accelerator-cerner-us-core-medications-sys-api/[Implementation Template] The following assets were also enhanced and improved for this release: -* Epic Administration System API | https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/epic-fhir-r4-administration-api/[API Specification] | https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/hc-accelerator-epic-us-core-administration-sys-api/[Implementation Template] -* Epic Clinical System API | https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/epic-fhir-r4-clinical-api/[API Specification] | https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/hc-accelerator-epic-us-core-clinical-sys-api/[Implementation Template] -* Epic Diagnostics System API | https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/epic-fhir-r4-diagnostics-api[API Specification] | https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/hc-accelerator-epic-us-core-diagnostics-sys-api/[Implementation Template] -* Epic Medications System API | https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/epic-fhir-r4-medications-api/[API Specification] | https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/hc-accelerator-epic-us-core-medications-sys-api/[Implementation Template] -* FHIR R4 Administration API | https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fhir-r4-administration-api/[API Specification] -* FHIR R4 Clinical API | https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fhir-r4-clinical-api/[API Specification] -* FHIR R4 Diagnostics API | https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fhir-r4-diagnostics-api/[API Specification] -* FHIR R4 Medications API | https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fhir-r4-medications-api/[API Specification] -* FHIR R4 Workflow API | https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fhir-r4-workflow-api/[API Specification] -* https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/hc-accelerator-sfdc-adt-api/[HL7 V2 ADT Process API] -* https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/hc-accelerator-sfdc-oru-api/[HL7 V2 ORU Process API] +* Epic Administration System API | https://anypoint.mulesoft.com/exchange/org.mule.examples/epic-fhir-r4-administration-api/[API Specification] | https://anypoint.mulesoft.com/exchange/org.mule.examples/hc-accelerator-epic-us-core-administration-sys-api/[Implementation Template] +* Epic Clinical System API | https://anypoint.mulesoft.com/exchange/org.mule.examples/epic-fhir-r4-clinical-api/[API Specification] | https://anypoint.mulesoft.com/exchange/org.mule.examples/hc-accelerator-epic-us-core-clinical-sys-api/[Implementation Template] +* Epic Diagnostics System API | https://anypoint.mulesoft.com/exchange/org.mule.examples/epic-fhir-r4-diagnostics-api[API Specification] | https://anypoint.mulesoft.com/exchange/org.mule.examples/hc-accelerator-epic-us-core-diagnostics-sys-api/[Implementation Template] +* Epic Medications System API | https://anypoint.mulesoft.com/exchange/org.mule.examples/epic-fhir-r4-medications-api/[API Specification] | https://anypoint.mulesoft.com/exchange/org.mule.examples/hc-accelerator-epic-us-core-medications-sys-api/[Implementation Template] +* FHIR R4 Administration API | https://anypoint.mulesoft.com/exchange/org.mule.examples/fhir-r4-administration-api/[API Specification] +* FHIR R4 Clinical API | https://anypoint.mulesoft.com/exchange/org.mule.examples/fhir-r4-clinical-api/[API Specification] +* FHIR R4 Diagnostics API | https://anypoint.mulesoft.com/exchange/org.mule.examples/fhir-r4-diagnostics-api/[API Specification] +* FHIR R4 Medications API | https://anypoint.mulesoft.com/exchange/org.mule.examples/fhir-r4-medications-api/[API Specification] +* FHIR R4 Workflow API | https://anypoint.mulesoft.com/exchange/org.mule.examples/fhir-r4-workflow-api/[API Specification] +* https://anypoint.mulesoft.com/exchange/org.mule.examples/hc-accelerator-sfdc-adt-api/[HL7 V2 ADT Process API] +* https://anypoint.mulesoft.com/exchange/org.mule.examples/hc-accelerator-sfdc-oru-api/[HL7 V2 ORU Process API] == v2.8 @@ -203,24 +203,24 @@ The following assets were also enhanced and improved for this release: This release includes: * Implementation templates added for the following Health Cloud and Epic APIs for Patient 360: - ** https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/hc-accelerator-epic-us-core-clinical-sys-api/[Epic Clinical System API] - ** https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/hc-accelerator-epic-us-core-diagnostics-sys-api/[Epic Diagnostics System API] - ** https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/hc-accelerator-epic-us-core-medications-sys-api/[Epic Medications System API] - ** https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/hc-accelerator-sfdc-us-core-clinical-sys-api/[Health Cloud Clinical System API] - ** https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/hc-accelerator-sfdc-us-core-diagnostics-sys-api/[Health Cloud Diagnostics System API] - ** https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/hc-accelerator-sfdc-us-core-medications-sys-api/[Health Cloud Medications System API] + ** https://anypoint.mulesoft.com/exchange/org.mule.examples/hc-accelerator-epic-us-core-clinical-sys-api/[Epic Clinical System API] + ** https://anypoint.mulesoft.com/exchange/org.mule.examples/hc-accelerator-epic-us-core-diagnostics-sys-api/[Epic Diagnostics System API] + ** https://anypoint.mulesoft.com/exchange/org.mule.examples/hc-accelerator-epic-us-core-medications-sys-api/[Epic Medications System API] + ** https://anypoint.mulesoft.com/exchange/org.mule.examples/hc-accelerator-sfdc-us-core-clinical-sys-api/[Health Cloud Clinical System API] + ** https://anypoint.mulesoft.com/exchange/org.mule.examples/hc-accelerator-sfdc-us-core-diagnostics-sys-api/[Health Cloud Diagnostics System API] + ** https://anypoint.mulesoft.com/exchange/org.mule.examples/hc-accelerator-sfdc-us-core-medications-sys-api/[Health Cloud Medications System API] * Enhancements and improvements made to the following templates: - ** https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/hc-accelerator-epic-us-core-administration-sys-api/[Epic Administration System API] - ** https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/hc-accelerator-sfdc-us-core-administration-sys-api/[Health Cloud Administration System API] + ** https://anypoint.mulesoft.com/exchange/org.mule.examples/hc-accelerator-epic-us-core-administration-sys-api/[Epic Administration System API] + ** https://anypoint.mulesoft.com/exchange/org.mule.examples/hc-accelerator-sfdc-us-core-administration-sys-api/[Health Cloud Administration System API] * Updated the following templates to support the Spring 2021 release of the Health Cloud data model: - ** https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/hc-accelerator-sfdc-adt-api/[HL7 V2 ADT Process API] - ** https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/hc-accelerator-sfdc-oru-api/[HL7 V2 ORU Process API] + ** https://anypoint.mulesoft.com/exchange/org.mule.examples/hc-accelerator-sfdc-adt-api/[HL7 V2 ADT Process API] + ** https://anypoint.mulesoft.com/exchange/org.mule.examples/hc-accelerator-sfdc-oru-api/[HL7 V2 ORU Process API] * Additional updates and improvements: - ** https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/hc-accelerator-hl7v2-to-fhir-sys-api/[HL7 V2 to FHIR System API] - ** https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fhir-r4-capabilitystatement-api/[FHIR R4 Capability Statement API] + ** https://anypoint.mulesoft.com/exchange/org.mule.examples/hc-accelerator-hl7v2-to-fhir-sys-api/[HL7 V2 to FHIR System API] + ** https://anypoint.mulesoft.com/exchange/org.mule.examples/fhir-r4-capabilitystatement-api/[FHIR R4 Capability Statement API] == v2.7 @@ -229,9 +229,9 @@ This release includes: This release includes: * Implementation templates for the Administration API for Patient 360: - * https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/hc-accelerator-sfdc-us-core-administration-sys-api/[Health Cloud Administration System API] - Supports the Spring 2021 release of the Health Cloud data model. - * https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/hc-accelerator-epic-us-core-administration-sys-api/[EPIC Administration System API] - Supports the Patient resource currently. Additional resources will be supported in the next release. -* Reference implementation for https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/hc-accelerator-okta-smartfhir/[SMART on FHIR with Okta]. + * https://anypoint.mulesoft.com/exchange/org.mule.examples/hc-accelerator-sfdc-us-core-administration-sys-api/[Health Cloud Administration System API] - Supports the Spring 2021 release of the Health Cloud data model. + * https://anypoint.mulesoft.com/exchange/org.mule.examples/hc-accelerator-epic-us-core-administration-sys-api/[EPIC Administration System API] - Supports the Patient resource currently. Additional resources will be supported in the next release. +* Reference implementation for https://anypoint.mulesoft.com/exchange/org.mule.examples/hc-accelerator-okta-smartfhir/[SMART on FHIR with Okta]. == v2.6 @@ -240,7 +240,7 @@ This release includes: This release includes: * API specifications for Patient 360 to support the Spring 2021 release of the Health Cloud data model. -* Added support for the ORU message type in the https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/hc-accelerator-hl7v2-to-fhir-sys-api/[HL7 v2 to FHIR converter]. +* Added support for the ORU message type in the https://anypoint.mulesoft.com/exchange/org.mule.examples/hc-accelerator-hl7v2-to-fhir-sys-api/[HL7 v2 to FHIR converter]. == v2.5 @@ -248,7 +248,7 @@ This release includes: This release provides Healthcare organizations with a reference implementation to convert HL7 v2 messages to FHIR to integrate with different systems using the https://build.fhir.org/ig/HL7/v2-to-fhir/mapping_guidelines.html[guidelines] provided by the https://build.fhir.org/ig/HL7/v2-to-fhir/[HL7 v2 to FHIR Implementation Guide]. -* https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fhir-r4-convert-api/[API specification] and https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/hc-accelerator-hl7v2-to-fhir-sys-api/[implementation template] for HL7 v2 to FHIR System API +* https://anypoint.mulesoft.com/exchange/org.mule.examples/fhir-r4-convert-api/[API specification] and https://anypoint.mulesoft.com/exchange/org.mule.examples/hc-accelerator-hl7v2-to-fhir-sys-api/[implementation template] for HL7 v2 to FHIR System API == v2.4 @@ -256,8 +256,8 @@ This release provides Healthcare organizations with a reference implementation t The focus of release 2.4 is on providing the API specifications and implementation templates for https://www.cms.gov/Regulations-and-Guidance/Guidance/Interoperability/index[CMS Interoperability and Patient Access final rule]. The release contains the following assets: -* https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fhir-r4-patient-access-clinical-exp-api/[API specification] and https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/hc-accelerator-sfdc-us-core-patientaccessclinicaldata-exp-api/[implementation template] for Patient Access API - Clinical Data as per the https://www.hl7.org/fhir/us/core/[US Core Implementation Guide]. -* https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fhir-r4-patient-access-claims-encounter-exp-api/[API specification] and https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/hc-accelerator-carin-patientclaimsencounterdata-exp-api/[implementation template] for Patient Access API - Claims and Encounter Data as per the https://build.fhir.org/ig/HL7/carin-bb/index.html[CARIN Implementation Guide for Blue Button]. +* https://anypoint.mulesoft.com/exchange/org.mule.examples/fhir-r4-patient-access-clinical-exp-api/[API specification] and https://anypoint.mulesoft.com/exchange/org.mule.examples/hc-accelerator-sfdc-us-core-patientaccessclinicaldata-exp-api/[implementation template] for Patient Access API - Clinical Data as per the https://www.hl7.org/fhir/us/core/[US Core Implementation Guide]. +* https://anypoint.mulesoft.com/exchange/org.mule.examples/fhir-r4-patient-access-claims-encounter-exp-api/[API specification] and https://anypoint.mulesoft.com/exchange/org.mule.examples/hc-accelerator-carin-patientclaimsencounterdata-exp-api/[implementation template] for Patient Access API - Claims and Encounter Data as per the https://build.fhir.org/ig/HL7/carin-bb/index.html[CARIN Implementation Guide for Blue Button]. * Minor bug fixes. == v2.3 @@ -266,8 +266,8 @@ The focus of release 2.4 is on providing the API specifications and implementati The focus of release 2.3 is on providing the API specifications and implementation templates for https://www.cms.gov/Regulations-and-Guidance/Guidance/Interoperability/index[CMS Interoperability and Patient Access final rule]. The release contains the following assets: -* https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fhir-r4-pdex-formulary-api/[API specification] and https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/hc-accelerator-pdex-formulary-exp-api/[implementation template] for Formulary API as per the http://build.fhir.org/ig/HL7/davinci-pdex-formulary/index.html[DaVinci PDEX US Drug Formulary Implementation Guide]. -* https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fhir-r4-plannet-providerdirectory-api/[API specification] and https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/hc-accelerator-plannet-providerdirectory-exp-api/[implementation template] for Provider Directory API as per the https://build.fhir.org/ig/HL7/davinci-pdex-plan-net/index.html[DaVinci PDEX Plan Net Implementation Guide]. +* https://anypoint.mulesoft.com/exchange/org.mule.examples/fhir-r4-pdex-formulary-api/[API specification] and https://anypoint.mulesoft.com/exchange/org.mule.examples/hc-accelerator-pdex-formulary-exp-api/[implementation template] for Formulary API as per the http://build.fhir.org/ig/HL7/davinci-pdex-formulary/index.html[DaVinci PDEX US Drug Formulary Implementation Guide]. +* https://anypoint.mulesoft.com/exchange/org.mule.examples/fhir-r4-plannet-providerdirectory-api/[API specification] and https://anypoint.mulesoft.com/exchange/org.mule.examples/hc-accelerator-plannet-providerdirectory-exp-api/[implementation template] for Provider Directory API as per the https://build.fhir.org/ig/HL7/davinci-pdex-plan-net/index.html[DaVinci PDEX Plan Net Implementation Guide]. * Minor bug fixes. == v2.2 @@ -276,8 +276,8 @@ The focus of release 2.3 is on providing the API specifications and implementati The focus of release 2.2 is on providing the implementation template for Electronic Laboratory Reporting to CalREDIE. The release contains the following assets: -* Implementation template for https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/hc-accelerator-lblims-calredie-process-bapi/[Electronic Laboratory Reporting], which is the notifiable condition to CalREDIE. -* API policy to return https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fhir-error-policy/[FHIR compliant OperationOutcome response]. +* Implementation template for https://anypoint.mulesoft.com/exchange/org.mule.examples/hc-accelerator-lblims-calredie-process-bapi/[Electronic Laboratory Reporting], which is the notifiable condition to CalREDIE. +* API policy to return https://anypoint.mulesoft.com/exchange/org.mule.examples/fhir-error-policy/[FHIR compliant OperationOutcome response]. * Minor bug fixes. == v2.1.1 diff --git a/healthcare/2.19/modules/ROOT/pages/sfdc-data-cloud-setup-guide.adoc b/healthcare/2.19/modules/ROOT/pages/sfdc-data-cloud-setup-guide.adoc index 961712f21..3bdd3db41 100644 --- a/healthcare/2.19/modules/ROOT/pages/sfdc-data-cloud-setup-guide.adoc +++ b/healthcare/2.19/modules/ROOT/pages/sfdc-data-cloud-setup-guide.adoc @@ -1,7 +1,7 @@ = Salesforce Data Cloud Setup Guide :hls-version: 2.19 -The following provides guidance on Salesforce Data Cloud setup required for the https://www.anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/mulesoft-accelerator-for-healthcare/minor/{hls-version}/pages/Use%20case%207%20-%20Population%20health%20management/[Population Health Management] use case. +The following provides guidance on Salesforce Data Cloud setup required for the https://www.anypoint.mulesoft.com/exchange/org.mule.examples/mulesoft-accelerator-for-healthcare/minor/{hls-version}/pages/Use%20case%207%20-%20Population%20health%20management/[Population Health Management] use case. * <> * <> @@ -25,7 +25,7 @@ Connectors are specialized data streams that communicate with external sources t Customer Data Platform has connectors for: Marketing Cloud Email Studio, MobileConnect, MobilePush, Marketing Cloud Data Extensions, for Salesforce CRM, Ingestion API, Interaction Studio, and for data outside Salesforce via cloud storage providers. -The https://www.anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/mulesoft-accelerator-for-healthcare/minor/{hls-version}/pages/Use%20case%207%20-%20Population%20health%20management/[Population Health Management] use case uses the following connectors to ingest data into cdp: +The https://www.anypoint.mulesoft.com/exchange/org.mule.examples/mulesoft-accelerator-for-healthcare/minor/{hls-version}/pages/Use%20case%207%20-%20Population%20health%20management/[Population Health Management] use case uses the following connectors to ingest data into cdp: * Salesforce CRM - to connect data from a Salesforce Health Cloud instance to Data Cloud * Ingestion API - to connect data from external source systems like Azure, Epic, Cerner, and other EHR systems via MuleSoft's CDP connector. @@ -50,7 +50,7 @@ Follow the below steps to create connection to your Salesforce Health Cloud org. After you create your Customer Data Platform instance and set up your Salesforce Health Cloud connection, you can install standard data bundles that are powered by data kits to deploy data within Customer Data Platform. -For the https://www.anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/mulesoft-accelerator-for-healthcare/minor/{hls-version}/pages/Use%20case%207%20-%20Population%20health%20management/[Population Health Management] use case, Service Cloud bundle is installed. Refer https://help.salesforce.com/s/articleView?id=sf.c360_a_install_standard_data_bundles_powered_by_data_kits.htm&type=5[link] to install the bundle. +For the https://www.anypoint.mulesoft.com/exchange/org.mule.examples/mulesoft-accelerator-for-healthcare/minor/{hls-version}/pages/Use%20case%207%20-%20Population%20health%20management/[Population Health Management] use case, Service Cloud bundle is installed. Refer https://help.salesforce.com/s/articleView?id=sf.c360_a_install_standard_data_bundles_powered_by_data_kits.htm&type=5[link] to install the bundle. === Ingestion API @@ -63,14 +63,14 @@ Follow the steps in each section below to setup and configure ingestion API to p . In Data Cloud, select Data Cloud Setup. . Click Ingestion API. . Click New, enter a name for the API source, then click Save. On the details page for the new connector, you must upload a schema file in OpenAPI (OAS) format with a `.yaml` file extension. The schema file describes how data transferred via the API is structured. *Note:* Ingestion API schemas have set requirements - review the schema requirements before ingestion. -. Click Upload Schema and navigate to the location of the file you want to use. Select the file and click Open. For the https://www.anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/mulesoft-accelerator-for-healthcare/minor/{hls-version}/pages/Use%20case%207%20-%20Population%20health%20management/[Population Health Management] use case the schema file `mule-hls-cdp-connector-schema.yaml` is available under `/src/test/resources` of the Implementation Template https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/hls-salesforce-cdp-sys-api[HLS CDP System API]. +. Click Upload Schema and navigate to the location of the file you want to use. Select the file and click Open. For the https://www.anypoint.mulesoft.com/exchange/org.mule.examples/mulesoft-accelerator-for-healthcare/minor/{hls-version}/pages/Use%20case%207%20-%20Population%20health%20management/[Population Health Management] use case the schema file `mule-hls-cdp-connector-schema.yaml` is available under `/src/test/resources` of the Implementation Template https://anypoint.mulesoft.com/exchange/org.mule.examples/hls-salesforce-cdp-sys-api[HLS CDP System API]. . Preview all the detected objects and their attributes in your schema. . Click Save. The connector page reflects the updated status. . After the schema file is uploaded, you can create data streams to begin sending data from your source system. -For the https://www.anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/mulesoft-accelerator-for-healthcare/minor/{hls-version}/pages/Use%20case%207%20-%20Population%20health%20management/[Population Health Management] use case, the external systems Azure, Epic, Cerner, and other EHR systems contain data to be pushed to Data Cloud through MuleSoft's CDP connector using the Ingestion API. The name of the Connector used will appear under `Ingestion API` drop down while creating a new Data Stream. +For the https://www.anypoint.mulesoft.com/exchange/org.mule.examples/mulesoft-accelerator-for-healthcare/minor/{hls-version}/pages/Use%20case%207%20-%20Population%20health%20management/[Population Health Management] use case, the external systems Azure, Epic, Cerner, and other EHR systems contain data to be pushed to Data Cloud through MuleSoft's CDP connector using the Ingestion API. The name of the Connector used will appear under `Ingestion API` drop down while creating a new Data Stream. -The schema used for the https://www.anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/mulesoft-accelerator-for-healthcare/minor/{hls-version}/pages/Use%20case%207%20-%20Population%20health%20management/[Population Health Management] use case can be found in the implementation template. The following objects are added for this use case: +The schema used for the https://www.anypoint.mulesoft.com/exchange/org.mule.examples/mulesoft-accelerator-for-healthcare/minor/{hls-version}/pages/Use%20case%207%20-%20Population%20health%20management/[Population Health Management] use case can be found in the implementation template. The following objects are added for this use case: * condition * immunization @@ -116,7 +116,7 @@ To create data streams from Salesforce CRM starter bundle: Refer this https://help.salesforce.com/s/articleView?id=sf.c360_a_create_crm_starter_bundle.htm&type=5[link] to create data streams using starter bundle to begin the flow of data from a Salesforce Health Cloud data source. -For the https://www.anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/mulesoft-accelerator-for-healthcare/minor/{hls-version}/pages/Use%20case%207%20-%20Population%20health%20management/[Population Health Management] use case, data streams for Salesforce Health Cloud Account and Contact objects are created using Salesforce CRM Service bundle. +For the https://www.anypoint.mulesoft.com/exchange/org.mule.examples/mulesoft-accelerator-for-healthcare/minor/{hls-version}/pages/Use%20case%207%20-%20Population%20health%20management/[Population Health Management] use case, data streams for Salesforce Health Cloud Account and Contact objects are created using Salesforce CRM Service bundle. To create data streams from Salesforce Health Cloud data source: @@ -134,11 +134,11 @@ To add permissions for objects and their fields: Repeat these steps for all objects and fields you want to ingest into Data Cloud. Now, create data streams for the required objects by following the steps in this https://help.salesforce.com/s/articleView?id=sf.c360_a_create_crm_data_stream.htm&type=5&language=en_US[link]. -For the https://www.anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/mulesoft-accelerator-for-healthcare/minor/{hls-version}/pages/Use%20case%207%20-%20Population%20health%20management/[Population Health Management] use case, data streams for Contact Point Objects, Identifier, and ContactContactRelation are created. +For the https://www.anypoint.mulesoft.com/exchange/org.mule.examples/mulesoft-accelerator-for-healthcare/minor/{hls-version}/pages/Use%20case%207%20-%20Population%20health%20management/[Population Health Management] use case, data streams for Contact Point Objects, Identifier, and ContactContactRelation are created. === Create an Ingestion API data stream -After uploading the schema file for Ingestion API Connector, create a data stream from your source objects. For the https://www.anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/mulesoft-accelerator-for-healthcare/minor/{hls-version}/pages/Use%20case%207%20-%20Population%20health%20management/[Population Health Management] use case, data streams for condition, immunization and webEngagement are created. +After uploading the schema file for Ingestion API Connector, create a data stream from your source objects. For the https://www.anypoint.mulesoft.com/exchange/org.mule.examples/mulesoft-accelerator-for-healthcare/minor/{hls-version}/pages/Use%20case%207%20-%20Population%20health%20management/[Population Health Management] use case, data streams for condition, immunization and webEngagement are created. . In Data Cloud, select Data Streams. . In recently viewed data streams, click New. @@ -147,7 +147,7 @@ After uploading the schema file for Ingestion API Connector, create a data strea . Check the objects found in the schema you want to use and click Next. . At the New Data Stream dialog box, configure the following: ** Primary Key: A true Primary Key needs to be leveraged for Data Cloud. If one does not exist, you will need to create a Formula Field for the Primary Key. - ** Category: Choose between Profile, Engagement or Other. *Note:* For the https://www.anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/mulesoft-accelerator-for-healthcare/minor/{hls-version}/pages/Use%20case%207%20-%20Population%20health%20management/[Population Health Management] use case, the category for all the objects in the schema are Other. + ** Category: Choose between Profile, Engagement or Other. *Note:* For the https://www.anypoint.mulesoft.com/exchange/org.mule.examples/mulesoft-accelerator-for-healthcare/minor/{hls-version}/pages/Use%20case%207%20-%20Population%20health%20management/[Population Health Management] use case, the category for all the objects in the schema are Other. ** Record Modified Date: To order Profile modifications, use the Record Modified Date. *Note:* A record modified field that indicates when each incoming record was last modified is required for Engagement object types. While the field requirement is optional for Profile and Other objects, it is encouraged to provide the record modified field to ensure incoming records are processed in the right order. ** Date Time Field: Used to represent when Engagement from an external source occurred at ingestion. ** Click the `New Formula Field` (Optional). @@ -156,7 +156,7 @@ After uploading the schema file for Ingestion API Connector, create a data strea . Click Deploy. If you have only created one data stream, the data stream's record page appears. If you've created multiple data streams, the view refreshes to show all recently viewed data streams. . Wait up to one hour for your data to appear in your data stream. Map your data stream to data model objects to start using your data. -For the https://www.anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/mulesoft-accelerator-for-healthcare/minor/{hls-version}/pages/Use%20case%207%20-%20Population%20health%20management/[Population Health Management] use case, data stream is created for the objects added in schema by following the steps above. At step 6, click `New Formula field` with `Field Label` as `uniqueId` with `Formula Return` Type as `Text`. Under `Transformation Formula`, the formula is created as below for each of the object. +For the https://www.anypoint.mulesoft.com/exchange/org.mule.examples/mulesoft-accelerator-for-healthcare/minor/{hls-version}/pages/Use%20case%207%20-%20Population%20health%20management/[Population Health Management] use case, data stream is created for the objects added in schema by following the steps above. At step 6, click `New Formula field` with `Field Label` as `uniqueId` with `Formula Return` Type as `Text`. Under `Transformation Formula`, the formula is created as below for each of the object. * condition: `CONCAT(sourceField['patientMrn'],"~",sourceField['conditionCode'])` * immunization: `CONCAT(sourceField['patientMrn'],"~",sourceField['vaccineCode'],"~",sourceField['vaccineStatus'],"~",sourceField['vaccineDate'])` @@ -178,9 +178,9 @@ As part of your Connected App set up for Ingestion API, you must select the foll The MuleSoft Connector for CDP provides customers a pipeline to send data into Data Cloud. This connector works with the Data Cloud Bulk and Streaming API, depending on the operation you configure. Each API call uses a request/response pattern over an HTTPS connection. All required request headers, error handling, and HTTPS connection configurations are built into the connector. -Refer to the https://dev-docs-internal.kqa.msap.io/beta-accelerators/salesforce-cdp-connector/1.1/[CDP Connector documentation] for additional details on configuration and available operations. +Refer to the https://docs.mulesoft.com/salesforce-cdp-connector/1.1/[CDP Connector documentation] for additional details on configuration and available operations. -For the https://www.anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/mulesoft-accelerator-for-healthcare/minor/{hls-version}/pages/Use%20case%207%20-%20Population%20health%20management/[Population Health Management] use case, refer to the https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/hls-salesforce-cdp-sys-api-spec/[HLS CDP System API] specification and https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/hls-salesforce-cdp-sys-api[HLS CDP System API] implementation template assets. +For the https://www.anypoint.mulesoft.com/exchange/org.mule.examples/mulesoft-accelerator-for-healthcare/minor/{hls-version}/pages/Use%20case%207%20-%20Population%20health%20management/[Population Health Management] use case, refer to the https://anypoint.mulesoft.com/exchange/org.mule.examples/hls-salesforce-cdp-sys-api-spec/[HLS CDP System API] specification and https://anypoint.mulesoft.com/exchange/org.mule.examples/hls-salesforce-cdp-sys-api[HLS CDP System API] implementation template assets. == Data modeling and data mapping @@ -220,7 +220,7 @@ Objects in the data model created by the customer for Data Cloud implementation When mapping your party area data, complete the required fields and relationships to successfully use Identity Resolution, Segmentation, and Activation. -Default mapping exists for Account and Contact Objects if service Bundle is used to create data streams. For the https://www.anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/mulesoft-accelerator-for-healthcare/minor/{hls-version}/pages/Use%20case%207%20-%20Population%20health%20management/[Population Health Management] use case, the default mapping from Account and Contact DSOs to Contact Point DMOs are removed. Data Streams to Data Model Objects (DMO) are mapped as per the below table. +Default mapping exists for Account and Contact Objects if service Bundle is used to create data streams. For the https://www.anypoint.mulesoft.com/exchange/org.mule.examples/mulesoft-accelerator-for-healthcare/minor/{hls-version}/pages/Use%20case%207%20-%20Population%20health%20management/[Population Health Management] use case, the default mapping from Account and Contact DSOs to Contact Point DMOs are removed. Data Streams to Data Model Objects (DMO) are mapped as per the below table. |=== | Data Stream Name (DSO) | Custom Data Model Object (DMO) | Standard Data Model Object (DMO) @@ -250,7 +250,7 @@ Default mapping exists for Account and Contact Objects if service Bundle is used | |=== -For the https://www.anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/mulesoft-accelerator-for-healthcare/minor/{hls-version}/pages/Use%20case%207%20-%20Population%20health%20management/[Population Health Management] use case, below Data Mappings are created between Data Streams and DMOs/custom DMOs. +For the https://www.anypoint.mulesoft.com/exchange/org.mule.examples/mulesoft-accelerator-for-healthcare/minor/{hls-version}/pages/Use%20case%207%20-%20Population%20health%20management/[Population Health Management] use case, below Data Mappings are created between Data Streams and DMOs/custom DMOs. *Data Mappings of Account Data Stream to Account DMO* @@ -490,7 +490,7 @@ Some of the mappings are added by default from Bundle. Mapping needs to be chang | userId |=== -For the https://www.anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/mulesoft-accelerator-for-healthcare/minor/{hls-version}/pages/Use%20case%207%20-%20Population%20health%20management/[Population Health Management] use case, below DMOs and relationships needs to be maintained when Data mappings are done between Data Stream and DMOs. +For the https://www.anypoint.mulesoft.com/exchange/org.mule.examples/mulesoft-accelerator-for-healthcare/minor/{hls-version}/pages/Use%20case%207%20-%20Population%20health%20management/[Population Health Management] use case, below DMOs and relationships needs to be maintained when Data mappings are done between Data Stream and DMOs. *Data Relationships between DMOs* @@ -542,7 +542,7 @@ For the https://www.anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10 == Identity Resolution -NOTE: For the https://www.anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/mulesoft-accelerator-for-healthcare/minor/{hls-version}/pages/Use%20case%207%20-%20Population%20health%20management/[Population Health Management] use case, identity resolution rulesets were not required. +NOTE: For the https://www.anypoint.mulesoft.com/exchange/org.mule.examples/mulesoft-accelerator-for-healthcare/minor/{hls-version}/pages/Use%20case%207%20-%20Population%20health%20management/[Population Health Management] use case, identity resolution rulesets were not required. Use identity resolution to consolidate data from difference sources into a comprehensive view of your customer called a unified profile. Identity resolution uses matching and reconciliation rules to link data about people into unified profiles. Each unified profile contains all the unique contact point values from all sources. @@ -550,7 +550,7 @@ Set up identity resolution rulesets after mapping source data to data model obje == Calculated Insights -NOTE: For the https://www.anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/mulesoft-accelerator-for-healthcare/minor/{hls-version}/pages/Use%20case%207%20-%20Population%20health%20management/[Population Health Management] use case, Calculated Insights were not required. +NOTE: For the https://www.anypoint.mulesoft.com/exchange/org.mule.examples/mulesoft-accelerator-for-healthcare/minor/{hls-version}/pages/Use%20case%207%20-%20Population%20health%20management/[Population Health Management] use case, Calculated Insights were not required. The Calculated Insights feature lets you define and calculate multidimensional metrics on your entire digital state stored in Salesforce Customer Data Platform. @@ -577,7 +577,7 @@ TIP: Leave the Publish Schedule as *Don't Refresh for now*, and then fill it in Segment On: Segment On defines the target entity (object) used to build your segment. For example, you can build a segment on Unified Individual or Account or Individual. You can choose any entity marked as type Profile during ingestion. -For the https://www.anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/mulesoft-accelerator-for-healthcare/minor/{hls-version}/pages/Use%20case%207%20-%20Population%20health%20management/[Population Health Management] use case, create Segments on Individual. +For the https://www.anypoint.mulesoft.com/exchange/org.mule.examples/mulesoft-accelerator-for-healthcare/minor/{hls-version}/pages/Use%20case%207%20-%20Population%20health%20management/[Population Health Management] use case, create Segments on Individual. Example segment: @@ -615,7 +615,7 @@ For the Publish Schedule, we update it to reflect a Publish Schedule of every 12 Create activation targets to build, and activate data segments with Data Cloud. -For the https://www.anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/mulesoft-accelerator-for-healthcare/minor/{hls-version}/pages/Use%20case%207%20-%20Population%20health%20management/[Population Health Management] use case, create a Marketing Cloud Activation Target. +For the https://www.anypoint.mulesoft.com/exchange/org.mule.examples/mulesoft-accelerator-for-healthcare/minor/{hls-version}/pages/Use%20case%207%20-%20Population%20health%20management/[Population Health Management] use case, create a Marketing Cloud Activation Target. *Activation Target - Marketing Cloud:* @@ -624,8 +624,8 @@ Before creating an activation target, configure the Marketing Cloud connector in . Click Setup gear icon and then Data Cloud Setup. . Select Marketing Cloud. . Enter the Credentials to authenticate your Marketing Cloud account. You can proceed with the next step in the setup only if the authentication is successful. -. Data Source setup - this step is optional. This needs to be set up if you are planning to ingest data from Marketing Cloud into Data Cloud. *Note:* For the https://www.anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/mulesoft-accelerator-for-healthcare/minor/{hls-version}/pages/Use%20case%207%20-%20Population%20health%20management/[Population Health Management] use case, this step is skipped. -. Select Business Units to activate - this step is optional. To add or remove business units (BU), click the arrows between the two columns. *Note:* For the https://www.anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/mulesoft-accelerator-for-healthcare/minor/{hls-version}/pages/Use%20case%207%20-%20Population%20health%20management/[Population Health Management] use case, select business units to publish segments to Marketing Cloud. +. Data Source setup - this step is optional. This needs to be set up if you are planning to ingest data from Marketing Cloud into Data Cloud. *Note:* For the https://www.anypoint.mulesoft.com/exchange/org.mule.examples/mulesoft-accelerator-for-healthcare/minor/{hls-version}/pages/Use%20case%207%20-%20Population%20health%20management/[Population Health Management] use case, this step is skipped. +. Select Business Units to activate - this step is optional. To add or remove business units (BU), click the arrows between the two columns. *Note:* For the https://www.anypoint.mulesoft.com/exchange/org.mule.examples/mulesoft-accelerator-for-healthcare/minor/{hls-version}/pages/Use%20case%207%20-%20Population%20health%20management/[Population Health Management] use case, select business units to publish segments to Marketing Cloud. Create an activation target in Data Cloud to publish segments to Marketing Cloud business units. diff --git a/healthcare/2.19/modules/ROOT/pages/sfdc-health-cloud-setup-guide.adoc b/healthcare/2.19/modules/ROOT/pages/sfdc-health-cloud-setup-guide.adoc index a4876f44d..b7bac4b99 100644 --- a/healthcare/2.19/modules/ROOT/pages/sfdc-health-cloud-setup-guide.adoc +++ b/healthcare/2.19/modules/ROOT/pages/sfdc-health-cloud-setup-guide.adoc @@ -41,13 +41,13 @@ This accelerator uses MuleSoft's HL7 Connector. If you're required to use custom * Modify the message structure schema file (for example, ADT_A31.esl) to include your custom segment (or modify an existing segment to fit your needs). * Modify the basedefs.esl file to include the changes for segment definitions. -The https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/hc-accelerator-sfdc-adt-api/[implementation template^] for storing ADT messages in Salesforce Health Cloud shows an example of custom segment processing. Please check the src/main/resources/config/hl7/v2_2 folder in the implementation template. This folder has the necessary changes required to process custom segment `ZG1`. +The https://anypoint.mulesoft.com/exchange/org.mule.examples/hc-accelerator-sfdc-adt-api/[implementation template^] for storing ADT messages in Salesforce Health Cloud shows an example of custom segment processing. Please check the src/main/resources/config/hl7/v2_2 folder in the implementation template. This folder has the necessary changes required to process custom segment `ZG1`. -For additional details on HL7 Connector, please refer to the https://dev-docs-internal.kqa.msap.io/beta-accelerators/connectors/hl7/hl7-connector[documentation^]. +For additional details on HL7 Connector, please refer to the https://docs.mulesoft.com/connectors/hl7/hl7-connector[documentation^]. == Maven POM Parent -In addition to some global settings and repository references, the Maven https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/accelerator-pom-parent-src/[POM parent^] config also defines the versions of all MuleSoft connectors and modules used by applications. Refer to the https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/accelerator-pom-parent-src/[Exchange documentation^] for information on how to make changes to the POM parent file. +In addition to some global settings and repository references, the Maven https://anypoint.mulesoft.com/exchange/org.mule.examples/accelerator-pom-parent-src/[POM parent^] config also defines the versions of all MuleSoft connectors and modules used by applications. Refer to the https://anypoint.mulesoft.com/exchange/org.mule.examples/accelerator-pom-parent-src/[Exchange documentation^] for information on how to make changes to the POM parent file. == See Also diff --git a/healthcare/2.19/modules/ROOT/pages/smart-fhir-okta.adoc b/healthcare/2.19/modules/ROOT/pages/smart-fhir-okta.adoc index 293f4ce13..809023dd4 100644 --- a/healthcare/2.19/modules/ROOT/pages/smart-fhir-okta.adoc +++ b/healthcare/2.19/modules/ROOT/pages/smart-fhir-okta.adoc @@ -1,6 +1,6 @@ = SMART on FHIR with Okta -See the https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/hc-accelerator-okta-smartfhir/[Okta SMART on FHIR - Implementation Template^] asset, which walks you through how to set up a reference SMART on FHIR implementation on Anypoint Platform using Okta as the identity provider. +See the https://anypoint.mulesoft.com/exchange/org.mule.examples/hc-accelerator-okta-smartfhir/[Okta SMART on FHIR - Implementation Template^] asset, which walks you through how to set up a reference SMART on FHIR implementation on Anypoint Platform using Okta as the identity provider. The **S**ubstitutable **M**edical **A**pplications and **R**eusable **T**echnology (SMART) is a web/mobile app, which is typically embedded in EHR but can also serve as a standalone smartphone app. SMART on FHIR provides a consistent approach to security and data requirements for health applications. It also provides a workflow to securely request access to data, receive the data, and use the data. @@ -20,13 +20,13 @@ SMART on FHIR addresses the following three key aspects: Anypoint platform supports SMART on FHIR in the following ways: * Identity and access management -** Provisioning third-party https://dev-docs-internal.kqa.msap.io/beta-accelerators/access-management/configure-client-management-openid-task[OIDC client provider^] like Okta for identity management -** Out-of-the-box https://dev-docs-internal.kqa.msap.io/beta-accelerators/api-manager/2.x/policy-openid-connect[OpenID Connect token enforcement policy^] +** Provisioning third-party https://docs.mulesoft.com/access-management/configure-client-management-openid-task[OIDC client provider^] like Okta for identity management +** Out-of-the-box https://docs.mulesoft.com/api-manager/2.x/policy-openid-connect[OpenID Connect token enforcement policy^] ** Leverage OAuth provider information in the `authentication` object for custom policy * Access to the data using FHIR based APIs ** MuleSoft Accelerator for Healthcare provides FHIR R4 specifications for all the FHIR resources -** Out-of-the-box https://dev-docs-internal.kqa.msap.io/beta-accelerators/api-manager/2.x/cors-policy[cross origin resource sharing (CORS) policy^] enables cross origin data exchange. +** Out-of-the-box https://docs.mulesoft.com/api-manager/2.x/cors-policy[cross origin resource sharing (CORS) policy^] enables cross origin data exchange. == See Also diff --git a/healthcare/2.19/modules/ROOT/pages/x12-fhir-converter.adoc b/healthcare/2.19/modules/ROOT/pages/x12-fhir-converter.adoc index 354475b59..69f9d3caa 100644 --- a/healthcare/2.19/modules/ROOT/pages/x12-fhir-converter.adoc +++ b/healthcare/2.19/modules/ROOT/pages/x12-fhir-converter.adoc @@ -1,10 +1,10 @@ = X12 to FHIR Converter -The https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/hls-fhir-to-x12-sys-api/[X12 to FHIR converter^] comes with a ready to use template for https://x12.org/[X12^] to FHIR conversion. This template can be extended or modified to meet specific conversion requirements. The converter converts FHIR R4 to X12 formats and its responses from X12 to FHIR R4. +The https://anypoint.mulesoft.com/exchange/org.mule.examples/hls-fhir-to-x12-sys-api/[X12 to FHIR converter^] comes with a ready to use template for https://x12.org/[X12^] to FHIR conversion. This template can be extended or modified to meet specific conversion requirements. The converter converts FHIR R4 to X12 formats and its responses from X12 to FHIR R4. == Functional Diagram -image:https://www.mulesoft.com/ext/solutions/draft/images/hls-x12-fhir-fx-diagram.svg[X12 to FHIR converter functional diagram,900,align="center"] +image:https://www.mulesoft.com/ext/solutions/images/hls-x12-fhir-fx-diagram.svg[X12 to FHIR converter functional diagram,900,align="center"] == Advantages diff --git a/healthcare/2.20/modules/ROOT/pages/ccda-fhir-converter.adoc b/healthcare/2.20/modules/ROOT/pages/ccda-fhir-converter.adoc index 11b76cb60..134619070 100644 --- a/healthcare/2.20/modules/ROOT/pages/ccda-fhir-converter.adoc +++ b/healthcare/2.20/modules/ROOT/pages/ccda-fhir-converter.adoc @@ -1,10 +1,10 @@ = C-CDA to FHIR Converter -The https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/hls-ccda-to-fhir-sys-api/[C-CDA to FHIR converter] comes with a ready to use template for https://www.hl7.org/implement/standards/product_brief.cfm?product_id=496[CDA] to FHIR conversion. This template can be extended or modified to meet specific conversion requirements. +The https://anypoint.mulesoft.com/exchange/org.mule.examples/hls-ccda-to-fhir-sys-api/[C-CDA to FHIR converter] comes with a ready to use template for https://www.hl7.org/implement/standards/product_brief.cfm?product_id=496[CDA] to FHIR conversion. This template can be extended or modified to meet specific conversion requirements. == Functional diagram -image:https://www.mulesoft.com/ext/solutions/draft/images/hls-ccda-fhir-fx-diagram.svg[CDA to FHIR converter functional diagram,900,align="center"] +image:https://www.mulesoft.com/ext/solutions/images/hls-ccda-fhir-fx-diagram.svg[CDA to FHIR converter functional diagram,900,align="center"] == Advantages diff --git a/healthcare/2.20/modules/ROOT/pages/fhir-r4-assets.adoc b/healthcare/2.20/modules/ROOT/pages/fhir-r4-assets.adoc index 134ba48f5..10d431db8 100644 --- a/healthcare/2.20/modules/ROOT/pages/fhir-r4-assets.adoc +++ b/healthcare/2.20/modules/ROOT/pages/fhir-r4-assets.adoc @@ -2,11 +2,11 @@ The following are a collection of assets to support MuleSoft customers who are developing Fast Healthcare Interoperability Resources (FHIR) APIs using MuleSoft. Visit the https://www.hl7.org/fhir/[official HL7 website] for more information. -* https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/hls-fhirjson-to-raml-sys-api-spec/[FHIR RAML auto-generator] - Utility to generate RAML specification(s) for FHIR resources directly from the JSON schema provided by HL7. +* https://anypoint.mulesoft.com/exchange/org.mule.examples/hls-fhirjson-to-raml-sys-api-spec/[FHIR RAML auto-generator] - Utility to generate RAML specification(s) for FHIR resources directly from the JSON schema provided by HL7. * xref:fhir-r4-us-core-profiles.adoc[FHIR R4 US Core Profile Assets] * xref:fhir-r4-resources.adoc[FHIR R4 Resources List] -* https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fhir-error-policy/[FHIR Error API Policy] - Captures error responses and formats them in an FHIR OperationOutcome-compliant format, since Anypoint Platform's out-of-the-box (OOTB) policies do not provide error messages in an FHIR-compliant format. This policy can also be used with other OOTB API policies provided in Anypoint Platform, such as OAuth or JWT. -* https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/hc-accelerator-okta-smartfhir/[Okta SMART on FHIR^] - Implementation template that walks you through how to set up a reference SMART on FHIR implementation on Anypoint Platform using Okta as the identity provider. +* https://anypoint.mulesoft.com/exchange/org.mule.examples/fhir-error-policy/[FHIR Error API Policy] - Captures error responses and formats them in an FHIR OperationOutcome-compliant format, since Anypoint Platform's out-of-the-box (OOTB) policies do not provide error messages in an FHIR-compliant format. This policy can also be used with other OOTB API policies provided in Anypoint Platform, such as OAuth or JWT. +* https://anypoint.mulesoft.com/exchange/org.mule.examples/hc-accelerator-okta-smartfhir/[Okta SMART on FHIR^] - Implementation template that walks you through how to set up a reference SMART on FHIR implementation on Anypoint Platform using Okta as the identity provider. == See Also diff --git a/healthcare/2.20/modules/ROOT/pages/fhir-r4-resources.adoc b/healthcare/2.20/modules/ROOT/pages/fhir-r4-resources.adoc index 062796d38..8414363f1 100644 --- a/healthcare/2.20/modules/ROOT/pages/fhir-r4-resources.adoc +++ b/healthcare/2.20/modules/ROOT/pages/fhir-r4-resources.adoc @@ -2,7 +2,7 @@ The MuleSoft Accelerator for Healthcare provides a library of United States Core Data for Interoperability (USCDI) and FHIR R4 resources to help healthcare developers adhere to interoperability needs and jumpstart the development of healthcare digital transformation initiatives. -You can also use the https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fhir-error-policy/[FHIR Error API Policy] to capture error responses and format them in an FHIR OperationOutcome-compliant format, since Anypoint Platform's out-of-the-box (OOTB) policies do not provide error messages in an FHIR-compliant format. This policy can also be used with other OOTB API policies provided in Anypoint Platform, such as OAuth or JWT. +You can also use the https://anypoint.mulesoft.com/exchange/org.mule.examples/fhir-error-policy/[FHIR Error API Policy] to capture error responses and format them in an FHIR OperationOutcome-compliant format, since Anypoint Platform's out-of-the-box (OOTB) policies do not provide error messages in an FHIR-compliant format. This policy can also be used with other OOTB API policies provided in Anypoint Platform, such as OAuth or JWT. For the list of US core profile assets, please refer to xref:fhir-r4-us-core-profiles.adoc[this link]. @@ -15,339 +15,339 @@ _API specifications, data types, and libraries built to meet compliance with FHI | Category| Library | API Specification .^| Foundation - Confirmance -| https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fhir-r4-capabilitystatement-library/[CapabilityStatement] ^[N]^ + -https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fhir-r4-structuredefinition-library/[StructureDefinition] ^[N]^ + -https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fhir-r4-implementationguide-library/[ImplementationGuide] + -https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fhir-r4-searchparameter-library/[SearchParameter] + -https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fhir-r4-operationdefinition-library/[OperationDefinition] ^[N]^ + -https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fhir-r4-compartmentdefinition-library/[CompartmentDefinition] + -https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fhir-r4-messagedefinition-library/[MessageDefinition] + -https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fhir-r4-structuremap-library/[StructureMap] + -https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fhir-r4-graphdefinition-library/[GraphDefinition] + -https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fhir-r4-examplescenario-library/[ExampleScenario] -| https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fhir-r4-capabilitystatement-api/[CapabilityStatement] ^[N]^ + -https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fhir-r4-structuredefinition-api/[StructureDefinition] ^[N]^ + -https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fhir-r4-implementationguide-api/[ImplementationGuide] + -https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fhir-r4-searchparameter-api/[SearchParameter] + -https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fhir-r4-operationdefinition-api/[OperationDefinition] ^[N]^ + -https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fhir-r4-compartmentdefinition-api/[CompartmentDefinition] + -https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fhir-r4-messagedefinition-api/[MessageDefinition] + -https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fhir-r4-structuremap-api/[StructureMap] + -https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fhir-r4-graphdefinition-api/[GraphDefinition] + -https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fhir-r4-examplescenario-api/[ExampleScenario] +| https://anypoint.mulesoft.com/exchange/org.mule.examples/fhir-r4-capabilitystatement-library/[CapabilityStatement] ^[N]^ + +https://anypoint.mulesoft.com/exchange/org.mule.examples/fhir-r4-structuredefinition-library/[StructureDefinition] ^[N]^ + +https://anypoint.mulesoft.com/exchange/org.mule.examples/fhir-r4-implementationguide-library/[ImplementationGuide] + +https://anypoint.mulesoft.com/exchange/org.mule.examples/fhir-r4-searchparameter-library/[SearchParameter] + +https://anypoint.mulesoft.com/exchange/org.mule.examples/fhir-r4-operationdefinition-library/[OperationDefinition] ^[N]^ + +https://anypoint.mulesoft.com/exchange/org.mule.examples/fhir-r4-compartmentdefinition-library/[CompartmentDefinition] + +https://anypoint.mulesoft.com/exchange/org.mule.examples/fhir-r4-messagedefinition-library/[MessageDefinition] + +https://anypoint.mulesoft.com/exchange/org.mule.examples/fhir-r4-structuremap-library/[StructureMap] + +https://anypoint.mulesoft.com/exchange/org.mule.examples/fhir-r4-graphdefinition-library/[GraphDefinition] + +https://anypoint.mulesoft.com/exchange/org.mule.examples/fhir-r4-examplescenario-library/[ExampleScenario] +| https://anypoint.mulesoft.com/exchange/org.mule.examples/fhir-r4-capabilitystatement-api/[CapabilityStatement] ^[N]^ + +https://anypoint.mulesoft.com/exchange/org.mule.examples/fhir-r4-structuredefinition-api/[StructureDefinition] ^[N]^ + +https://anypoint.mulesoft.com/exchange/org.mule.examples/fhir-r4-implementationguide-api/[ImplementationGuide] + +https://anypoint.mulesoft.com/exchange/org.mule.examples/fhir-r4-searchparameter-api/[SearchParameter] + +https://anypoint.mulesoft.com/exchange/org.mule.examples/fhir-r4-operationdefinition-api/[OperationDefinition] ^[N]^ + +https://anypoint.mulesoft.com/exchange/org.mule.examples/fhir-r4-compartmentdefinition-api/[CompartmentDefinition] + +https://anypoint.mulesoft.com/exchange/org.mule.examples/fhir-r4-messagedefinition-api/[MessageDefinition] + +https://anypoint.mulesoft.com/exchange/org.mule.examples/fhir-r4-structuremap-api/[StructureMap] + +https://anypoint.mulesoft.com/exchange/org.mule.examples/fhir-r4-graphdefinition-api/[GraphDefinition] + +https://anypoint.mulesoft.com/exchange/org.mule.examples/fhir-r4-examplescenario-api/[ExampleScenario] .^| Foundation - Terminology -| https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fhir-r4-codesystem-library/[CodeSystem] ^[N]^ + -https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fhir-r4-valueset-library/[ValueSet] ^[N]^ + -https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fhir-r4-conceptmap-library/[ConceptMap] + -https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fhir-r4-namingsystem-library/[NamingSystem] + -https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fhir-r4-terminologycapabilities-library/[TerminologiesCapabilities] -| https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fhir-r4-codesystem-api/[CodeSystem] ^[N]^ + -https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fhir-r4-valueset-api/[ValueSet] ^[N]^ + -https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fhir-r4-conceptmap-api/[ConceptMap] + -https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fhir-r4-namingsystem-api/[NamingSystem] + -https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fhir-r4-terminologycapabilities-api/[TerminologiesCapabilities] +| https://anypoint.mulesoft.com/exchange/org.mule.examples/fhir-r4-codesystem-library/[CodeSystem] ^[N]^ + +https://anypoint.mulesoft.com/exchange/org.mule.examples/fhir-r4-valueset-library/[ValueSet] ^[N]^ + +https://anypoint.mulesoft.com/exchange/org.mule.examples/fhir-r4-conceptmap-library/[ConceptMap] + +https://anypoint.mulesoft.com/exchange/org.mule.examples/fhir-r4-namingsystem-library/[NamingSystem] + +https://anypoint.mulesoft.com/exchange/org.mule.examples/fhir-r4-terminologycapabilities-library/[TerminologiesCapabilities] +| https://anypoint.mulesoft.com/exchange/org.mule.examples/fhir-r4-codesystem-api/[CodeSystem] ^[N]^ + +https://anypoint.mulesoft.com/exchange/org.mule.examples/fhir-r4-valueset-api/[ValueSet] ^[N]^ + +https://anypoint.mulesoft.com/exchange/org.mule.examples/fhir-r4-conceptmap-api/[ConceptMap] + +https://anypoint.mulesoft.com/exchange/org.mule.examples/fhir-r4-namingsystem-api/[NamingSystem] + +https://anypoint.mulesoft.com/exchange/org.mule.examples/fhir-r4-terminologycapabilities-api/[TerminologiesCapabilities] .^| Foundation - Security -| https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fhir-r4-provenance-library/[Provenance] + -https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fhir-r4-auditevent-library/[AuditEvent] + -https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fhir-r4-consent-library/[Consent] -| https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fhir-r4-provenance-api/[Provenance] + -https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fhir-r4-auditevent-api/[AuditEvent] + -https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fhir-r4-consent-api/[Consent] +| https://anypoint.mulesoft.com/exchange/org.mule.examples/fhir-r4-provenance-library/[Provenance] + +https://anypoint.mulesoft.com/exchange/org.mule.examples/fhir-r4-auditevent-library/[AuditEvent] + +https://anypoint.mulesoft.com/exchange/org.mule.examples/fhir-r4-consent-library/[Consent] +| https://anypoint.mulesoft.com/exchange/org.mule.examples/fhir-r4-provenance-api/[Provenance] + +https://anypoint.mulesoft.com/exchange/org.mule.examples/fhir-r4-auditevent-api/[AuditEvent] + +https://anypoint.mulesoft.com/exchange/org.mule.examples/fhir-r4-consent-api/[Consent] .^| Foundation - Documents -| https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fhir-r4-composition-library/[Composition] + -https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fhir-r4-documentmanifest-library/[DocumentManifest] + -https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fhir-r4-documentreference-library/[DocumentReference] + -https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fhir-r4-catalogentry-library/[CatalogEntry] -| https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fhir-r4-composition-api/[Composition] + -https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fhir-r4-documentmanifest-api/[DocumentManifest] + -https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fhir-r4-documentreference-api/[DocumentReference] + -https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fhir-r4-catalogentry-api/[CatalogEntry] +| https://anypoint.mulesoft.com/exchange/org.mule.examples/fhir-r4-composition-library/[Composition] + +https://anypoint.mulesoft.com/exchange/org.mule.examples/fhir-r4-documentmanifest-library/[DocumentManifest] + +https://anypoint.mulesoft.com/exchange/org.mule.examples/fhir-r4-documentreference-library/[DocumentReference] + +https://anypoint.mulesoft.com/exchange/org.mule.examples/fhir-r4-catalogentry-library/[CatalogEntry] +| https://anypoint.mulesoft.com/exchange/org.mule.examples/fhir-r4-composition-api/[Composition] + +https://anypoint.mulesoft.com/exchange/org.mule.examples/fhir-r4-documentmanifest-api/[DocumentManifest] + +https://anypoint.mulesoft.com/exchange/org.mule.examples/fhir-r4-documentreference-api/[DocumentReference] + +https://anypoint.mulesoft.com/exchange/org.mule.examples/fhir-r4-catalogentry-api/[CatalogEntry] .^| Foundation - Other -| https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fhir-r4-basic-library/[Basic] + -https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fhir-r4-binary-library/[Binary] ^[N]^ + -https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fhir-r4-linkage-library/[Linkage] + -https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fhir-r4-messageheader-library/[MessageHeader] + -https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fhir-r4-parameters-library/[Parameters] ^[N]^ + -https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fhir-r4-subscription-library/[Subscription] + +| https://anypoint.mulesoft.com/exchange/org.mule.examples/fhir-r4-basic-library/[Basic] + +https://anypoint.mulesoft.com/exchange/org.mule.examples/fhir-r4-binary-library/[Binary] ^[N]^ + +https://anypoint.mulesoft.com/exchange/org.mule.examples/fhir-r4-linkage-library/[Linkage] + +https://anypoint.mulesoft.com/exchange/org.mule.examples/fhir-r4-messageheader-library/[MessageHeader] + +https://anypoint.mulesoft.com/exchange/org.mule.examples/fhir-r4-parameters-library/[Parameters] ^[N]^ + +https://anypoint.mulesoft.com/exchange/org.mule.examples/fhir-r4-subscription-library/[Subscription] + ++++++ -| https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fhir-r4-basic-api/[Basic] + -https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fhir-r4-binary-api/[Binary] ^[N]^ + -https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fhir-r4-linkage-api/[Linkage] + -https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fhir-r4-messageheader-api/[MessageHeader] + -https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fhir-r4-parameters-api/[Parameters] ^[N]^ + -https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fhir-r4-subscription-api/[Subscription] +| https://anypoint.mulesoft.com/exchange/org.mule.examples/fhir-r4-basic-api/[Basic] + +https://anypoint.mulesoft.com/exchange/org.mule.examples/fhir-r4-binary-api/[Binary] ^[N]^ + +https://anypoint.mulesoft.com/exchange/org.mule.examples/fhir-r4-linkage-api/[Linkage] + +https://anypoint.mulesoft.com/exchange/org.mule.examples/fhir-r4-messageheader-api/[MessageHeader] + +https://anypoint.mulesoft.com/exchange/org.mule.examples/fhir-r4-parameters-api/[Parameters] ^[N]^ + +https://anypoint.mulesoft.com/exchange/org.mule.examples/fhir-r4-subscription-api/[Subscription] .^| Base - Individuals -| https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fhir-r4-patient-library/[Patient] ^[N]^ + -https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fhir-r4-practitioner-library/[Practitioner] + -https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fhir-r4-practitionerrole-library/[PractitionerRole] + -https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fhir-r4-relatedperson-library/[RelatedPerson] + -https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fhir-r4-person-library/[Person] + -https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fhir-r4-group-library/[Group] + +| https://anypoint.mulesoft.com/exchange/org.mule.examples/fhir-r4-patient-library/[Patient] ^[N]^ + +https://anypoint.mulesoft.com/exchange/org.mule.examples/fhir-r4-practitioner-library/[Practitioner] + +https://anypoint.mulesoft.com/exchange/org.mule.examples/fhir-r4-practitionerrole-library/[PractitionerRole] + +https://anypoint.mulesoft.com/exchange/org.mule.examples/fhir-r4-relatedperson-library/[RelatedPerson] + +https://anypoint.mulesoft.com/exchange/org.mule.examples/fhir-r4-person-library/[Person] + +https://anypoint.mulesoft.com/exchange/org.mule.examples/fhir-r4-group-library/[Group] + ++++++ -| https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fhir-r4-patient-api/[Patient] ^[N]^ + -https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fhir-r4-practitioner-api/[Practitioner] + -https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fhir-r4-practitionerrole-api/[PractitionerRole] + -https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fhir-r4-relatedperson-api/[RelatedPerson] + -https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fhir-r4-person-api/[Person] + -https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fhir-r4-group-api/[Group] +| https://anypoint.mulesoft.com/exchange/org.mule.examples/fhir-r4-patient-api/[Patient] ^[N]^ + +https://anypoint.mulesoft.com/exchange/org.mule.examples/fhir-r4-practitioner-api/[Practitioner] + +https://anypoint.mulesoft.com/exchange/org.mule.examples/fhir-r4-practitionerrole-api/[PractitionerRole] + +https://anypoint.mulesoft.com/exchange/org.mule.examples/fhir-r4-relatedperson-api/[RelatedPerson] + +https://anypoint.mulesoft.com/exchange/org.mule.examples/fhir-r4-person-api/[Person] + +https://anypoint.mulesoft.com/exchange/org.mule.examples/fhir-r4-group-api/[Group] .^| Base - Entities #1 -| https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fhir-r4-organization-library/[Organization] + -https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fhir-r4-organizationaffiliation-library/[OrganizationAffiliation] + -https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fhir-r4-healthcareservice-library/[HealthcareService] + -https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fhir-r4-endpoint-library/[Endpoint] + -https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fhir-r4-location-library/[Location] + +| https://anypoint.mulesoft.com/exchange/org.mule.examples/fhir-r4-organization-library/[Organization] + +https://anypoint.mulesoft.com/exchange/org.mule.examples/fhir-r4-organizationaffiliation-library/[OrganizationAffiliation] + +https://anypoint.mulesoft.com/exchange/org.mule.examples/fhir-r4-healthcareservice-library/[HealthcareService] + +https://anypoint.mulesoft.com/exchange/org.mule.examples/fhir-r4-endpoint-library/[Endpoint] + +https://anypoint.mulesoft.com/exchange/org.mule.examples/fhir-r4-location-library/[Location] + ++++++ -| https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fhir-r4-organization-api/[Organization] + -https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fhir-r4-organizationaffiliation-api/[OrganizationAffiliation] + -https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fhir-r4-healthcareservice-api/[HealthcareService] + -https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fhir-r4-endpoint-api/[Endpoint] + -https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fhir-r4-location-api/[Location] +| https://anypoint.mulesoft.com/exchange/org.mule.examples/fhir-r4-organization-api/[Organization] + +https://anypoint.mulesoft.com/exchange/org.mule.examples/fhir-r4-organizationaffiliation-api/[OrganizationAffiliation] + +https://anypoint.mulesoft.com/exchange/org.mule.examples/fhir-r4-healthcareservice-api/[HealthcareService] + +https://anypoint.mulesoft.com/exchange/org.mule.examples/fhir-r4-endpoint-api/[Endpoint] + +https://anypoint.mulesoft.com/exchange/org.mule.examples/fhir-r4-location-api/[Location] .^| Base - Entities #2 -| https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fhir-r4-substance-library/[Substance] + -https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fhir-r4-biologicallyderivedproduct-library/[BiologicallyDerivedProduct #] + -https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fhir-r4-device-library/[Device] + -https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fhir-r4-devicemetric-library/[DeviceMetric] + +| https://anypoint.mulesoft.com/exchange/org.mule.examples/fhir-r4-substance-library/[Substance] + +https://anypoint.mulesoft.com/exchange/org.mule.examples/fhir-r4-biologicallyderivedproduct-library/[BiologicallyDerivedProduct #] + +https://anypoint.mulesoft.com/exchange/org.mule.examples/fhir-r4-device-library/[Device] + +https://anypoint.mulesoft.com/exchange/org.mule.examples/fhir-r4-devicemetric-library/[DeviceMetric] + ++++++ -| https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fhir-r4-substance-api/[Substance] + -https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fhir-r4-biologicallyderivedproduct-api/[BiologicallyDerivedProduct #] + -https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fhir-r4-device-api/[Device] + -https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fhir-r4-devicemetric-api/[DeviceMetric] +| https://anypoint.mulesoft.com/exchange/org.mule.examples/fhir-r4-substance-api/[Substance] + +https://anypoint.mulesoft.com/exchange/org.mule.examples/fhir-r4-biologicallyderivedproduct-api/[BiologicallyDerivedProduct #] + +https://anypoint.mulesoft.com/exchange/org.mule.examples/fhir-r4-device-api/[Device] + +https://anypoint.mulesoft.com/exchange/org.mule.examples/fhir-r4-devicemetric-api/[DeviceMetric] .^| Base - Workflow -| https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fhir-r4-task-library/[Task] + -https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fhir-r4-appointment-library/[Appointment] + -https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fhir-r4-appointmentresponse-library/[AppointmentResponse] + -https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fhir-r4-schedule-library/[Schedule] + -https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fhir-r4-slot-library/[Slot] + -https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fhir-r4-verificationresult-library/[VerificationResult] -| https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fhir-r4-task-api/[Task] + -https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fhir-r4-appointment-api/[Appointment] + -https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fhir-r4-appointmentresponse-api/[AppointmentResponse] + -https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fhir-r4-schedule-api/[Schedule] + -https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fhir-r4-slot-api/[Slot] + -https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fhir-r4-verificationresult-api/[VerificationResult] +| https://anypoint.mulesoft.com/exchange/org.mule.examples/fhir-r4-task-library/[Task] + +https://anypoint.mulesoft.com/exchange/org.mule.examples/fhir-r4-appointment-library/[Appointment] + +https://anypoint.mulesoft.com/exchange/org.mule.examples/fhir-r4-appointmentresponse-library/[AppointmentResponse] + +https://anypoint.mulesoft.com/exchange/org.mule.examples/fhir-r4-schedule-library/[Schedule] + +https://anypoint.mulesoft.com/exchange/org.mule.examples/fhir-r4-slot-library/[Slot] + +https://anypoint.mulesoft.com/exchange/org.mule.examples/fhir-r4-verificationresult-library/[VerificationResult] +| https://anypoint.mulesoft.com/exchange/org.mule.examples/fhir-r4-task-api/[Task] + +https://anypoint.mulesoft.com/exchange/org.mule.examples/fhir-r4-appointment-api/[Appointment] + +https://anypoint.mulesoft.com/exchange/org.mule.examples/fhir-r4-appointmentresponse-api/[AppointmentResponse] + +https://anypoint.mulesoft.com/exchange/org.mule.examples/fhir-r4-schedule-api/[Schedule] + +https://anypoint.mulesoft.com/exchange/org.mule.examples/fhir-r4-slot-api/[Slot] + +https://anypoint.mulesoft.com/exchange/org.mule.examples/fhir-r4-verificationresult-api/[VerificationResult] .^| Base - Management -| https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fhir-r4-encounter-library/[Encounter] + -https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fhir-r4-episodeofcare-library/[EpisodeOfCare] + -https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fhir-r4-flag-library/[Flag] + -https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fhir-r4-list-library/[List] + -https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fhir-r4-library-library/[Library] -| https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fhir-r4-encounter-api/[Encounter] + -https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fhir-r4-episodeofcare-api/[EpisodeOfCare] + -https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fhir-r4-flag-api/[Flag] + -https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fhir-r4-list-api/[List] + -https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fhir-r4-library-api/[Library] +| https://anypoint.mulesoft.com/exchange/org.mule.examples/fhir-r4-encounter-library/[Encounter] + +https://anypoint.mulesoft.com/exchange/org.mule.examples/fhir-r4-episodeofcare-library/[EpisodeOfCare] + +https://anypoint.mulesoft.com/exchange/org.mule.examples/fhir-r4-flag-library/[Flag] + +https://anypoint.mulesoft.com/exchange/org.mule.examples/fhir-r4-list-library/[List] + +https://anypoint.mulesoft.com/exchange/org.mule.examples/fhir-r4-library-library/[Library] +| https://anypoint.mulesoft.com/exchange/org.mule.examples/fhir-r4-encounter-api/[Encounter] + +https://anypoint.mulesoft.com/exchange/org.mule.examples/fhir-r4-episodeofcare-api/[EpisodeOfCare] + +https://anypoint.mulesoft.com/exchange/org.mule.examples/fhir-r4-flag-api/[Flag] + +https://anypoint.mulesoft.com/exchange/org.mule.examples/fhir-r4-list-api/[List] + +https://anypoint.mulesoft.com/exchange/org.mule.examples/fhir-r4-library-api/[Library] .^| Clinical - Summary -| https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fhir-r4-allergyintolerance-library/[AllergyIntolerance] + -https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fhir-r4-adverseevent-library/[AdverseEvent] + -https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fhir-r4-condition-library/[Condition(Problem)] + -https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fhir-r4-procedure-library/[Procedure] + -https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fhir-r4-familymemberhistory-library/[FamilyMemberHistory] + -https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fhir-r4-clinicalimpression-library/[ClinicalImpression #] + -https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fhir-r4-clinicalimpression-library/[Note] + -https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fhir-r4-detectedissue-library/[DetectedIssue] -| https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fhir-r4-allergyintolerance-api/[AllergyIntolerance] + -https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fhir-r4-adverseevent-api/[AdverseEvent] + -https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fhir-r4-condition-api/[Condition(Problem)] + -https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fhir-r4-procedure-api/[Procedure] + -https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fhir-r4-familymemberhistory-api/[FamilyMemberHistory] + -https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fhir-r4-clinicalimpression-api/[ClinicalImpression #] + -https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fhir-r4-clinicalimpression-api/[Note] + -https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fhir-r4-detectedissue-api/[DetectedIssue] +| https://anypoint.mulesoft.com/exchange/org.mule.examples/fhir-r4-allergyintolerance-library/[AllergyIntolerance] + +https://anypoint.mulesoft.com/exchange/org.mule.examples/fhir-r4-adverseevent-library/[AdverseEvent] + +https://anypoint.mulesoft.com/exchange/org.mule.examples/fhir-r4-condition-library/[Condition(Problem)] + +https://anypoint.mulesoft.com/exchange/org.mule.examples/fhir-r4-procedure-library/[Procedure] + +https://anypoint.mulesoft.com/exchange/org.mule.examples/fhir-r4-familymemberhistory-library/[FamilyMemberHistory] + +https://anypoint.mulesoft.com/exchange/org.mule.examples/fhir-r4-clinicalimpression-library/[ClinicalImpression #] + +https://anypoint.mulesoft.com/exchange/org.mule.examples/fhir-r4-clinicalimpression-library/[Note] + +https://anypoint.mulesoft.com/exchange/org.mule.examples/fhir-r4-detectedissue-library/[DetectedIssue] +| https://anypoint.mulesoft.com/exchange/org.mule.examples/fhir-r4-allergyintolerance-api/[AllergyIntolerance] + +https://anypoint.mulesoft.com/exchange/org.mule.examples/fhir-r4-adverseevent-api/[AdverseEvent] + +https://anypoint.mulesoft.com/exchange/org.mule.examples/fhir-r4-condition-api/[Condition(Problem)] + +https://anypoint.mulesoft.com/exchange/org.mule.examples/fhir-r4-procedure-api/[Procedure] + +https://anypoint.mulesoft.com/exchange/org.mule.examples/fhir-r4-familymemberhistory-api/[FamilyMemberHistory] + +https://anypoint.mulesoft.com/exchange/org.mule.examples/fhir-r4-clinicalimpression-api/[ClinicalImpression #] + +https://anypoint.mulesoft.com/exchange/org.mule.examples/fhir-r4-clinicalimpression-api/[Note] + +https://anypoint.mulesoft.com/exchange/org.mule.examples/fhir-r4-detectedissue-api/[DetectedIssue] .^| Clinical - Diagnostics -| https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fhir-r4-observation-library/[Observation] ^[N]^ + -https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fhir-r4-media-library/[Media] ^[u]^ + -https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fhir-r4-diagnosticreport-library/[DiagnosticReport] + -https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fhir-r4-specimen-library/[Specimen] + -https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fhir-r4-bodystructure-library/[BodyStructure] + -https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fhir-r4-imagingstudy-library/[ImagingStudy] + -https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fhir-r4-questionnaireresponse-library/[QuestionnaireResponse ] + -https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fhir-r4-molecularsequence-library/[MolecularSequence] -| https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fhir-r4-observation-api/[Observation] ^[N]^ + -https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fhir-r4-media-api/[Media] ^[u]^ + -https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fhir-r4-diagnosticreport-api/[DiagnosticReport] + -https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fhir-r4-specimen-api/[Specimen] + -https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fhir-r4-bodystructure-api/[BodyStructure] + -https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fhir-r4-imagingstudy-api/[ImagingStudy] + -https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fhir-r4-questionnaireresponse-api/[QuestionnaireResponse ] + -https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fhir-r4-molecularsequence-api/[MolecularSequence] +| https://anypoint.mulesoft.com/exchange/org.mule.examples/fhir-r4-observation-library/[Observation] ^[N]^ + +https://anypoint.mulesoft.com/exchange/org.mule.examples/fhir-r4-media-library/[Media] ^[u]^ + +https://anypoint.mulesoft.com/exchange/org.mule.examples/fhir-r4-diagnosticreport-library/[DiagnosticReport] + +https://anypoint.mulesoft.com/exchange/org.mule.examples/fhir-r4-specimen-library/[Specimen] + +https://anypoint.mulesoft.com/exchange/org.mule.examples/fhir-r4-bodystructure-library/[BodyStructure] + +https://anypoint.mulesoft.com/exchange/org.mule.examples/fhir-r4-imagingstudy-library/[ImagingStudy] + +https://anypoint.mulesoft.com/exchange/org.mule.examples/fhir-r4-questionnaireresponse-library/[QuestionnaireResponse ] + +https://anypoint.mulesoft.com/exchange/org.mule.examples/fhir-r4-molecularsequence-library/[MolecularSequence] +| https://anypoint.mulesoft.com/exchange/org.mule.examples/fhir-r4-observation-api/[Observation] ^[N]^ + +https://anypoint.mulesoft.com/exchange/org.mule.examples/fhir-r4-media-api/[Media] ^[u]^ + +https://anypoint.mulesoft.com/exchange/org.mule.examples/fhir-r4-diagnosticreport-api/[DiagnosticReport] + +https://anypoint.mulesoft.com/exchange/org.mule.examples/fhir-r4-specimen-api/[Specimen] + +https://anypoint.mulesoft.com/exchange/org.mule.examples/fhir-r4-bodystructure-api/[BodyStructure] + +https://anypoint.mulesoft.com/exchange/org.mule.examples/fhir-r4-imagingstudy-api/[ImagingStudy] + +https://anypoint.mulesoft.com/exchange/org.mule.examples/fhir-r4-questionnaireresponse-api/[QuestionnaireResponse ] + +https://anypoint.mulesoft.com/exchange/org.mule.examples/fhir-r4-molecularsequence-api/[MolecularSequence] .^| Clinical - Medications -| https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fhir-r4-medicationrequest-library/[MedicationRequest] + -https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fhir-r4-medicationadministration-library/[MedicationAdministration] + -https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fhir-r4-medicationdispense-library/[MedicationDispense] + -https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fhir-r4-medicationstatement-library/[MedicationStatement] + -https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fhir-r4-medication-library/[Medication] + -https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fhir-r4-medicationknowledge-library/[MedicationKnowledge] + -https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fhir-r4-immunization-library/[Immunization] + -https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fhir-r4-immunizationevaluation-library/[ImmunizationEvaluation] + -https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fhir-r4-immunizationrecommendation-library/[ImmunizationRecommendation] -| https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fhir-r4-medicationrequest-api/[MedicationRequest] + -https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fhir-r4-medicationadministration-api/[MedicationAdministration] + -https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fhir-r4-medicationdispense-api/[MedicationDispense] + -https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fhir-r4-medicationstatement-api/[MedicationStatement] + -https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fhir-r4-medication-api/[Medication] + -https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fhir-r4-medicationknowledge-api/[MedicationKnowledge] + -https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fhir-r4-immunization-api/[Immunization] + -https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fhir-r4-immunizationevaluation-api/[ImmunizationEvaluation] + -https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fhir-r4-immunizationrecommendation-api/[ImmunizationRecommendation] +| https://anypoint.mulesoft.com/exchange/org.mule.examples/fhir-r4-medicationrequest-library/[MedicationRequest] + +https://anypoint.mulesoft.com/exchange/org.mule.examples/fhir-r4-medicationadministration-library/[MedicationAdministration] + +https://anypoint.mulesoft.com/exchange/org.mule.examples/fhir-r4-medicationdispense-library/[MedicationDispense] + +https://anypoint.mulesoft.com/exchange/org.mule.examples/fhir-r4-medicationstatement-library/[MedicationStatement] + +https://anypoint.mulesoft.com/exchange/org.mule.examples/fhir-r4-medication-library/[Medication] + +https://anypoint.mulesoft.com/exchange/org.mule.examples/fhir-r4-medicationknowledge-library/[MedicationKnowledge] + +https://anypoint.mulesoft.com/exchange/org.mule.examples/fhir-r4-immunization-library/[Immunization] + +https://anypoint.mulesoft.com/exchange/org.mule.examples/fhir-r4-immunizationevaluation-library/[ImmunizationEvaluation] + +https://anypoint.mulesoft.com/exchange/org.mule.examples/fhir-r4-immunizationrecommendation-library/[ImmunizationRecommendation] +| https://anypoint.mulesoft.com/exchange/org.mule.examples/fhir-r4-medicationrequest-api/[MedicationRequest] + +https://anypoint.mulesoft.com/exchange/org.mule.examples/fhir-r4-medicationadministration-api/[MedicationAdministration] + +https://anypoint.mulesoft.com/exchange/org.mule.examples/fhir-r4-medicationdispense-api/[MedicationDispense] + +https://anypoint.mulesoft.com/exchange/org.mule.examples/fhir-r4-medicationstatement-api/[MedicationStatement] + +https://anypoint.mulesoft.com/exchange/org.mule.examples/fhir-r4-medication-api/[Medication] + +https://anypoint.mulesoft.com/exchange/org.mule.examples/fhir-r4-medicationknowledge-api/[MedicationKnowledge] + +https://anypoint.mulesoft.com/exchange/org.mule.examples/fhir-r4-immunization-api/[Immunization] + +https://anypoint.mulesoft.com/exchange/org.mule.examples/fhir-r4-immunizationevaluation-api/[ImmunizationEvaluation] + +https://anypoint.mulesoft.com/exchange/org.mule.examples/fhir-r4-immunizationrecommendation-api/[ImmunizationRecommendation] .^| Clinical - Care Provision -| https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fhir-r4-careplan-library/[CarePlan] + -https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fhir-r4-careteam-library/[CareTeam] + -https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fhir-r4-goal-library/[Goal] + -https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fhir-r4-servicerequest-library/[ServiceRequest] + -https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fhir-r4-nutritionorder-library/[NutritionOrder] + -https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fhir-r4-visionprescription-library/[VisionPrescription] + -https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fhir-r4-riskassessment-library/[RiskAssessment] + -https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fhir-r4-requestgroup-library/[RequestGroup] -| https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fhir-r4-careplan-api/[CarePlan] + -https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fhir-r4-careteam-api/[CareTeam] + -https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fhir-r4-goal-api/[Goal] + -https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fhir-r4-servicerequest-api/[ServiceRequest] + -https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fhir-r4-nutritionorder-api/[NutritionOrder] + -https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fhir-r4-visionprescription-api/[VisionPrescription] + -https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fhir-r4-riskassessment-api/[RiskAssessment] + -https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fhir-r4-requestgroup-api/[RequestGroup] +| https://anypoint.mulesoft.com/exchange/org.mule.examples/fhir-r4-careplan-library/[CarePlan] + +https://anypoint.mulesoft.com/exchange/org.mule.examples/fhir-r4-careteam-library/[CareTeam] + +https://anypoint.mulesoft.com/exchange/org.mule.examples/fhir-r4-goal-library/[Goal] + +https://anypoint.mulesoft.com/exchange/org.mule.examples/fhir-r4-servicerequest-library/[ServiceRequest] + +https://anypoint.mulesoft.com/exchange/org.mule.examples/fhir-r4-nutritionorder-library/[NutritionOrder] + +https://anypoint.mulesoft.com/exchange/org.mule.examples/fhir-r4-visionprescription-library/[VisionPrescription] + +https://anypoint.mulesoft.com/exchange/org.mule.examples/fhir-r4-riskassessment-library/[RiskAssessment] + +https://anypoint.mulesoft.com/exchange/org.mule.examples/fhir-r4-requestgroup-library/[RequestGroup] +| https://anypoint.mulesoft.com/exchange/org.mule.examples/fhir-r4-careplan-api/[CarePlan] + +https://anypoint.mulesoft.com/exchange/org.mule.examples/fhir-r4-careteam-api/[CareTeam] + +https://anypoint.mulesoft.com/exchange/org.mule.examples/fhir-r4-goal-api/[Goal] + +https://anypoint.mulesoft.com/exchange/org.mule.examples/fhir-r4-servicerequest-api/[ServiceRequest] + +https://anypoint.mulesoft.com/exchange/org.mule.examples/fhir-r4-nutritionorder-api/[NutritionOrder] + +https://anypoint.mulesoft.com/exchange/org.mule.examples/fhir-r4-visionprescription-api/[VisionPrescription] + +https://anypoint.mulesoft.com/exchange/org.mule.examples/fhir-r4-riskassessment-api/[RiskAssessment] + +https://anypoint.mulesoft.com/exchange/org.mule.examples/fhir-r4-requestgroup-api/[RequestGroup] .^| Clinical - Request & Response -| https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fhir-r4-communication-library/[Communication] + -https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fhir-r4-communicationrequest-library/[CommunicationRequest] + -https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fhir-r4-devicerequest-library/[DeviceRequest #] + -https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fhir-r4-deviceusestatement-library/[DeviceUseStatement] ^[u]^ + -https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fhir-r4-guidanceresponse-library/[GuidanceResponse] + -https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fhir-r4-supplyrequest-library/[SupplyRequest #] + -https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fhir-r4-supplydelivery-library/[SupplyDelivery] -| https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fhir-r4-communication-api/[Communication] + -https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fhir-r4-communicationrequest-api/[CommunicationRequest] + -https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fhir-r4-devicerequest-api/[DeviceRequest #] + -https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fhir-r4-deviceusestatement-api/[DeviceUseStatement] ^[u]^ + -https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fhir-r4-guidanceresponse-api/[GuidanceResponse] + -https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fhir-r4-supplyrequest-api/[SupplyRequest #] + -https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fhir-r4-supplydelivery-api/[SupplyDelivery] +| https://anypoint.mulesoft.com/exchange/org.mule.examples/fhir-r4-communication-library/[Communication] + +https://anypoint.mulesoft.com/exchange/org.mule.examples/fhir-r4-communicationrequest-library/[CommunicationRequest] + +https://anypoint.mulesoft.com/exchange/org.mule.examples/fhir-r4-devicerequest-library/[DeviceRequest #] + +https://anypoint.mulesoft.com/exchange/org.mule.examples/fhir-r4-deviceusestatement-library/[DeviceUseStatement] ^[u]^ + +https://anypoint.mulesoft.com/exchange/org.mule.examples/fhir-r4-guidanceresponse-library/[GuidanceResponse] + +https://anypoint.mulesoft.com/exchange/org.mule.examples/fhir-r4-supplyrequest-library/[SupplyRequest #] + +https://anypoint.mulesoft.com/exchange/org.mule.examples/fhir-r4-supplydelivery-library/[SupplyDelivery] +| https://anypoint.mulesoft.com/exchange/org.mule.examples/fhir-r4-communication-api/[Communication] + +https://anypoint.mulesoft.com/exchange/org.mule.examples/fhir-r4-communicationrequest-api/[CommunicationRequest] + +https://anypoint.mulesoft.com/exchange/org.mule.examples/fhir-r4-devicerequest-api/[DeviceRequest #] + +https://anypoint.mulesoft.com/exchange/org.mule.examples/fhir-r4-deviceusestatement-api/[DeviceUseStatement] ^[u]^ + +https://anypoint.mulesoft.com/exchange/org.mule.examples/fhir-r4-guidanceresponse-api/[GuidanceResponse] + +https://anypoint.mulesoft.com/exchange/org.mule.examples/fhir-r4-supplyrequest-api/[SupplyRequest #] + +https://anypoint.mulesoft.com/exchange/org.mule.examples/fhir-r4-supplydelivery-api/[SupplyDelivery] .^| Financial - Support -| https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fhir-r4-coverage-library/[Coverage] + -https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fhir-r4-coverageeligibilityrequest-library/[CoverageEligibilityRequest] + -https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fhir-r4-coverageeligibilityresponse-library/[CoverageEligibilityResponse] + -https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fhir-r4-enrollmentrequest-library/[EnrollmentRequest] ^[u]^ + -https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fhir-r4-enrollmentresponse-library/[EnrollmentResponse] ^[u]^ -| https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fhir-r4-coverage-api/[Coverage] + -https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fhir-r4-coverageeligibilityrequest-api/[CoverageEligibilityRequest] + -https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fhir-r4-coverageeligibilityresponse-api/[CoverageEligibilityResponse] + -https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fhir-r4-enrollmentrequest-api/[EnrollmentRequest] ^[u]^ + -https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fhir-r4-enrollmentresponse-api/[EnrollmentResponse] ^[u]^ +| https://anypoint.mulesoft.com/exchange/org.mule.examples/fhir-r4-coverage-library/[Coverage] + +https://anypoint.mulesoft.com/exchange/org.mule.examples/fhir-r4-coverageeligibilityrequest-library/[CoverageEligibilityRequest] + +https://anypoint.mulesoft.com/exchange/org.mule.examples/fhir-r4-coverageeligibilityresponse-library/[CoverageEligibilityResponse] + +https://anypoint.mulesoft.com/exchange/org.mule.examples/fhir-r4-enrollmentrequest-library/[EnrollmentRequest] ^[u]^ + +https://anypoint.mulesoft.com/exchange/org.mule.examples/fhir-r4-enrollmentresponse-library/[EnrollmentResponse] ^[u]^ +| https://anypoint.mulesoft.com/exchange/org.mule.examples/fhir-r4-coverage-api/[Coverage] + +https://anypoint.mulesoft.com/exchange/org.mule.examples/fhir-r4-coverageeligibilityrequest-api/[CoverageEligibilityRequest] + +https://anypoint.mulesoft.com/exchange/org.mule.examples/fhir-r4-coverageeligibilityresponse-api/[CoverageEligibilityResponse] + +https://anypoint.mulesoft.com/exchange/org.mule.examples/fhir-r4-enrollmentrequest-api/[EnrollmentRequest] ^[u]^ + +https://anypoint.mulesoft.com/exchange/org.mule.examples/fhir-r4-enrollmentresponse-api/[EnrollmentResponse] ^[u]^ .^| Financial - Billing -| https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fhir-r4-claim-library/[Claim] + -https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fhir-r4-claimresponse-library/[ClaimResponse] + -https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fhir-r4-invoice-library/[Invoice] -| https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fhir-r4-claim-api/[Claim] + -https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fhir-r4-claimresponse-api/[ClaimResponse] + -https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fhir-r4-invoice-api/[Invoice] - -.^| Financial - Payment | https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fhir-r4-paymentnotice-library/[PaymentNotice] + -https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fhir-r4-paymentreconciliation-library/[PaymentReconcilliation] -| https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fhir-r4-paymentnotice-api/[PaymentNotice] + -https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fhir-r4-paymentreconciliation-api/[PaymentReconcilliation] - -.^| Financial - General | https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fhir-r4-account-library/[Account] + -https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fhir-r4-chargeitem-library/[ChargeItem] + -https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fhir-r4-chargeitemdefinition-library/[ChargeItemDefinition] + -https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fhir-r4-contract-library/[Contract] + -https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fhir-r4-explanationofbenefit-library/[ExplanationOfBenefit] + -https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fhir-r4-insuranceplan-library/[InsurancePlan] -| https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fhir-r4-account-api/[Account] + -https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fhir-r4-chargeitem-api/[ChargeItem] + -https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fhir-r4-chargeitemdefinition-api/[ChargeItemDefinition] + -https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fhir-r4-contract-api/[Contract] + -https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fhir-r4-explanationofbenefit-api/[ExplanationOfBenefit] + -https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fhir-r4-insuranceplan-api/[InsurancePlan] - -.^| Specialized - Public Health & Research | https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fhir-r4-researchstudy-library/[ResearchStudy] + -https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fhir-r4-researchsubject-library/[ResearchSubject] -| https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fhir-r4-researchstudy-api/[ResearchStudy] + -https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fhir-r4-researchsubject-api/[ResearchSubject] - -.^| Specialized - Definitional Artifacts | https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fhir-r4-activitydefinition-library/[ActivityDefinition] + -https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fhir-r4-devicedefinition-library/[DeviceDefinition] + -https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fhir-r4-eventdefinition-library/[EventDefinition] + -https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fhir-r4-observationdefinition-library/[ObservationDefinition] ^[u]^ + -https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fhir-r4-plandefinition-library/[PlanDefinition] + -https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fhir-r4-questionnaire-library/[Questionnaire] + -https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fhir-r4-specimendefinition-library/[SpecimenDefinition] -| https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fhir-r4-activitydefinition-api/[ActivityDefinition] + -https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fhir-r4-devicedefinition-api/[DeviceDefinition] + -https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fhir-r4-eventdefinition-api/[EventDefinition] + -https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fhir-r4-observationdefinition-api/[ObservationDefinition] ^[u]^ + -https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fhir-r4-plandefinition-api/[PlanDefinition] + -https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fhir-r4-questionnaire-api/[Questionnaire] + -https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fhir-r4-specimendefinition-api/[SpecimenDefinition] - -.^| Specialized - Evidence Based Medicine | https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fhir-r4-researchdefinition-library/[ResearchDefinition] + -https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fhir-r4-researchelementdefinition-library/[ResearchElementDefinition] + -https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fhir-r4-evidence-library/[Evidence] + -https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fhir-r4-evidencevariable-library/[EvidenceVariable] + -https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fhir-r4-effectevidencesynthesis-library/[EffectEvidenceSynthesis] + -https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fhir-r4-riskevidencesynthesis-library/[RiskEvidenceSynthesis] -| https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fhir-r4-researchdefinition-api/[ResearchDefinition] + -https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fhir-r4-researchelementdefinition-api/[ResearchElementDefinition] + -https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fhir-r4-evidence-api/[Evidence] + -https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fhir-r4-evidencevariable-api/[EvidenceVariable] + -https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fhir-r4-effectevidencesynthesis-api/[EffectEvidenceSynthesis] + -https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fhir-r4-riskevidencesynthesis-api/[RiskEvidenceSynthesis] - -.^| Specialized - Quality Reporting & Testing | https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fhir-r4-measure-library/[Measure] + -https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fhir-r4-measurereport-library/[MeasureReport] + -https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fhir-r4-testscript-library/[TestScript] + -https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fhir-r4-testreport-library/[TestReport] -| https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fhir-r4-measure-api/[Measure] + -https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fhir-r4-measurereport-api/[MeasureReport] + -https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fhir-r4-testscript-api/[TestScript] + -https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fhir-r4-testreport-api/[TestReport] - -.^| Specialized - Medication Definition | https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fhir-r4-medicinalproduct-library/[MedicinalProduct] ^[u]^ + -https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fhir-r4-medicinalproductauthorization-library/[MedicinalProductAuthorization] ^[u]^ + -https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fhir-r4-medicinalproductcontraindication-library/[MedicinalProductContraindication] + -https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fhir-r4-medicinalproductindication-library/[MedicinalProductIndication] + -https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fhir-r4-medicinalproductingredient-library/[MedicinalProductIngredient] ^[u]^ + -https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fhir-r4-medicinalproductinteraction-library/[MedicinalProductInteraction] + -https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fhir-r4-medicinalproductmanufactured-library/[MedicinalProductManufactured] + -https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fhir-r4-medicinalproductpackaged-library/[MedicinalProductPackaged] ^[u]^ + -https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fhir-r4-medicinalproductpharmaceutical-library/[MedicinalProductPharmaceutical] ^[u]^ + -https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fhir-r4-medicinalproductundesirableeffect-library/[MedicinalProductUndesirableEffect] + -https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fhir-r4-substancenucleicacid-library/[SubstanceNucleicAcid] + -https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fhir-r4-substancepolymer-library/[SubstancePolymer] ^[u]^ + -https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fhir-r4-substanceprotein-library/[SubstanceProtein] + -https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fhir-r4-substancereferenceinformation-library/[SubstanceReferenceInformation] ^[u]^ + -https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fhir-r4-substancespecification-library/[SubstanceSpecification] ^[u]^ + -https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fhir-r4-substancesourcematerial-library/[SubstanceSourceMaterial] -| https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fhir-r4-medicinalproduct-api/[MedicinalProduct] ^[u]^ + -https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fhir-r4-medicinalproductauthorization-api/[MedicinalProductAuthorization] ^[u]^ + -https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fhir-r4-medicinalproductcontraindication-api/[MedicinalProductContraindication] + -https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fhir-r4-medicinalproductindication-api/[MedicinalProductIndication] + -https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fhir-r4-medicinalproductingredient-api/[MedicinalProductIngredient] ^[u]^ + -https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fhir-r4-medicinalproductinteraction-api/[MedicinalProductInteraction] + -https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fhir-r4-medicinalproductmanufactured-api/[MedicinalProductManufactured] + -https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fhir-r4-medicinalproductpackaged-api/[MedicinalProductPackaged] ^[u]^ + -https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fhir-r4-medicinalproductpharmaceutical-api/[MedicinalProductPharmaceutical] ^[u]^ + -https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fhir-r4-medicinalproductundesirableeffect-api/[MedicinalProductUndesirableEffect] + -https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fhir-r4-substancenucleicacid-api/[SubstanceNucleicAcid] + -https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fhir-r4-substancepolymer-api/[SubstancePolymer] ^[u]^ + -https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fhir-r4-substanceprotein-api/[SubstanceProtein] + -https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fhir-r4-substancereferenceinformation-api/[SubstanceReferenceInformation] ^[u]^ + -https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fhir-r4-substancespecification-api/[SubstanceSpecification] ^[u]^ + -https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fhir-r4-substancesourcematerial-api/[SubstanceSourceMaterial] +| https://anypoint.mulesoft.com/exchange/org.mule.examples/fhir-r4-claim-library/[Claim] + +https://anypoint.mulesoft.com/exchange/org.mule.examples/fhir-r4-claimresponse-library/[ClaimResponse] + +https://anypoint.mulesoft.com/exchange/org.mule.examples/fhir-r4-invoice-library/[Invoice] +| https://anypoint.mulesoft.com/exchange/org.mule.examples/fhir-r4-claim-api/[Claim] + +https://anypoint.mulesoft.com/exchange/org.mule.examples/fhir-r4-claimresponse-api/[ClaimResponse] + +https://anypoint.mulesoft.com/exchange/org.mule.examples/fhir-r4-invoice-api/[Invoice] + +.^| Financial - Payment | https://anypoint.mulesoft.com/exchange/org.mule.examples/fhir-r4-paymentnotice-library/[PaymentNotice] + +https://anypoint.mulesoft.com/exchange/org.mule.examples/fhir-r4-paymentreconciliation-library/[PaymentReconcilliation] +| https://anypoint.mulesoft.com/exchange/org.mule.examples/fhir-r4-paymentnotice-api/[PaymentNotice] + +https://anypoint.mulesoft.com/exchange/org.mule.examples/fhir-r4-paymentreconciliation-api/[PaymentReconcilliation] + +.^| Financial - General | https://anypoint.mulesoft.com/exchange/org.mule.examples/fhir-r4-account-library/[Account] + +https://anypoint.mulesoft.com/exchange/org.mule.examples/fhir-r4-chargeitem-library/[ChargeItem] + +https://anypoint.mulesoft.com/exchange/org.mule.examples/fhir-r4-chargeitemdefinition-library/[ChargeItemDefinition] + +https://anypoint.mulesoft.com/exchange/org.mule.examples/fhir-r4-contract-library/[Contract] + +https://anypoint.mulesoft.com/exchange/org.mule.examples/fhir-r4-explanationofbenefit-library/[ExplanationOfBenefit] + +https://anypoint.mulesoft.com/exchange/org.mule.examples/fhir-r4-insuranceplan-library/[InsurancePlan] +| https://anypoint.mulesoft.com/exchange/org.mule.examples/fhir-r4-account-api/[Account] + +https://anypoint.mulesoft.com/exchange/org.mule.examples/fhir-r4-chargeitem-api/[ChargeItem] + +https://anypoint.mulesoft.com/exchange/org.mule.examples/fhir-r4-chargeitemdefinition-api/[ChargeItemDefinition] + +https://anypoint.mulesoft.com/exchange/org.mule.examples/fhir-r4-contract-api/[Contract] + +https://anypoint.mulesoft.com/exchange/org.mule.examples/fhir-r4-explanationofbenefit-api/[ExplanationOfBenefit] + +https://anypoint.mulesoft.com/exchange/org.mule.examples/fhir-r4-insuranceplan-api/[InsurancePlan] + +.^| Specialized - Public Health & Research | https://anypoint.mulesoft.com/exchange/org.mule.examples/fhir-r4-researchstudy-library/[ResearchStudy] + +https://anypoint.mulesoft.com/exchange/org.mule.examples/fhir-r4-researchsubject-library/[ResearchSubject] +| https://anypoint.mulesoft.com/exchange/org.mule.examples/fhir-r4-researchstudy-api/[ResearchStudy] + +https://anypoint.mulesoft.com/exchange/org.mule.examples/fhir-r4-researchsubject-api/[ResearchSubject] + +.^| Specialized - Definitional Artifacts | https://anypoint.mulesoft.com/exchange/org.mule.examples/fhir-r4-activitydefinition-library/[ActivityDefinition] + +https://anypoint.mulesoft.com/exchange/org.mule.examples/fhir-r4-devicedefinition-library/[DeviceDefinition] + +https://anypoint.mulesoft.com/exchange/org.mule.examples/fhir-r4-eventdefinition-library/[EventDefinition] + +https://anypoint.mulesoft.com/exchange/org.mule.examples/fhir-r4-observationdefinition-library/[ObservationDefinition] ^[u]^ + +https://anypoint.mulesoft.com/exchange/org.mule.examples/fhir-r4-plandefinition-library/[PlanDefinition] + +https://anypoint.mulesoft.com/exchange/org.mule.examples/fhir-r4-questionnaire-library/[Questionnaire] + +https://anypoint.mulesoft.com/exchange/org.mule.examples/fhir-r4-specimendefinition-library/[SpecimenDefinition] +| https://anypoint.mulesoft.com/exchange/org.mule.examples/fhir-r4-activitydefinition-api/[ActivityDefinition] + +https://anypoint.mulesoft.com/exchange/org.mule.examples/fhir-r4-devicedefinition-api/[DeviceDefinition] + +https://anypoint.mulesoft.com/exchange/org.mule.examples/fhir-r4-eventdefinition-api/[EventDefinition] + +https://anypoint.mulesoft.com/exchange/org.mule.examples/fhir-r4-observationdefinition-api/[ObservationDefinition] ^[u]^ + +https://anypoint.mulesoft.com/exchange/org.mule.examples/fhir-r4-plandefinition-api/[PlanDefinition] + +https://anypoint.mulesoft.com/exchange/org.mule.examples/fhir-r4-questionnaire-api/[Questionnaire] + +https://anypoint.mulesoft.com/exchange/org.mule.examples/fhir-r4-specimendefinition-api/[SpecimenDefinition] + +.^| Specialized - Evidence Based Medicine | https://anypoint.mulesoft.com/exchange/org.mule.examples/fhir-r4-researchdefinition-library/[ResearchDefinition] + +https://anypoint.mulesoft.com/exchange/org.mule.examples/fhir-r4-researchelementdefinition-library/[ResearchElementDefinition] + +https://anypoint.mulesoft.com/exchange/org.mule.examples/fhir-r4-evidence-library/[Evidence] + +https://anypoint.mulesoft.com/exchange/org.mule.examples/fhir-r4-evidencevariable-library/[EvidenceVariable] + +https://anypoint.mulesoft.com/exchange/org.mule.examples/fhir-r4-effectevidencesynthesis-library/[EffectEvidenceSynthesis] + +https://anypoint.mulesoft.com/exchange/org.mule.examples/fhir-r4-riskevidencesynthesis-library/[RiskEvidenceSynthesis] +| https://anypoint.mulesoft.com/exchange/org.mule.examples/fhir-r4-researchdefinition-api/[ResearchDefinition] + +https://anypoint.mulesoft.com/exchange/org.mule.examples/fhir-r4-researchelementdefinition-api/[ResearchElementDefinition] + +https://anypoint.mulesoft.com/exchange/org.mule.examples/fhir-r4-evidence-api/[Evidence] + +https://anypoint.mulesoft.com/exchange/org.mule.examples/fhir-r4-evidencevariable-api/[EvidenceVariable] + +https://anypoint.mulesoft.com/exchange/org.mule.examples/fhir-r4-effectevidencesynthesis-api/[EffectEvidenceSynthesis] + +https://anypoint.mulesoft.com/exchange/org.mule.examples/fhir-r4-riskevidencesynthesis-api/[RiskEvidenceSynthesis] + +.^| Specialized - Quality Reporting & Testing | https://anypoint.mulesoft.com/exchange/org.mule.examples/fhir-r4-measure-library/[Measure] + +https://anypoint.mulesoft.com/exchange/org.mule.examples/fhir-r4-measurereport-library/[MeasureReport] + +https://anypoint.mulesoft.com/exchange/org.mule.examples/fhir-r4-testscript-library/[TestScript] + +https://anypoint.mulesoft.com/exchange/org.mule.examples/fhir-r4-testreport-library/[TestReport] +| https://anypoint.mulesoft.com/exchange/org.mule.examples/fhir-r4-measure-api/[Measure] + +https://anypoint.mulesoft.com/exchange/org.mule.examples/fhir-r4-measurereport-api/[MeasureReport] + +https://anypoint.mulesoft.com/exchange/org.mule.examples/fhir-r4-testscript-api/[TestScript] + +https://anypoint.mulesoft.com/exchange/org.mule.examples/fhir-r4-testreport-api/[TestReport] + +.^| Specialized - Medication Definition | https://anypoint.mulesoft.com/exchange/org.mule.examples/fhir-r4-medicinalproduct-library/[MedicinalProduct] ^[u]^ + +https://anypoint.mulesoft.com/exchange/org.mule.examples/fhir-r4-medicinalproductauthorization-library/[MedicinalProductAuthorization] ^[u]^ + +https://anypoint.mulesoft.com/exchange/org.mule.examples/fhir-r4-medicinalproductcontraindication-library/[MedicinalProductContraindication] + +https://anypoint.mulesoft.com/exchange/org.mule.examples/fhir-r4-medicinalproductindication-library/[MedicinalProductIndication] + +https://anypoint.mulesoft.com/exchange/org.mule.examples/fhir-r4-medicinalproductingredient-library/[MedicinalProductIngredient] ^[u]^ + +https://anypoint.mulesoft.com/exchange/org.mule.examples/fhir-r4-medicinalproductinteraction-library/[MedicinalProductInteraction] + +https://anypoint.mulesoft.com/exchange/org.mule.examples/fhir-r4-medicinalproductmanufactured-library/[MedicinalProductManufactured] + +https://anypoint.mulesoft.com/exchange/org.mule.examples/fhir-r4-medicinalproductpackaged-library/[MedicinalProductPackaged] ^[u]^ + +https://anypoint.mulesoft.com/exchange/org.mule.examples/fhir-r4-medicinalproductpharmaceutical-library/[MedicinalProductPharmaceutical] ^[u]^ + +https://anypoint.mulesoft.com/exchange/org.mule.examples/fhir-r4-medicinalproductundesirableeffect-library/[MedicinalProductUndesirableEffect] + +https://anypoint.mulesoft.com/exchange/org.mule.examples/fhir-r4-substancenucleicacid-library/[SubstanceNucleicAcid] + +https://anypoint.mulesoft.com/exchange/org.mule.examples/fhir-r4-substancepolymer-library/[SubstancePolymer] ^[u]^ + +https://anypoint.mulesoft.com/exchange/org.mule.examples/fhir-r4-substanceprotein-library/[SubstanceProtein] + +https://anypoint.mulesoft.com/exchange/org.mule.examples/fhir-r4-substancereferenceinformation-library/[SubstanceReferenceInformation] ^[u]^ + +https://anypoint.mulesoft.com/exchange/org.mule.examples/fhir-r4-substancespecification-library/[SubstanceSpecification] ^[u]^ + +https://anypoint.mulesoft.com/exchange/org.mule.examples/fhir-r4-substancesourcematerial-library/[SubstanceSourceMaterial] +| https://anypoint.mulesoft.com/exchange/org.mule.examples/fhir-r4-medicinalproduct-api/[MedicinalProduct] ^[u]^ + +https://anypoint.mulesoft.com/exchange/org.mule.examples/fhir-r4-medicinalproductauthorization-api/[MedicinalProductAuthorization] ^[u]^ + +https://anypoint.mulesoft.com/exchange/org.mule.examples/fhir-r4-medicinalproductcontraindication-api/[MedicinalProductContraindication] + +https://anypoint.mulesoft.com/exchange/org.mule.examples/fhir-r4-medicinalproductindication-api/[MedicinalProductIndication] + +https://anypoint.mulesoft.com/exchange/org.mule.examples/fhir-r4-medicinalproductingredient-api/[MedicinalProductIngredient] ^[u]^ + +https://anypoint.mulesoft.com/exchange/org.mule.examples/fhir-r4-medicinalproductinteraction-api/[MedicinalProductInteraction] + +https://anypoint.mulesoft.com/exchange/org.mule.examples/fhir-r4-medicinalproductmanufactured-api/[MedicinalProductManufactured] + +https://anypoint.mulesoft.com/exchange/org.mule.examples/fhir-r4-medicinalproductpackaged-api/[MedicinalProductPackaged] ^[u]^ + +https://anypoint.mulesoft.com/exchange/org.mule.examples/fhir-r4-medicinalproductpharmaceutical-api/[MedicinalProductPharmaceutical] ^[u]^ + +https://anypoint.mulesoft.com/exchange/org.mule.examples/fhir-r4-medicinalproductundesirableeffect-api/[MedicinalProductUndesirableEffect] + +https://anypoint.mulesoft.com/exchange/org.mule.examples/fhir-r4-substancenucleicacid-api/[SubstanceNucleicAcid] + +https://anypoint.mulesoft.com/exchange/org.mule.examples/fhir-r4-substancepolymer-api/[SubstancePolymer] ^[u]^ + +https://anypoint.mulesoft.com/exchange/org.mule.examples/fhir-r4-substanceprotein-api/[SubstanceProtein] + +https://anypoint.mulesoft.com/exchange/org.mule.examples/fhir-r4-substancereferenceinformation-api/[SubstanceReferenceInformation] ^[u]^ + +https://anypoint.mulesoft.com/exchange/org.mule.examples/fhir-r4-substancespecification-api/[SubstanceSpecification] ^[u]^ + +https://anypoint.mulesoft.com/exchange/org.mule.examples/fhir-r4-substancesourcematerial-api/[SubstanceSourceMaterial] |=== NOTE: @@ -364,7 +364,7 @@ This FHIR Error API policy can be used to capture error responses and format the See the following page to learn more about the FHIR Error API Policy: -* https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fhir-error-policy/[FHIR Error API Policy] +* https://anypoint.mulesoft.com/exchange/org.mule.examples/fhir-error-policy/[FHIR Error API Policy] == See Also diff --git a/healthcare/2.20/modules/ROOT/pages/fhir-r4-us-core-profiles.adoc b/healthcare/2.20/modules/ROOT/pages/fhir-r4-us-core-profiles.adoc index bd9f34445..22b48f675 100644 --- a/healthcare/2.20/modules/ROOT/pages/fhir-r4-us-core-profiles.adoc +++ b/healthcare/2.20/modules/ROOT/pages/fhir-r4-us-core-profiles.adoc @@ -2,7 +2,7 @@ The MuleSoft Accelerator for Healthcare provides a library of United States Core Data for Interoperability (USCDI) and FHIR R4 resources to help healthcare developers adhere to interoperability needs and jumpstart the development of healthcare digital transformation initiatives. -You can also use the https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fhir-error-policy/[FHIR Error API Policy] to capture error responses and format them in an FHIR OperationOutcome-compliant format, since Anypoint Platform's out-of-the-box (OOTB) policies do not provide error messages in an FHIR-compliant format. This policy can also be used with other OOTB API policies provided in Anypoint Platform, such as OAuth or JWT. +You can also use the https://anypoint.mulesoft.com/exchange/org.mule.examples/fhir-error-policy/[FHIR Error API Policy] to capture error responses and format them in an FHIR OperationOutcome-compliant format, since Anypoint Platform's out-of-the-box (OOTB) policies do not provide error messages in an FHIR-compliant format. This policy can also be used with other OOTB API policies provided in Anypoint Platform, such as OAuth or JWT. For the list of all FHIR R4 assets, please refer to xref:fhir-r4-resources.adoc[this link]. @@ -15,68 +15,68 @@ _API specifications, data types, and libraries built to meet compliance with FHI | Module | Library | API specification | Data Types -| https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fhir-r4-commons-library/[FHIR R4 Common Library] + -https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fhir-r4-resource-types-library/[Resource Types Library] + +| https://anypoint.mulesoft.com/exchange/org.mule.examples/fhir-r4-commons-library/[FHIR R4 Common Library] + +https://anypoint.mulesoft.com/exchange/org.mule.examples/fhir-r4-resource-types-library/[Resource Types Library] + | NA | Foundation -| https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fhir-r4-documentreference-library/[DocumentReference Library] -| https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fhir-r4-documentreference-api/[DocumentReference API] +| https://anypoint.mulesoft.com/exchange/org.mule.examples/fhir-r4-documentreference-library/[DocumentReference Library] +| https://anypoint.mulesoft.com/exchange/org.mule.examples/fhir-r4-documentreference-api/[DocumentReference API] | Security -| https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fhir-r4-provenance-library/[Provenance Library] -| https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fhir-r4-provenance-api/[Provenance API] +| https://anypoint.mulesoft.com/exchange/org.mule.examples/fhir-r4-provenance-library/[Provenance Library] +| https://anypoint.mulesoft.com/exchange/org.mule.examples/fhir-r4-provenance-api/[Provenance API] | Conformance -| https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fhir-r4-capabilitystatement-library/[CapabilityStatement Library] -| https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fhir-r4-capabilitystatement-api/[CapabilityStatement API] +| https://anypoint.mulesoft.com/exchange/org.mule.examples/fhir-r4-capabilitystatement-library/[CapabilityStatement Library] +| https://anypoint.mulesoft.com/exchange/org.mule.examples/fhir-r4-capabilitystatement-api/[CapabilityStatement API] | Administration -| https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fhir-r4-us-core-patient-library/[Patient Library] + -https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fhir-r4-practitioner-library/[Practitioner Library] + -https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fhir-r4-practitionerrole-library/[PractitionerRole Library] + -https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fhir-r4-device-library/[Device Library] + -https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fhir-r4-organization-library/[Organization Library] + -https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fhir-r4-location-library/[Location Library] + -https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fhir-r4-careteam-library/[CareTeam Library] + -https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fhir-r4-encounter-library/[Encounter Library] + - -| https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fhir-r4-us-core-patient-api/[Patient API*] + -https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fhir-r4-practitioner-api/[Practitioner API] + -https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fhir-r4-practitionerrole-api/[PractitionerRole API] + -https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fhir-r4-device-api/[Device API] + -https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fhir-r4-organization-api/[Organization API] + -https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fhir-r4-location-api/[Location API] + -https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fhir-r4-careteam-api/[CareTeam API] + -https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fhir-r4-encounter-api/[Encounter API] +| https://anypoint.mulesoft.com/exchange/org.mule.examples/fhir-r4-us-core-patient-library/[Patient Library] + +https://anypoint.mulesoft.com/exchange/org.mule.examples/fhir-r4-practitioner-library/[Practitioner Library] + +https://anypoint.mulesoft.com/exchange/org.mule.examples/fhir-r4-practitionerrole-library/[PractitionerRole Library] + +https://anypoint.mulesoft.com/exchange/org.mule.examples/fhir-r4-device-library/[Device Library] + +https://anypoint.mulesoft.com/exchange/org.mule.examples/fhir-r4-organization-library/[Organization Library] + +https://anypoint.mulesoft.com/exchange/org.mule.examples/fhir-r4-location-library/[Location Library] + +https://anypoint.mulesoft.com/exchange/org.mule.examples/fhir-r4-careteam-library/[CareTeam Library] + +https://anypoint.mulesoft.com/exchange/org.mule.examples/fhir-r4-encounter-library/[Encounter Library] + + +| https://anypoint.mulesoft.com/exchange/org.mule.examples/fhir-r4-us-core-patient-api/[Patient API*] + +https://anypoint.mulesoft.com/exchange/org.mule.examples/fhir-r4-practitioner-api/[Practitioner API] + +https://anypoint.mulesoft.com/exchange/org.mule.examples/fhir-r4-practitionerrole-api/[PractitionerRole API] + +https://anypoint.mulesoft.com/exchange/org.mule.examples/fhir-r4-device-api/[Device API] + +https://anypoint.mulesoft.com/exchange/org.mule.examples/fhir-r4-organization-api/[Organization API] + +https://anypoint.mulesoft.com/exchange/org.mule.examples/fhir-r4-location-api/[Location API] + +https://anypoint.mulesoft.com/exchange/org.mule.examples/fhir-r4-careteam-api/[CareTeam API] + +https://anypoint.mulesoft.com/exchange/org.mule.examples/fhir-r4-encounter-api/[Encounter API] | Clinical -| https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fhir-r4-us-core-allergyintolerance-library/[AllergyIntolerance Library] + -https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fhir-r4-careplan-library/[CarePlan Library] + -https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fhir-r4-goal-library/[Goal Library] + -https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fhir-r4-procedure-library/[Procedure Library] + -https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fhir-r4-us-core-condition-library/[Condition Library] + - -| https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fhir-r4-us-core-allergyintolerance-api/[AllergyIntolerance API*] + -https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fhir-r4-careplan-api/[CarePlan API] + -https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fhir-r4-goal-api/[Goal API] + -https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fhir-r4-procedure-api/[Procedure API] + -https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fhir-r4-us-core-condition-api/[Condition API] +| https://anypoint.mulesoft.com/exchange/org.mule.examples/fhir-r4-us-core-allergyintolerance-library/[AllergyIntolerance Library] + +https://anypoint.mulesoft.com/exchange/org.mule.examples/fhir-r4-careplan-library/[CarePlan Library] + +https://anypoint.mulesoft.com/exchange/org.mule.examples/fhir-r4-goal-library/[Goal Library] + +https://anypoint.mulesoft.com/exchange/org.mule.examples/fhir-r4-procedure-library/[Procedure Library] + +https://anypoint.mulesoft.com/exchange/org.mule.examples/fhir-r4-us-core-condition-library/[Condition Library] + + +| https://anypoint.mulesoft.com/exchange/org.mule.examples/fhir-r4-us-core-allergyintolerance-api/[AllergyIntolerance API*] + +https://anypoint.mulesoft.com/exchange/org.mule.examples/fhir-r4-careplan-api/[CarePlan API] + +https://anypoint.mulesoft.com/exchange/org.mule.examples/fhir-r4-goal-api/[Goal API] + +https://anypoint.mulesoft.com/exchange/org.mule.examples/fhir-r4-procedure-api/[Procedure API] + +https://anypoint.mulesoft.com/exchange/org.mule.examples/fhir-r4-us-core-condition-api/[Condition API] | Diagnostics -| https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fhir-r4-us-core-observation-library/[Observation Library] + -https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fhir-r4-diagnosticreport-library/[DiagnosticReport Library] -| https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fhir-r4-us-core-observation-api/[Observation API*] + -https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fhir-r4-diagnosticreport-api/[DiagnosticReport API] +| https://anypoint.mulesoft.com/exchange/org.mule.examples/fhir-r4-us-core-observation-library/[Observation Library] + +https://anypoint.mulesoft.com/exchange/org.mule.examples/fhir-r4-diagnosticreport-library/[DiagnosticReport Library] +| https://anypoint.mulesoft.com/exchange/org.mule.examples/fhir-r4-us-core-observation-api/[Observation API*] + +https://anypoint.mulesoft.com/exchange/org.mule.examples/fhir-r4-diagnosticreport-api/[DiagnosticReport API] | Medications -| https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fhir-r4-immunization-library/[Immunization Library] + -https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fhir-r4-medication-library/[Medication Library] + -https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fhir-r4-medicationrequest-library/[MedicationRequest Library] -| https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fhir-r4-immunization-api/[Immunization API] + -https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fhir-r4-medication-api/[Medication API] + -https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fhir-r4-medicationrequest-api/[MedicationRequest API] +| https://anypoint.mulesoft.com/exchange/org.mule.examples/fhir-r4-immunization-library/[Immunization Library] + +https://anypoint.mulesoft.com/exchange/org.mule.examples/fhir-r4-medication-library/[Medication Library] + +https://anypoint.mulesoft.com/exchange/org.mule.examples/fhir-r4-medicationrequest-library/[MedicationRequest Library] +| https://anypoint.mulesoft.com/exchange/org.mule.examples/fhir-r4-immunization-api/[Immunization API] + +https://anypoint.mulesoft.com/exchange/org.mule.examples/fhir-r4-medication-api/[Medication API] + +https://anypoint.mulesoft.com/exchange/org.mule.examples/fhir-r4-medicationrequest-api/[MedicationRequest API] |=== _APIs marked with `*` have both FHIR R4 and US Core-specific Library and API specification available._ diff --git a/healthcare/2.20/modules/ROOT/pages/hl7-v2-fhir-converter.adoc b/healthcare/2.20/modules/ROOT/pages/hl7-v2-fhir-converter.adoc index 737ae28d6..d750bb00e 100644 --- a/healthcare/2.20/modules/ROOT/pages/hl7-v2-fhir-converter.adoc +++ b/healthcare/2.20/modules/ROOT/pages/hl7-v2-fhir-converter.adoc @@ -1,10 +1,10 @@ = HL7 v2 to FHIR Converter -The https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/hc-accelerator-hl7v2-to-fhir-sys-api[HL7 v2 to FHIR converter] comes with a ready to use template for HL7 v2 to FHIR conversion, which is based on the guidance provided by the https://build.fhir.org/ig/HL7/v2-to-fhir[HL7 v2 to FHIR Implementation Guide]. This template can be extended or modified to meet specific conversion requirements. +The https://anypoint.mulesoft.com/exchange/org.mule.examples/hc-accelerator-hl7v2-to-fhir-sys-api[HL7 v2 to FHIR converter] comes with a ready to use template for HL7 v2 to FHIR conversion, which is based on the guidance provided by the https://build.fhir.org/ig/HL7/v2-to-fhir[HL7 v2 to FHIR Implementation Guide]. This template can be extended or modified to meet specific conversion requirements. == Functional diagram -image:https://www.mulesoft.com/ext/solutions/draft/images/hc-hl7v2-to-fhir-usecase-diagram.png[hc-hl7v2-to-fhir-usecase-diagram.png,799,align="center"] +image:https://www.mulesoft.com/ext/solutions/images/hc-hl7v2-to-fhir-usecase-diagram.png[hc-hl7v2-to-fhir-usecase-diagram.png,799,align="center"] == Advantages diff --git a/healthcare/2.20/modules/ROOT/pages/index.adoc b/healthcare/2.20/modules/ROOT/pages/index.adoc index 7fa784de2..366f4c508 100644 --- a/healthcare/2.20/modules/ROOT/pages/index.adoc +++ b/healthcare/2.20/modules/ROOT/pages/index.adoc @@ -9,13 +9,13 @@ For solutions related to life sciences, the xref:life-sciences::index.adoc[MuleS The following describes the use cases supported by the MuleSoft Accelerator for Healthcare: -* https://www.anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/mulesoft-accelerator-for-healthcare/minor/{hls-version}/pages/Use%20case%201%20-%20Patient%20360/[Patient 360^] — This use case accelerates Patient 360 efforts by providing pre-built APIs and implementation templates to integrate critical data from EHRs with other emerging technologies and applications. This solution provides both HL7 v2 and FHIR-based capabilities to allow organizations to support a variety of use cases and realize value regardless of the industry standard that is present in their organization's ecosystem. -* https://www.anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/mulesoft-accelerator-for-healthcare/minor/{hls-version}/pages/Use%20case%202%20-%20CMS%20Interoperability/[CMS Interoperability^] — Includes assets to help you meet CMS Interoperability and Patient Access final rule. -* https://www.anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/mulesoft-accelerator-for-healthcare/minor/{hls-version}/pages/Use%20case%203%20-%20Labs%20integration/[Labs integration^] — Includes the The Electronic Laboratory Reporting (ELR) to CalREDIE implementation template, which helps you transmit laboratory reports that identify a notifiable condition to public health agencies (for example, California Department of Public Health). -* https://www.anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/mulesoft-accelerator-for-healthcare/minor/{hls-version}/pages/Use%20case%204%20-%20Appointment%20scheduling/[Appointment scheduling^] — Includes the Appointment Scheduling Process API for both Cerner and Epic, which enables call center agents to schedule, update, and cancel appointments on behalf of the patient. See the implementation template for more information. -* https://www.anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/mulesoft-accelerator-for-healthcare/minor/{hls-version}/pages/Use%20case%205%20-%20Benefits%20and%20eligibility%20verification/[Benefits and eligibility verification^] — Enables call center agents and care staff to perform real-time benefits and eligibility verification. Providers can electronically verify a patient's insurance coverage in real-time for medical treatment directly within Salesforce Health Cloud. -* https://www.anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/mulesoft-accelerator-for-healthcare/minor/{hls-version}/pages/Use%20case%206%20-%20Prior%20Authorization/[Prior Authorization^] — Includes CRD, DTR, and PAS API specifications and implementation templates to automate the prior authorization process for more immediate authorizations, leading to better outcomes and increased satisfaction for patients, providers, and payers. -* https://www.anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/mulesoft-accelerator-for-healthcare/minor/{hls-version}/pages/Use%20case%207%20-%20Population%20health%20management/[Population health management^] - Convert and surface valuable population health data into Amazon HealthLake to improve clinical outcomes. +* https://www.anypoint.mulesoft.com/exchange/org.mule.examples/mulesoft-accelerator-for-healthcare/minor/{hls-version}/pages/Use%20case%201%20-%20Patient%20360/[Patient 360^] — This use case accelerates Patient 360 efforts by providing pre-built APIs and implementation templates to integrate critical data from EHRs with other emerging technologies and applications. This solution provides both HL7 v2 and FHIR-based capabilities to allow organizations to support a variety of use cases and realize value regardless of the industry standard that is present in their organization's ecosystem. +* https://www.anypoint.mulesoft.com/exchange/org.mule.examples/mulesoft-accelerator-for-healthcare/minor/{hls-version}/pages/Use%20case%202%20-%20CMS%20Interoperability/[CMS Interoperability^] — Includes assets to help you meet CMS Interoperability and Patient Access final rule. +* https://www.anypoint.mulesoft.com/exchange/org.mule.examples/mulesoft-accelerator-for-healthcare/minor/{hls-version}/pages/Use%20case%203%20-%20Labs%20integration/[Labs integration^] — Includes the The Electronic Laboratory Reporting (ELR) to CalREDIE implementation template, which helps you transmit laboratory reports that identify a notifiable condition to public health agencies (for example, California Department of Public Health). +* https://www.anypoint.mulesoft.com/exchange/org.mule.examples/mulesoft-accelerator-for-healthcare/minor/{hls-version}/pages/Use%20case%204%20-%20Appointment%20scheduling/[Appointment scheduling^] — Includes the Appointment Scheduling Process API for both Cerner and Epic, which enables call center agents to schedule, update, and cancel appointments on behalf of the patient. See the implementation template for more information. +* https://www.anypoint.mulesoft.com/exchange/org.mule.examples/mulesoft-accelerator-for-healthcare/minor/{hls-version}/pages/Use%20case%205%20-%20Benefits%20and%20eligibility%20verification/[Benefits and eligibility verification^] — Enables call center agents and care staff to perform real-time benefits and eligibility verification. Providers can electronically verify a patient's insurance coverage in real-time for medical treatment directly within Salesforce Health Cloud. +* https://www.anypoint.mulesoft.com/exchange/org.mule.examples/mulesoft-accelerator-for-healthcare/minor/{hls-version}/pages/Use%20case%206%20-%20Prior%20Authorization/[Prior Authorization^] — Includes CRD, DTR, and PAS API specifications and implementation templates to automate the prior authorization process for more immediate authorizations, leading to better outcomes and increased satisfaction for patients, providers, and payers. +* https://www.anypoint.mulesoft.com/exchange/org.mule.examples/mulesoft-accelerator-for-healthcare/minor/{hls-version}/pages/Use%20case%207%20-%20Population%20health%20management/[Population health management^] - Convert and surface valuable population health data into Amazon HealthLake to improve clinical outcomes. === Use Case Agnostic Assets @@ -32,4 +32,4 @@ The following use-case agnostic assets are also available: * xref:prerequisites.adoc[Prerequisites] * xref:fhir-r4-assets.adoc[Available Assets] * xref:release-notes.adoc[Release Notes] -* https://www.anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/mulesoft-accelerator-for-healthcare/[MuleSoft Accelerator for Healthcare on Exchange^] +* https://www.anypoint.mulesoft.com/exchange/org.mule.examples/mulesoft-accelerator-for-healthcare/[MuleSoft Accelerator for Healthcare on Exchange^] diff --git a/healthcare/2.20/modules/ROOT/pages/release-notes.adoc b/healthcare/2.20/modules/ROOT/pages/release-notes.adoc index dbe728eec..336e3684f 100644 --- a/healthcare/2.20/modules/ROOT/pages/release-notes.adoc +++ b/healthcare/2.20/modules/ROOT/pages/release-notes.adoc @@ -5,10 +5,10 @@ *August 23, 2023* -This release extends the solution provided for the https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/mulesoft-accelerator-for-healthcare/minor/{hls-version}/pages/Use%20case%201%20-%20Patient%20360/[Patient 360 use case] to allow customers to discover and deploy from Salesforce using MuleSoft Direct for Health Cloud. The following updates are included: +This release extends the solution provided for the https://anypoint.mulesoft.com/exchange/org.mule.examples/mulesoft-accelerator-for-healthcare/minor/{hls-version}/pages/Use%20case%201%20-%20Patient%20360/[Patient 360 use case] to allow customers to discover and deploy from Salesforce using MuleSoft Direct for Health Cloud. The following updates are included: -* Patient Summary - EMR Integration | https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/hls-hc-fhir-r4-sync-prc-api-impl[Application] -* Event-based ingestion into Health Cloud | https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/hls-hl7v2-events-mgmt-listener-impl[Application] +* Patient Summary - EMR Integration | https://anypoint.mulesoft.com/exchange/org.mule.examples/hls-hc-fhir-r4-sync-prc-api-impl[Application] +* Event-based ingestion into Health Cloud | https://anypoint.mulesoft.com/exchange/org.mule.examples/hls-hl7v2-events-mgmt-listener-impl[Application] * Enhanced FHIR R4 RAML libraries and specifications to leverage the new version of AMF parser to better align with industry standards. @@ -16,7 +16,7 @@ This release extends the solution provided for the https://anypoint.mulesoft.com *May 30, 2023* -This release includes the following enhancements to the https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/mulesoft-accelerator-for-healthcare/minor/{hls-version}/pages/Use%20case%201%20-%20Patient%20360/[Patient 360 use case] and https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/mulesoft-accelerator-for-healthcare/minor/2.19/pages/dkv-pq7/FHIR%20API%20assets%20and%20converters%20(HL7%20v2%2C%20CDA%20and%20X12)/[FHIR API assets and converters]: +This release includes the following enhancements to the https://anypoint.mulesoft.com/exchange/org.mule.examples/mulesoft-accelerator-for-healthcare/minor/{hls-version}/pages/Use%20case%201%20-%20Patient%20360/[Patient 360 use case] and https://anypoint.mulesoft.com/exchange/org.mule.examples/mulesoft-accelerator-for-healthcare/minor/2.19/pages/dkv-pq7/FHIR%20API%20assets%20and%20converters%20(HL7%20v2%2C%20CDA%20and%20X12)/[FHIR API assets and converters]: * Expanded the library of assets to allow organizations to more easily ingest critical information from clinical systems into Salesforce Health Cloud, which enables users to view the information included in the supported HL7 v2 events natively in their Salesforce console. ** Added support for ADT^A02, ADT^A03, ADT^A04, ADT^A05, SIU^S12, SIU^S13, SIU^S14, and SIU^S15. @@ -29,19 +29,19 @@ This release includes the following enhancements to the https://anypoint.mulesof 13 December 2022 -This release extends the solution provided for https://www.anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/mulesoft-accelerator-for-healthcare/minor/{hls-version}/pages/Use%20case%207%20-%20Population%20health%20management/[Population health management] to enable organizations to surface valuable population health data from EHR systems into Amazon HealthLake and Salesforce Customer Data Platform to improve clinical outcomes. +This release extends the solution provided for https://www.anypoint.mulesoft.com/exchange/org.mule.examples/mulesoft-accelerator-for-healthcare/minor/{hls-version}/pages/Use%20case%207%20-%20Population%20health%20management/[Population health management] to enable organizations to surface valuable population health data from EHR systems into Amazon HealthLake and Salesforce Customer Data Platform to improve clinical outcomes. -* FHIR Bulk Export System API | https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/hls-fhir-bulk-export-sys-api-spec[API Specification] | https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/hls-fhir-bulk-export-sys-api[Implementation Template] -* Population Health Management Process API | https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/hls-population-health-mgmt-prc-api/[Implementation Template] -* Salesforce CDP System API | https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/hls-salesforce-cdp-sys-api-spec[API Specification] | https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/hls-salesforce-cdp-sys-api[Implementation Template] -* Azure Web Engagement System API | https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/hls-engagements-sys-api-spec[API Specification] | https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/hls-azure-patient-engmt-sys-api[Implementation Template] -* Patient Segmentation Process API | https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/hls-patient-segmentation-prc-api/[Implementation Template] +* FHIR Bulk Export System API | https://anypoint.mulesoft.com/exchange/org.mule.examples/hls-fhir-bulk-export-sys-api-spec[API Specification] | https://anypoint.mulesoft.com/exchange/org.mule.examples/hls-fhir-bulk-export-sys-api[Implementation Template] +* Population Health Management Process API | https://anypoint.mulesoft.com/exchange/org.mule.examples/hls-population-health-mgmt-prc-api/[Implementation Template] +* Salesforce CDP System API | https://anypoint.mulesoft.com/exchange/org.mule.examples/hls-salesforce-cdp-sys-api-spec[API Specification] | https://anypoint.mulesoft.com/exchange/org.mule.examples/hls-salesforce-cdp-sys-api[Implementation Template] +* Azure Web Engagement System API | https://anypoint.mulesoft.com/exchange/org.mule.examples/hls-engagements-sys-api-spec[API Specification] | https://anypoint.mulesoft.com/exchange/org.mule.examples/hls-azure-patient-engmt-sys-api[Implementation Template] +* Patient Segmentation Process API | https://anypoint.mulesoft.com/exchange/org.mule.examples/hls-patient-segmentation-prc-api/[Implementation Template] == v2.17 20 October 2022 -This release provides a solution for https://www.anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/mulesoft-accelerator-for-healthcare/minor/{hls-version}/pages/Use%20case%207%20-%20Population%20health%20management/[Population health management] to enable organizations to convert and surface valuable population health data into Amazon HealthLake to improve clinical outcomes. +This release provides a solution for https://www.anypoint.mulesoft.com/exchange/org.mule.examples/mulesoft-accelerator-for-healthcare/minor/{hls-version}/pages/Use%20case%207%20-%20Population%20health%20management/[Population health management] to enable organizations to convert and surface valuable population health data into Amazon HealthLake to improve clinical outcomes. As part of this release, existing assets used to convert from HL7 v2, C-CDA and X12 formats to FHIR R4 were enhanced to fix defects and enable use with Amazon HealthLake. @@ -57,8 +57,8 @@ This release provides a support to additional CDA document types in xref:ccda-fh This release provides Healthcare organizations with a reference implementations to xref:fhir-r4-assets.adoc[convert FHIR R4 resources from HL7 FHIR JSON format to RAML specification] and xref:ccda-fhir-converter.adoc[convert C-CDA messages to FHIR]. -* FHIR RAML auto-generator | https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/hls-fhirjson-to-raml-sys-api-spec/[API specification] | https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/hls-fhirjson-to-raml-sys-api/[Implementation Template] -* C-CDA to FHIR System API | https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/hls-ccda-to-fhir-sys-api-spec/[API specification] | https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/hls-ccda-to-fhir-sys-api/[Implementation Template] +* FHIR RAML auto-generator | https://anypoint.mulesoft.com/exchange/org.mule.examples/hls-fhirjson-to-raml-sys-api-spec/[API specification] | https://anypoint.mulesoft.com/exchange/org.mule.examples/hls-fhirjson-to-raml-sys-api/[Implementation Template] +* C-CDA to FHIR System API | https://anypoint.mulesoft.com/exchange/org.mule.examples/hls-ccda-to-fhir-sys-api-spec/[API specification] | https://anypoint.mulesoft.com/exchange/org.mule.examples/hls-ccda-to-fhir-sys-api/[Implementation Template] == v2.14.1 @@ -66,29 +66,29 @@ This release provides Healthcare organizations with a reference implementations This minor release includes an upgrade to the dependencies on the assets that perform FHIR resource validation. -* Health Cloud Administration System API | https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/hc-accelerator-sfdc-us-core-administration-sys-api/[Implementation Template] -* Health Cloud Clinical System API | https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/hc-accelerator-sfdc-us-core-clinical-sys-api/[Implementation Template] -* Health Cloud Diagnostics System API | https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/hc-accelerator-sfdc-us-core-diagnostics-sys-api/[Implementation Template] -* Health Cloud Medications System API | https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/hc-accelerator-sfdc-us-core-medications-sys-api/[Implementation Template] -* Health Cloud Financial System API | https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/hc-accelerator-sfdc-financial-sys-api/[Implementation Template] -* Cerner Administration System API | https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/hc-accelerator-cerner-us-core-administration-sys-api/[Implementation Template] -* Cerner Clinical System API | https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/hc-accelerator-cerner-us-core-clinical-sys-api/[Implementation Template] -* Cerner Diagnostics System API | https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/hc-accelerator-cerner-us-core-diagnostics-sys-api/[Implementation Template] -* Cerner Medications System API | https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/hc-accelerator-cerner-us-core-medications-sys-api/[Implementation Template] -* Cerner Workflow System API | https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/hc-accelerator-cerner-workflow-sys-api/[Implementation Template] -* Cerner Financial System API | https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/hc-accelerator-cerner-financial-sys-api/[Implementation Template] -* Epic Administration System API | https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/hc-accelerator-epic-us-core-administration-sys-api/[Implementation Template] -* Epic Clinical System API | https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/hc-accelerator-epic-us-core-clinical-sys-api/[Implementation Template] -* Epic Diagnostics System API | https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/hc-accelerator-epic-us-core-diagnostics-sys-api/[Implementation Template] -* Epic Medications System API | https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/hc-accelerator-epic-us-core-medications-sys-api/[Implementation Template] -* Epic Financial System API | https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/hc-accelerator-epic-financial-sys-api/[Implementation Template] -* Benefits Verification Process API | https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/hc-accelerator-benefits-verification-prc-api/[Implementation Template] -* Benefits Eligibility Verification System API | https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/hc-accelerator-availity-financial-sys-api/[Implementation Template] -* CRD Clinical Decision Support System API | https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/hc-accelerator-cds-services-sys-api/[Implementation Template] -* DTR System API | https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/hc-accelerator-davinci-dtr-sys-api/[Implementation Template] -* Prior Authorization System API | https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/hc-accelerator-prior-authorization-sys-api[Implementation Template] -* HL7 V2 to FHIR System API | https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/hc-accelerator-hl7v2-to-fhir-sys-api/[Implementation Template] -* X12 to FHIR System API | https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/hls-fhir-to-x12-sys-api/[Implementation Template] +* Health Cloud Administration System API | https://anypoint.mulesoft.com/exchange/org.mule.examples/hc-accelerator-sfdc-us-core-administration-sys-api/[Implementation Template] +* Health Cloud Clinical System API | https://anypoint.mulesoft.com/exchange/org.mule.examples/hc-accelerator-sfdc-us-core-clinical-sys-api/[Implementation Template] +* Health Cloud Diagnostics System API | https://anypoint.mulesoft.com/exchange/org.mule.examples/hc-accelerator-sfdc-us-core-diagnostics-sys-api/[Implementation Template] +* Health Cloud Medications System API | https://anypoint.mulesoft.com/exchange/org.mule.examples/hc-accelerator-sfdc-us-core-medications-sys-api/[Implementation Template] +* Health Cloud Financial System API | https://anypoint.mulesoft.com/exchange/org.mule.examples/hc-accelerator-sfdc-financial-sys-api/[Implementation Template] +* Cerner Administration System API | https://anypoint.mulesoft.com/exchange/org.mule.examples/hc-accelerator-cerner-us-core-administration-sys-api/[Implementation Template] +* Cerner Clinical System API | https://anypoint.mulesoft.com/exchange/org.mule.examples/hc-accelerator-cerner-us-core-clinical-sys-api/[Implementation Template] +* Cerner Diagnostics System API | https://anypoint.mulesoft.com/exchange/org.mule.examples/hc-accelerator-cerner-us-core-diagnostics-sys-api/[Implementation Template] +* Cerner Medications System API | https://anypoint.mulesoft.com/exchange/org.mule.examples/hc-accelerator-cerner-us-core-medications-sys-api/[Implementation Template] +* Cerner Workflow System API | https://anypoint.mulesoft.com/exchange/org.mule.examples/hc-accelerator-cerner-workflow-sys-api/[Implementation Template] +* Cerner Financial System API | https://anypoint.mulesoft.com/exchange/org.mule.examples/hc-accelerator-cerner-financial-sys-api/[Implementation Template] +* Epic Administration System API | https://anypoint.mulesoft.com/exchange/org.mule.examples/hc-accelerator-epic-us-core-administration-sys-api/[Implementation Template] +* Epic Clinical System API | https://anypoint.mulesoft.com/exchange/org.mule.examples/hc-accelerator-epic-us-core-clinical-sys-api/[Implementation Template] +* Epic Diagnostics System API | https://anypoint.mulesoft.com/exchange/org.mule.examples/hc-accelerator-epic-us-core-diagnostics-sys-api/[Implementation Template] +* Epic Medications System API | https://anypoint.mulesoft.com/exchange/org.mule.examples/hc-accelerator-epic-us-core-medications-sys-api/[Implementation Template] +* Epic Financial System API | https://anypoint.mulesoft.com/exchange/org.mule.examples/hc-accelerator-epic-financial-sys-api/[Implementation Template] +* Benefits Verification Process API | https://anypoint.mulesoft.com/exchange/org.mule.examples/hc-accelerator-benefits-verification-prc-api/[Implementation Template] +* Benefits Eligibility Verification System API | https://anypoint.mulesoft.com/exchange/org.mule.examples/hc-accelerator-availity-financial-sys-api/[Implementation Template] +* CRD Clinical Decision Support System API | https://anypoint.mulesoft.com/exchange/org.mule.examples/hc-accelerator-cds-services-sys-api/[Implementation Template] +* DTR System API | https://anypoint.mulesoft.com/exchange/org.mule.examples/hc-accelerator-davinci-dtr-sys-api/[Implementation Template] +* Prior Authorization System API | https://anypoint.mulesoft.com/exchange/org.mule.examples/hc-accelerator-prior-authorization-sys-api[Implementation Template] +* HL7 V2 to FHIR System API | https://anypoint.mulesoft.com/exchange/org.mule.examples/hc-accelerator-hl7v2-to-fhir-sys-api/[Implementation Template] +* X12 to FHIR System API | https://anypoint.mulesoft.com/exchange/org.mule.examples/hls-fhir-to-x12-sys-api/[Implementation Template] == v2.14 @@ -96,7 +96,7 @@ This minor release includes an upgrade to the dependencies on the assets that pe This release provides Healthcare organizations with a reference implementation to xref:x12-fhir-converter.adoc[convert X12 messages to FHIR]. -* https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/hls-fhir-r4-to-x12-sys-api-spec/[API specification] and https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/hls-fhir-to-x12-sys-api/[implementation template] for the X12 to FHIR System API. +* https://anypoint.mulesoft.com/exchange/org.mule.examples/hls-fhir-r4-to-x12-sys-api-spec/[API specification] and https://anypoint.mulesoft.com/exchange/org.mule.examples/hls-fhir-to-x12-sys-api/[implementation template] for the X12 to FHIR System API. == v2.13 @@ -104,9 +104,9 @@ This release provides Healthcare organizations with a reference implementation t This release provides an end-to-end solution for prior authorization, which includes CRD, DTR, and PAS API specifications and implementation templates to automate the prior authorization process for more immediate authorizations: -* CRD Clinical Decision Support System API | https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/hls-cds-services-sys-api-spec/[API Specification] | https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/hc-accelerator-cds-services-sys-api/[Implementation Template] -* DTR System API | https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fhir-r4-davinci-dtr-api/[API Specification] | https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/hc-accelerator-davinci-dtr-sys-api/[Implementation Template] -* Prior Authorization System API | https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fhir-r4-prior-authorization-api[API Specification] | https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/hc-accelerator-prior-authorization-sys-api[Implementation Template] +* CRD Clinical Decision Support System API | https://anypoint.mulesoft.com/exchange/org.mule.examples/hls-cds-services-sys-api-spec/[API Specification] | https://anypoint.mulesoft.com/exchange/org.mule.examples/hc-accelerator-cds-services-sys-api/[Implementation Template] +* DTR System API | https://anypoint.mulesoft.com/exchange/org.mule.examples/fhir-r4-davinci-dtr-api/[API Specification] | https://anypoint.mulesoft.com/exchange/org.mule.examples/hc-accelerator-davinci-dtr-sys-api/[Implementation Template] +* Prior Authorization System API | https://anypoint.mulesoft.com/exchange/org.mule.examples/fhir-r4-prior-authorization-api[API Specification] | https://anypoint.mulesoft.com/exchange/org.mule.examples/hc-accelerator-prior-authorization-sys-api[Implementation Template] == v2.12.1 @@ -114,7 +114,7 @@ This release provides an end-to-end solution for prior authorization, which incl This minor release includes an upgrade to the assets to be EMR agnostic, which allows customers to choose any EMR as a System of Record: -* Patient Sync Process API | https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/patient-sync-prc-api/[API Specification] | https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/hc-accelerator-patient-sync-prc-api/[Implementation Template] +* Patient Sync Process API | https://anypoint.mulesoft.com/exchange/org.mule.examples/patient-sync-prc-api/[API Specification] | https://anypoint.mulesoft.com/exchange/org.mule.examples/hc-accelerator-patient-sync-prc-api/[Implementation Template] == v2.12 @@ -122,8 +122,8 @@ This minor release includes an upgrade to the assets to be EMR agnostic, which a This release provides an end-to-end solution for prior authorization support, which automates the prior authorization process for more immediate authorizations. The following assets are also available: -* Prior Authorization System API | https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fhir-r4-prior-authorization-api[API Specification] | https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/hc-accelerator-prior-authorization-sys-api[Implementation Template] -* Aidbox Administration System API | https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fhir-r4-administration-api/[API Specification] | https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/hc-accelerator-aidbox-us-core-administration-sys-api/[Implementation Template] +* Prior Authorization System API | https://anypoint.mulesoft.com/exchange/org.mule.examples/fhir-r4-prior-authorization-api[API Specification] | https://anypoint.mulesoft.com/exchange/org.mule.examples/hc-accelerator-prior-authorization-sys-api[Implementation Template] +* Aidbox Administration System API | https://anypoint.mulesoft.com/exchange/org.mule.examples/fhir-r4-administration-api/[API Specification] | https://anypoint.mulesoft.com/exchange/org.mule.examples/hc-accelerator-aidbox-us-core-administration-sys-api/[Implementation Template] == v2.11 @@ -131,12 +131,12 @@ This release provides an end-to-end solution for prior authorization support, wh This release provides an end-to-end solution for benefits and eligibility verification using Health Cloud, Epic, and Cerner as the reference backend systems: -* Benefits Verification Process API | https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/benefits-verification-prc-api/[API Specification] | https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/hc-accelerator-benefits-verification-prc-api/[Implementation Template] -* Cerner Financial System API | https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/cerner-fhir-r4-financial-api/[API Specification] | https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/hc-accelerator-cerner-financial-sys-api/[Implementation Template] -* Epic Financial System API | https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/epic-fhir-r4-financial-api/[API Specification] | https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/hc-accelerator-epic-financial-sys-api/[Implementation Template] -* Benefits Eligibility Verification System API | https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/availity-fhir-r4-financial-api/[API Specification] | https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/hc-accelerator-availity-financial-sys-api/[Implementation Template] -* Health Cloud Financial System API | https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fhir-r4-financial-api/[API Specification] | https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/hc-accelerator-sfdc-financial-sys-api/[Implementation Template] -* Health Cloud Benefits Verification Lightning Web Component | https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/hc-accelerator-benefits-verification-lwc-src/[Source] +* Benefits Verification Process API | https://anypoint.mulesoft.com/exchange/org.mule.examples/benefits-verification-prc-api/[API Specification] | https://anypoint.mulesoft.com/exchange/org.mule.examples/hc-accelerator-benefits-verification-prc-api/[Implementation Template] +* Cerner Financial System API | https://anypoint.mulesoft.com/exchange/org.mule.examples/cerner-fhir-r4-financial-api/[API Specification] | https://anypoint.mulesoft.com/exchange/org.mule.examples/hc-accelerator-cerner-financial-sys-api/[Implementation Template] +* Epic Financial System API | https://anypoint.mulesoft.com/exchange/org.mule.examples/epic-fhir-r4-financial-api/[API Specification] | https://anypoint.mulesoft.com/exchange/org.mule.examples/hc-accelerator-epic-financial-sys-api/[Implementation Template] +* Benefits Eligibility Verification System API | https://anypoint.mulesoft.com/exchange/org.mule.examples/availity-fhir-r4-financial-api/[API Specification] | https://anypoint.mulesoft.com/exchange/org.mule.examples/hc-accelerator-availity-financial-sys-api/[Implementation Template] +* Health Cloud Financial System API | https://anypoint.mulesoft.com/exchange/org.mule.examples/fhir-r4-financial-api/[API Specification] | https://anypoint.mulesoft.com/exchange/org.mule.examples/hc-accelerator-sfdc-financial-sys-api/[Implementation Template] +* Health Cloud Benefits Verification Lightning Web Component | https://anypoint.mulesoft.com/exchange/org.mule.examples/hc-accelerator-benefits-verification-lwc-src/[Source] == v2.10 @@ -144,37 +144,37 @@ This release provides an end-to-end solution for benefits and eligibility verifi The focus of the 2.10 release is to provide assets for the patient sync capabilities: -* Patient sync Lightning Web Component | https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/hc-accelerator-sfdc-patient-sync-lwc-src/[Source] -* Patient Sync Process API | https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/patient-sync-prc-api/[API Specification] | https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/hc-accelerator-patient-sync-prc-api/[Implementation Template] +* Patient sync Lightning Web Component | https://anypoint.mulesoft.com/exchange/org.mule.examples/hc-accelerator-sfdc-patient-sync-lwc-src/[Source] +* Patient Sync Process API | https://anypoint.mulesoft.com/exchange/org.mule.examples/patient-sync-prc-api/[API Specification] | https://anypoint.mulesoft.com/exchange/org.mule.examples/hc-accelerator-patient-sync-prc-api/[Implementation Template] The following assets were also enhanced and improved for this release: -* FHIR R4 Location Library | https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fhir-r4-location-library/[API Specification Fragment] -* FHIR R4 Procedure Library | https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fhir-r4-procedure-library/[API Specification Fragment] -* FHIR R4 Administration API | https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fhir-r4-administration-api/[API Specification] -* FHIR R4 Clinical API | https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fhir-r4-clinical-api/[API Specification] -* Epic FHIR R4 Administration API | https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/epic-fhir-r4-administration-api/[API Specification] -* Epic FHIR R4 Clinical API | https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/epic-fhir-r4-clinical-api/[API Specification] -* Epic FHIR R4 Medications API | https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/epic-fhir-r4-medications-api/[API Specification] -* Cerner FHIR R4 Administration API | https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/cerner-fhir-r4-administration-api/[API Specification] -* Cerner Administration System API | https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/hc-accelerator-cerner-us-core-administration-sys-api/[Implementation Template] -* Health Cloud Clinical System API | https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/hc-accelerator-sfdc-us-core-clinical-sys-api/[Implementation Template] -* Health Cloud Diagnostics System API | https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/hc-accelerator-sfdc-us-core-diagnostics-sys-api/[Implementation Template] -* Health Cloud Medications System API | https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/hc-accelerator-sfdc-us-core-medications-sys-api/[Implementation Template] -* Health Cloud Administration System API | https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/hc-accelerator-sfdc-us-core-administration-sys-api/[Implementation Template] +* FHIR R4 Location Library | https://anypoint.mulesoft.com/exchange/org.mule.examples/fhir-r4-location-library/[API Specification Fragment] +* FHIR R4 Procedure Library | https://anypoint.mulesoft.com/exchange/org.mule.examples/fhir-r4-procedure-library/[API Specification Fragment] +* FHIR R4 Administration API | https://anypoint.mulesoft.com/exchange/org.mule.examples/fhir-r4-administration-api/[API Specification] +* FHIR R4 Clinical API | https://anypoint.mulesoft.com/exchange/org.mule.examples/fhir-r4-clinical-api/[API Specification] +* Epic FHIR R4 Administration API | https://anypoint.mulesoft.com/exchange/org.mule.examples/epic-fhir-r4-administration-api/[API Specification] +* Epic FHIR R4 Clinical API | https://anypoint.mulesoft.com/exchange/org.mule.examples/epic-fhir-r4-clinical-api/[API Specification] +* Epic FHIR R4 Medications API | https://anypoint.mulesoft.com/exchange/org.mule.examples/epic-fhir-r4-medications-api/[API Specification] +* Cerner FHIR R4 Administration API | https://anypoint.mulesoft.com/exchange/org.mule.examples/cerner-fhir-r4-administration-api/[API Specification] +* Cerner Administration System API | https://anypoint.mulesoft.com/exchange/org.mule.examples/hc-accelerator-cerner-us-core-administration-sys-api/[Implementation Template] +* Health Cloud Clinical System API | https://anypoint.mulesoft.com/exchange/org.mule.examples/hc-accelerator-sfdc-us-core-clinical-sys-api/[Implementation Template] +* Health Cloud Diagnostics System API | https://anypoint.mulesoft.com/exchange/org.mule.examples/hc-accelerator-sfdc-us-core-diagnostics-sys-api/[Implementation Template] +* Health Cloud Medications System API | https://anypoint.mulesoft.com/exchange/org.mule.examples/hc-accelerator-sfdc-us-core-medications-sys-api/[Implementation Template] +* Health Cloud Administration System API | https://anypoint.mulesoft.com/exchange/org.mule.examples/hc-accelerator-sfdc-us-core-administration-sys-api/[Implementation Template] The following assets are modified to support XML format for existing Epic System APIs: -* Epic Clinical System API | https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/hc-accelerator-epic-us-core-clinical-sys-api/[Implementation Template] -* Epic Diagnostics System API | https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/hc-accelerator-epic-us-core-diagnostics-sys-api/[Implementation Template] -* Epic Medications System API | https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/hc-accelerator-epic-us-core-medications-sys-api/[Implementation Template] -* Epic Administration System API | https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/hc-accelerator-epic-us-core-administration-sys-api/[Implementation Template] +* Epic Clinical System API | https://anypoint.mulesoft.com/exchange/org.mule.examples/hc-accelerator-epic-us-core-clinical-sys-api/[Implementation Template] +* Epic Diagnostics System API | https://anypoint.mulesoft.com/exchange/org.mule.examples/hc-accelerator-epic-us-core-diagnostics-sys-api/[Implementation Template] +* Epic Medications System API | https://anypoint.mulesoft.com/exchange/org.mule.examples/hc-accelerator-epic-us-core-medications-sys-api/[Implementation Template] +* Epic Administration System API | https://anypoint.mulesoft.com/exchange/org.mule.examples/hc-accelerator-epic-us-core-administration-sys-api/[Implementation Template] The following assets are modified to support updated API specifications for existing Cerner System APIs: -* Cerner Administration System API | https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/hc-accelerator-cerner-us-core-administration-sys-api/[Implementation Template] -* Cerner Clinical System API | https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/hc-accelerator-cerner-us-core-clinical-sys-api/[Implementation Template] -* Cerner Medications System API | https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/hc-accelerator-cerner-us-core-medications-sys-api/[Implementation Template] +* Cerner Administration System API | https://anypoint.mulesoft.com/exchange/org.mule.examples/hc-accelerator-cerner-us-core-administration-sys-api/[Implementation Template] +* Cerner Clinical System API | https://anypoint.mulesoft.com/exchange/org.mule.examples/hc-accelerator-cerner-us-core-clinical-sys-api/[Implementation Template] +* Cerner Medications System API | https://anypoint.mulesoft.com/exchange/org.mule.examples/hc-accelerator-cerner-us-core-medications-sys-api/[Implementation Template] == v2.9 @@ -182,30 +182,30 @@ The following assets are modified to support updated API specifications for exis This release provides API specifications and implementation templates for the Appointment Scheduling use case described https://www.hl7.org/fhir/workflow-module.html[here]: -* Appointment Scheduling Process API | https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fhir-r4-appointment-scheduling-api/[API Specification] | https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/hc-accelerator-appointment-scheduling-prc-api/[Implementation Template] -* Cerner Workflow System API | https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/cerner-fhir-r4-workflow-api/[API Specification] | https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/hc-accelerator-cerner-workflow-sys-api/[Implementation Template] -* Epic Workflow System API | https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/epic-fhir-r4-workflow-api/[API Specification] | https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/hc-accelerator-epic-workflow-sys-api/[Implementation Template] +* Appointment Scheduling Process API | https://anypoint.mulesoft.com/exchange/org.mule.examples/fhir-r4-appointment-scheduling-api/[API Specification] | https://anypoint.mulesoft.com/exchange/org.mule.examples/hc-accelerator-appointment-scheduling-prc-api/[Implementation Template] +* Cerner Workflow System API | https://anypoint.mulesoft.com/exchange/org.mule.examples/cerner-fhir-r4-workflow-api/[API Specification] | https://anypoint.mulesoft.com/exchange/org.mule.examples/hc-accelerator-cerner-workflow-sys-api/[Implementation Template] +* Epic Workflow System API | https://anypoint.mulesoft.com/exchange/org.mule.examples/epic-fhir-r4-workflow-api/[API Specification] | https://anypoint.mulesoft.com/exchange/org.mule.examples/hc-accelerator-epic-workflow-sys-api/[Implementation Template] It also includes the following Cerner assets for Patient 360: -* Cerner Administration System API | https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/cerner-fhir-r4-administration-api/[API Specification] | https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/hc-accelerator-cerner-us-core-administration-sys-api/[Implementation Template] -* Cerner Clinical System API | https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/cerner-fhir-r4-clinical-api/[API Specification] | https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/hc-accelerator-cerner-us-core-clinical-sys-api/[Implementation Template] -* Cerner Diagnostics System API | https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/cerner-fhir-r4-diagnostics-api/[API Specification] | https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/hc-accelerator-cerner-us-core-diagnostics-sys-api/[Implementation Template] -* Cerner Medications System API | https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/cerner-fhir-r4-medications-api/[API Specification] | https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/hc-accelerator-cerner-us-core-medications-sys-api/[Implementation Template] +* Cerner Administration System API | https://anypoint.mulesoft.com/exchange/org.mule.examples/cerner-fhir-r4-administration-api/[API Specification] | https://anypoint.mulesoft.com/exchange/org.mule.examples/hc-accelerator-cerner-us-core-administration-sys-api/[Implementation Template] +* Cerner Clinical System API | https://anypoint.mulesoft.com/exchange/org.mule.examples/cerner-fhir-r4-clinical-api/[API Specification] | https://anypoint.mulesoft.com/exchange/org.mule.examples/hc-accelerator-cerner-us-core-clinical-sys-api/[Implementation Template] +* Cerner Diagnostics System API | https://anypoint.mulesoft.com/exchange/org.mule.examples/cerner-fhir-r4-diagnostics-api/[API Specification] | https://anypoint.mulesoft.com/exchange/org.mule.examples/hc-accelerator-cerner-us-core-diagnostics-sys-api/[Implementation Template] +* Cerner Medications System API | https://anypoint.mulesoft.com/exchange/org.mule.examples/cerner-fhir-r4-medications-api/[API Specification] | https://anypoint.mulesoft.com/exchange/org.mule.examples/hc-accelerator-cerner-us-core-medications-sys-api/[Implementation Template] The following assets were also enhanced and improved for this release: -* Epic Administration System API | https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/epic-fhir-r4-administration-api/[API Specification] | https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/hc-accelerator-epic-us-core-administration-sys-api/[Implementation Template] -* Epic Clinical System API | https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/epic-fhir-r4-clinical-api/[API Specification] | https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/hc-accelerator-epic-us-core-clinical-sys-api/[Implementation Template] -* Epic Diagnostics System API | https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/epic-fhir-r4-diagnostics-api[API Specification] | https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/hc-accelerator-epic-us-core-diagnostics-sys-api/[Implementation Template] -* Epic Medications System API | https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/epic-fhir-r4-medications-api/[API Specification] | https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/hc-accelerator-epic-us-core-medications-sys-api/[Implementation Template] -* FHIR R4 Administration API | https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fhir-r4-administration-api/[API Specification] -* FHIR R4 Clinical API | https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fhir-r4-clinical-api/[API Specification] -* FHIR R4 Diagnostics API | https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fhir-r4-diagnostics-api/[API Specification] -* FHIR R4 Medications API | https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fhir-r4-medications-api/[API Specification] -* FHIR R4 Workflow API | https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fhir-r4-workflow-api/[API Specification] -* https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/hc-accelerator-sfdc-adt-api/[HL7 V2 ADT Process API] -* https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/hc-accelerator-sfdc-oru-api/[HL7 V2 ORU Process API] +* Epic Administration System API | https://anypoint.mulesoft.com/exchange/org.mule.examples/epic-fhir-r4-administration-api/[API Specification] | https://anypoint.mulesoft.com/exchange/org.mule.examples/hc-accelerator-epic-us-core-administration-sys-api/[Implementation Template] +* Epic Clinical System API | https://anypoint.mulesoft.com/exchange/org.mule.examples/epic-fhir-r4-clinical-api/[API Specification] | https://anypoint.mulesoft.com/exchange/org.mule.examples/hc-accelerator-epic-us-core-clinical-sys-api/[Implementation Template] +* Epic Diagnostics System API | https://anypoint.mulesoft.com/exchange/org.mule.examples/epic-fhir-r4-diagnostics-api[API Specification] | https://anypoint.mulesoft.com/exchange/org.mule.examples/hc-accelerator-epic-us-core-diagnostics-sys-api/[Implementation Template] +* Epic Medications System API | https://anypoint.mulesoft.com/exchange/org.mule.examples/epic-fhir-r4-medications-api/[API Specification] | https://anypoint.mulesoft.com/exchange/org.mule.examples/hc-accelerator-epic-us-core-medications-sys-api/[Implementation Template] +* FHIR R4 Administration API | https://anypoint.mulesoft.com/exchange/org.mule.examples/fhir-r4-administration-api/[API Specification] +* FHIR R4 Clinical API | https://anypoint.mulesoft.com/exchange/org.mule.examples/fhir-r4-clinical-api/[API Specification] +* FHIR R4 Diagnostics API | https://anypoint.mulesoft.com/exchange/org.mule.examples/fhir-r4-diagnostics-api/[API Specification] +* FHIR R4 Medications API | https://anypoint.mulesoft.com/exchange/org.mule.examples/fhir-r4-medications-api/[API Specification] +* FHIR R4 Workflow API | https://anypoint.mulesoft.com/exchange/org.mule.examples/fhir-r4-workflow-api/[API Specification] +* https://anypoint.mulesoft.com/exchange/org.mule.examples/hc-accelerator-sfdc-adt-api/[HL7 V2 ADT Process API] +* https://anypoint.mulesoft.com/exchange/org.mule.examples/hc-accelerator-sfdc-oru-api/[HL7 V2 ORU Process API] == v2.8 @@ -214,24 +214,24 @@ The following assets were also enhanced and improved for this release: This release includes: * Implementation templates added for the following Health Cloud and Epic APIs for Patient 360: - ** https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/hc-accelerator-epic-us-core-clinical-sys-api/[Epic Clinical System API] - ** https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/hc-accelerator-epic-us-core-diagnostics-sys-api/[Epic Diagnostics System API] - ** https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/hc-accelerator-epic-us-core-medications-sys-api/[Epic Medications System API] - ** https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/hc-accelerator-sfdc-us-core-clinical-sys-api/[Health Cloud Clinical System API] - ** https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/hc-accelerator-sfdc-us-core-diagnostics-sys-api/[Health Cloud Diagnostics System API] - ** https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/hc-accelerator-sfdc-us-core-medications-sys-api/[Health Cloud Medications System API] + ** https://anypoint.mulesoft.com/exchange/org.mule.examples/hc-accelerator-epic-us-core-clinical-sys-api/[Epic Clinical System API] + ** https://anypoint.mulesoft.com/exchange/org.mule.examples/hc-accelerator-epic-us-core-diagnostics-sys-api/[Epic Diagnostics System API] + ** https://anypoint.mulesoft.com/exchange/org.mule.examples/hc-accelerator-epic-us-core-medications-sys-api/[Epic Medications System API] + ** https://anypoint.mulesoft.com/exchange/org.mule.examples/hc-accelerator-sfdc-us-core-clinical-sys-api/[Health Cloud Clinical System API] + ** https://anypoint.mulesoft.com/exchange/org.mule.examples/hc-accelerator-sfdc-us-core-diagnostics-sys-api/[Health Cloud Diagnostics System API] + ** https://anypoint.mulesoft.com/exchange/org.mule.examples/hc-accelerator-sfdc-us-core-medications-sys-api/[Health Cloud Medications System API] * Enhancements and improvements made to the following templates: - ** https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/hc-accelerator-epic-us-core-administration-sys-api/[Epic Administration System API] - ** https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/hc-accelerator-sfdc-us-core-administration-sys-api/[Health Cloud Administration System API] + ** https://anypoint.mulesoft.com/exchange/org.mule.examples/hc-accelerator-epic-us-core-administration-sys-api/[Epic Administration System API] + ** https://anypoint.mulesoft.com/exchange/org.mule.examples/hc-accelerator-sfdc-us-core-administration-sys-api/[Health Cloud Administration System API] * Updated the following templates to support the Spring 2021 release of the Health Cloud data model: - ** https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/hc-accelerator-sfdc-adt-api/[HL7 V2 ADT Process API] - ** https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/hc-accelerator-sfdc-oru-api/[HL7 V2 ORU Process API] + ** https://anypoint.mulesoft.com/exchange/org.mule.examples/hc-accelerator-sfdc-adt-api/[HL7 V2 ADT Process API] + ** https://anypoint.mulesoft.com/exchange/org.mule.examples/hc-accelerator-sfdc-oru-api/[HL7 V2 ORU Process API] * Additional updates and improvements: - ** https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/hc-accelerator-hl7v2-to-fhir-sys-api/[HL7 V2 to FHIR System API] - ** https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fhir-r4-capabilitystatement-api/[FHIR R4 Capability Statement API] + ** https://anypoint.mulesoft.com/exchange/org.mule.examples/hc-accelerator-hl7v2-to-fhir-sys-api/[HL7 V2 to FHIR System API] + ** https://anypoint.mulesoft.com/exchange/org.mule.examples/fhir-r4-capabilitystatement-api/[FHIR R4 Capability Statement API] == v2.7 @@ -240,9 +240,9 @@ This release includes: This release includes: * Implementation templates for the Administration API for Patient 360: - * https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/hc-accelerator-sfdc-us-core-administration-sys-api/[Health Cloud Administration System API] - Supports the Spring 2021 release of the Health Cloud data model. - * https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/hc-accelerator-epic-us-core-administration-sys-api/[EPIC Administration System API] - Supports the Patient resource currently. Additional resources will be supported in the next release. -* Reference implementation for https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/hc-accelerator-okta-smartfhir/[SMART on FHIR with Okta]. + * https://anypoint.mulesoft.com/exchange/org.mule.examples/hc-accelerator-sfdc-us-core-administration-sys-api/[Health Cloud Administration System API] - Supports the Spring 2021 release of the Health Cloud data model. + * https://anypoint.mulesoft.com/exchange/org.mule.examples/hc-accelerator-epic-us-core-administration-sys-api/[EPIC Administration System API] - Supports the Patient resource currently. Additional resources will be supported in the next release. +* Reference implementation for https://anypoint.mulesoft.com/exchange/org.mule.examples/hc-accelerator-okta-smartfhir/[SMART on FHIR with Okta]. == v2.6 @@ -251,7 +251,7 @@ This release includes: This release includes: * API specifications for Patient 360 to support the Spring 2021 release of the Health Cloud data model. -* Added support for the ORU message type in the https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/hc-accelerator-hl7v2-to-fhir-sys-api/[HL7 v2 to FHIR converter]. +* Added support for the ORU message type in the https://anypoint.mulesoft.com/exchange/org.mule.examples/hc-accelerator-hl7v2-to-fhir-sys-api/[HL7 v2 to FHIR converter]. == v2.5 @@ -259,7 +259,7 @@ This release includes: This release provides Healthcare organizations with a reference implementation to convert HL7 v2 messages to FHIR to integrate with different systems using the https://build.fhir.org/ig/HL7/v2-to-fhir/mapping_guidelines.html[guidelines] provided by the https://build.fhir.org/ig/HL7/v2-to-fhir/[HL7 v2 to FHIR Implementation Guide]. -* https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fhir-r4-convert-api/[API specification] and https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/hc-accelerator-hl7v2-to-fhir-sys-api/[implementation template] for HL7 v2 to FHIR System API +* https://anypoint.mulesoft.com/exchange/org.mule.examples/fhir-r4-convert-api/[API specification] and https://anypoint.mulesoft.com/exchange/org.mule.examples/hc-accelerator-hl7v2-to-fhir-sys-api/[implementation template] for HL7 v2 to FHIR System API == v2.4 @@ -267,8 +267,8 @@ This release provides Healthcare organizations with a reference implementation t The focus of release 2.4 is on providing the API specifications and implementation templates for https://www.cms.gov/Regulations-and-Guidance/Guidance/Interoperability/index[CMS Interoperability and Patient Access final rule]. The release contains the following assets: -* https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fhir-r4-patient-access-clinical-exp-api/[API specification] and https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/hc-accelerator-sfdc-us-core-patientaccessclinicaldata-exp-api/[implementation template] for Patient Access API - Clinical Data as per the https://www.hl7.org/fhir/us/core/[US Core Implementation Guide]. -* https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fhir-r4-patient-access-claims-encounter-exp-api/[API specification] and https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/hc-accelerator-carin-patientclaimsencounterdata-exp-api/[implementation template] for Patient Access API - Claims and Encounter Data as per the https://build.fhir.org/ig/HL7/carin-bb/index.html[CARIN Implementation Guide for Blue Button]. +* https://anypoint.mulesoft.com/exchange/org.mule.examples/fhir-r4-patient-access-clinical-exp-api/[API specification] and https://anypoint.mulesoft.com/exchange/org.mule.examples/hc-accelerator-sfdc-us-core-patientaccessclinicaldata-exp-api/[implementation template] for Patient Access API - Clinical Data as per the https://www.hl7.org/fhir/us/core/[US Core Implementation Guide]. +* https://anypoint.mulesoft.com/exchange/org.mule.examples/fhir-r4-patient-access-claims-encounter-exp-api/[API specification] and https://anypoint.mulesoft.com/exchange/org.mule.examples/hc-accelerator-carin-patientclaimsencounterdata-exp-api/[implementation template] for Patient Access API - Claims and Encounter Data as per the https://build.fhir.org/ig/HL7/carin-bb/index.html[CARIN Implementation Guide for Blue Button]. * Minor bug fixes. == v2.3 @@ -277,8 +277,8 @@ The focus of release 2.4 is on providing the API specifications and implementati The focus of release 2.3 is on providing the API specifications and implementation templates for https://www.cms.gov/Regulations-and-Guidance/Guidance/Interoperability/index[CMS Interoperability and Patient Access final rule]. The release contains the following assets: -* https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fhir-r4-pdex-formulary-api/[API specification] and https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/hc-accelerator-pdex-formulary-exp-api/[implementation template] for Formulary API as per the http://build.fhir.org/ig/HL7/davinci-pdex-formulary/index.html[DaVinci PDEX US Drug Formulary Implementation Guide]. -* https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fhir-r4-plannet-providerdirectory-api/[API specification] and https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/hc-accelerator-plannet-providerdirectory-exp-api/[implementation template] for Provider Directory API as per the https://build.fhir.org/ig/HL7/davinci-pdex-plan-net/index.html[DaVinci PDEX Plan Net Implementation Guide]. +* https://anypoint.mulesoft.com/exchange/org.mule.examples/fhir-r4-pdex-formulary-api/[API specification] and https://anypoint.mulesoft.com/exchange/org.mule.examples/hc-accelerator-pdex-formulary-exp-api/[implementation template] for Formulary API as per the http://build.fhir.org/ig/HL7/davinci-pdex-formulary/index.html[DaVinci PDEX US Drug Formulary Implementation Guide]. +* https://anypoint.mulesoft.com/exchange/org.mule.examples/fhir-r4-plannet-providerdirectory-api/[API specification] and https://anypoint.mulesoft.com/exchange/org.mule.examples/hc-accelerator-plannet-providerdirectory-exp-api/[implementation template] for Provider Directory API as per the https://build.fhir.org/ig/HL7/davinci-pdex-plan-net/index.html[DaVinci PDEX Plan Net Implementation Guide]. * Minor bug fixes. == v2.2 @@ -287,8 +287,8 @@ The focus of release 2.3 is on providing the API specifications and implementati The focus of release 2.2 is on providing the implementation template for Electronic Laboratory Reporting to CalREDIE. The release contains the following assets: -* Implementation template for https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/hc-accelerator-lblims-calredie-process-bapi/[Electronic Laboratory Reporting], which is the notifiable condition to CalREDIE. -* API policy to return https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fhir-error-policy/[FHIR compliant OperationOutcome response]. +* Implementation template for https://anypoint.mulesoft.com/exchange/org.mule.examples/hc-accelerator-lblims-calredie-process-bapi/[Electronic Laboratory Reporting], which is the notifiable condition to CalREDIE. +* API policy to return https://anypoint.mulesoft.com/exchange/org.mule.examples/fhir-error-policy/[FHIR compliant OperationOutcome response]. * Minor bug fixes. == v2.1.1 diff --git a/healthcare/2.20/modules/ROOT/pages/sfdc-data-cloud-setup-guide.adoc b/healthcare/2.20/modules/ROOT/pages/sfdc-data-cloud-setup-guide.adoc index 84494a74b..0eb1a7e3e 100644 --- a/healthcare/2.20/modules/ROOT/pages/sfdc-data-cloud-setup-guide.adoc +++ b/healthcare/2.20/modules/ROOT/pages/sfdc-data-cloud-setup-guide.adoc @@ -1,7 +1,7 @@ = Salesforce Data Cloud Setup Guide :hls-version: 2.20 -The following provides guidance on Salesforce Data Cloud setup required for the https://www.anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/mulesoft-accelerator-for-healthcare/minor/{hls-version}/pages/Use%20case%207%20-%20Population%20health%20management/[Population Health Management] use case. +The following provides guidance on Salesforce Data Cloud setup required for the https://www.anypoint.mulesoft.com/exchange/org.mule.examples/mulesoft-accelerator-for-healthcare/minor/{hls-version}/pages/Use%20case%207%20-%20Population%20health%20management/[Population Health Management] use case. * <> * <> @@ -25,7 +25,7 @@ Connectors are specialized data streams that communicate with external sources t Customer Data Platform has connectors for: Marketing Cloud Email Studio, MobileConnect, MobilePush, Marketing Cloud Data Extensions, for Salesforce CRM, Ingestion API, Interaction Studio, and for data outside Salesforce via cloud storage providers. -The https://www.anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/mulesoft-accelerator-for-healthcare/minor/{hls-version}/pages/Use%20case%207%20-%20Population%20health%20management/[Population Health Management] use case uses the following connectors to ingest data into cdp: +The https://www.anypoint.mulesoft.com/exchange/org.mule.examples/mulesoft-accelerator-for-healthcare/minor/{hls-version}/pages/Use%20case%207%20-%20Population%20health%20management/[Population Health Management] use case uses the following connectors to ingest data into cdp: * Salesforce CRM - to connect data from a Salesforce Health Cloud instance to Data Cloud * Ingestion API - to connect data from external source systems like Azure, Epic, Cerner, and other EHR systems via MuleSoft's CDP connector. @@ -50,7 +50,7 @@ Follow the below steps to create connection to your Salesforce Health Cloud org. After you create your Customer Data Platform instance and set up your Salesforce Health Cloud connection, you can install standard data bundles that are powered by data kits to deploy data within Customer Data Platform. -For the https://www.anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/mulesoft-accelerator-for-healthcare/minor/{hls-version}/pages/Use%20case%207%20-%20Population%20health%20management/[Population Health Management] use case, Service Cloud bundle is installed. Refer https://help.salesforce.com/s/articleView?id=sf.c360_a_install_standard_data_bundles_powered_by_data_kits.htm&type=5[link] to install the bundle. +For the https://www.anypoint.mulesoft.com/exchange/org.mule.examples/mulesoft-accelerator-for-healthcare/minor/{hls-version}/pages/Use%20case%207%20-%20Population%20health%20management/[Population Health Management] use case, Service Cloud bundle is installed. Refer https://help.salesforce.com/s/articleView?id=sf.c360_a_install_standard_data_bundles_powered_by_data_kits.htm&type=5[link] to install the bundle. === Ingestion API @@ -63,14 +63,14 @@ Follow the steps in each section below to setup and configure ingestion API to p . In Data Cloud, select Data Cloud Setup. . Click Ingestion API. . Click New, enter a name for the API source, then click Save. On the details page for the new connector, you must upload a schema file in OpenAPI (OAS) format with a `.yaml` file extension. The schema file describes how data transferred via the API is structured. *Note:* Ingestion API schemas have set requirements - review the schema requirements before ingestion. -. Click Upload Schema and navigate to the location of the file you want to use. Select the file and click Open. For the https://www.anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/mulesoft-accelerator-for-healthcare/minor/{hls-version}/pages/Use%20case%207%20-%20Population%20health%20management/[Population Health Management] use case the schema file `mule-hls-cdp-connector-schema.yaml` is available under `/src/test/resources` of the Implementation Template https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/hls-salesforce-cdp-sys-api[HLS CDP System API]. +. Click Upload Schema and navigate to the location of the file you want to use. Select the file and click Open. For the https://www.anypoint.mulesoft.com/exchange/org.mule.examples/mulesoft-accelerator-for-healthcare/minor/{hls-version}/pages/Use%20case%207%20-%20Population%20health%20management/[Population Health Management] use case the schema file `mule-hls-cdp-connector-schema.yaml` is available under `/src/test/resources` of the Implementation Template https://anypoint.mulesoft.com/exchange/org.mule.examples/hls-salesforce-cdp-sys-api[HLS CDP System API]. . Preview all the detected objects and their attributes in your schema. . Click Save. The connector page reflects the updated status. . After the schema file is uploaded, you can create data streams to begin sending data from your source system. -For the https://www.anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/mulesoft-accelerator-for-healthcare/minor/{hls-version}/pages/Use%20case%207%20-%20Population%20health%20management/[Population Health Management] use case, the external systems Azure, Epic, Cerner, and other EHR systems contain data to be pushed to Data Cloud through MuleSoft's CDP connector using the Ingestion API. The name of the Connector used will appear under `Ingestion API` drop down while creating a new Data Stream. +For the https://www.anypoint.mulesoft.com/exchange/org.mule.examples/mulesoft-accelerator-for-healthcare/minor/{hls-version}/pages/Use%20case%207%20-%20Population%20health%20management/[Population Health Management] use case, the external systems Azure, Epic, Cerner, and other EHR systems contain data to be pushed to Data Cloud through MuleSoft's CDP connector using the Ingestion API. The name of the Connector used will appear under `Ingestion API` drop down while creating a new Data Stream. -The schema used for the https://www.anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/mulesoft-accelerator-for-healthcare/minor/{hls-version}/pages/Use%20case%207%20-%20Population%20health%20management/[Population Health Management] use case can be found in the implementation template. The following objects are added for this use case: +The schema used for the https://www.anypoint.mulesoft.com/exchange/org.mule.examples/mulesoft-accelerator-for-healthcare/minor/{hls-version}/pages/Use%20case%207%20-%20Population%20health%20management/[Population Health Management] use case can be found in the implementation template. The following objects are added for this use case: * condition * immunization @@ -116,7 +116,7 @@ To create data streams from Salesforce CRM starter bundle: Refer this https://help.salesforce.com/s/articleView?id=sf.c360_a_create_crm_starter_bundle.htm&type=5[link] to create data streams using starter bundle to begin the flow of data from a Salesforce Health Cloud data source. -For the https://www.anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/mulesoft-accelerator-for-healthcare/minor/{hls-version}/pages/Use%20case%207%20-%20Population%20health%20management/[Population Health Management] use case, data streams for Salesforce Health Cloud Account and Contact objects are created using Salesforce CRM Service bundle. +For the https://www.anypoint.mulesoft.com/exchange/org.mule.examples/mulesoft-accelerator-for-healthcare/minor/{hls-version}/pages/Use%20case%207%20-%20Population%20health%20management/[Population Health Management] use case, data streams for Salesforce Health Cloud Account and Contact objects are created using Salesforce CRM Service bundle. To create data streams from Salesforce Health Cloud data source: @@ -134,11 +134,11 @@ To add permissions for objects and their fields: Repeat these steps for all objects and fields you want to ingest into Data Cloud. Now, create data streams for the required objects by following the steps in this https://help.salesforce.com/s/articleView?id=sf.c360_a_create_crm_data_stream.htm&type=5&language=en_US[link]. -For the https://www.anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/mulesoft-accelerator-for-healthcare/minor/{hls-version}/pages/Use%20case%207%20-%20Population%20health%20management/[Population Health Management] use case, data streams for Contact Point Objects, Identifier, and ContactContactRelation are created. +For the https://www.anypoint.mulesoft.com/exchange/org.mule.examples/mulesoft-accelerator-for-healthcare/minor/{hls-version}/pages/Use%20case%207%20-%20Population%20health%20management/[Population Health Management] use case, data streams for Contact Point Objects, Identifier, and ContactContactRelation are created. === Create an Ingestion API data stream -After uploading the schema file for Ingestion API Connector, create a data stream from your source objects. For the https://www.anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/mulesoft-accelerator-for-healthcare/minor/{hls-version}/pages/Use%20case%207%20-%20Population%20health%20management/[Population Health Management] use case, data streams for condition, immunization and webEngagement are created. +After uploading the schema file for Ingestion API Connector, create a data stream from your source objects. For the https://www.anypoint.mulesoft.com/exchange/org.mule.examples/mulesoft-accelerator-for-healthcare/minor/{hls-version}/pages/Use%20case%207%20-%20Population%20health%20management/[Population Health Management] use case, data streams for condition, immunization and webEngagement are created. . In Data Cloud, select Data Streams. . In recently viewed data streams, click New. @@ -147,7 +147,7 @@ After uploading the schema file for Ingestion API Connector, create a data strea . Check the objects found in the schema you want to use and click Next. . At the New Data Stream dialog box, configure the following: ** Primary Key: A true Primary Key needs to be leveraged for Data Cloud. If one does not exist, you will need to create a Formula Field for the Primary Key. - ** Category: Choose between Profile, Engagement or Other. *Note:* For the https://www.anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/mulesoft-accelerator-for-healthcare/minor/{hls-version}/pages/Use%20case%207%20-%20Population%20health%20management/[Population Health Management] use case, the category for all the objects in the schema are Other. + ** Category: Choose between Profile, Engagement or Other. *Note:* For the https://www.anypoint.mulesoft.com/exchange/org.mule.examples/mulesoft-accelerator-for-healthcare/minor/{hls-version}/pages/Use%20case%207%20-%20Population%20health%20management/[Population Health Management] use case, the category for all the objects in the schema are Other. ** Record Modified Date: To order Profile modifications, use the Record Modified Date. *Note:* A record modified field that indicates when each incoming record was last modified is required for Engagement object types. While the field requirement is optional for Profile and Other objects, it is encouraged to provide the record modified field to ensure incoming records are processed in the right order. ** Date Time Field: Used to represent when Engagement from an external source occurred at ingestion. ** Click the `New Formula Field` (Optional). @@ -156,7 +156,7 @@ After uploading the schema file for Ingestion API Connector, create a data strea . Click Deploy. If you have only created one data stream, the data stream's record page appears. If you've created multiple data streams, the view refreshes to show all recently viewed data streams. . Wait up to one hour for your data to appear in your data stream. Map your data stream to data model objects to start using your data. -For the https://www.anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/mulesoft-accelerator-for-healthcare/minor/{hls-version}/pages/Use%20case%207%20-%20Population%20health%20management/[Population Health Management] use case, data stream is created for the objects added in schema by following the steps above. At step 6, click `New Formula field` with `Field Label` as `uniqueId` with `Formula Return` Type as `Text`. Under `Transformation Formula`, the formula is created as below for each of the object. +For the https://www.anypoint.mulesoft.com/exchange/org.mule.examples/mulesoft-accelerator-for-healthcare/minor/{hls-version}/pages/Use%20case%207%20-%20Population%20health%20management/[Population Health Management] use case, data stream is created for the objects added in schema by following the steps above. At step 6, click `New Formula field` with `Field Label` as `uniqueId` with `Formula Return` Type as `Text`. Under `Transformation Formula`, the formula is created as below for each of the object. * condition: `CONCAT(sourceField['patientMrn'],"~",sourceField['conditionCode'])` * immunization: `CONCAT(sourceField['patientMrn'],"~",sourceField['vaccineCode'],"~",sourceField['vaccineStatus'],"~",sourceField['vaccineDate'])` @@ -178,9 +178,9 @@ As part of your Connected App set up for Ingestion API, you must select the foll The MuleSoft Connector for CDP provides customers a pipeline to send data into Data Cloud. This connector works with the Data Cloud Bulk and Streaming API, depending on the operation you configure. Each API call uses a request/response pattern over an HTTPS connection. All required request headers, error handling, and HTTPS connection configurations are built into the connector. -Refer to the https://dev-docs-internal.kqa.msap.io/beta-accelerators/salesforce-cdp-connector/1.1/[CDP Connector documentation] for additional details on configuration and available operations. +Refer to the https://docs.mulesoft.com/salesforce-cdp-connector/1.1/[CDP Connector documentation] for additional details on configuration and available operations. -For the https://www.anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/mulesoft-accelerator-for-healthcare/minor/{hls-version}/pages/Use%20case%207%20-%20Population%20health%20management/[Population Health Management] use case, refer to the https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/hls-salesforce-cdp-sys-api-spec/[HLS CDP System API] specification and https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/hls-salesforce-cdp-sys-api[HLS CDP System API] implementation template assets. +For the https://www.anypoint.mulesoft.com/exchange/org.mule.examples/mulesoft-accelerator-for-healthcare/minor/{hls-version}/pages/Use%20case%207%20-%20Population%20health%20management/[Population Health Management] use case, refer to the https://anypoint.mulesoft.com/exchange/org.mule.examples/hls-salesforce-cdp-sys-api-spec/[HLS CDP System API] specification and https://anypoint.mulesoft.com/exchange/org.mule.examples/hls-salesforce-cdp-sys-api[HLS CDP System API] implementation template assets. == Data modeling and data mapping @@ -220,7 +220,7 @@ Objects in the data model created by the customer for Data Cloud implementation When mapping your party area data, complete the required fields and relationships to successfully use Identity Resolution, Segmentation, and Activation. -Default mapping exists for Account and Contact Objects if service Bundle is used to create data streams. For the https://www.anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/mulesoft-accelerator-for-healthcare/minor/{hls-version}/pages/Use%20case%207%20-%20Population%20health%20management/[Population Health Management] use case, the default mapping from Account and Contact DSOs to Contact Point DMOs are removed. Data Streams to Data Model Objects (DMO) are mapped as per the below table. +Default mapping exists for Account and Contact Objects if service Bundle is used to create data streams. For the https://www.anypoint.mulesoft.com/exchange/org.mule.examples/mulesoft-accelerator-for-healthcare/minor/{hls-version}/pages/Use%20case%207%20-%20Population%20health%20management/[Population Health Management] use case, the default mapping from Account and Contact DSOs to Contact Point DMOs are removed. Data Streams to Data Model Objects (DMO) are mapped as per the below table. |=== | Data Stream Name (DSO) | Custom Data Model Object (DMO) | Standard Data Model Object (DMO) @@ -250,7 +250,7 @@ Default mapping exists for Account and Contact Objects if service Bundle is used | |=== -For the https://www.anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/mulesoft-accelerator-for-healthcare/minor/{hls-version}/pages/Use%20case%207%20-%20Population%20health%20management/[Population Health Management] use case, below Data Mappings are created between Data Streams and DMOs/custom DMOs. +For the https://www.anypoint.mulesoft.com/exchange/org.mule.examples/mulesoft-accelerator-for-healthcare/minor/{hls-version}/pages/Use%20case%207%20-%20Population%20health%20management/[Population Health Management] use case, below Data Mappings are created between Data Streams and DMOs/custom DMOs. *Data Mappings of Account Data Stream to Account DMO* @@ -490,7 +490,7 @@ Some of the mappings are added by default from Bundle. Mapping needs to be chang | userId |=== -For the https://www.anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/mulesoft-accelerator-for-healthcare/minor/{hls-version}/pages/Use%20case%207%20-%20Population%20health%20management/[Population Health Management] use case, below DMOs and relationships needs to be maintained when Data mappings are done between Data Stream and DMOs. +For the https://www.anypoint.mulesoft.com/exchange/org.mule.examples/mulesoft-accelerator-for-healthcare/minor/{hls-version}/pages/Use%20case%207%20-%20Population%20health%20management/[Population Health Management] use case, below DMOs and relationships needs to be maintained when Data mappings are done between Data Stream and DMOs. *Data Relationships between DMOs* @@ -542,7 +542,7 @@ For the https://www.anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10 == Identity Resolution -NOTE: For the https://www.anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/mulesoft-accelerator-for-healthcare/minor/{hls-version}/pages/Use%20case%207%20-%20Population%20health%20management/[Population Health Management] use case, identity resolution rulesets were not required. +NOTE: For the https://www.anypoint.mulesoft.com/exchange/org.mule.examples/mulesoft-accelerator-for-healthcare/minor/{hls-version}/pages/Use%20case%207%20-%20Population%20health%20management/[Population Health Management] use case, identity resolution rulesets were not required. Use identity resolution to consolidate data from difference sources into a comprehensive view of your customer called a unified profile. Identity resolution uses matching and reconciliation rules to link data about people into unified profiles. Each unified profile contains all the unique contact point values from all sources. @@ -550,7 +550,7 @@ Set up identity resolution rulesets after mapping source data to data model obje == Calculated Insights -NOTE: For the https://www.anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/mulesoft-accelerator-for-healthcare/minor/{hls-version}/pages/Use%20case%207%20-%20Population%20health%20management/[Population Health Management] use case, Calculated Insights were not required. +NOTE: For the https://www.anypoint.mulesoft.com/exchange/org.mule.examples/mulesoft-accelerator-for-healthcare/minor/{hls-version}/pages/Use%20case%207%20-%20Population%20health%20management/[Population Health Management] use case, Calculated Insights were not required. The Calculated Insights feature lets you define and calculate multidimensional metrics on your entire digital state stored in Salesforce Customer Data Platform. @@ -577,7 +577,7 @@ TIP: Leave the Publish Schedule as *Don't Refresh for now*, and then fill it in Segment On: Segment On defines the target entity (object) used to build your segment. For example, you can build a segment on Unified Individual or Account or Individual. You can choose any entity marked as type Profile during ingestion. -For the https://www.anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/mulesoft-accelerator-for-healthcare/minor/{hls-version}/pages/Use%20case%207%20-%20Population%20health%20management/[Population Health Management] use case, create Segments on Individual. +For the https://www.anypoint.mulesoft.com/exchange/org.mule.examples/mulesoft-accelerator-for-healthcare/minor/{hls-version}/pages/Use%20case%207%20-%20Population%20health%20management/[Population Health Management] use case, create Segments on Individual. Example segment: @@ -615,7 +615,7 @@ For the Publish Schedule, we update it to reflect a Publish Schedule of every 12 Create activation targets to build, and activate data segments with Data Cloud. -For the https://www.anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/mulesoft-accelerator-for-healthcare/minor/{hls-version}/pages/Use%20case%207%20-%20Population%20health%20management/[Population Health Management] use case, create a Marketing Cloud Activation Target. +For the https://www.anypoint.mulesoft.com/exchange/org.mule.examples/mulesoft-accelerator-for-healthcare/minor/{hls-version}/pages/Use%20case%207%20-%20Population%20health%20management/[Population Health Management] use case, create a Marketing Cloud Activation Target. *Activation Target - Marketing Cloud:* @@ -624,8 +624,8 @@ Before creating an activation target, configure the Marketing Cloud connector in . Click Setup gear icon and then Data Cloud Setup. . Select Marketing Cloud. . Enter the Credentials to authenticate your Marketing Cloud account. You can proceed with the next step in the setup only if the authentication is successful. -. Data Source setup - this step is optional. This needs to be set up if you are planning to ingest data from Marketing Cloud into Data Cloud. *Note:* For the https://www.anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/mulesoft-accelerator-for-healthcare/minor/{hls-version}/pages/Use%20case%207%20-%20Population%20health%20management/[Population Health Management] use case, this step is skipped. -. Select Business Units to activate - this step is optional. To add or remove business units (BU), click the arrows between the two columns. *Note:* For the https://www.anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/mulesoft-accelerator-for-healthcare/minor/{hls-version}/pages/Use%20case%207%20-%20Population%20health%20management/[Population Health Management] use case, select business units to publish segments to Marketing Cloud. +. Data Source setup - this step is optional. This needs to be set up if you are planning to ingest data from Marketing Cloud into Data Cloud. *Note:* For the https://www.anypoint.mulesoft.com/exchange/org.mule.examples/mulesoft-accelerator-for-healthcare/minor/{hls-version}/pages/Use%20case%207%20-%20Population%20health%20management/[Population Health Management] use case, this step is skipped. +. Select Business Units to activate - this step is optional. To add or remove business units (BU), click the arrows between the two columns. *Note:* For the https://www.anypoint.mulesoft.com/exchange/org.mule.examples/mulesoft-accelerator-for-healthcare/minor/{hls-version}/pages/Use%20case%207%20-%20Population%20health%20management/[Population Health Management] use case, select business units to publish segments to Marketing Cloud. Create an activation target in Data Cloud to publish segments to Marketing Cloud business units. diff --git a/healthcare/2.20/modules/ROOT/pages/sfdc-health-cloud-setup-guide.adoc b/healthcare/2.20/modules/ROOT/pages/sfdc-health-cloud-setup-guide.adoc index a4876f44d..b7bac4b99 100644 --- a/healthcare/2.20/modules/ROOT/pages/sfdc-health-cloud-setup-guide.adoc +++ b/healthcare/2.20/modules/ROOT/pages/sfdc-health-cloud-setup-guide.adoc @@ -41,13 +41,13 @@ This accelerator uses MuleSoft's HL7 Connector. If you're required to use custom * Modify the message structure schema file (for example, ADT_A31.esl) to include your custom segment (or modify an existing segment to fit your needs). * Modify the basedefs.esl file to include the changes for segment definitions. -The https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/hc-accelerator-sfdc-adt-api/[implementation template^] for storing ADT messages in Salesforce Health Cloud shows an example of custom segment processing. Please check the src/main/resources/config/hl7/v2_2 folder in the implementation template. This folder has the necessary changes required to process custom segment `ZG1`. +The https://anypoint.mulesoft.com/exchange/org.mule.examples/hc-accelerator-sfdc-adt-api/[implementation template^] for storing ADT messages in Salesforce Health Cloud shows an example of custom segment processing. Please check the src/main/resources/config/hl7/v2_2 folder in the implementation template. This folder has the necessary changes required to process custom segment `ZG1`. -For additional details on HL7 Connector, please refer to the https://dev-docs-internal.kqa.msap.io/beta-accelerators/connectors/hl7/hl7-connector[documentation^]. +For additional details on HL7 Connector, please refer to the https://docs.mulesoft.com/connectors/hl7/hl7-connector[documentation^]. == Maven POM Parent -In addition to some global settings and repository references, the Maven https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/accelerator-pom-parent-src/[POM parent^] config also defines the versions of all MuleSoft connectors and modules used by applications. Refer to the https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/accelerator-pom-parent-src/[Exchange documentation^] for information on how to make changes to the POM parent file. +In addition to some global settings and repository references, the Maven https://anypoint.mulesoft.com/exchange/org.mule.examples/accelerator-pom-parent-src/[POM parent^] config also defines the versions of all MuleSoft connectors and modules used by applications. Refer to the https://anypoint.mulesoft.com/exchange/org.mule.examples/accelerator-pom-parent-src/[Exchange documentation^] for information on how to make changes to the POM parent file. == See Also diff --git a/healthcare/2.20/modules/ROOT/pages/smart-fhir-okta.adoc b/healthcare/2.20/modules/ROOT/pages/smart-fhir-okta.adoc index 293f4ce13..809023dd4 100644 --- a/healthcare/2.20/modules/ROOT/pages/smart-fhir-okta.adoc +++ b/healthcare/2.20/modules/ROOT/pages/smart-fhir-okta.adoc @@ -1,6 +1,6 @@ = SMART on FHIR with Okta -See the https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/hc-accelerator-okta-smartfhir/[Okta SMART on FHIR - Implementation Template^] asset, which walks you through how to set up a reference SMART on FHIR implementation on Anypoint Platform using Okta as the identity provider. +See the https://anypoint.mulesoft.com/exchange/org.mule.examples/hc-accelerator-okta-smartfhir/[Okta SMART on FHIR - Implementation Template^] asset, which walks you through how to set up a reference SMART on FHIR implementation on Anypoint Platform using Okta as the identity provider. The **S**ubstitutable **M**edical **A**pplications and **R**eusable **T**echnology (SMART) is a web/mobile app, which is typically embedded in EHR but can also serve as a standalone smartphone app. SMART on FHIR provides a consistent approach to security and data requirements for health applications. It also provides a workflow to securely request access to data, receive the data, and use the data. @@ -20,13 +20,13 @@ SMART on FHIR addresses the following three key aspects: Anypoint platform supports SMART on FHIR in the following ways: * Identity and access management -** Provisioning third-party https://dev-docs-internal.kqa.msap.io/beta-accelerators/access-management/configure-client-management-openid-task[OIDC client provider^] like Okta for identity management -** Out-of-the-box https://dev-docs-internal.kqa.msap.io/beta-accelerators/api-manager/2.x/policy-openid-connect[OpenID Connect token enforcement policy^] +** Provisioning third-party https://docs.mulesoft.com/access-management/configure-client-management-openid-task[OIDC client provider^] like Okta for identity management +** Out-of-the-box https://docs.mulesoft.com/api-manager/2.x/policy-openid-connect[OpenID Connect token enforcement policy^] ** Leverage OAuth provider information in the `authentication` object for custom policy * Access to the data using FHIR based APIs ** MuleSoft Accelerator for Healthcare provides FHIR R4 specifications for all the FHIR resources -** Out-of-the-box https://dev-docs-internal.kqa.msap.io/beta-accelerators/api-manager/2.x/cors-policy[cross origin resource sharing (CORS) policy^] enables cross origin data exchange. +** Out-of-the-box https://docs.mulesoft.com/api-manager/2.x/cors-policy[cross origin resource sharing (CORS) policy^] enables cross origin data exchange. == See Also diff --git a/healthcare/2.20/modules/ROOT/pages/x12-fhir-converter.adoc b/healthcare/2.20/modules/ROOT/pages/x12-fhir-converter.adoc index 354475b59..69f9d3caa 100644 --- a/healthcare/2.20/modules/ROOT/pages/x12-fhir-converter.adoc +++ b/healthcare/2.20/modules/ROOT/pages/x12-fhir-converter.adoc @@ -1,10 +1,10 @@ = X12 to FHIR Converter -The https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/hls-fhir-to-x12-sys-api/[X12 to FHIR converter^] comes with a ready to use template for https://x12.org/[X12^] to FHIR conversion. This template can be extended or modified to meet specific conversion requirements. The converter converts FHIR R4 to X12 formats and its responses from X12 to FHIR R4. +The https://anypoint.mulesoft.com/exchange/org.mule.examples/hls-fhir-to-x12-sys-api/[X12 to FHIR converter^] comes with a ready to use template for https://x12.org/[X12^] to FHIR conversion. This template can be extended or modified to meet specific conversion requirements. The converter converts FHIR R4 to X12 formats and its responses from X12 to FHIR R4. == Functional Diagram -image:https://www.mulesoft.com/ext/solutions/draft/images/hls-x12-fhir-fx-diagram.svg[X12 to FHIR converter functional diagram,900,align="center"] +image:https://www.mulesoft.com/ext/solutions/images/hls-x12-fhir-fx-diagram.svg[X12 to FHIR converter functional diagram,900,align="center"] == Advantages diff --git a/healthcare/2.21/modules/ROOT/pages/ccda-fhir-converter.adoc b/healthcare/2.21/modules/ROOT/pages/ccda-fhir-converter.adoc index 11b76cb60..134619070 100644 --- a/healthcare/2.21/modules/ROOT/pages/ccda-fhir-converter.adoc +++ b/healthcare/2.21/modules/ROOT/pages/ccda-fhir-converter.adoc @@ -1,10 +1,10 @@ = C-CDA to FHIR Converter -The https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/hls-ccda-to-fhir-sys-api/[C-CDA to FHIR converter] comes with a ready to use template for https://www.hl7.org/implement/standards/product_brief.cfm?product_id=496[CDA] to FHIR conversion. This template can be extended or modified to meet specific conversion requirements. +The https://anypoint.mulesoft.com/exchange/org.mule.examples/hls-ccda-to-fhir-sys-api/[C-CDA to FHIR converter] comes with a ready to use template for https://www.hl7.org/implement/standards/product_brief.cfm?product_id=496[CDA] to FHIR conversion. This template can be extended or modified to meet specific conversion requirements. == Functional diagram -image:https://www.mulesoft.com/ext/solutions/draft/images/hls-ccda-fhir-fx-diagram.svg[CDA to FHIR converter functional diagram,900,align="center"] +image:https://www.mulesoft.com/ext/solutions/images/hls-ccda-fhir-fx-diagram.svg[CDA to FHIR converter functional diagram,900,align="center"] == Advantages diff --git a/healthcare/2.21/modules/ROOT/pages/fhir-r4-assets.adoc b/healthcare/2.21/modules/ROOT/pages/fhir-r4-assets.adoc index 134ba48f5..10d431db8 100644 --- a/healthcare/2.21/modules/ROOT/pages/fhir-r4-assets.adoc +++ b/healthcare/2.21/modules/ROOT/pages/fhir-r4-assets.adoc @@ -2,11 +2,11 @@ The following are a collection of assets to support MuleSoft customers who are developing Fast Healthcare Interoperability Resources (FHIR) APIs using MuleSoft. Visit the https://www.hl7.org/fhir/[official HL7 website] for more information. -* https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/hls-fhirjson-to-raml-sys-api-spec/[FHIR RAML auto-generator] - Utility to generate RAML specification(s) for FHIR resources directly from the JSON schema provided by HL7. +* https://anypoint.mulesoft.com/exchange/org.mule.examples/hls-fhirjson-to-raml-sys-api-spec/[FHIR RAML auto-generator] - Utility to generate RAML specification(s) for FHIR resources directly from the JSON schema provided by HL7. * xref:fhir-r4-us-core-profiles.adoc[FHIR R4 US Core Profile Assets] * xref:fhir-r4-resources.adoc[FHIR R4 Resources List] -* https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fhir-error-policy/[FHIR Error API Policy] - Captures error responses and formats them in an FHIR OperationOutcome-compliant format, since Anypoint Platform's out-of-the-box (OOTB) policies do not provide error messages in an FHIR-compliant format. This policy can also be used with other OOTB API policies provided in Anypoint Platform, such as OAuth or JWT. -* https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/hc-accelerator-okta-smartfhir/[Okta SMART on FHIR^] - Implementation template that walks you through how to set up a reference SMART on FHIR implementation on Anypoint Platform using Okta as the identity provider. +* https://anypoint.mulesoft.com/exchange/org.mule.examples/fhir-error-policy/[FHIR Error API Policy] - Captures error responses and formats them in an FHIR OperationOutcome-compliant format, since Anypoint Platform's out-of-the-box (OOTB) policies do not provide error messages in an FHIR-compliant format. This policy can also be used with other OOTB API policies provided in Anypoint Platform, such as OAuth or JWT. +* https://anypoint.mulesoft.com/exchange/org.mule.examples/hc-accelerator-okta-smartfhir/[Okta SMART on FHIR^] - Implementation template that walks you through how to set up a reference SMART on FHIR implementation on Anypoint Platform using Okta as the identity provider. == See Also diff --git a/healthcare/2.21/modules/ROOT/pages/fhir-r4-resources.adoc b/healthcare/2.21/modules/ROOT/pages/fhir-r4-resources.adoc index 062796d38..8414363f1 100644 --- a/healthcare/2.21/modules/ROOT/pages/fhir-r4-resources.adoc +++ b/healthcare/2.21/modules/ROOT/pages/fhir-r4-resources.adoc @@ -2,7 +2,7 @@ The MuleSoft Accelerator for Healthcare provides a library of United States Core Data for Interoperability (USCDI) and FHIR R4 resources to help healthcare developers adhere to interoperability needs and jumpstart the development of healthcare digital transformation initiatives. -You can also use the https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fhir-error-policy/[FHIR Error API Policy] to capture error responses and format them in an FHIR OperationOutcome-compliant format, since Anypoint Platform's out-of-the-box (OOTB) policies do not provide error messages in an FHIR-compliant format. This policy can also be used with other OOTB API policies provided in Anypoint Platform, such as OAuth or JWT. +You can also use the https://anypoint.mulesoft.com/exchange/org.mule.examples/fhir-error-policy/[FHIR Error API Policy] to capture error responses and format them in an FHIR OperationOutcome-compliant format, since Anypoint Platform's out-of-the-box (OOTB) policies do not provide error messages in an FHIR-compliant format. This policy can also be used with other OOTB API policies provided in Anypoint Platform, such as OAuth or JWT. For the list of US core profile assets, please refer to xref:fhir-r4-us-core-profiles.adoc[this link]. @@ -15,339 +15,339 @@ _API specifications, data types, and libraries built to meet compliance with FHI | Category| Library | API Specification .^| Foundation - Confirmance -| https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fhir-r4-capabilitystatement-library/[CapabilityStatement] ^[N]^ + -https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fhir-r4-structuredefinition-library/[StructureDefinition] ^[N]^ + -https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fhir-r4-implementationguide-library/[ImplementationGuide] + -https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fhir-r4-searchparameter-library/[SearchParameter] + -https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fhir-r4-operationdefinition-library/[OperationDefinition] ^[N]^ + -https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fhir-r4-compartmentdefinition-library/[CompartmentDefinition] + -https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fhir-r4-messagedefinition-library/[MessageDefinition] + -https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fhir-r4-structuremap-library/[StructureMap] + -https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fhir-r4-graphdefinition-library/[GraphDefinition] + -https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fhir-r4-examplescenario-library/[ExampleScenario] -| https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fhir-r4-capabilitystatement-api/[CapabilityStatement] ^[N]^ + -https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fhir-r4-structuredefinition-api/[StructureDefinition] ^[N]^ + -https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fhir-r4-implementationguide-api/[ImplementationGuide] + -https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fhir-r4-searchparameter-api/[SearchParameter] + -https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fhir-r4-operationdefinition-api/[OperationDefinition] ^[N]^ + -https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fhir-r4-compartmentdefinition-api/[CompartmentDefinition] + -https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fhir-r4-messagedefinition-api/[MessageDefinition] + -https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fhir-r4-structuremap-api/[StructureMap] + -https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fhir-r4-graphdefinition-api/[GraphDefinition] + -https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fhir-r4-examplescenario-api/[ExampleScenario] +| https://anypoint.mulesoft.com/exchange/org.mule.examples/fhir-r4-capabilitystatement-library/[CapabilityStatement] ^[N]^ + +https://anypoint.mulesoft.com/exchange/org.mule.examples/fhir-r4-structuredefinition-library/[StructureDefinition] ^[N]^ + +https://anypoint.mulesoft.com/exchange/org.mule.examples/fhir-r4-implementationguide-library/[ImplementationGuide] + +https://anypoint.mulesoft.com/exchange/org.mule.examples/fhir-r4-searchparameter-library/[SearchParameter] + +https://anypoint.mulesoft.com/exchange/org.mule.examples/fhir-r4-operationdefinition-library/[OperationDefinition] ^[N]^ + +https://anypoint.mulesoft.com/exchange/org.mule.examples/fhir-r4-compartmentdefinition-library/[CompartmentDefinition] + +https://anypoint.mulesoft.com/exchange/org.mule.examples/fhir-r4-messagedefinition-library/[MessageDefinition] + +https://anypoint.mulesoft.com/exchange/org.mule.examples/fhir-r4-structuremap-library/[StructureMap] + +https://anypoint.mulesoft.com/exchange/org.mule.examples/fhir-r4-graphdefinition-library/[GraphDefinition] + +https://anypoint.mulesoft.com/exchange/org.mule.examples/fhir-r4-examplescenario-library/[ExampleScenario] +| https://anypoint.mulesoft.com/exchange/org.mule.examples/fhir-r4-capabilitystatement-api/[CapabilityStatement] ^[N]^ + +https://anypoint.mulesoft.com/exchange/org.mule.examples/fhir-r4-structuredefinition-api/[StructureDefinition] ^[N]^ + +https://anypoint.mulesoft.com/exchange/org.mule.examples/fhir-r4-implementationguide-api/[ImplementationGuide] + +https://anypoint.mulesoft.com/exchange/org.mule.examples/fhir-r4-searchparameter-api/[SearchParameter] + +https://anypoint.mulesoft.com/exchange/org.mule.examples/fhir-r4-operationdefinition-api/[OperationDefinition] ^[N]^ + +https://anypoint.mulesoft.com/exchange/org.mule.examples/fhir-r4-compartmentdefinition-api/[CompartmentDefinition] + +https://anypoint.mulesoft.com/exchange/org.mule.examples/fhir-r4-messagedefinition-api/[MessageDefinition] + +https://anypoint.mulesoft.com/exchange/org.mule.examples/fhir-r4-structuremap-api/[StructureMap] + +https://anypoint.mulesoft.com/exchange/org.mule.examples/fhir-r4-graphdefinition-api/[GraphDefinition] + +https://anypoint.mulesoft.com/exchange/org.mule.examples/fhir-r4-examplescenario-api/[ExampleScenario] .^| Foundation - Terminology -| https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fhir-r4-codesystem-library/[CodeSystem] ^[N]^ + -https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fhir-r4-valueset-library/[ValueSet] ^[N]^ + -https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fhir-r4-conceptmap-library/[ConceptMap] + -https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fhir-r4-namingsystem-library/[NamingSystem] + -https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fhir-r4-terminologycapabilities-library/[TerminologiesCapabilities] -| https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fhir-r4-codesystem-api/[CodeSystem] ^[N]^ + -https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fhir-r4-valueset-api/[ValueSet] ^[N]^ + -https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fhir-r4-conceptmap-api/[ConceptMap] + -https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fhir-r4-namingsystem-api/[NamingSystem] + -https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fhir-r4-terminologycapabilities-api/[TerminologiesCapabilities] +| https://anypoint.mulesoft.com/exchange/org.mule.examples/fhir-r4-codesystem-library/[CodeSystem] ^[N]^ + +https://anypoint.mulesoft.com/exchange/org.mule.examples/fhir-r4-valueset-library/[ValueSet] ^[N]^ + +https://anypoint.mulesoft.com/exchange/org.mule.examples/fhir-r4-conceptmap-library/[ConceptMap] + +https://anypoint.mulesoft.com/exchange/org.mule.examples/fhir-r4-namingsystem-library/[NamingSystem] + +https://anypoint.mulesoft.com/exchange/org.mule.examples/fhir-r4-terminologycapabilities-library/[TerminologiesCapabilities] +| https://anypoint.mulesoft.com/exchange/org.mule.examples/fhir-r4-codesystem-api/[CodeSystem] ^[N]^ + +https://anypoint.mulesoft.com/exchange/org.mule.examples/fhir-r4-valueset-api/[ValueSet] ^[N]^ + +https://anypoint.mulesoft.com/exchange/org.mule.examples/fhir-r4-conceptmap-api/[ConceptMap] + +https://anypoint.mulesoft.com/exchange/org.mule.examples/fhir-r4-namingsystem-api/[NamingSystem] + +https://anypoint.mulesoft.com/exchange/org.mule.examples/fhir-r4-terminologycapabilities-api/[TerminologiesCapabilities] .^| Foundation - Security -| https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fhir-r4-provenance-library/[Provenance] + -https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fhir-r4-auditevent-library/[AuditEvent] + -https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fhir-r4-consent-library/[Consent] -| https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fhir-r4-provenance-api/[Provenance] + -https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fhir-r4-auditevent-api/[AuditEvent] + -https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fhir-r4-consent-api/[Consent] +| https://anypoint.mulesoft.com/exchange/org.mule.examples/fhir-r4-provenance-library/[Provenance] + +https://anypoint.mulesoft.com/exchange/org.mule.examples/fhir-r4-auditevent-library/[AuditEvent] + +https://anypoint.mulesoft.com/exchange/org.mule.examples/fhir-r4-consent-library/[Consent] +| https://anypoint.mulesoft.com/exchange/org.mule.examples/fhir-r4-provenance-api/[Provenance] + +https://anypoint.mulesoft.com/exchange/org.mule.examples/fhir-r4-auditevent-api/[AuditEvent] + +https://anypoint.mulesoft.com/exchange/org.mule.examples/fhir-r4-consent-api/[Consent] .^| Foundation - Documents -| https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fhir-r4-composition-library/[Composition] + -https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fhir-r4-documentmanifest-library/[DocumentManifest] + -https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fhir-r4-documentreference-library/[DocumentReference] + -https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fhir-r4-catalogentry-library/[CatalogEntry] -| https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fhir-r4-composition-api/[Composition] + -https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fhir-r4-documentmanifest-api/[DocumentManifest] + -https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fhir-r4-documentreference-api/[DocumentReference] + -https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fhir-r4-catalogentry-api/[CatalogEntry] +| https://anypoint.mulesoft.com/exchange/org.mule.examples/fhir-r4-composition-library/[Composition] + +https://anypoint.mulesoft.com/exchange/org.mule.examples/fhir-r4-documentmanifest-library/[DocumentManifest] + +https://anypoint.mulesoft.com/exchange/org.mule.examples/fhir-r4-documentreference-library/[DocumentReference] + +https://anypoint.mulesoft.com/exchange/org.mule.examples/fhir-r4-catalogentry-library/[CatalogEntry] +| https://anypoint.mulesoft.com/exchange/org.mule.examples/fhir-r4-composition-api/[Composition] + +https://anypoint.mulesoft.com/exchange/org.mule.examples/fhir-r4-documentmanifest-api/[DocumentManifest] + +https://anypoint.mulesoft.com/exchange/org.mule.examples/fhir-r4-documentreference-api/[DocumentReference] + +https://anypoint.mulesoft.com/exchange/org.mule.examples/fhir-r4-catalogentry-api/[CatalogEntry] .^| Foundation - Other -| https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fhir-r4-basic-library/[Basic] + -https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fhir-r4-binary-library/[Binary] ^[N]^ + -https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fhir-r4-linkage-library/[Linkage] + -https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fhir-r4-messageheader-library/[MessageHeader] + -https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fhir-r4-parameters-library/[Parameters] ^[N]^ + -https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fhir-r4-subscription-library/[Subscription] + +| https://anypoint.mulesoft.com/exchange/org.mule.examples/fhir-r4-basic-library/[Basic] + +https://anypoint.mulesoft.com/exchange/org.mule.examples/fhir-r4-binary-library/[Binary] ^[N]^ + +https://anypoint.mulesoft.com/exchange/org.mule.examples/fhir-r4-linkage-library/[Linkage] + +https://anypoint.mulesoft.com/exchange/org.mule.examples/fhir-r4-messageheader-library/[MessageHeader] + +https://anypoint.mulesoft.com/exchange/org.mule.examples/fhir-r4-parameters-library/[Parameters] ^[N]^ + +https://anypoint.mulesoft.com/exchange/org.mule.examples/fhir-r4-subscription-library/[Subscription] + ++++++ -| https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fhir-r4-basic-api/[Basic] + -https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fhir-r4-binary-api/[Binary] ^[N]^ + -https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fhir-r4-linkage-api/[Linkage] + -https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fhir-r4-messageheader-api/[MessageHeader] + -https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fhir-r4-parameters-api/[Parameters] ^[N]^ + -https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fhir-r4-subscription-api/[Subscription] +| https://anypoint.mulesoft.com/exchange/org.mule.examples/fhir-r4-basic-api/[Basic] + +https://anypoint.mulesoft.com/exchange/org.mule.examples/fhir-r4-binary-api/[Binary] ^[N]^ + +https://anypoint.mulesoft.com/exchange/org.mule.examples/fhir-r4-linkage-api/[Linkage] + +https://anypoint.mulesoft.com/exchange/org.mule.examples/fhir-r4-messageheader-api/[MessageHeader] + +https://anypoint.mulesoft.com/exchange/org.mule.examples/fhir-r4-parameters-api/[Parameters] ^[N]^ + +https://anypoint.mulesoft.com/exchange/org.mule.examples/fhir-r4-subscription-api/[Subscription] .^| Base - Individuals -| https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fhir-r4-patient-library/[Patient] ^[N]^ + -https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fhir-r4-practitioner-library/[Practitioner] + -https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fhir-r4-practitionerrole-library/[PractitionerRole] + -https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fhir-r4-relatedperson-library/[RelatedPerson] + -https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fhir-r4-person-library/[Person] + -https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fhir-r4-group-library/[Group] + +| https://anypoint.mulesoft.com/exchange/org.mule.examples/fhir-r4-patient-library/[Patient] ^[N]^ + +https://anypoint.mulesoft.com/exchange/org.mule.examples/fhir-r4-practitioner-library/[Practitioner] + +https://anypoint.mulesoft.com/exchange/org.mule.examples/fhir-r4-practitionerrole-library/[PractitionerRole] + +https://anypoint.mulesoft.com/exchange/org.mule.examples/fhir-r4-relatedperson-library/[RelatedPerson] + +https://anypoint.mulesoft.com/exchange/org.mule.examples/fhir-r4-person-library/[Person] + +https://anypoint.mulesoft.com/exchange/org.mule.examples/fhir-r4-group-library/[Group] + ++++++ -| https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fhir-r4-patient-api/[Patient] ^[N]^ + -https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fhir-r4-practitioner-api/[Practitioner] + -https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fhir-r4-practitionerrole-api/[PractitionerRole] + -https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fhir-r4-relatedperson-api/[RelatedPerson] + -https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fhir-r4-person-api/[Person] + -https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fhir-r4-group-api/[Group] +| https://anypoint.mulesoft.com/exchange/org.mule.examples/fhir-r4-patient-api/[Patient] ^[N]^ + +https://anypoint.mulesoft.com/exchange/org.mule.examples/fhir-r4-practitioner-api/[Practitioner] + +https://anypoint.mulesoft.com/exchange/org.mule.examples/fhir-r4-practitionerrole-api/[PractitionerRole] + +https://anypoint.mulesoft.com/exchange/org.mule.examples/fhir-r4-relatedperson-api/[RelatedPerson] + +https://anypoint.mulesoft.com/exchange/org.mule.examples/fhir-r4-person-api/[Person] + +https://anypoint.mulesoft.com/exchange/org.mule.examples/fhir-r4-group-api/[Group] .^| Base - Entities #1 -| https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fhir-r4-organization-library/[Organization] + -https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fhir-r4-organizationaffiliation-library/[OrganizationAffiliation] + -https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fhir-r4-healthcareservice-library/[HealthcareService] + -https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fhir-r4-endpoint-library/[Endpoint] + -https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fhir-r4-location-library/[Location] + +| https://anypoint.mulesoft.com/exchange/org.mule.examples/fhir-r4-organization-library/[Organization] + +https://anypoint.mulesoft.com/exchange/org.mule.examples/fhir-r4-organizationaffiliation-library/[OrganizationAffiliation] + +https://anypoint.mulesoft.com/exchange/org.mule.examples/fhir-r4-healthcareservice-library/[HealthcareService] + +https://anypoint.mulesoft.com/exchange/org.mule.examples/fhir-r4-endpoint-library/[Endpoint] + +https://anypoint.mulesoft.com/exchange/org.mule.examples/fhir-r4-location-library/[Location] + ++++++ -| https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fhir-r4-organization-api/[Organization] + -https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fhir-r4-organizationaffiliation-api/[OrganizationAffiliation] + -https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fhir-r4-healthcareservice-api/[HealthcareService] + -https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fhir-r4-endpoint-api/[Endpoint] + -https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fhir-r4-location-api/[Location] +| https://anypoint.mulesoft.com/exchange/org.mule.examples/fhir-r4-organization-api/[Organization] + +https://anypoint.mulesoft.com/exchange/org.mule.examples/fhir-r4-organizationaffiliation-api/[OrganizationAffiliation] + +https://anypoint.mulesoft.com/exchange/org.mule.examples/fhir-r4-healthcareservice-api/[HealthcareService] + +https://anypoint.mulesoft.com/exchange/org.mule.examples/fhir-r4-endpoint-api/[Endpoint] + +https://anypoint.mulesoft.com/exchange/org.mule.examples/fhir-r4-location-api/[Location] .^| Base - Entities #2 -| https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fhir-r4-substance-library/[Substance] + -https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fhir-r4-biologicallyderivedproduct-library/[BiologicallyDerivedProduct #] + -https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fhir-r4-device-library/[Device] + -https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fhir-r4-devicemetric-library/[DeviceMetric] + +| https://anypoint.mulesoft.com/exchange/org.mule.examples/fhir-r4-substance-library/[Substance] + +https://anypoint.mulesoft.com/exchange/org.mule.examples/fhir-r4-biologicallyderivedproduct-library/[BiologicallyDerivedProduct #] + +https://anypoint.mulesoft.com/exchange/org.mule.examples/fhir-r4-device-library/[Device] + +https://anypoint.mulesoft.com/exchange/org.mule.examples/fhir-r4-devicemetric-library/[DeviceMetric] + ++++++ -| https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fhir-r4-substance-api/[Substance] + -https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fhir-r4-biologicallyderivedproduct-api/[BiologicallyDerivedProduct #] + -https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fhir-r4-device-api/[Device] + -https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fhir-r4-devicemetric-api/[DeviceMetric] +| https://anypoint.mulesoft.com/exchange/org.mule.examples/fhir-r4-substance-api/[Substance] + +https://anypoint.mulesoft.com/exchange/org.mule.examples/fhir-r4-biologicallyderivedproduct-api/[BiologicallyDerivedProduct #] + +https://anypoint.mulesoft.com/exchange/org.mule.examples/fhir-r4-device-api/[Device] + +https://anypoint.mulesoft.com/exchange/org.mule.examples/fhir-r4-devicemetric-api/[DeviceMetric] .^| Base - Workflow -| https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fhir-r4-task-library/[Task] + -https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fhir-r4-appointment-library/[Appointment] + -https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fhir-r4-appointmentresponse-library/[AppointmentResponse] + -https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fhir-r4-schedule-library/[Schedule] + -https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fhir-r4-slot-library/[Slot] + -https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fhir-r4-verificationresult-library/[VerificationResult] -| https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fhir-r4-task-api/[Task] + -https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fhir-r4-appointment-api/[Appointment] + -https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fhir-r4-appointmentresponse-api/[AppointmentResponse] + -https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fhir-r4-schedule-api/[Schedule] + -https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fhir-r4-slot-api/[Slot] + -https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fhir-r4-verificationresult-api/[VerificationResult] +| https://anypoint.mulesoft.com/exchange/org.mule.examples/fhir-r4-task-library/[Task] + +https://anypoint.mulesoft.com/exchange/org.mule.examples/fhir-r4-appointment-library/[Appointment] + +https://anypoint.mulesoft.com/exchange/org.mule.examples/fhir-r4-appointmentresponse-library/[AppointmentResponse] + +https://anypoint.mulesoft.com/exchange/org.mule.examples/fhir-r4-schedule-library/[Schedule] + +https://anypoint.mulesoft.com/exchange/org.mule.examples/fhir-r4-slot-library/[Slot] + +https://anypoint.mulesoft.com/exchange/org.mule.examples/fhir-r4-verificationresult-library/[VerificationResult] +| https://anypoint.mulesoft.com/exchange/org.mule.examples/fhir-r4-task-api/[Task] + +https://anypoint.mulesoft.com/exchange/org.mule.examples/fhir-r4-appointment-api/[Appointment] + +https://anypoint.mulesoft.com/exchange/org.mule.examples/fhir-r4-appointmentresponse-api/[AppointmentResponse] + +https://anypoint.mulesoft.com/exchange/org.mule.examples/fhir-r4-schedule-api/[Schedule] + +https://anypoint.mulesoft.com/exchange/org.mule.examples/fhir-r4-slot-api/[Slot] + +https://anypoint.mulesoft.com/exchange/org.mule.examples/fhir-r4-verificationresult-api/[VerificationResult] .^| Base - Management -| https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fhir-r4-encounter-library/[Encounter] + -https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fhir-r4-episodeofcare-library/[EpisodeOfCare] + -https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fhir-r4-flag-library/[Flag] + -https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fhir-r4-list-library/[List] + -https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fhir-r4-library-library/[Library] -| https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fhir-r4-encounter-api/[Encounter] + -https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fhir-r4-episodeofcare-api/[EpisodeOfCare] + -https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fhir-r4-flag-api/[Flag] + -https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fhir-r4-list-api/[List] + -https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fhir-r4-library-api/[Library] +| https://anypoint.mulesoft.com/exchange/org.mule.examples/fhir-r4-encounter-library/[Encounter] + +https://anypoint.mulesoft.com/exchange/org.mule.examples/fhir-r4-episodeofcare-library/[EpisodeOfCare] + +https://anypoint.mulesoft.com/exchange/org.mule.examples/fhir-r4-flag-library/[Flag] + +https://anypoint.mulesoft.com/exchange/org.mule.examples/fhir-r4-list-library/[List] + +https://anypoint.mulesoft.com/exchange/org.mule.examples/fhir-r4-library-library/[Library] +| https://anypoint.mulesoft.com/exchange/org.mule.examples/fhir-r4-encounter-api/[Encounter] + +https://anypoint.mulesoft.com/exchange/org.mule.examples/fhir-r4-episodeofcare-api/[EpisodeOfCare] + +https://anypoint.mulesoft.com/exchange/org.mule.examples/fhir-r4-flag-api/[Flag] + +https://anypoint.mulesoft.com/exchange/org.mule.examples/fhir-r4-list-api/[List] + +https://anypoint.mulesoft.com/exchange/org.mule.examples/fhir-r4-library-api/[Library] .^| Clinical - Summary -| https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fhir-r4-allergyintolerance-library/[AllergyIntolerance] + -https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fhir-r4-adverseevent-library/[AdverseEvent] + -https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fhir-r4-condition-library/[Condition(Problem)] + -https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fhir-r4-procedure-library/[Procedure] + -https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fhir-r4-familymemberhistory-library/[FamilyMemberHistory] + -https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fhir-r4-clinicalimpression-library/[ClinicalImpression #] + -https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fhir-r4-clinicalimpression-library/[Note] + -https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fhir-r4-detectedissue-library/[DetectedIssue] -| https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fhir-r4-allergyintolerance-api/[AllergyIntolerance] + -https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fhir-r4-adverseevent-api/[AdverseEvent] + -https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fhir-r4-condition-api/[Condition(Problem)] + -https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fhir-r4-procedure-api/[Procedure] + -https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fhir-r4-familymemberhistory-api/[FamilyMemberHistory] + -https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fhir-r4-clinicalimpression-api/[ClinicalImpression #] + -https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fhir-r4-clinicalimpression-api/[Note] + -https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fhir-r4-detectedissue-api/[DetectedIssue] +| https://anypoint.mulesoft.com/exchange/org.mule.examples/fhir-r4-allergyintolerance-library/[AllergyIntolerance] + +https://anypoint.mulesoft.com/exchange/org.mule.examples/fhir-r4-adverseevent-library/[AdverseEvent] + +https://anypoint.mulesoft.com/exchange/org.mule.examples/fhir-r4-condition-library/[Condition(Problem)] + +https://anypoint.mulesoft.com/exchange/org.mule.examples/fhir-r4-procedure-library/[Procedure] + +https://anypoint.mulesoft.com/exchange/org.mule.examples/fhir-r4-familymemberhistory-library/[FamilyMemberHistory] + +https://anypoint.mulesoft.com/exchange/org.mule.examples/fhir-r4-clinicalimpression-library/[ClinicalImpression #] + +https://anypoint.mulesoft.com/exchange/org.mule.examples/fhir-r4-clinicalimpression-library/[Note] + +https://anypoint.mulesoft.com/exchange/org.mule.examples/fhir-r4-detectedissue-library/[DetectedIssue] +| https://anypoint.mulesoft.com/exchange/org.mule.examples/fhir-r4-allergyintolerance-api/[AllergyIntolerance] + +https://anypoint.mulesoft.com/exchange/org.mule.examples/fhir-r4-adverseevent-api/[AdverseEvent] + +https://anypoint.mulesoft.com/exchange/org.mule.examples/fhir-r4-condition-api/[Condition(Problem)] + +https://anypoint.mulesoft.com/exchange/org.mule.examples/fhir-r4-procedure-api/[Procedure] + +https://anypoint.mulesoft.com/exchange/org.mule.examples/fhir-r4-familymemberhistory-api/[FamilyMemberHistory] + +https://anypoint.mulesoft.com/exchange/org.mule.examples/fhir-r4-clinicalimpression-api/[ClinicalImpression #] + +https://anypoint.mulesoft.com/exchange/org.mule.examples/fhir-r4-clinicalimpression-api/[Note] + +https://anypoint.mulesoft.com/exchange/org.mule.examples/fhir-r4-detectedissue-api/[DetectedIssue] .^| Clinical - Diagnostics -| https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fhir-r4-observation-library/[Observation] ^[N]^ + -https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fhir-r4-media-library/[Media] ^[u]^ + -https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fhir-r4-diagnosticreport-library/[DiagnosticReport] + -https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fhir-r4-specimen-library/[Specimen] + -https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fhir-r4-bodystructure-library/[BodyStructure] + -https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fhir-r4-imagingstudy-library/[ImagingStudy] + -https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fhir-r4-questionnaireresponse-library/[QuestionnaireResponse ] + -https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fhir-r4-molecularsequence-library/[MolecularSequence] -| https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fhir-r4-observation-api/[Observation] ^[N]^ + -https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fhir-r4-media-api/[Media] ^[u]^ + -https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fhir-r4-diagnosticreport-api/[DiagnosticReport] + -https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fhir-r4-specimen-api/[Specimen] + -https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fhir-r4-bodystructure-api/[BodyStructure] + -https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fhir-r4-imagingstudy-api/[ImagingStudy] + -https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fhir-r4-questionnaireresponse-api/[QuestionnaireResponse ] + -https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fhir-r4-molecularsequence-api/[MolecularSequence] +| https://anypoint.mulesoft.com/exchange/org.mule.examples/fhir-r4-observation-library/[Observation] ^[N]^ + +https://anypoint.mulesoft.com/exchange/org.mule.examples/fhir-r4-media-library/[Media] ^[u]^ + +https://anypoint.mulesoft.com/exchange/org.mule.examples/fhir-r4-diagnosticreport-library/[DiagnosticReport] + +https://anypoint.mulesoft.com/exchange/org.mule.examples/fhir-r4-specimen-library/[Specimen] + +https://anypoint.mulesoft.com/exchange/org.mule.examples/fhir-r4-bodystructure-library/[BodyStructure] + +https://anypoint.mulesoft.com/exchange/org.mule.examples/fhir-r4-imagingstudy-library/[ImagingStudy] + +https://anypoint.mulesoft.com/exchange/org.mule.examples/fhir-r4-questionnaireresponse-library/[QuestionnaireResponse ] + +https://anypoint.mulesoft.com/exchange/org.mule.examples/fhir-r4-molecularsequence-library/[MolecularSequence] +| https://anypoint.mulesoft.com/exchange/org.mule.examples/fhir-r4-observation-api/[Observation] ^[N]^ + +https://anypoint.mulesoft.com/exchange/org.mule.examples/fhir-r4-media-api/[Media] ^[u]^ + +https://anypoint.mulesoft.com/exchange/org.mule.examples/fhir-r4-diagnosticreport-api/[DiagnosticReport] + +https://anypoint.mulesoft.com/exchange/org.mule.examples/fhir-r4-specimen-api/[Specimen] + +https://anypoint.mulesoft.com/exchange/org.mule.examples/fhir-r4-bodystructure-api/[BodyStructure] + +https://anypoint.mulesoft.com/exchange/org.mule.examples/fhir-r4-imagingstudy-api/[ImagingStudy] + +https://anypoint.mulesoft.com/exchange/org.mule.examples/fhir-r4-questionnaireresponse-api/[QuestionnaireResponse ] + +https://anypoint.mulesoft.com/exchange/org.mule.examples/fhir-r4-molecularsequence-api/[MolecularSequence] .^| Clinical - Medications -| https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fhir-r4-medicationrequest-library/[MedicationRequest] + -https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fhir-r4-medicationadministration-library/[MedicationAdministration] + -https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fhir-r4-medicationdispense-library/[MedicationDispense] + -https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fhir-r4-medicationstatement-library/[MedicationStatement] + -https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fhir-r4-medication-library/[Medication] + -https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fhir-r4-medicationknowledge-library/[MedicationKnowledge] + -https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fhir-r4-immunization-library/[Immunization] + -https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fhir-r4-immunizationevaluation-library/[ImmunizationEvaluation] + -https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fhir-r4-immunizationrecommendation-library/[ImmunizationRecommendation] -| https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fhir-r4-medicationrequest-api/[MedicationRequest] + -https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fhir-r4-medicationadministration-api/[MedicationAdministration] + -https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fhir-r4-medicationdispense-api/[MedicationDispense] + -https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fhir-r4-medicationstatement-api/[MedicationStatement] + -https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fhir-r4-medication-api/[Medication] + -https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fhir-r4-medicationknowledge-api/[MedicationKnowledge] + -https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fhir-r4-immunization-api/[Immunization] + -https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fhir-r4-immunizationevaluation-api/[ImmunizationEvaluation] + -https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fhir-r4-immunizationrecommendation-api/[ImmunizationRecommendation] +| https://anypoint.mulesoft.com/exchange/org.mule.examples/fhir-r4-medicationrequest-library/[MedicationRequest] + +https://anypoint.mulesoft.com/exchange/org.mule.examples/fhir-r4-medicationadministration-library/[MedicationAdministration] + +https://anypoint.mulesoft.com/exchange/org.mule.examples/fhir-r4-medicationdispense-library/[MedicationDispense] + +https://anypoint.mulesoft.com/exchange/org.mule.examples/fhir-r4-medicationstatement-library/[MedicationStatement] + +https://anypoint.mulesoft.com/exchange/org.mule.examples/fhir-r4-medication-library/[Medication] + +https://anypoint.mulesoft.com/exchange/org.mule.examples/fhir-r4-medicationknowledge-library/[MedicationKnowledge] + +https://anypoint.mulesoft.com/exchange/org.mule.examples/fhir-r4-immunization-library/[Immunization] + +https://anypoint.mulesoft.com/exchange/org.mule.examples/fhir-r4-immunizationevaluation-library/[ImmunizationEvaluation] + +https://anypoint.mulesoft.com/exchange/org.mule.examples/fhir-r4-immunizationrecommendation-library/[ImmunizationRecommendation] +| https://anypoint.mulesoft.com/exchange/org.mule.examples/fhir-r4-medicationrequest-api/[MedicationRequest] + +https://anypoint.mulesoft.com/exchange/org.mule.examples/fhir-r4-medicationadministration-api/[MedicationAdministration] + +https://anypoint.mulesoft.com/exchange/org.mule.examples/fhir-r4-medicationdispense-api/[MedicationDispense] + +https://anypoint.mulesoft.com/exchange/org.mule.examples/fhir-r4-medicationstatement-api/[MedicationStatement] + +https://anypoint.mulesoft.com/exchange/org.mule.examples/fhir-r4-medication-api/[Medication] + +https://anypoint.mulesoft.com/exchange/org.mule.examples/fhir-r4-medicationknowledge-api/[MedicationKnowledge] + +https://anypoint.mulesoft.com/exchange/org.mule.examples/fhir-r4-immunization-api/[Immunization] + +https://anypoint.mulesoft.com/exchange/org.mule.examples/fhir-r4-immunizationevaluation-api/[ImmunizationEvaluation] + +https://anypoint.mulesoft.com/exchange/org.mule.examples/fhir-r4-immunizationrecommendation-api/[ImmunizationRecommendation] .^| Clinical - Care Provision -| https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fhir-r4-careplan-library/[CarePlan] + -https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fhir-r4-careteam-library/[CareTeam] + -https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fhir-r4-goal-library/[Goal] + -https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fhir-r4-servicerequest-library/[ServiceRequest] + -https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fhir-r4-nutritionorder-library/[NutritionOrder] + -https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fhir-r4-visionprescription-library/[VisionPrescription] + -https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fhir-r4-riskassessment-library/[RiskAssessment] + -https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fhir-r4-requestgroup-library/[RequestGroup] -| https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fhir-r4-careplan-api/[CarePlan] + -https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fhir-r4-careteam-api/[CareTeam] + -https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fhir-r4-goal-api/[Goal] + -https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fhir-r4-servicerequest-api/[ServiceRequest] + -https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fhir-r4-nutritionorder-api/[NutritionOrder] + -https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fhir-r4-visionprescription-api/[VisionPrescription] + -https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fhir-r4-riskassessment-api/[RiskAssessment] + -https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fhir-r4-requestgroup-api/[RequestGroup] +| https://anypoint.mulesoft.com/exchange/org.mule.examples/fhir-r4-careplan-library/[CarePlan] + +https://anypoint.mulesoft.com/exchange/org.mule.examples/fhir-r4-careteam-library/[CareTeam] + +https://anypoint.mulesoft.com/exchange/org.mule.examples/fhir-r4-goal-library/[Goal] + +https://anypoint.mulesoft.com/exchange/org.mule.examples/fhir-r4-servicerequest-library/[ServiceRequest] + +https://anypoint.mulesoft.com/exchange/org.mule.examples/fhir-r4-nutritionorder-library/[NutritionOrder] + +https://anypoint.mulesoft.com/exchange/org.mule.examples/fhir-r4-visionprescription-library/[VisionPrescription] + +https://anypoint.mulesoft.com/exchange/org.mule.examples/fhir-r4-riskassessment-library/[RiskAssessment] + +https://anypoint.mulesoft.com/exchange/org.mule.examples/fhir-r4-requestgroup-library/[RequestGroup] +| https://anypoint.mulesoft.com/exchange/org.mule.examples/fhir-r4-careplan-api/[CarePlan] + +https://anypoint.mulesoft.com/exchange/org.mule.examples/fhir-r4-careteam-api/[CareTeam] + +https://anypoint.mulesoft.com/exchange/org.mule.examples/fhir-r4-goal-api/[Goal] + +https://anypoint.mulesoft.com/exchange/org.mule.examples/fhir-r4-servicerequest-api/[ServiceRequest] + +https://anypoint.mulesoft.com/exchange/org.mule.examples/fhir-r4-nutritionorder-api/[NutritionOrder] + +https://anypoint.mulesoft.com/exchange/org.mule.examples/fhir-r4-visionprescription-api/[VisionPrescription] + +https://anypoint.mulesoft.com/exchange/org.mule.examples/fhir-r4-riskassessment-api/[RiskAssessment] + +https://anypoint.mulesoft.com/exchange/org.mule.examples/fhir-r4-requestgroup-api/[RequestGroup] .^| Clinical - Request & Response -| https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fhir-r4-communication-library/[Communication] + -https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fhir-r4-communicationrequest-library/[CommunicationRequest] + -https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fhir-r4-devicerequest-library/[DeviceRequest #] + -https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fhir-r4-deviceusestatement-library/[DeviceUseStatement] ^[u]^ + -https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fhir-r4-guidanceresponse-library/[GuidanceResponse] + -https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fhir-r4-supplyrequest-library/[SupplyRequest #] + -https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fhir-r4-supplydelivery-library/[SupplyDelivery] -| https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fhir-r4-communication-api/[Communication] + -https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fhir-r4-communicationrequest-api/[CommunicationRequest] + -https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fhir-r4-devicerequest-api/[DeviceRequest #] + -https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fhir-r4-deviceusestatement-api/[DeviceUseStatement] ^[u]^ + -https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fhir-r4-guidanceresponse-api/[GuidanceResponse] + -https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fhir-r4-supplyrequest-api/[SupplyRequest #] + -https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fhir-r4-supplydelivery-api/[SupplyDelivery] +| https://anypoint.mulesoft.com/exchange/org.mule.examples/fhir-r4-communication-library/[Communication] + +https://anypoint.mulesoft.com/exchange/org.mule.examples/fhir-r4-communicationrequest-library/[CommunicationRequest] + +https://anypoint.mulesoft.com/exchange/org.mule.examples/fhir-r4-devicerequest-library/[DeviceRequest #] + +https://anypoint.mulesoft.com/exchange/org.mule.examples/fhir-r4-deviceusestatement-library/[DeviceUseStatement] ^[u]^ + +https://anypoint.mulesoft.com/exchange/org.mule.examples/fhir-r4-guidanceresponse-library/[GuidanceResponse] + +https://anypoint.mulesoft.com/exchange/org.mule.examples/fhir-r4-supplyrequest-library/[SupplyRequest #] + +https://anypoint.mulesoft.com/exchange/org.mule.examples/fhir-r4-supplydelivery-library/[SupplyDelivery] +| https://anypoint.mulesoft.com/exchange/org.mule.examples/fhir-r4-communication-api/[Communication] + +https://anypoint.mulesoft.com/exchange/org.mule.examples/fhir-r4-communicationrequest-api/[CommunicationRequest] + +https://anypoint.mulesoft.com/exchange/org.mule.examples/fhir-r4-devicerequest-api/[DeviceRequest #] + +https://anypoint.mulesoft.com/exchange/org.mule.examples/fhir-r4-deviceusestatement-api/[DeviceUseStatement] ^[u]^ + +https://anypoint.mulesoft.com/exchange/org.mule.examples/fhir-r4-guidanceresponse-api/[GuidanceResponse] + +https://anypoint.mulesoft.com/exchange/org.mule.examples/fhir-r4-supplyrequest-api/[SupplyRequest #] + +https://anypoint.mulesoft.com/exchange/org.mule.examples/fhir-r4-supplydelivery-api/[SupplyDelivery] .^| Financial - Support -| https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fhir-r4-coverage-library/[Coverage] + -https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fhir-r4-coverageeligibilityrequest-library/[CoverageEligibilityRequest] + -https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fhir-r4-coverageeligibilityresponse-library/[CoverageEligibilityResponse] + -https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fhir-r4-enrollmentrequest-library/[EnrollmentRequest] ^[u]^ + -https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fhir-r4-enrollmentresponse-library/[EnrollmentResponse] ^[u]^ -| https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fhir-r4-coverage-api/[Coverage] + -https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fhir-r4-coverageeligibilityrequest-api/[CoverageEligibilityRequest] + -https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fhir-r4-coverageeligibilityresponse-api/[CoverageEligibilityResponse] + -https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fhir-r4-enrollmentrequest-api/[EnrollmentRequest] ^[u]^ + -https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fhir-r4-enrollmentresponse-api/[EnrollmentResponse] ^[u]^ +| https://anypoint.mulesoft.com/exchange/org.mule.examples/fhir-r4-coverage-library/[Coverage] + +https://anypoint.mulesoft.com/exchange/org.mule.examples/fhir-r4-coverageeligibilityrequest-library/[CoverageEligibilityRequest] + +https://anypoint.mulesoft.com/exchange/org.mule.examples/fhir-r4-coverageeligibilityresponse-library/[CoverageEligibilityResponse] + +https://anypoint.mulesoft.com/exchange/org.mule.examples/fhir-r4-enrollmentrequest-library/[EnrollmentRequest] ^[u]^ + +https://anypoint.mulesoft.com/exchange/org.mule.examples/fhir-r4-enrollmentresponse-library/[EnrollmentResponse] ^[u]^ +| https://anypoint.mulesoft.com/exchange/org.mule.examples/fhir-r4-coverage-api/[Coverage] + +https://anypoint.mulesoft.com/exchange/org.mule.examples/fhir-r4-coverageeligibilityrequest-api/[CoverageEligibilityRequest] + +https://anypoint.mulesoft.com/exchange/org.mule.examples/fhir-r4-coverageeligibilityresponse-api/[CoverageEligibilityResponse] + +https://anypoint.mulesoft.com/exchange/org.mule.examples/fhir-r4-enrollmentrequest-api/[EnrollmentRequest] ^[u]^ + +https://anypoint.mulesoft.com/exchange/org.mule.examples/fhir-r4-enrollmentresponse-api/[EnrollmentResponse] ^[u]^ .^| Financial - Billing -| https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fhir-r4-claim-library/[Claim] + -https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fhir-r4-claimresponse-library/[ClaimResponse] + -https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fhir-r4-invoice-library/[Invoice] -| https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fhir-r4-claim-api/[Claim] + -https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fhir-r4-claimresponse-api/[ClaimResponse] + -https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fhir-r4-invoice-api/[Invoice] - -.^| Financial - Payment | https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fhir-r4-paymentnotice-library/[PaymentNotice] + -https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fhir-r4-paymentreconciliation-library/[PaymentReconcilliation] -| https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fhir-r4-paymentnotice-api/[PaymentNotice] + -https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fhir-r4-paymentreconciliation-api/[PaymentReconcilliation] - -.^| Financial - General | https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fhir-r4-account-library/[Account] + -https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fhir-r4-chargeitem-library/[ChargeItem] + -https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fhir-r4-chargeitemdefinition-library/[ChargeItemDefinition] + -https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fhir-r4-contract-library/[Contract] + -https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fhir-r4-explanationofbenefit-library/[ExplanationOfBenefit] + -https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fhir-r4-insuranceplan-library/[InsurancePlan] -| https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fhir-r4-account-api/[Account] + -https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fhir-r4-chargeitem-api/[ChargeItem] + -https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fhir-r4-chargeitemdefinition-api/[ChargeItemDefinition] + -https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fhir-r4-contract-api/[Contract] + -https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fhir-r4-explanationofbenefit-api/[ExplanationOfBenefit] + -https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fhir-r4-insuranceplan-api/[InsurancePlan] - -.^| Specialized - Public Health & Research | https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fhir-r4-researchstudy-library/[ResearchStudy] + -https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fhir-r4-researchsubject-library/[ResearchSubject] -| https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fhir-r4-researchstudy-api/[ResearchStudy] + -https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fhir-r4-researchsubject-api/[ResearchSubject] - -.^| Specialized - Definitional Artifacts | https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fhir-r4-activitydefinition-library/[ActivityDefinition] + -https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fhir-r4-devicedefinition-library/[DeviceDefinition] + -https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fhir-r4-eventdefinition-library/[EventDefinition] + -https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fhir-r4-observationdefinition-library/[ObservationDefinition] ^[u]^ + -https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fhir-r4-plandefinition-library/[PlanDefinition] + -https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fhir-r4-questionnaire-library/[Questionnaire] + -https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fhir-r4-specimendefinition-library/[SpecimenDefinition] -| https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fhir-r4-activitydefinition-api/[ActivityDefinition] + -https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fhir-r4-devicedefinition-api/[DeviceDefinition] + -https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fhir-r4-eventdefinition-api/[EventDefinition] + -https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fhir-r4-observationdefinition-api/[ObservationDefinition] ^[u]^ + -https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fhir-r4-plandefinition-api/[PlanDefinition] + -https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fhir-r4-questionnaire-api/[Questionnaire] + -https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fhir-r4-specimendefinition-api/[SpecimenDefinition] - -.^| Specialized - Evidence Based Medicine | https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fhir-r4-researchdefinition-library/[ResearchDefinition] + -https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fhir-r4-researchelementdefinition-library/[ResearchElementDefinition] + -https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fhir-r4-evidence-library/[Evidence] + -https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fhir-r4-evidencevariable-library/[EvidenceVariable] + -https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fhir-r4-effectevidencesynthesis-library/[EffectEvidenceSynthesis] + -https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fhir-r4-riskevidencesynthesis-library/[RiskEvidenceSynthesis] -| https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fhir-r4-researchdefinition-api/[ResearchDefinition] + -https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fhir-r4-researchelementdefinition-api/[ResearchElementDefinition] + -https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fhir-r4-evidence-api/[Evidence] + -https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fhir-r4-evidencevariable-api/[EvidenceVariable] + -https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fhir-r4-effectevidencesynthesis-api/[EffectEvidenceSynthesis] + -https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fhir-r4-riskevidencesynthesis-api/[RiskEvidenceSynthesis] - -.^| Specialized - Quality Reporting & Testing | https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fhir-r4-measure-library/[Measure] + -https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fhir-r4-measurereport-library/[MeasureReport] + -https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fhir-r4-testscript-library/[TestScript] + -https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fhir-r4-testreport-library/[TestReport] -| https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fhir-r4-measure-api/[Measure] + -https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fhir-r4-measurereport-api/[MeasureReport] + -https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fhir-r4-testscript-api/[TestScript] + -https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fhir-r4-testreport-api/[TestReport] - -.^| Specialized - Medication Definition | https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fhir-r4-medicinalproduct-library/[MedicinalProduct] ^[u]^ + -https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fhir-r4-medicinalproductauthorization-library/[MedicinalProductAuthorization] ^[u]^ + -https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fhir-r4-medicinalproductcontraindication-library/[MedicinalProductContraindication] + -https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fhir-r4-medicinalproductindication-library/[MedicinalProductIndication] + -https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fhir-r4-medicinalproductingredient-library/[MedicinalProductIngredient] ^[u]^ + -https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fhir-r4-medicinalproductinteraction-library/[MedicinalProductInteraction] + -https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fhir-r4-medicinalproductmanufactured-library/[MedicinalProductManufactured] + -https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fhir-r4-medicinalproductpackaged-library/[MedicinalProductPackaged] ^[u]^ + -https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fhir-r4-medicinalproductpharmaceutical-library/[MedicinalProductPharmaceutical] ^[u]^ + -https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fhir-r4-medicinalproductundesirableeffect-library/[MedicinalProductUndesirableEffect] + -https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fhir-r4-substancenucleicacid-library/[SubstanceNucleicAcid] + -https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fhir-r4-substancepolymer-library/[SubstancePolymer] ^[u]^ + -https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fhir-r4-substanceprotein-library/[SubstanceProtein] + -https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fhir-r4-substancereferenceinformation-library/[SubstanceReferenceInformation] ^[u]^ + -https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fhir-r4-substancespecification-library/[SubstanceSpecification] ^[u]^ + -https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fhir-r4-substancesourcematerial-library/[SubstanceSourceMaterial] -| https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fhir-r4-medicinalproduct-api/[MedicinalProduct] ^[u]^ + -https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fhir-r4-medicinalproductauthorization-api/[MedicinalProductAuthorization] ^[u]^ + -https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fhir-r4-medicinalproductcontraindication-api/[MedicinalProductContraindication] + -https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fhir-r4-medicinalproductindication-api/[MedicinalProductIndication] + -https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fhir-r4-medicinalproductingredient-api/[MedicinalProductIngredient] ^[u]^ + -https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fhir-r4-medicinalproductinteraction-api/[MedicinalProductInteraction] + -https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fhir-r4-medicinalproductmanufactured-api/[MedicinalProductManufactured] + -https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fhir-r4-medicinalproductpackaged-api/[MedicinalProductPackaged] ^[u]^ + -https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fhir-r4-medicinalproductpharmaceutical-api/[MedicinalProductPharmaceutical] ^[u]^ + -https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fhir-r4-medicinalproductundesirableeffect-api/[MedicinalProductUndesirableEffect] + -https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fhir-r4-substancenucleicacid-api/[SubstanceNucleicAcid] + -https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fhir-r4-substancepolymer-api/[SubstancePolymer] ^[u]^ + -https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fhir-r4-substanceprotein-api/[SubstanceProtein] + -https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fhir-r4-substancereferenceinformation-api/[SubstanceReferenceInformation] ^[u]^ + -https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fhir-r4-substancespecification-api/[SubstanceSpecification] ^[u]^ + -https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fhir-r4-substancesourcematerial-api/[SubstanceSourceMaterial] +| https://anypoint.mulesoft.com/exchange/org.mule.examples/fhir-r4-claim-library/[Claim] + +https://anypoint.mulesoft.com/exchange/org.mule.examples/fhir-r4-claimresponse-library/[ClaimResponse] + +https://anypoint.mulesoft.com/exchange/org.mule.examples/fhir-r4-invoice-library/[Invoice] +| https://anypoint.mulesoft.com/exchange/org.mule.examples/fhir-r4-claim-api/[Claim] + +https://anypoint.mulesoft.com/exchange/org.mule.examples/fhir-r4-claimresponse-api/[ClaimResponse] + +https://anypoint.mulesoft.com/exchange/org.mule.examples/fhir-r4-invoice-api/[Invoice] + +.^| Financial - Payment | https://anypoint.mulesoft.com/exchange/org.mule.examples/fhir-r4-paymentnotice-library/[PaymentNotice] + +https://anypoint.mulesoft.com/exchange/org.mule.examples/fhir-r4-paymentreconciliation-library/[PaymentReconcilliation] +| https://anypoint.mulesoft.com/exchange/org.mule.examples/fhir-r4-paymentnotice-api/[PaymentNotice] + +https://anypoint.mulesoft.com/exchange/org.mule.examples/fhir-r4-paymentreconciliation-api/[PaymentReconcilliation] + +.^| Financial - General | https://anypoint.mulesoft.com/exchange/org.mule.examples/fhir-r4-account-library/[Account] + +https://anypoint.mulesoft.com/exchange/org.mule.examples/fhir-r4-chargeitem-library/[ChargeItem] + +https://anypoint.mulesoft.com/exchange/org.mule.examples/fhir-r4-chargeitemdefinition-library/[ChargeItemDefinition] + +https://anypoint.mulesoft.com/exchange/org.mule.examples/fhir-r4-contract-library/[Contract] + +https://anypoint.mulesoft.com/exchange/org.mule.examples/fhir-r4-explanationofbenefit-library/[ExplanationOfBenefit] + +https://anypoint.mulesoft.com/exchange/org.mule.examples/fhir-r4-insuranceplan-library/[InsurancePlan] +| https://anypoint.mulesoft.com/exchange/org.mule.examples/fhir-r4-account-api/[Account] + +https://anypoint.mulesoft.com/exchange/org.mule.examples/fhir-r4-chargeitem-api/[ChargeItem] + +https://anypoint.mulesoft.com/exchange/org.mule.examples/fhir-r4-chargeitemdefinition-api/[ChargeItemDefinition] + +https://anypoint.mulesoft.com/exchange/org.mule.examples/fhir-r4-contract-api/[Contract] + +https://anypoint.mulesoft.com/exchange/org.mule.examples/fhir-r4-explanationofbenefit-api/[ExplanationOfBenefit] + +https://anypoint.mulesoft.com/exchange/org.mule.examples/fhir-r4-insuranceplan-api/[InsurancePlan] + +.^| Specialized - Public Health & Research | https://anypoint.mulesoft.com/exchange/org.mule.examples/fhir-r4-researchstudy-library/[ResearchStudy] + +https://anypoint.mulesoft.com/exchange/org.mule.examples/fhir-r4-researchsubject-library/[ResearchSubject] +| https://anypoint.mulesoft.com/exchange/org.mule.examples/fhir-r4-researchstudy-api/[ResearchStudy] + +https://anypoint.mulesoft.com/exchange/org.mule.examples/fhir-r4-researchsubject-api/[ResearchSubject] + +.^| Specialized - Definitional Artifacts | https://anypoint.mulesoft.com/exchange/org.mule.examples/fhir-r4-activitydefinition-library/[ActivityDefinition] + +https://anypoint.mulesoft.com/exchange/org.mule.examples/fhir-r4-devicedefinition-library/[DeviceDefinition] + +https://anypoint.mulesoft.com/exchange/org.mule.examples/fhir-r4-eventdefinition-library/[EventDefinition] + +https://anypoint.mulesoft.com/exchange/org.mule.examples/fhir-r4-observationdefinition-library/[ObservationDefinition] ^[u]^ + +https://anypoint.mulesoft.com/exchange/org.mule.examples/fhir-r4-plandefinition-library/[PlanDefinition] + +https://anypoint.mulesoft.com/exchange/org.mule.examples/fhir-r4-questionnaire-library/[Questionnaire] + +https://anypoint.mulesoft.com/exchange/org.mule.examples/fhir-r4-specimendefinition-library/[SpecimenDefinition] +| https://anypoint.mulesoft.com/exchange/org.mule.examples/fhir-r4-activitydefinition-api/[ActivityDefinition] + +https://anypoint.mulesoft.com/exchange/org.mule.examples/fhir-r4-devicedefinition-api/[DeviceDefinition] + +https://anypoint.mulesoft.com/exchange/org.mule.examples/fhir-r4-eventdefinition-api/[EventDefinition] + +https://anypoint.mulesoft.com/exchange/org.mule.examples/fhir-r4-observationdefinition-api/[ObservationDefinition] ^[u]^ + +https://anypoint.mulesoft.com/exchange/org.mule.examples/fhir-r4-plandefinition-api/[PlanDefinition] + +https://anypoint.mulesoft.com/exchange/org.mule.examples/fhir-r4-questionnaire-api/[Questionnaire] + +https://anypoint.mulesoft.com/exchange/org.mule.examples/fhir-r4-specimendefinition-api/[SpecimenDefinition] + +.^| Specialized - Evidence Based Medicine | https://anypoint.mulesoft.com/exchange/org.mule.examples/fhir-r4-researchdefinition-library/[ResearchDefinition] + +https://anypoint.mulesoft.com/exchange/org.mule.examples/fhir-r4-researchelementdefinition-library/[ResearchElementDefinition] + +https://anypoint.mulesoft.com/exchange/org.mule.examples/fhir-r4-evidence-library/[Evidence] + +https://anypoint.mulesoft.com/exchange/org.mule.examples/fhir-r4-evidencevariable-library/[EvidenceVariable] + +https://anypoint.mulesoft.com/exchange/org.mule.examples/fhir-r4-effectevidencesynthesis-library/[EffectEvidenceSynthesis] + +https://anypoint.mulesoft.com/exchange/org.mule.examples/fhir-r4-riskevidencesynthesis-library/[RiskEvidenceSynthesis] +| https://anypoint.mulesoft.com/exchange/org.mule.examples/fhir-r4-researchdefinition-api/[ResearchDefinition] + +https://anypoint.mulesoft.com/exchange/org.mule.examples/fhir-r4-researchelementdefinition-api/[ResearchElementDefinition] + +https://anypoint.mulesoft.com/exchange/org.mule.examples/fhir-r4-evidence-api/[Evidence] + +https://anypoint.mulesoft.com/exchange/org.mule.examples/fhir-r4-evidencevariable-api/[EvidenceVariable] + +https://anypoint.mulesoft.com/exchange/org.mule.examples/fhir-r4-effectevidencesynthesis-api/[EffectEvidenceSynthesis] + +https://anypoint.mulesoft.com/exchange/org.mule.examples/fhir-r4-riskevidencesynthesis-api/[RiskEvidenceSynthesis] + +.^| Specialized - Quality Reporting & Testing | https://anypoint.mulesoft.com/exchange/org.mule.examples/fhir-r4-measure-library/[Measure] + +https://anypoint.mulesoft.com/exchange/org.mule.examples/fhir-r4-measurereport-library/[MeasureReport] + +https://anypoint.mulesoft.com/exchange/org.mule.examples/fhir-r4-testscript-library/[TestScript] + +https://anypoint.mulesoft.com/exchange/org.mule.examples/fhir-r4-testreport-library/[TestReport] +| https://anypoint.mulesoft.com/exchange/org.mule.examples/fhir-r4-measure-api/[Measure] + +https://anypoint.mulesoft.com/exchange/org.mule.examples/fhir-r4-measurereport-api/[MeasureReport] + +https://anypoint.mulesoft.com/exchange/org.mule.examples/fhir-r4-testscript-api/[TestScript] + +https://anypoint.mulesoft.com/exchange/org.mule.examples/fhir-r4-testreport-api/[TestReport] + +.^| Specialized - Medication Definition | https://anypoint.mulesoft.com/exchange/org.mule.examples/fhir-r4-medicinalproduct-library/[MedicinalProduct] ^[u]^ + +https://anypoint.mulesoft.com/exchange/org.mule.examples/fhir-r4-medicinalproductauthorization-library/[MedicinalProductAuthorization] ^[u]^ + +https://anypoint.mulesoft.com/exchange/org.mule.examples/fhir-r4-medicinalproductcontraindication-library/[MedicinalProductContraindication] + +https://anypoint.mulesoft.com/exchange/org.mule.examples/fhir-r4-medicinalproductindication-library/[MedicinalProductIndication] + +https://anypoint.mulesoft.com/exchange/org.mule.examples/fhir-r4-medicinalproductingredient-library/[MedicinalProductIngredient] ^[u]^ + +https://anypoint.mulesoft.com/exchange/org.mule.examples/fhir-r4-medicinalproductinteraction-library/[MedicinalProductInteraction] + +https://anypoint.mulesoft.com/exchange/org.mule.examples/fhir-r4-medicinalproductmanufactured-library/[MedicinalProductManufactured] + +https://anypoint.mulesoft.com/exchange/org.mule.examples/fhir-r4-medicinalproductpackaged-library/[MedicinalProductPackaged] ^[u]^ + +https://anypoint.mulesoft.com/exchange/org.mule.examples/fhir-r4-medicinalproductpharmaceutical-library/[MedicinalProductPharmaceutical] ^[u]^ + +https://anypoint.mulesoft.com/exchange/org.mule.examples/fhir-r4-medicinalproductundesirableeffect-library/[MedicinalProductUndesirableEffect] + +https://anypoint.mulesoft.com/exchange/org.mule.examples/fhir-r4-substancenucleicacid-library/[SubstanceNucleicAcid] + +https://anypoint.mulesoft.com/exchange/org.mule.examples/fhir-r4-substancepolymer-library/[SubstancePolymer] ^[u]^ + +https://anypoint.mulesoft.com/exchange/org.mule.examples/fhir-r4-substanceprotein-library/[SubstanceProtein] + +https://anypoint.mulesoft.com/exchange/org.mule.examples/fhir-r4-substancereferenceinformation-library/[SubstanceReferenceInformation] ^[u]^ + +https://anypoint.mulesoft.com/exchange/org.mule.examples/fhir-r4-substancespecification-library/[SubstanceSpecification] ^[u]^ + +https://anypoint.mulesoft.com/exchange/org.mule.examples/fhir-r4-substancesourcematerial-library/[SubstanceSourceMaterial] +| https://anypoint.mulesoft.com/exchange/org.mule.examples/fhir-r4-medicinalproduct-api/[MedicinalProduct] ^[u]^ + +https://anypoint.mulesoft.com/exchange/org.mule.examples/fhir-r4-medicinalproductauthorization-api/[MedicinalProductAuthorization] ^[u]^ + +https://anypoint.mulesoft.com/exchange/org.mule.examples/fhir-r4-medicinalproductcontraindication-api/[MedicinalProductContraindication] + +https://anypoint.mulesoft.com/exchange/org.mule.examples/fhir-r4-medicinalproductindication-api/[MedicinalProductIndication] + +https://anypoint.mulesoft.com/exchange/org.mule.examples/fhir-r4-medicinalproductingredient-api/[MedicinalProductIngredient] ^[u]^ + +https://anypoint.mulesoft.com/exchange/org.mule.examples/fhir-r4-medicinalproductinteraction-api/[MedicinalProductInteraction] + +https://anypoint.mulesoft.com/exchange/org.mule.examples/fhir-r4-medicinalproductmanufactured-api/[MedicinalProductManufactured] + +https://anypoint.mulesoft.com/exchange/org.mule.examples/fhir-r4-medicinalproductpackaged-api/[MedicinalProductPackaged] ^[u]^ + +https://anypoint.mulesoft.com/exchange/org.mule.examples/fhir-r4-medicinalproductpharmaceutical-api/[MedicinalProductPharmaceutical] ^[u]^ + +https://anypoint.mulesoft.com/exchange/org.mule.examples/fhir-r4-medicinalproductundesirableeffect-api/[MedicinalProductUndesirableEffect] + +https://anypoint.mulesoft.com/exchange/org.mule.examples/fhir-r4-substancenucleicacid-api/[SubstanceNucleicAcid] + +https://anypoint.mulesoft.com/exchange/org.mule.examples/fhir-r4-substancepolymer-api/[SubstancePolymer] ^[u]^ + +https://anypoint.mulesoft.com/exchange/org.mule.examples/fhir-r4-substanceprotein-api/[SubstanceProtein] + +https://anypoint.mulesoft.com/exchange/org.mule.examples/fhir-r4-substancereferenceinformation-api/[SubstanceReferenceInformation] ^[u]^ + +https://anypoint.mulesoft.com/exchange/org.mule.examples/fhir-r4-substancespecification-api/[SubstanceSpecification] ^[u]^ + +https://anypoint.mulesoft.com/exchange/org.mule.examples/fhir-r4-substancesourcematerial-api/[SubstanceSourceMaterial] |=== NOTE: @@ -364,7 +364,7 @@ This FHIR Error API policy can be used to capture error responses and format the See the following page to learn more about the FHIR Error API Policy: -* https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fhir-error-policy/[FHIR Error API Policy] +* https://anypoint.mulesoft.com/exchange/org.mule.examples/fhir-error-policy/[FHIR Error API Policy] == See Also diff --git a/healthcare/2.21/modules/ROOT/pages/fhir-r4-us-core-profiles.adoc b/healthcare/2.21/modules/ROOT/pages/fhir-r4-us-core-profiles.adoc index bd9f34445..22b48f675 100644 --- a/healthcare/2.21/modules/ROOT/pages/fhir-r4-us-core-profiles.adoc +++ b/healthcare/2.21/modules/ROOT/pages/fhir-r4-us-core-profiles.adoc @@ -2,7 +2,7 @@ The MuleSoft Accelerator for Healthcare provides a library of United States Core Data for Interoperability (USCDI) and FHIR R4 resources to help healthcare developers adhere to interoperability needs and jumpstart the development of healthcare digital transformation initiatives. -You can also use the https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fhir-error-policy/[FHIR Error API Policy] to capture error responses and format them in an FHIR OperationOutcome-compliant format, since Anypoint Platform's out-of-the-box (OOTB) policies do not provide error messages in an FHIR-compliant format. This policy can also be used with other OOTB API policies provided in Anypoint Platform, such as OAuth or JWT. +You can also use the https://anypoint.mulesoft.com/exchange/org.mule.examples/fhir-error-policy/[FHIR Error API Policy] to capture error responses and format them in an FHIR OperationOutcome-compliant format, since Anypoint Platform's out-of-the-box (OOTB) policies do not provide error messages in an FHIR-compliant format. This policy can also be used with other OOTB API policies provided in Anypoint Platform, such as OAuth or JWT. For the list of all FHIR R4 assets, please refer to xref:fhir-r4-resources.adoc[this link]. @@ -15,68 +15,68 @@ _API specifications, data types, and libraries built to meet compliance with FHI | Module | Library | API specification | Data Types -| https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fhir-r4-commons-library/[FHIR R4 Common Library] + -https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fhir-r4-resource-types-library/[Resource Types Library] + +| https://anypoint.mulesoft.com/exchange/org.mule.examples/fhir-r4-commons-library/[FHIR R4 Common Library] + +https://anypoint.mulesoft.com/exchange/org.mule.examples/fhir-r4-resource-types-library/[Resource Types Library] + | NA | Foundation -| https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fhir-r4-documentreference-library/[DocumentReference Library] -| https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fhir-r4-documentreference-api/[DocumentReference API] +| https://anypoint.mulesoft.com/exchange/org.mule.examples/fhir-r4-documentreference-library/[DocumentReference Library] +| https://anypoint.mulesoft.com/exchange/org.mule.examples/fhir-r4-documentreference-api/[DocumentReference API] | Security -| https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fhir-r4-provenance-library/[Provenance Library] -| https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fhir-r4-provenance-api/[Provenance API] +| https://anypoint.mulesoft.com/exchange/org.mule.examples/fhir-r4-provenance-library/[Provenance Library] +| https://anypoint.mulesoft.com/exchange/org.mule.examples/fhir-r4-provenance-api/[Provenance API] | Conformance -| https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fhir-r4-capabilitystatement-library/[CapabilityStatement Library] -| https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fhir-r4-capabilitystatement-api/[CapabilityStatement API] +| https://anypoint.mulesoft.com/exchange/org.mule.examples/fhir-r4-capabilitystatement-library/[CapabilityStatement Library] +| https://anypoint.mulesoft.com/exchange/org.mule.examples/fhir-r4-capabilitystatement-api/[CapabilityStatement API] | Administration -| https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fhir-r4-us-core-patient-library/[Patient Library] + -https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fhir-r4-practitioner-library/[Practitioner Library] + -https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fhir-r4-practitionerrole-library/[PractitionerRole Library] + -https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fhir-r4-device-library/[Device Library] + -https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fhir-r4-organization-library/[Organization Library] + -https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fhir-r4-location-library/[Location Library] + -https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fhir-r4-careteam-library/[CareTeam Library] + -https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fhir-r4-encounter-library/[Encounter Library] + - -| https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fhir-r4-us-core-patient-api/[Patient API*] + -https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fhir-r4-practitioner-api/[Practitioner API] + -https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fhir-r4-practitionerrole-api/[PractitionerRole API] + -https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fhir-r4-device-api/[Device API] + -https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fhir-r4-organization-api/[Organization API] + -https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fhir-r4-location-api/[Location API] + -https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fhir-r4-careteam-api/[CareTeam API] + -https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fhir-r4-encounter-api/[Encounter API] +| https://anypoint.mulesoft.com/exchange/org.mule.examples/fhir-r4-us-core-patient-library/[Patient Library] + +https://anypoint.mulesoft.com/exchange/org.mule.examples/fhir-r4-practitioner-library/[Practitioner Library] + +https://anypoint.mulesoft.com/exchange/org.mule.examples/fhir-r4-practitionerrole-library/[PractitionerRole Library] + +https://anypoint.mulesoft.com/exchange/org.mule.examples/fhir-r4-device-library/[Device Library] + +https://anypoint.mulesoft.com/exchange/org.mule.examples/fhir-r4-organization-library/[Organization Library] + +https://anypoint.mulesoft.com/exchange/org.mule.examples/fhir-r4-location-library/[Location Library] + +https://anypoint.mulesoft.com/exchange/org.mule.examples/fhir-r4-careteam-library/[CareTeam Library] + +https://anypoint.mulesoft.com/exchange/org.mule.examples/fhir-r4-encounter-library/[Encounter Library] + + +| https://anypoint.mulesoft.com/exchange/org.mule.examples/fhir-r4-us-core-patient-api/[Patient API*] + +https://anypoint.mulesoft.com/exchange/org.mule.examples/fhir-r4-practitioner-api/[Practitioner API] + +https://anypoint.mulesoft.com/exchange/org.mule.examples/fhir-r4-practitionerrole-api/[PractitionerRole API] + +https://anypoint.mulesoft.com/exchange/org.mule.examples/fhir-r4-device-api/[Device API] + +https://anypoint.mulesoft.com/exchange/org.mule.examples/fhir-r4-organization-api/[Organization API] + +https://anypoint.mulesoft.com/exchange/org.mule.examples/fhir-r4-location-api/[Location API] + +https://anypoint.mulesoft.com/exchange/org.mule.examples/fhir-r4-careteam-api/[CareTeam API] + +https://anypoint.mulesoft.com/exchange/org.mule.examples/fhir-r4-encounter-api/[Encounter API] | Clinical -| https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fhir-r4-us-core-allergyintolerance-library/[AllergyIntolerance Library] + -https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fhir-r4-careplan-library/[CarePlan Library] + -https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fhir-r4-goal-library/[Goal Library] + -https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fhir-r4-procedure-library/[Procedure Library] + -https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fhir-r4-us-core-condition-library/[Condition Library] + - -| https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fhir-r4-us-core-allergyintolerance-api/[AllergyIntolerance API*] + -https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fhir-r4-careplan-api/[CarePlan API] + -https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fhir-r4-goal-api/[Goal API] + -https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fhir-r4-procedure-api/[Procedure API] + -https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fhir-r4-us-core-condition-api/[Condition API] +| https://anypoint.mulesoft.com/exchange/org.mule.examples/fhir-r4-us-core-allergyintolerance-library/[AllergyIntolerance Library] + +https://anypoint.mulesoft.com/exchange/org.mule.examples/fhir-r4-careplan-library/[CarePlan Library] + +https://anypoint.mulesoft.com/exchange/org.mule.examples/fhir-r4-goal-library/[Goal Library] + +https://anypoint.mulesoft.com/exchange/org.mule.examples/fhir-r4-procedure-library/[Procedure Library] + +https://anypoint.mulesoft.com/exchange/org.mule.examples/fhir-r4-us-core-condition-library/[Condition Library] + + +| https://anypoint.mulesoft.com/exchange/org.mule.examples/fhir-r4-us-core-allergyintolerance-api/[AllergyIntolerance API*] + +https://anypoint.mulesoft.com/exchange/org.mule.examples/fhir-r4-careplan-api/[CarePlan API] + +https://anypoint.mulesoft.com/exchange/org.mule.examples/fhir-r4-goal-api/[Goal API] + +https://anypoint.mulesoft.com/exchange/org.mule.examples/fhir-r4-procedure-api/[Procedure API] + +https://anypoint.mulesoft.com/exchange/org.mule.examples/fhir-r4-us-core-condition-api/[Condition API] | Diagnostics -| https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fhir-r4-us-core-observation-library/[Observation Library] + -https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fhir-r4-diagnosticreport-library/[DiagnosticReport Library] -| https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fhir-r4-us-core-observation-api/[Observation API*] + -https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fhir-r4-diagnosticreport-api/[DiagnosticReport API] +| https://anypoint.mulesoft.com/exchange/org.mule.examples/fhir-r4-us-core-observation-library/[Observation Library] + +https://anypoint.mulesoft.com/exchange/org.mule.examples/fhir-r4-diagnosticreport-library/[DiagnosticReport Library] +| https://anypoint.mulesoft.com/exchange/org.mule.examples/fhir-r4-us-core-observation-api/[Observation API*] + +https://anypoint.mulesoft.com/exchange/org.mule.examples/fhir-r4-diagnosticreport-api/[DiagnosticReport API] | Medications -| https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fhir-r4-immunization-library/[Immunization Library] + -https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fhir-r4-medication-library/[Medication Library] + -https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fhir-r4-medicationrequest-library/[MedicationRequest Library] -| https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fhir-r4-immunization-api/[Immunization API] + -https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fhir-r4-medication-api/[Medication API] + -https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fhir-r4-medicationrequest-api/[MedicationRequest API] +| https://anypoint.mulesoft.com/exchange/org.mule.examples/fhir-r4-immunization-library/[Immunization Library] + +https://anypoint.mulesoft.com/exchange/org.mule.examples/fhir-r4-medication-library/[Medication Library] + +https://anypoint.mulesoft.com/exchange/org.mule.examples/fhir-r4-medicationrequest-library/[MedicationRequest Library] +| https://anypoint.mulesoft.com/exchange/org.mule.examples/fhir-r4-immunization-api/[Immunization API] + +https://anypoint.mulesoft.com/exchange/org.mule.examples/fhir-r4-medication-api/[Medication API] + +https://anypoint.mulesoft.com/exchange/org.mule.examples/fhir-r4-medicationrequest-api/[MedicationRequest API] |=== _APIs marked with `*` have both FHIR R4 and US Core-specific Library and API specification available._ diff --git a/healthcare/2.21/modules/ROOT/pages/hl7-v2-fhir-converter.adoc b/healthcare/2.21/modules/ROOT/pages/hl7-v2-fhir-converter.adoc index 737ae28d6..d750bb00e 100644 --- a/healthcare/2.21/modules/ROOT/pages/hl7-v2-fhir-converter.adoc +++ b/healthcare/2.21/modules/ROOT/pages/hl7-v2-fhir-converter.adoc @@ -1,10 +1,10 @@ = HL7 v2 to FHIR Converter -The https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/hc-accelerator-hl7v2-to-fhir-sys-api[HL7 v2 to FHIR converter] comes with a ready to use template for HL7 v2 to FHIR conversion, which is based on the guidance provided by the https://build.fhir.org/ig/HL7/v2-to-fhir[HL7 v2 to FHIR Implementation Guide]. This template can be extended or modified to meet specific conversion requirements. +The https://anypoint.mulesoft.com/exchange/org.mule.examples/hc-accelerator-hl7v2-to-fhir-sys-api[HL7 v2 to FHIR converter] comes with a ready to use template for HL7 v2 to FHIR conversion, which is based on the guidance provided by the https://build.fhir.org/ig/HL7/v2-to-fhir[HL7 v2 to FHIR Implementation Guide]. This template can be extended or modified to meet specific conversion requirements. == Functional diagram -image:https://www.mulesoft.com/ext/solutions/draft/images/hc-hl7v2-to-fhir-usecase-diagram.png[hc-hl7v2-to-fhir-usecase-diagram.png,799,align="center"] +image:https://www.mulesoft.com/ext/solutions/images/hc-hl7v2-to-fhir-usecase-diagram.png[hc-hl7v2-to-fhir-usecase-diagram.png,799,align="center"] == Advantages diff --git a/healthcare/2.21/modules/ROOT/pages/index.adoc b/healthcare/2.21/modules/ROOT/pages/index.adoc index 583c85e5e..ac939e42e 100644 --- a/healthcare/2.21/modules/ROOT/pages/index.adoc +++ b/healthcare/2.21/modules/ROOT/pages/index.adoc @@ -9,13 +9,13 @@ For solutions related to life sciences, the xref:life-sciences::index.adoc[MuleS The following describes the use cases supported by the MuleSoft Accelerator for Healthcare: -* https://www.anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/mulesoft-accelerator-for-healthcare/minor/{hls-version}/pages/Use%20case%201%20-%20Patient%20360/[Patient 360^] — This use case accelerates Patient 360 efforts by providing pre-built APIs and implementation templates to integrate critical data from EHRs with other emerging technologies and applications. This solution provides both HL7 v2 and FHIR-based capabilities to allow organizations to support a variety of use cases and realize value regardless of the industry standard that is present in their organization's ecosystem. -* https://www.anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/mulesoft-accelerator-for-healthcare/minor/{hls-version}/pages/Use%20case%202%20-%20CMS%20Interoperability/[CMS Interoperability^] — Includes assets to help you meet CMS Interoperability and Patient Access final rule. -* https://www.anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/mulesoft-accelerator-for-healthcare/minor/{hls-version}/pages/Use%20case%203%20-%20Labs%20integration/[Labs integration^] — Includes the The Electronic Laboratory Reporting (ELR) to CalREDIE implementation template, which helps you transmit laboratory reports that identify a notifiable condition to public health agencies (for example, California Department of Public Health). -* https://www.anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/mulesoft-accelerator-for-healthcare/minor/{hls-version}/pages/Use%20case%204%20-%20Appointment%20scheduling/[Appointment scheduling^] — Includes the Appointment Scheduling Process API for both Cerner and Epic, which enables call center agents to schedule, update, and cancel appointments on behalf of the patient. See the implementation template for more information. -* https://www.anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/mulesoft-accelerator-for-healthcare/minor/{hls-version}/pages/Use%20case%205%20-%20Benefits%20and%20eligibility%20verification/[Benefits and eligibility verification^] — Enables call center agents and care staff to perform real-time benefits and eligibility verification. Providers can electronically verify a patient's insurance coverage in real-time for medical treatment directly within Salesforce Health Cloud. -* https://www.anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/mulesoft-accelerator-for-healthcare/minor/{hls-version}/pages/Use%20case%206%20-%20Prior%20Authorization/[Prior Authorization^] — Includes CRD, DTR, and PAS API specifications and implementation templates to automate the prior authorization process for more immediate authorizations, leading to better outcomes and increased satisfaction for patients, providers, and payers. -* https://www.anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/mulesoft-accelerator-for-healthcare/minor/{hls-version}/pages/Use%20case%207%20-%20Population%20health%20management/[Population health management^] - Convert and surface valuable population health data into Amazon HealthLake to improve clinical outcomes. +* https://www.anypoint.mulesoft.com/exchange/org.mule.examples/mulesoft-accelerator-for-healthcare/minor/{hls-version}/pages/Use%20case%201%20-%20Patient%20360/[Patient 360^] — This use case accelerates Patient 360 efforts by providing pre-built APIs and implementation templates to integrate critical data from EHRs with other emerging technologies and applications. This solution provides both HL7 v2 and FHIR-based capabilities to allow organizations to support a variety of use cases and realize value regardless of the industry standard that is present in their organization's ecosystem. +* https://www.anypoint.mulesoft.com/exchange/org.mule.examples/mulesoft-accelerator-for-healthcare/minor/{hls-version}/pages/Use%20case%202%20-%20CMS%20Interoperability/[CMS Interoperability^] — Includes assets to help you meet CMS Interoperability and Patient Access final rule. +* https://www.anypoint.mulesoft.com/exchange/org.mule.examples/mulesoft-accelerator-for-healthcare/minor/{hls-version}/pages/Use%20case%203%20-%20Labs%20integration/[Labs integration^] — Includes the The Electronic Laboratory Reporting (ELR) to CalREDIE implementation template, which helps you transmit laboratory reports that identify a notifiable condition to public health agencies (for example, California Department of Public Health). +* https://www.anypoint.mulesoft.com/exchange/org.mule.examples/mulesoft-accelerator-for-healthcare/minor/{hls-version}/pages/Use%20case%204%20-%20Appointment%20scheduling/[Appointment scheduling^] — Includes the Appointment Scheduling Process API for both Cerner and Epic, which enables call center agents to schedule, update, and cancel appointments on behalf of the patient. See the implementation template for more information. +* https://www.anypoint.mulesoft.com/exchange/org.mule.examples/mulesoft-accelerator-for-healthcare/minor/{hls-version}/pages/Use%20case%205%20-%20Benefits%20and%20eligibility%20verification/[Benefits and eligibility verification^] — Enables call center agents and care staff to perform real-time benefits and eligibility verification. Providers can electronically verify a patient's insurance coverage in real-time for medical treatment directly within Salesforce Health Cloud. +* https://www.anypoint.mulesoft.com/exchange/org.mule.examples/mulesoft-accelerator-for-healthcare/minor/{hls-version}/pages/Use%20case%206%20-%20Prior%20Authorization/[Prior Authorization^] — Includes CRD, DTR, and PAS API specifications and implementation templates to automate the prior authorization process for more immediate authorizations, leading to better outcomes and increased satisfaction for patients, providers, and payers. +* https://www.anypoint.mulesoft.com/exchange/org.mule.examples/mulesoft-accelerator-for-healthcare/minor/{hls-version}/pages/Use%20case%207%20-%20Population%20health%20management/[Population health management^] - Convert and surface valuable population health data into Amazon HealthLake to improve clinical outcomes. === Use Case Agnostic Assets @@ -32,4 +32,4 @@ The following use-case agnostic assets are also available: * xref:prerequisites.adoc[Prerequisites] * xref:fhir-r4-assets.adoc[Available Assets] * xref:release-notes::accelerators/healthcare/healthcare-release-notes.adoc[Release Notes] -* https://www.anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/mulesoft-accelerator-for-healthcare/[MuleSoft Accelerator for Healthcare on Exchange^] +* https://www.anypoint.mulesoft.com/exchange/org.mule.examples/mulesoft-accelerator-for-healthcare/[MuleSoft Accelerator for Healthcare on Exchange^] diff --git a/healthcare/2.21/modules/ROOT/pages/sfdc-data-cloud-setup-guide.adoc b/healthcare/2.21/modules/ROOT/pages/sfdc-data-cloud-setup-guide.adoc index 84494a74b..0eb1a7e3e 100644 --- a/healthcare/2.21/modules/ROOT/pages/sfdc-data-cloud-setup-guide.adoc +++ b/healthcare/2.21/modules/ROOT/pages/sfdc-data-cloud-setup-guide.adoc @@ -1,7 +1,7 @@ = Salesforce Data Cloud Setup Guide :hls-version: 2.20 -The following provides guidance on Salesforce Data Cloud setup required for the https://www.anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/mulesoft-accelerator-for-healthcare/minor/{hls-version}/pages/Use%20case%207%20-%20Population%20health%20management/[Population Health Management] use case. +The following provides guidance on Salesforce Data Cloud setup required for the https://www.anypoint.mulesoft.com/exchange/org.mule.examples/mulesoft-accelerator-for-healthcare/minor/{hls-version}/pages/Use%20case%207%20-%20Population%20health%20management/[Population Health Management] use case. * <> * <> @@ -25,7 +25,7 @@ Connectors are specialized data streams that communicate with external sources t Customer Data Platform has connectors for: Marketing Cloud Email Studio, MobileConnect, MobilePush, Marketing Cloud Data Extensions, for Salesforce CRM, Ingestion API, Interaction Studio, and for data outside Salesforce via cloud storage providers. -The https://www.anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/mulesoft-accelerator-for-healthcare/minor/{hls-version}/pages/Use%20case%207%20-%20Population%20health%20management/[Population Health Management] use case uses the following connectors to ingest data into cdp: +The https://www.anypoint.mulesoft.com/exchange/org.mule.examples/mulesoft-accelerator-for-healthcare/minor/{hls-version}/pages/Use%20case%207%20-%20Population%20health%20management/[Population Health Management] use case uses the following connectors to ingest data into cdp: * Salesforce CRM - to connect data from a Salesforce Health Cloud instance to Data Cloud * Ingestion API - to connect data from external source systems like Azure, Epic, Cerner, and other EHR systems via MuleSoft's CDP connector. @@ -50,7 +50,7 @@ Follow the below steps to create connection to your Salesforce Health Cloud org. After you create your Customer Data Platform instance and set up your Salesforce Health Cloud connection, you can install standard data bundles that are powered by data kits to deploy data within Customer Data Platform. -For the https://www.anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/mulesoft-accelerator-for-healthcare/minor/{hls-version}/pages/Use%20case%207%20-%20Population%20health%20management/[Population Health Management] use case, Service Cloud bundle is installed. Refer https://help.salesforce.com/s/articleView?id=sf.c360_a_install_standard_data_bundles_powered_by_data_kits.htm&type=5[link] to install the bundle. +For the https://www.anypoint.mulesoft.com/exchange/org.mule.examples/mulesoft-accelerator-for-healthcare/minor/{hls-version}/pages/Use%20case%207%20-%20Population%20health%20management/[Population Health Management] use case, Service Cloud bundle is installed. Refer https://help.salesforce.com/s/articleView?id=sf.c360_a_install_standard_data_bundles_powered_by_data_kits.htm&type=5[link] to install the bundle. === Ingestion API @@ -63,14 +63,14 @@ Follow the steps in each section below to setup and configure ingestion API to p . In Data Cloud, select Data Cloud Setup. . Click Ingestion API. . Click New, enter a name for the API source, then click Save. On the details page for the new connector, you must upload a schema file in OpenAPI (OAS) format with a `.yaml` file extension. The schema file describes how data transferred via the API is structured. *Note:* Ingestion API schemas have set requirements - review the schema requirements before ingestion. -. Click Upload Schema and navigate to the location of the file you want to use. Select the file and click Open. For the https://www.anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/mulesoft-accelerator-for-healthcare/minor/{hls-version}/pages/Use%20case%207%20-%20Population%20health%20management/[Population Health Management] use case the schema file `mule-hls-cdp-connector-schema.yaml` is available under `/src/test/resources` of the Implementation Template https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/hls-salesforce-cdp-sys-api[HLS CDP System API]. +. Click Upload Schema and navigate to the location of the file you want to use. Select the file and click Open. For the https://www.anypoint.mulesoft.com/exchange/org.mule.examples/mulesoft-accelerator-for-healthcare/minor/{hls-version}/pages/Use%20case%207%20-%20Population%20health%20management/[Population Health Management] use case the schema file `mule-hls-cdp-connector-schema.yaml` is available under `/src/test/resources` of the Implementation Template https://anypoint.mulesoft.com/exchange/org.mule.examples/hls-salesforce-cdp-sys-api[HLS CDP System API]. . Preview all the detected objects and their attributes in your schema. . Click Save. The connector page reflects the updated status. . After the schema file is uploaded, you can create data streams to begin sending data from your source system. -For the https://www.anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/mulesoft-accelerator-for-healthcare/minor/{hls-version}/pages/Use%20case%207%20-%20Population%20health%20management/[Population Health Management] use case, the external systems Azure, Epic, Cerner, and other EHR systems contain data to be pushed to Data Cloud through MuleSoft's CDP connector using the Ingestion API. The name of the Connector used will appear under `Ingestion API` drop down while creating a new Data Stream. +For the https://www.anypoint.mulesoft.com/exchange/org.mule.examples/mulesoft-accelerator-for-healthcare/minor/{hls-version}/pages/Use%20case%207%20-%20Population%20health%20management/[Population Health Management] use case, the external systems Azure, Epic, Cerner, and other EHR systems contain data to be pushed to Data Cloud through MuleSoft's CDP connector using the Ingestion API. The name of the Connector used will appear under `Ingestion API` drop down while creating a new Data Stream. -The schema used for the https://www.anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/mulesoft-accelerator-for-healthcare/minor/{hls-version}/pages/Use%20case%207%20-%20Population%20health%20management/[Population Health Management] use case can be found in the implementation template. The following objects are added for this use case: +The schema used for the https://www.anypoint.mulesoft.com/exchange/org.mule.examples/mulesoft-accelerator-for-healthcare/minor/{hls-version}/pages/Use%20case%207%20-%20Population%20health%20management/[Population Health Management] use case can be found in the implementation template. The following objects are added for this use case: * condition * immunization @@ -116,7 +116,7 @@ To create data streams from Salesforce CRM starter bundle: Refer this https://help.salesforce.com/s/articleView?id=sf.c360_a_create_crm_starter_bundle.htm&type=5[link] to create data streams using starter bundle to begin the flow of data from a Salesforce Health Cloud data source. -For the https://www.anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/mulesoft-accelerator-for-healthcare/minor/{hls-version}/pages/Use%20case%207%20-%20Population%20health%20management/[Population Health Management] use case, data streams for Salesforce Health Cloud Account and Contact objects are created using Salesforce CRM Service bundle. +For the https://www.anypoint.mulesoft.com/exchange/org.mule.examples/mulesoft-accelerator-for-healthcare/minor/{hls-version}/pages/Use%20case%207%20-%20Population%20health%20management/[Population Health Management] use case, data streams for Salesforce Health Cloud Account and Contact objects are created using Salesforce CRM Service bundle. To create data streams from Salesforce Health Cloud data source: @@ -134,11 +134,11 @@ To add permissions for objects and their fields: Repeat these steps for all objects and fields you want to ingest into Data Cloud. Now, create data streams for the required objects by following the steps in this https://help.salesforce.com/s/articleView?id=sf.c360_a_create_crm_data_stream.htm&type=5&language=en_US[link]. -For the https://www.anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/mulesoft-accelerator-for-healthcare/minor/{hls-version}/pages/Use%20case%207%20-%20Population%20health%20management/[Population Health Management] use case, data streams for Contact Point Objects, Identifier, and ContactContactRelation are created. +For the https://www.anypoint.mulesoft.com/exchange/org.mule.examples/mulesoft-accelerator-for-healthcare/minor/{hls-version}/pages/Use%20case%207%20-%20Population%20health%20management/[Population Health Management] use case, data streams for Contact Point Objects, Identifier, and ContactContactRelation are created. === Create an Ingestion API data stream -After uploading the schema file for Ingestion API Connector, create a data stream from your source objects. For the https://www.anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/mulesoft-accelerator-for-healthcare/minor/{hls-version}/pages/Use%20case%207%20-%20Population%20health%20management/[Population Health Management] use case, data streams for condition, immunization and webEngagement are created. +After uploading the schema file for Ingestion API Connector, create a data stream from your source objects. For the https://www.anypoint.mulesoft.com/exchange/org.mule.examples/mulesoft-accelerator-for-healthcare/minor/{hls-version}/pages/Use%20case%207%20-%20Population%20health%20management/[Population Health Management] use case, data streams for condition, immunization and webEngagement are created. . In Data Cloud, select Data Streams. . In recently viewed data streams, click New. @@ -147,7 +147,7 @@ After uploading the schema file for Ingestion API Connector, create a data strea . Check the objects found in the schema you want to use and click Next. . At the New Data Stream dialog box, configure the following: ** Primary Key: A true Primary Key needs to be leveraged for Data Cloud. If one does not exist, you will need to create a Formula Field for the Primary Key. - ** Category: Choose between Profile, Engagement or Other. *Note:* For the https://www.anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/mulesoft-accelerator-for-healthcare/minor/{hls-version}/pages/Use%20case%207%20-%20Population%20health%20management/[Population Health Management] use case, the category for all the objects in the schema are Other. + ** Category: Choose between Profile, Engagement or Other. *Note:* For the https://www.anypoint.mulesoft.com/exchange/org.mule.examples/mulesoft-accelerator-for-healthcare/minor/{hls-version}/pages/Use%20case%207%20-%20Population%20health%20management/[Population Health Management] use case, the category for all the objects in the schema are Other. ** Record Modified Date: To order Profile modifications, use the Record Modified Date. *Note:* A record modified field that indicates when each incoming record was last modified is required for Engagement object types. While the field requirement is optional for Profile and Other objects, it is encouraged to provide the record modified field to ensure incoming records are processed in the right order. ** Date Time Field: Used to represent when Engagement from an external source occurred at ingestion. ** Click the `New Formula Field` (Optional). @@ -156,7 +156,7 @@ After uploading the schema file for Ingestion API Connector, create a data strea . Click Deploy. If you have only created one data stream, the data stream's record page appears. If you've created multiple data streams, the view refreshes to show all recently viewed data streams. . Wait up to one hour for your data to appear in your data stream. Map your data stream to data model objects to start using your data. -For the https://www.anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/mulesoft-accelerator-for-healthcare/minor/{hls-version}/pages/Use%20case%207%20-%20Population%20health%20management/[Population Health Management] use case, data stream is created for the objects added in schema by following the steps above. At step 6, click `New Formula field` with `Field Label` as `uniqueId` with `Formula Return` Type as `Text`. Under `Transformation Formula`, the formula is created as below for each of the object. +For the https://www.anypoint.mulesoft.com/exchange/org.mule.examples/mulesoft-accelerator-for-healthcare/minor/{hls-version}/pages/Use%20case%207%20-%20Population%20health%20management/[Population Health Management] use case, data stream is created for the objects added in schema by following the steps above. At step 6, click `New Formula field` with `Field Label` as `uniqueId` with `Formula Return` Type as `Text`. Under `Transformation Formula`, the formula is created as below for each of the object. * condition: `CONCAT(sourceField['patientMrn'],"~",sourceField['conditionCode'])` * immunization: `CONCAT(sourceField['patientMrn'],"~",sourceField['vaccineCode'],"~",sourceField['vaccineStatus'],"~",sourceField['vaccineDate'])` @@ -178,9 +178,9 @@ As part of your Connected App set up for Ingestion API, you must select the foll The MuleSoft Connector for CDP provides customers a pipeline to send data into Data Cloud. This connector works with the Data Cloud Bulk and Streaming API, depending on the operation you configure. Each API call uses a request/response pattern over an HTTPS connection. All required request headers, error handling, and HTTPS connection configurations are built into the connector. -Refer to the https://dev-docs-internal.kqa.msap.io/beta-accelerators/salesforce-cdp-connector/1.1/[CDP Connector documentation] for additional details on configuration and available operations. +Refer to the https://docs.mulesoft.com/salesforce-cdp-connector/1.1/[CDP Connector documentation] for additional details on configuration and available operations. -For the https://www.anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/mulesoft-accelerator-for-healthcare/minor/{hls-version}/pages/Use%20case%207%20-%20Population%20health%20management/[Population Health Management] use case, refer to the https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/hls-salesforce-cdp-sys-api-spec/[HLS CDP System API] specification and https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/hls-salesforce-cdp-sys-api[HLS CDP System API] implementation template assets. +For the https://www.anypoint.mulesoft.com/exchange/org.mule.examples/mulesoft-accelerator-for-healthcare/minor/{hls-version}/pages/Use%20case%207%20-%20Population%20health%20management/[Population Health Management] use case, refer to the https://anypoint.mulesoft.com/exchange/org.mule.examples/hls-salesforce-cdp-sys-api-spec/[HLS CDP System API] specification and https://anypoint.mulesoft.com/exchange/org.mule.examples/hls-salesforce-cdp-sys-api[HLS CDP System API] implementation template assets. == Data modeling and data mapping @@ -220,7 +220,7 @@ Objects in the data model created by the customer for Data Cloud implementation When mapping your party area data, complete the required fields and relationships to successfully use Identity Resolution, Segmentation, and Activation. -Default mapping exists for Account and Contact Objects if service Bundle is used to create data streams. For the https://www.anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/mulesoft-accelerator-for-healthcare/minor/{hls-version}/pages/Use%20case%207%20-%20Population%20health%20management/[Population Health Management] use case, the default mapping from Account and Contact DSOs to Contact Point DMOs are removed. Data Streams to Data Model Objects (DMO) are mapped as per the below table. +Default mapping exists for Account and Contact Objects if service Bundle is used to create data streams. For the https://www.anypoint.mulesoft.com/exchange/org.mule.examples/mulesoft-accelerator-for-healthcare/minor/{hls-version}/pages/Use%20case%207%20-%20Population%20health%20management/[Population Health Management] use case, the default mapping from Account and Contact DSOs to Contact Point DMOs are removed. Data Streams to Data Model Objects (DMO) are mapped as per the below table. |=== | Data Stream Name (DSO) | Custom Data Model Object (DMO) | Standard Data Model Object (DMO) @@ -250,7 +250,7 @@ Default mapping exists for Account and Contact Objects if service Bundle is used | |=== -For the https://www.anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/mulesoft-accelerator-for-healthcare/minor/{hls-version}/pages/Use%20case%207%20-%20Population%20health%20management/[Population Health Management] use case, below Data Mappings are created between Data Streams and DMOs/custom DMOs. +For the https://www.anypoint.mulesoft.com/exchange/org.mule.examples/mulesoft-accelerator-for-healthcare/minor/{hls-version}/pages/Use%20case%207%20-%20Population%20health%20management/[Population Health Management] use case, below Data Mappings are created between Data Streams and DMOs/custom DMOs. *Data Mappings of Account Data Stream to Account DMO* @@ -490,7 +490,7 @@ Some of the mappings are added by default from Bundle. Mapping needs to be chang | userId |=== -For the https://www.anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/mulesoft-accelerator-for-healthcare/minor/{hls-version}/pages/Use%20case%207%20-%20Population%20health%20management/[Population Health Management] use case, below DMOs and relationships needs to be maintained when Data mappings are done between Data Stream and DMOs. +For the https://www.anypoint.mulesoft.com/exchange/org.mule.examples/mulesoft-accelerator-for-healthcare/minor/{hls-version}/pages/Use%20case%207%20-%20Population%20health%20management/[Population Health Management] use case, below DMOs and relationships needs to be maintained when Data mappings are done between Data Stream and DMOs. *Data Relationships between DMOs* @@ -542,7 +542,7 @@ For the https://www.anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10 == Identity Resolution -NOTE: For the https://www.anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/mulesoft-accelerator-for-healthcare/minor/{hls-version}/pages/Use%20case%207%20-%20Population%20health%20management/[Population Health Management] use case, identity resolution rulesets were not required. +NOTE: For the https://www.anypoint.mulesoft.com/exchange/org.mule.examples/mulesoft-accelerator-for-healthcare/minor/{hls-version}/pages/Use%20case%207%20-%20Population%20health%20management/[Population Health Management] use case, identity resolution rulesets were not required. Use identity resolution to consolidate data from difference sources into a comprehensive view of your customer called a unified profile. Identity resolution uses matching and reconciliation rules to link data about people into unified profiles. Each unified profile contains all the unique contact point values from all sources. @@ -550,7 +550,7 @@ Set up identity resolution rulesets after mapping source data to data model obje == Calculated Insights -NOTE: For the https://www.anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/mulesoft-accelerator-for-healthcare/minor/{hls-version}/pages/Use%20case%207%20-%20Population%20health%20management/[Population Health Management] use case, Calculated Insights were not required. +NOTE: For the https://www.anypoint.mulesoft.com/exchange/org.mule.examples/mulesoft-accelerator-for-healthcare/minor/{hls-version}/pages/Use%20case%207%20-%20Population%20health%20management/[Population Health Management] use case, Calculated Insights were not required. The Calculated Insights feature lets you define and calculate multidimensional metrics on your entire digital state stored in Salesforce Customer Data Platform. @@ -577,7 +577,7 @@ TIP: Leave the Publish Schedule as *Don't Refresh for now*, and then fill it in Segment On: Segment On defines the target entity (object) used to build your segment. For example, you can build a segment on Unified Individual or Account or Individual. You can choose any entity marked as type Profile during ingestion. -For the https://www.anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/mulesoft-accelerator-for-healthcare/minor/{hls-version}/pages/Use%20case%207%20-%20Population%20health%20management/[Population Health Management] use case, create Segments on Individual. +For the https://www.anypoint.mulesoft.com/exchange/org.mule.examples/mulesoft-accelerator-for-healthcare/minor/{hls-version}/pages/Use%20case%207%20-%20Population%20health%20management/[Population Health Management] use case, create Segments on Individual. Example segment: @@ -615,7 +615,7 @@ For the Publish Schedule, we update it to reflect a Publish Schedule of every 12 Create activation targets to build, and activate data segments with Data Cloud. -For the https://www.anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/mulesoft-accelerator-for-healthcare/minor/{hls-version}/pages/Use%20case%207%20-%20Population%20health%20management/[Population Health Management] use case, create a Marketing Cloud Activation Target. +For the https://www.anypoint.mulesoft.com/exchange/org.mule.examples/mulesoft-accelerator-for-healthcare/minor/{hls-version}/pages/Use%20case%207%20-%20Population%20health%20management/[Population Health Management] use case, create a Marketing Cloud Activation Target. *Activation Target - Marketing Cloud:* @@ -624,8 +624,8 @@ Before creating an activation target, configure the Marketing Cloud connector in . Click Setup gear icon and then Data Cloud Setup. . Select Marketing Cloud. . Enter the Credentials to authenticate your Marketing Cloud account. You can proceed with the next step in the setup only if the authentication is successful. -. Data Source setup - this step is optional. This needs to be set up if you are planning to ingest data from Marketing Cloud into Data Cloud. *Note:* For the https://www.anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/mulesoft-accelerator-for-healthcare/minor/{hls-version}/pages/Use%20case%207%20-%20Population%20health%20management/[Population Health Management] use case, this step is skipped. -. Select Business Units to activate - this step is optional. To add or remove business units (BU), click the arrows between the two columns. *Note:* For the https://www.anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/mulesoft-accelerator-for-healthcare/minor/{hls-version}/pages/Use%20case%207%20-%20Population%20health%20management/[Population Health Management] use case, select business units to publish segments to Marketing Cloud. +. Data Source setup - this step is optional. This needs to be set up if you are planning to ingest data from Marketing Cloud into Data Cloud. *Note:* For the https://www.anypoint.mulesoft.com/exchange/org.mule.examples/mulesoft-accelerator-for-healthcare/minor/{hls-version}/pages/Use%20case%207%20-%20Population%20health%20management/[Population Health Management] use case, this step is skipped. +. Select Business Units to activate - this step is optional. To add or remove business units (BU), click the arrows between the two columns. *Note:* For the https://www.anypoint.mulesoft.com/exchange/org.mule.examples/mulesoft-accelerator-for-healthcare/minor/{hls-version}/pages/Use%20case%207%20-%20Population%20health%20management/[Population Health Management] use case, select business units to publish segments to Marketing Cloud. Create an activation target in Data Cloud to publish segments to Marketing Cloud business units. diff --git a/healthcare/2.21/modules/ROOT/pages/sfdc-health-cloud-setup-guide.adoc b/healthcare/2.21/modules/ROOT/pages/sfdc-health-cloud-setup-guide.adoc index a4876f44d..b7bac4b99 100644 --- a/healthcare/2.21/modules/ROOT/pages/sfdc-health-cloud-setup-guide.adoc +++ b/healthcare/2.21/modules/ROOT/pages/sfdc-health-cloud-setup-guide.adoc @@ -41,13 +41,13 @@ This accelerator uses MuleSoft's HL7 Connector. If you're required to use custom * Modify the message structure schema file (for example, ADT_A31.esl) to include your custom segment (or modify an existing segment to fit your needs). * Modify the basedefs.esl file to include the changes for segment definitions. -The https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/hc-accelerator-sfdc-adt-api/[implementation template^] for storing ADT messages in Salesforce Health Cloud shows an example of custom segment processing. Please check the src/main/resources/config/hl7/v2_2 folder in the implementation template. This folder has the necessary changes required to process custom segment `ZG1`. +The https://anypoint.mulesoft.com/exchange/org.mule.examples/hc-accelerator-sfdc-adt-api/[implementation template^] for storing ADT messages in Salesforce Health Cloud shows an example of custom segment processing. Please check the src/main/resources/config/hl7/v2_2 folder in the implementation template. This folder has the necessary changes required to process custom segment `ZG1`. -For additional details on HL7 Connector, please refer to the https://dev-docs-internal.kqa.msap.io/beta-accelerators/connectors/hl7/hl7-connector[documentation^]. +For additional details on HL7 Connector, please refer to the https://docs.mulesoft.com/connectors/hl7/hl7-connector[documentation^]. == Maven POM Parent -In addition to some global settings and repository references, the Maven https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/accelerator-pom-parent-src/[POM parent^] config also defines the versions of all MuleSoft connectors and modules used by applications. Refer to the https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/accelerator-pom-parent-src/[Exchange documentation^] for information on how to make changes to the POM parent file. +In addition to some global settings and repository references, the Maven https://anypoint.mulesoft.com/exchange/org.mule.examples/accelerator-pom-parent-src/[POM parent^] config also defines the versions of all MuleSoft connectors and modules used by applications. Refer to the https://anypoint.mulesoft.com/exchange/org.mule.examples/accelerator-pom-parent-src/[Exchange documentation^] for information on how to make changes to the POM parent file. == See Also diff --git a/healthcare/2.21/modules/ROOT/pages/smart-fhir-okta.adoc b/healthcare/2.21/modules/ROOT/pages/smart-fhir-okta.adoc index 293f4ce13..809023dd4 100644 --- a/healthcare/2.21/modules/ROOT/pages/smart-fhir-okta.adoc +++ b/healthcare/2.21/modules/ROOT/pages/smart-fhir-okta.adoc @@ -1,6 +1,6 @@ = SMART on FHIR with Okta -See the https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/hc-accelerator-okta-smartfhir/[Okta SMART on FHIR - Implementation Template^] asset, which walks you through how to set up a reference SMART on FHIR implementation on Anypoint Platform using Okta as the identity provider. +See the https://anypoint.mulesoft.com/exchange/org.mule.examples/hc-accelerator-okta-smartfhir/[Okta SMART on FHIR - Implementation Template^] asset, which walks you through how to set up a reference SMART on FHIR implementation on Anypoint Platform using Okta as the identity provider. The **S**ubstitutable **M**edical **A**pplications and **R**eusable **T**echnology (SMART) is a web/mobile app, which is typically embedded in EHR but can also serve as a standalone smartphone app. SMART on FHIR provides a consistent approach to security and data requirements for health applications. It also provides a workflow to securely request access to data, receive the data, and use the data. @@ -20,13 +20,13 @@ SMART on FHIR addresses the following three key aspects: Anypoint platform supports SMART on FHIR in the following ways: * Identity and access management -** Provisioning third-party https://dev-docs-internal.kqa.msap.io/beta-accelerators/access-management/configure-client-management-openid-task[OIDC client provider^] like Okta for identity management -** Out-of-the-box https://dev-docs-internal.kqa.msap.io/beta-accelerators/api-manager/2.x/policy-openid-connect[OpenID Connect token enforcement policy^] +** Provisioning third-party https://docs.mulesoft.com/access-management/configure-client-management-openid-task[OIDC client provider^] like Okta for identity management +** Out-of-the-box https://docs.mulesoft.com/api-manager/2.x/policy-openid-connect[OpenID Connect token enforcement policy^] ** Leverage OAuth provider information in the `authentication` object for custom policy * Access to the data using FHIR based APIs ** MuleSoft Accelerator for Healthcare provides FHIR R4 specifications for all the FHIR resources -** Out-of-the-box https://dev-docs-internal.kqa.msap.io/beta-accelerators/api-manager/2.x/cors-policy[cross origin resource sharing (CORS) policy^] enables cross origin data exchange. +** Out-of-the-box https://docs.mulesoft.com/api-manager/2.x/cors-policy[cross origin resource sharing (CORS) policy^] enables cross origin data exchange. == See Also diff --git a/healthcare/2.21/modules/ROOT/pages/x12-fhir-converter.adoc b/healthcare/2.21/modules/ROOT/pages/x12-fhir-converter.adoc index 354475b59..69f9d3caa 100644 --- a/healthcare/2.21/modules/ROOT/pages/x12-fhir-converter.adoc +++ b/healthcare/2.21/modules/ROOT/pages/x12-fhir-converter.adoc @@ -1,10 +1,10 @@ = X12 to FHIR Converter -The https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/hls-fhir-to-x12-sys-api/[X12 to FHIR converter^] comes with a ready to use template for https://x12.org/[X12^] to FHIR conversion. This template can be extended or modified to meet specific conversion requirements. The converter converts FHIR R4 to X12 formats and its responses from X12 to FHIR R4. +The https://anypoint.mulesoft.com/exchange/org.mule.examples/hls-fhir-to-x12-sys-api/[X12 to FHIR converter^] comes with a ready to use template for https://x12.org/[X12^] to FHIR conversion. This template can be extended or modified to meet specific conversion requirements. The converter converts FHIR R4 to X12 formats and its responses from X12 to FHIR R4. == Functional Diagram -image:https://www.mulesoft.com/ext/solutions/draft/images/hls-x12-fhir-fx-diagram.svg[X12 to FHIR converter functional diagram,900,align="center"] +image:https://www.mulesoft.com/ext/solutions/images/hls-x12-fhir-fx-diagram.svg[X12 to FHIR converter functional diagram,900,align="center"] == Advantages diff --git a/healthcare/2.22/modules/ROOT/pages/ccda-fhir-converter.adoc b/healthcare/2.22/modules/ROOT/pages/ccda-fhir-converter.adoc index 11b76cb60..134619070 100644 --- a/healthcare/2.22/modules/ROOT/pages/ccda-fhir-converter.adoc +++ b/healthcare/2.22/modules/ROOT/pages/ccda-fhir-converter.adoc @@ -1,10 +1,10 @@ = C-CDA to FHIR Converter -The https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/hls-ccda-to-fhir-sys-api/[C-CDA to FHIR converter] comes with a ready to use template for https://www.hl7.org/implement/standards/product_brief.cfm?product_id=496[CDA] to FHIR conversion. This template can be extended or modified to meet specific conversion requirements. +The https://anypoint.mulesoft.com/exchange/org.mule.examples/hls-ccda-to-fhir-sys-api/[C-CDA to FHIR converter] comes with a ready to use template for https://www.hl7.org/implement/standards/product_brief.cfm?product_id=496[CDA] to FHIR conversion. This template can be extended or modified to meet specific conversion requirements. == Functional diagram -image:https://www.mulesoft.com/ext/solutions/draft/images/hls-ccda-fhir-fx-diagram.svg[CDA to FHIR converter functional diagram,900,align="center"] +image:https://www.mulesoft.com/ext/solutions/images/hls-ccda-fhir-fx-diagram.svg[CDA to FHIR converter functional diagram,900,align="center"] == Advantages diff --git a/healthcare/2.22/modules/ROOT/pages/fhir-r4-assets.adoc b/healthcare/2.22/modules/ROOT/pages/fhir-r4-assets.adoc index 134ba48f5..10d431db8 100644 --- a/healthcare/2.22/modules/ROOT/pages/fhir-r4-assets.adoc +++ b/healthcare/2.22/modules/ROOT/pages/fhir-r4-assets.adoc @@ -2,11 +2,11 @@ The following are a collection of assets to support MuleSoft customers who are developing Fast Healthcare Interoperability Resources (FHIR) APIs using MuleSoft. Visit the https://www.hl7.org/fhir/[official HL7 website] for more information. -* https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/hls-fhirjson-to-raml-sys-api-spec/[FHIR RAML auto-generator] - Utility to generate RAML specification(s) for FHIR resources directly from the JSON schema provided by HL7. +* https://anypoint.mulesoft.com/exchange/org.mule.examples/hls-fhirjson-to-raml-sys-api-spec/[FHIR RAML auto-generator] - Utility to generate RAML specification(s) for FHIR resources directly from the JSON schema provided by HL7. * xref:fhir-r4-us-core-profiles.adoc[FHIR R4 US Core Profile Assets] * xref:fhir-r4-resources.adoc[FHIR R4 Resources List] -* https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fhir-error-policy/[FHIR Error API Policy] - Captures error responses and formats them in an FHIR OperationOutcome-compliant format, since Anypoint Platform's out-of-the-box (OOTB) policies do not provide error messages in an FHIR-compliant format. This policy can also be used with other OOTB API policies provided in Anypoint Platform, such as OAuth or JWT. -* https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/hc-accelerator-okta-smartfhir/[Okta SMART on FHIR^] - Implementation template that walks you through how to set up a reference SMART on FHIR implementation on Anypoint Platform using Okta as the identity provider. +* https://anypoint.mulesoft.com/exchange/org.mule.examples/fhir-error-policy/[FHIR Error API Policy] - Captures error responses and formats them in an FHIR OperationOutcome-compliant format, since Anypoint Platform's out-of-the-box (OOTB) policies do not provide error messages in an FHIR-compliant format. This policy can also be used with other OOTB API policies provided in Anypoint Platform, such as OAuth or JWT. +* https://anypoint.mulesoft.com/exchange/org.mule.examples/hc-accelerator-okta-smartfhir/[Okta SMART on FHIR^] - Implementation template that walks you through how to set up a reference SMART on FHIR implementation on Anypoint Platform using Okta as the identity provider. == See Also diff --git a/healthcare/2.22/modules/ROOT/pages/fhir-r4-resources.adoc b/healthcare/2.22/modules/ROOT/pages/fhir-r4-resources.adoc index 062796d38..8414363f1 100644 --- a/healthcare/2.22/modules/ROOT/pages/fhir-r4-resources.adoc +++ b/healthcare/2.22/modules/ROOT/pages/fhir-r4-resources.adoc @@ -2,7 +2,7 @@ The MuleSoft Accelerator for Healthcare provides a library of United States Core Data for Interoperability (USCDI) and FHIR R4 resources to help healthcare developers adhere to interoperability needs and jumpstart the development of healthcare digital transformation initiatives. -You can also use the https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fhir-error-policy/[FHIR Error API Policy] to capture error responses and format them in an FHIR OperationOutcome-compliant format, since Anypoint Platform's out-of-the-box (OOTB) policies do not provide error messages in an FHIR-compliant format. This policy can also be used with other OOTB API policies provided in Anypoint Platform, such as OAuth or JWT. +You can also use the https://anypoint.mulesoft.com/exchange/org.mule.examples/fhir-error-policy/[FHIR Error API Policy] to capture error responses and format them in an FHIR OperationOutcome-compliant format, since Anypoint Platform's out-of-the-box (OOTB) policies do not provide error messages in an FHIR-compliant format. This policy can also be used with other OOTB API policies provided in Anypoint Platform, such as OAuth or JWT. For the list of US core profile assets, please refer to xref:fhir-r4-us-core-profiles.adoc[this link]. @@ -15,339 +15,339 @@ _API specifications, data types, and libraries built to meet compliance with FHI | Category| Library | API Specification .^| Foundation - Confirmance -| https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fhir-r4-capabilitystatement-library/[CapabilityStatement] ^[N]^ + -https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fhir-r4-structuredefinition-library/[StructureDefinition] ^[N]^ + -https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fhir-r4-implementationguide-library/[ImplementationGuide] + -https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fhir-r4-searchparameter-library/[SearchParameter] + -https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fhir-r4-operationdefinition-library/[OperationDefinition] ^[N]^ + -https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fhir-r4-compartmentdefinition-library/[CompartmentDefinition] + -https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fhir-r4-messagedefinition-library/[MessageDefinition] + -https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fhir-r4-structuremap-library/[StructureMap] + -https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fhir-r4-graphdefinition-library/[GraphDefinition] + -https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fhir-r4-examplescenario-library/[ExampleScenario] -| https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fhir-r4-capabilitystatement-api/[CapabilityStatement] ^[N]^ + -https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fhir-r4-structuredefinition-api/[StructureDefinition] ^[N]^ + -https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fhir-r4-implementationguide-api/[ImplementationGuide] + -https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fhir-r4-searchparameter-api/[SearchParameter] + -https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fhir-r4-operationdefinition-api/[OperationDefinition] ^[N]^ + -https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fhir-r4-compartmentdefinition-api/[CompartmentDefinition] + -https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fhir-r4-messagedefinition-api/[MessageDefinition] + -https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fhir-r4-structuremap-api/[StructureMap] + -https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fhir-r4-graphdefinition-api/[GraphDefinition] + -https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fhir-r4-examplescenario-api/[ExampleScenario] +| https://anypoint.mulesoft.com/exchange/org.mule.examples/fhir-r4-capabilitystatement-library/[CapabilityStatement] ^[N]^ + +https://anypoint.mulesoft.com/exchange/org.mule.examples/fhir-r4-structuredefinition-library/[StructureDefinition] ^[N]^ + +https://anypoint.mulesoft.com/exchange/org.mule.examples/fhir-r4-implementationguide-library/[ImplementationGuide] + +https://anypoint.mulesoft.com/exchange/org.mule.examples/fhir-r4-searchparameter-library/[SearchParameter] + +https://anypoint.mulesoft.com/exchange/org.mule.examples/fhir-r4-operationdefinition-library/[OperationDefinition] ^[N]^ + +https://anypoint.mulesoft.com/exchange/org.mule.examples/fhir-r4-compartmentdefinition-library/[CompartmentDefinition] + +https://anypoint.mulesoft.com/exchange/org.mule.examples/fhir-r4-messagedefinition-library/[MessageDefinition] + +https://anypoint.mulesoft.com/exchange/org.mule.examples/fhir-r4-structuremap-library/[StructureMap] + +https://anypoint.mulesoft.com/exchange/org.mule.examples/fhir-r4-graphdefinition-library/[GraphDefinition] + +https://anypoint.mulesoft.com/exchange/org.mule.examples/fhir-r4-examplescenario-library/[ExampleScenario] +| https://anypoint.mulesoft.com/exchange/org.mule.examples/fhir-r4-capabilitystatement-api/[CapabilityStatement] ^[N]^ + +https://anypoint.mulesoft.com/exchange/org.mule.examples/fhir-r4-structuredefinition-api/[StructureDefinition] ^[N]^ + +https://anypoint.mulesoft.com/exchange/org.mule.examples/fhir-r4-implementationguide-api/[ImplementationGuide] + +https://anypoint.mulesoft.com/exchange/org.mule.examples/fhir-r4-searchparameter-api/[SearchParameter] + +https://anypoint.mulesoft.com/exchange/org.mule.examples/fhir-r4-operationdefinition-api/[OperationDefinition] ^[N]^ + +https://anypoint.mulesoft.com/exchange/org.mule.examples/fhir-r4-compartmentdefinition-api/[CompartmentDefinition] + +https://anypoint.mulesoft.com/exchange/org.mule.examples/fhir-r4-messagedefinition-api/[MessageDefinition] + +https://anypoint.mulesoft.com/exchange/org.mule.examples/fhir-r4-structuremap-api/[StructureMap] + +https://anypoint.mulesoft.com/exchange/org.mule.examples/fhir-r4-graphdefinition-api/[GraphDefinition] + +https://anypoint.mulesoft.com/exchange/org.mule.examples/fhir-r4-examplescenario-api/[ExampleScenario] .^| Foundation - Terminology -| https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fhir-r4-codesystem-library/[CodeSystem] ^[N]^ + -https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fhir-r4-valueset-library/[ValueSet] ^[N]^ + -https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fhir-r4-conceptmap-library/[ConceptMap] + -https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fhir-r4-namingsystem-library/[NamingSystem] + -https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fhir-r4-terminologycapabilities-library/[TerminologiesCapabilities] -| https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fhir-r4-codesystem-api/[CodeSystem] ^[N]^ + -https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fhir-r4-valueset-api/[ValueSet] ^[N]^ + -https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fhir-r4-conceptmap-api/[ConceptMap] + -https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fhir-r4-namingsystem-api/[NamingSystem] + -https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fhir-r4-terminologycapabilities-api/[TerminologiesCapabilities] +| https://anypoint.mulesoft.com/exchange/org.mule.examples/fhir-r4-codesystem-library/[CodeSystem] ^[N]^ + +https://anypoint.mulesoft.com/exchange/org.mule.examples/fhir-r4-valueset-library/[ValueSet] ^[N]^ + +https://anypoint.mulesoft.com/exchange/org.mule.examples/fhir-r4-conceptmap-library/[ConceptMap] + +https://anypoint.mulesoft.com/exchange/org.mule.examples/fhir-r4-namingsystem-library/[NamingSystem] + +https://anypoint.mulesoft.com/exchange/org.mule.examples/fhir-r4-terminologycapabilities-library/[TerminologiesCapabilities] +| https://anypoint.mulesoft.com/exchange/org.mule.examples/fhir-r4-codesystem-api/[CodeSystem] ^[N]^ + +https://anypoint.mulesoft.com/exchange/org.mule.examples/fhir-r4-valueset-api/[ValueSet] ^[N]^ + +https://anypoint.mulesoft.com/exchange/org.mule.examples/fhir-r4-conceptmap-api/[ConceptMap] + +https://anypoint.mulesoft.com/exchange/org.mule.examples/fhir-r4-namingsystem-api/[NamingSystem] + +https://anypoint.mulesoft.com/exchange/org.mule.examples/fhir-r4-terminologycapabilities-api/[TerminologiesCapabilities] .^| Foundation - Security -| https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fhir-r4-provenance-library/[Provenance] + -https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fhir-r4-auditevent-library/[AuditEvent] + -https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fhir-r4-consent-library/[Consent] -| https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fhir-r4-provenance-api/[Provenance] + -https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fhir-r4-auditevent-api/[AuditEvent] + -https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fhir-r4-consent-api/[Consent] +| https://anypoint.mulesoft.com/exchange/org.mule.examples/fhir-r4-provenance-library/[Provenance] + +https://anypoint.mulesoft.com/exchange/org.mule.examples/fhir-r4-auditevent-library/[AuditEvent] + +https://anypoint.mulesoft.com/exchange/org.mule.examples/fhir-r4-consent-library/[Consent] +| https://anypoint.mulesoft.com/exchange/org.mule.examples/fhir-r4-provenance-api/[Provenance] + +https://anypoint.mulesoft.com/exchange/org.mule.examples/fhir-r4-auditevent-api/[AuditEvent] + +https://anypoint.mulesoft.com/exchange/org.mule.examples/fhir-r4-consent-api/[Consent] .^| Foundation - Documents -| https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fhir-r4-composition-library/[Composition] + -https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fhir-r4-documentmanifest-library/[DocumentManifest] + -https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fhir-r4-documentreference-library/[DocumentReference] + -https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fhir-r4-catalogentry-library/[CatalogEntry] -| https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fhir-r4-composition-api/[Composition] + -https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fhir-r4-documentmanifest-api/[DocumentManifest] + -https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fhir-r4-documentreference-api/[DocumentReference] + -https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fhir-r4-catalogentry-api/[CatalogEntry] +| https://anypoint.mulesoft.com/exchange/org.mule.examples/fhir-r4-composition-library/[Composition] + +https://anypoint.mulesoft.com/exchange/org.mule.examples/fhir-r4-documentmanifest-library/[DocumentManifest] + +https://anypoint.mulesoft.com/exchange/org.mule.examples/fhir-r4-documentreference-library/[DocumentReference] + +https://anypoint.mulesoft.com/exchange/org.mule.examples/fhir-r4-catalogentry-library/[CatalogEntry] +| https://anypoint.mulesoft.com/exchange/org.mule.examples/fhir-r4-composition-api/[Composition] + +https://anypoint.mulesoft.com/exchange/org.mule.examples/fhir-r4-documentmanifest-api/[DocumentManifest] + +https://anypoint.mulesoft.com/exchange/org.mule.examples/fhir-r4-documentreference-api/[DocumentReference] + +https://anypoint.mulesoft.com/exchange/org.mule.examples/fhir-r4-catalogentry-api/[CatalogEntry] .^| Foundation - Other -| https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fhir-r4-basic-library/[Basic] + -https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fhir-r4-binary-library/[Binary] ^[N]^ + -https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fhir-r4-linkage-library/[Linkage] + -https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fhir-r4-messageheader-library/[MessageHeader] + -https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fhir-r4-parameters-library/[Parameters] ^[N]^ + -https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fhir-r4-subscription-library/[Subscription] + +| https://anypoint.mulesoft.com/exchange/org.mule.examples/fhir-r4-basic-library/[Basic] + +https://anypoint.mulesoft.com/exchange/org.mule.examples/fhir-r4-binary-library/[Binary] ^[N]^ + +https://anypoint.mulesoft.com/exchange/org.mule.examples/fhir-r4-linkage-library/[Linkage] + +https://anypoint.mulesoft.com/exchange/org.mule.examples/fhir-r4-messageheader-library/[MessageHeader] + +https://anypoint.mulesoft.com/exchange/org.mule.examples/fhir-r4-parameters-library/[Parameters] ^[N]^ + +https://anypoint.mulesoft.com/exchange/org.mule.examples/fhir-r4-subscription-library/[Subscription] + ++++++ -| https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fhir-r4-basic-api/[Basic] + -https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fhir-r4-binary-api/[Binary] ^[N]^ + -https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fhir-r4-linkage-api/[Linkage] + -https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fhir-r4-messageheader-api/[MessageHeader] + -https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fhir-r4-parameters-api/[Parameters] ^[N]^ + -https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fhir-r4-subscription-api/[Subscription] +| https://anypoint.mulesoft.com/exchange/org.mule.examples/fhir-r4-basic-api/[Basic] + +https://anypoint.mulesoft.com/exchange/org.mule.examples/fhir-r4-binary-api/[Binary] ^[N]^ + +https://anypoint.mulesoft.com/exchange/org.mule.examples/fhir-r4-linkage-api/[Linkage] + +https://anypoint.mulesoft.com/exchange/org.mule.examples/fhir-r4-messageheader-api/[MessageHeader] + +https://anypoint.mulesoft.com/exchange/org.mule.examples/fhir-r4-parameters-api/[Parameters] ^[N]^ + +https://anypoint.mulesoft.com/exchange/org.mule.examples/fhir-r4-subscription-api/[Subscription] .^| Base - Individuals -| https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fhir-r4-patient-library/[Patient] ^[N]^ + -https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fhir-r4-practitioner-library/[Practitioner] + -https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fhir-r4-practitionerrole-library/[PractitionerRole] + -https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fhir-r4-relatedperson-library/[RelatedPerson] + -https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fhir-r4-person-library/[Person] + -https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fhir-r4-group-library/[Group] + +| https://anypoint.mulesoft.com/exchange/org.mule.examples/fhir-r4-patient-library/[Patient] ^[N]^ + +https://anypoint.mulesoft.com/exchange/org.mule.examples/fhir-r4-practitioner-library/[Practitioner] + +https://anypoint.mulesoft.com/exchange/org.mule.examples/fhir-r4-practitionerrole-library/[PractitionerRole] + +https://anypoint.mulesoft.com/exchange/org.mule.examples/fhir-r4-relatedperson-library/[RelatedPerson] + +https://anypoint.mulesoft.com/exchange/org.mule.examples/fhir-r4-person-library/[Person] + +https://anypoint.mulesoft.com/exchange/org.mule.examples/fhir-r4-group-library/[Group] + ++++++ -| https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fhir-r4-patient-api/[Patient] ^[N]^ + -https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fhir-r4-practitioner-api/[Practitioner] + -https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fhir-r4-practitionerrole-api/[PractitionerRole] + -https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fhir-r4-relatedperson-api/[RelatedPerson] + -https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fhir-r4-person-api/[Person] + -https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fhir-r4-group-api/[Group] +| https://anypoint.mulesoft.com/exchange/org.mule.examples/fhir-r4-patient-api/[Patient] ^[N]^ + +https://anypoint.mulesoft.com/exchange/org.mule.examples/fhir-r4-practitioner-api/[Practitioner] + +https://anypoint.mulesoft.com/exchange/org.mule.examples/fhir-r4-practitionerrole-api/[PractitionerRole] + +https://anypoint.mulesoft.com/exchange/org.mule.examples/fhir-r4-relatedperson-api/[RelatedPerson] + +https://anypoint.mulesoft.com/exchange/org.mule.examples/fhir-r4-person-api/[Person] + +https://anypoint.mulesoft.com/exchange/org.mule.examples/fhir-r4-group-api/[Group] .^| Base - Entities #1 -| https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fhir-r4-organization-library/[Organization] + -https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fhir-r4-organizationaffiliation-library/[OrganizationAffiliation] + -https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fhir-r4-healthcareservice-library/[HealthcareService] + -https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fhir-r4-endpoint-library/[Endpoint] + -https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fhir-r4-location-library/[Location] + +| https://anypoint.mulesoft.com/exchange/org.mule.examples/fhir-r4-organization-library/[Organization] + +https://anypoint.mulesoft.com/exchange/org.mule.examples/fhir-r4-organizationaffiliation-library/[OrganizationAffiliation] + +https://anypoint.mulesoft.com/exchange/org.mule.examples/fhir-r4-healthcareservice-library/[HealthcareService] + +https://anypoint.mulesoft.com/exchange/org.mule.examples/fhir-r4-endpoint-library/[Endpoint] + +https://anypoint.mulesoft.com/exchange/org.mule.examples/fhir-r4-location-library/[Location] + ++++++ -| https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fhir-r4-organization-api/[Organization] + -https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fhir-r4-organizationaffiliation-api/[OrganizationAffiliation] + -https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fhir-r4-healthcareservice-api/[HealthcareService] + -https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fhir-r4-endpoint-api/[Endpoint] + -https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fhir-r4-location-api/[Location] +| https://anypoint.mulesoft.com/exchange/org.mule.examples/fhir-r4-organization-api/[Organization] + +https://anypoint.mulesoft.com/exchange/org.mule.examples/fhir-r4-organizationaffiliation-api/[OrganizationAffiliation] + +https://anypoint.mulesoft.com/exchange/org.mule.examples/fhir-r4-healthcareservice-api/[HealthcareService] + +https://anypoint.mulesoft.com/exchange/org.mule.examples/fhir-r4-endpoint-api/[Endpoint] + +https://anypoint.mulesoft.com/exchange/org.mule.examples/fhir-r4-location-api/[Location] .^| Base - Entities #2 -| https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fhir-r4-substance-library/[Substance] + -https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fhir-r4-biologicallyderivedproduct-library/[BiologicallyDerivedProduct #] + -https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fhir-r4-device-library/[Device] + -https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fhir-r4-devicemetric-library/[DeviceMetric] + +| https://anypoint.mulesoft.com/exchange/org.mule.examples/fhir-r4-substance-library/[Substance] + +https://anypoint.mulesoft.com/exchange/org.mule.examples/fhir-r4-biologicallyderivedproduct-library/[BiologicallyDerivedProduct #] + +https://anypoint.mulesoft.com/exchange/org.mule.examples/fhir-r4-device-library/[Device] + +https://anypoint.mulesoft.com/exchange/org.mule.examples/fhir-r4-devicemetric-library/[DeviceMetric] + ++++++ -| https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fhir-r4-substance-api/[Substance] + -https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fhir-r4-biologicallyderivedproduct-api/[BiologicallyDerivedProduct #] + -https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fhir-r4-device-api/[Device] + -https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fhir-r4-devicemetric-api/[DeviceMetric] +| https://anypoint.mulesoft.com/exchange/org.mule.examples/fhir-r4-substance-api/[Substance] + +https://anypoint.mulesoft.com/exchange/org.mule.examples/fhir-r4-biologicallyderivedproduct-api/[BiologicallyDerivedProduct #] + +https://anypoint.mulesoft.com/exchange/org.mule.examples/fhir-r4-device-api/[Device] + +https://anypoint.mulesoft.com/exchange/org.mule.examples/fhir-r4-devicemetric-api/[DeviceMetric] .^| Base - Workflow -| https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fhir-r4-task-library/[Task] + -https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fhir-r4-appointment-library/[Appointment] + -https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fhir-r4-appointmentresponse-library/[AppointmentResponse] + -https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fhir-r4-schedule-library/[Schedule] + -https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fhir-r4-slot-library/[Slot] + -https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fhir-r4-verificationresult-library/[VerificationResult] -| https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fhir-r4-task-api/[Task] + -https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fhir-r4-appointment-api/[Appointment] + -https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fhir-r4-appointmentresponse-api/[AppointmentResponse] + -https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fhir-r4-schedule-api/[Schedule] + -https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fhir-r4-slot-api/[Slot] + -https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fhir-r4-verificationresult-api/[VerificationResult] +| https://anypoint.mulesoft.com/exchange/org.mule.examples/fhir-r4-task-library/[Task] + +https://anypoint.mulesoft.com/exchange/org.mule.examples/fhir-r4-appointment-library/[Appointment] + +https://anypoint.mulesoft.com/exchange/org.mule.examples/fhir-r4-appointmentresponse-library/[AppointmentResponse] + +https://anypoint.mulesoft.com/exchange/org.mule.examples/fhir-r4-schedule-library/[Schedule] + +https://anypoint.mulesoft.com/exchange/org.mule.examples/fhir-r4-slot-library/[Slot] + +https://anypoint.mulesoft.com/exchange/org.mule.examples/fhir-r4-verificationresult-library/[VerificationResult] +| https://anypoint.mulesoft.com/exchange/org.mule.examples/fhir-r4-task-api/[Task] + +https://anypoint.mulesoft.com/exchange/org.mule.examples/fhir-r4-appointment-api/[Appointment] + +https://anypoint.mulesoft.com/exchange/org.mule.examples/fhir-r4-appointmentresponse-api/[AppointmentResponse] + +https://anypoint.mulesoft.com/exchange/org.mule.examples/fhir-r4-schedule-api/[Schedule] + +https://anypoint.mulesoft.com/exchange/org.mule.examples/fhir-r4-slot-api/[Slot] + +https://anypoint.mulesoft.com/exchange/org.mule.examples/fhir-r4-verificationresult-api/[VerificationResult] .^| Base - Management -| https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fhir-r4-encounter-library/[Encounter] + -https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fhir-r4-episodeofcare-library/[EpisodeOfCare] + -https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fhir-r4-flag-library/[Flag] + -https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fhir-r4-list-library/[List] + -https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fhir-r4-library-library/[Library] -| https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fhir-r4-encounter-api/[Encounter] + -https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fhir-r4-episodeofcare-api/[EpisodeOfCare] + -https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fhir-r4-flag-api/[Flag] + -https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fhir-r4-list-api/[List] + -https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fhir-r4-library-api/[Library] +| https://anypoint.mulesoft.com/exchange/org.mule.examples/fhir-r4-encounter-library/[Encounter] + +https://anypoint.mulesoft.com/exchange/org.mule.examples/fhir-r4-episodeofcare-library/[EpisodeOfCare] + +https://anypoint.mulesoft.com/exchange/org.mule.examples/fhir-r4-flag-library/[Flag] + +https://anypoint.mulesoft.com/exchange/org.mule.examples/fhir-r4-list-library/[List] + +https://anypoint.mulesoft.com/exchange/org.mule.examples/fhir-r4-library-library/[Library] +| https://anypoint.mulesoft.com/exchange/org.mule.examples/fhir-r4-encounter-api/[Encounter] + +https://anypoint.mulesoft.com/exchange/org.mule.examples/fhir-r4-episodeofcare-api/[EpisodeOfCare] + +https://anypoint.mulesoft.com/exchange/org.mule.examples/fhir-r4-flag-api/[Flag] + +https://anypoint.mulesoft.com/exchange/org.mule.examples/fhir-r4-list-api/[List] + +https://anypoint.mulesoft.com/exchange/org.mule.examples/fhir-r4-library-api/[Library] .^| Clinical - Summary -| https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fhir-r4-allergyintolerance-library/[AllergyIntolerance] + -https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fhir-r4-adverseevent-library/[AdverseEvent] + -https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fhir-r4-condition-library/[Condition(Problem)] + -https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fhir-r4-procedure-library/[Procedure] + -https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fhir-r4-familymemberhistory-library/[FamilyMemberHistory] + -https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fhir-r4-clinicalimpression-library/[ClinicalImpression #] + -https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fhir-r4-clinicalimpression-library/[Note] + -https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fhir-r4-detectedissue-library/[DetectedIssue] -| https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fhir-r4-allergyintolerance-api/[AllergyIntolerance] + -https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fhir-r4-adverseevent-api/[AdverseEvent] + -https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fhir-r4-condition-api/[Condition(Problem)] + -https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fhir-r4-procedure-api/[Procedure] + -https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fhir-r4-familymemberhistory-api/[FamilyMemberHistory] + -https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fhir-r4-clinicalimpression-api/[ClinicalImpression #] + -https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fhir-r4-clinicalimpression-api/[Note] + -https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fhir-r4-detectedissue-api/[DetectedIssue] +| https://anypoint.mulesoft.com/exchange/org.mule.examples/fhir-r4-allergyintolerance-library/[AllergyIntolerance] + +https://anypoint.mulesoft.com/exchange/org.mule.examples/fhir-r4-adverseevent-library/[AdverseEvent] + +https://anypoint.mulesoft.com/exchange/org.mule.examples/fhir-r4-condition-library/[Condition(Problem)] + +https://anypoint.mulesoft.com/exchange/org.mule.examples/fhir-r4-procedure-library/[Procedure] + +https://anypoint.mulesoft.com/exchange/org.mule.examples/fhir-r4-familymemberhistory-library/[FamilyMemberHistory] + +https://anypoint.mulesoft.com/exchange/org.mule.examples/fhir-r4-clinicalimpression-library/[ClinicalImpression #] + +https://anypoint.mulesoft.com/exchange/org.mule.examples/fhir-r4-clinicalimpression-library/[Note] + +https://anypoint.mulesoft.com/exchange/org.mule.examples/fhir-r4-detectedissue-library/[DetectedIssue] +| https://anypoint.mulesoft.com/exchange/org.mule.examples/fhir-r4-allergyintolerance-api/[AllergyIntolerance] + +https://anypoint.mulesoft.com/exchange/org.mule.examples/fhir-r4-adverseevent-api/[AdverseEvent] + +https://anypoint.mulesoft.com/exchange/org.mule.examples/fhir-r4-condition-api/[Condition(Problem)] + +https://anypoint.mulesoft.com/exchange/org.mule.examples/fhir-r4-procedure-api/[Procedure] + +https://anypoint.mulesoft.com/exchange/org.mule.examples/fhir-r4-familymemberhistory-api/[FamilyMemberHistory] + +https://anypoint.mulesoft.com/exchange/org.mule.examples/fhir-r4-clinicalimpression-api/[ClinicalImpression #] + +https://anypoint.mulesoft.com/exchange/org.mule.examples/fhir-r4-clinicalimpression-api/[Note] + +https://anypoint.mulesoft.com/exchange/org.mule.examples/fhir-r4-detectedissue-api/[DetectedIssue] .^| Clinical - Diagnostics -| https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fhir-r4-observation-library/[Observation] ^[N]^ + -https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fhir-r4-media-library/[Media] ^[u]^ + -https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fhir-r4-diagnosticreport-library/[DiagnosticReport] + -https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fhir-r4-specimen-library/[Specimen] + -https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fhir-r4-bodystructure-library/[BodyStructure] + -https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fhir-r4-imagingstudy-library/[ImagingStudy] + -https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fhir-r4-questionnaireresponse-library/[QuestionnaireResponse ] + -https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fhir-r4-molecularsequence-library/[MolecularSequence] -| https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fhir-r4-observation-api/[Observation] ^[N]^ + -https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fhir-r4-media-api/[Media] ^[u]^ + -https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fhir-r4-diagnosticreport-api/[DiagnosticReport] + -https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fhir-r4-specimen-api/[Specimen] + -https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fhir-r4-bodystructure-api/[BodyStructure] + -https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fhir-r4-imagingstudy-api/[ImagingStudy] + -https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fhir-r4-questionnaireresponse-api/[QuestionnaireResponse ] + -https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fhir-r4-molecularsequence-api/[MolecularSequence] +| https://anypoint.mulesoft.com/exchange/org.mule.examples/fhir-r4-observation-library/[Observation] ^[N]^ + +https://anypoint.mulesoft.com/exchange/org.mule.examples/fhir-r4-media-library/[Media] ^[u]^ + +https://anypoint.mulesoft.com/exchange/org.mule.examples/fhir-r4-diagnosticreport-library/[DiagnosticReport] + +https://anypoint.mulesoft.com/exchange/org.mule.examples/fhir-r4-specimen-library/[Specimen] + +https://anypoint.mulesoft.com/exchange/org.mule.examples/fhir-r4-bodystructure-library/[BodyStructure] + +https://anypoint.mulesoft.com/exchange/org.mule.examples/fhir-r4-imagingstudy-library/[ImagingStudy] + +https://anypoint.mulesoft.com/exchange/org.mule.examples/fhir-r4-questionnaireresponse-library/[QuestionnaireResponse ] + +https://anypoint.mulesoft.com/exchange/org.mule.examples/fhir-r4-molecularsequence-library/[MolecularSequence] +| https://anypoint.mulesoft.com/exchange/org.mule.examples/fhir-r4-observation-api/[Observation] ^[N]^ + +https://anypoint.mulesoft.com/exchange/org.mule.examples/fhir-r4-media-api/[Media] ^[u]^ + +https://anypoint.mulesoft.com/exchange/org.mule.examples/fhir-r4-diagnosticreport-api/[DiagnosticReport] + +https://anypoint.mulesoft.com/exchange/org.mule.examples/fhir-r4-specimen-api/[Specimen] + +https://anypoint.mulesoft.com/exchange/org.mule.examples/fhir-r4-bodystructure-api/[BodyStructure] + +https://anypoint.mulesoft.com/exchange/org.mule.examples/fhir-r4-imagingstudy-api/[ImagingStudy] + +https://anypoint.mulesoft.com/exchange/org.mule.examples/fhir-r4-questionnaireresponse-api/[QuestionnaireResponse ] + +https://anypoint.mulesoft.com/exchange/org.mule.examples/fhir-r4-molecularsequence-api/[MolecularSequence] .^| Clinical - Medications -| https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fhir-r4-medicationrequest-library/[MedicationRequest] + -https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fhir-r4-medicationadministration-library/[MedicationAdministration] + -https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fhir-r4-medicationdispense-library/[MedicationDispense] + -https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fhir-r4-medicationstatement-library/[MedicationStatement] + -https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fhir-r4-medication-library/[Medication] + -https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fhir-r4-medicationknowledge-library/[MedicationKnowledge] + -https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fhir-r4-immunization-library/[Immunization] + -https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fhir-r4-immunizationevaluation-library/[ImmunizationEvaluation] + -https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fhir-r4-immunizationrecommendation-library/[ImmunizationRecommendation] -| https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fhir-r4-medicationrequest-api/[MedicationRequest] + -https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fhir-r4-medicationadministration-api/[MedicationAdministration] + -https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fhir-r4-medicationdispense-api/[MedicationDispense] + -https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fhir-r4-medicationstatement-api/[MedicationStatement] + -https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fhir-r4-medication-api/[Medication] + -https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fhir-r4-medicationknowledge-api/[MedicationKnowledge] + -https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fhir-r4-immunization-api/[Immunization] + -https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fhir-r4-immunizationevaluation-api/[ImmunizationEvaluation] + -https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fhir-r4-immunizationrecommendation-api/[ImmunizationRecommendation] +| https://anypoint.mulesoft.com/exchange/org.mule.examples/fhir-r4-medicationrequest-library/[MedicationRequest] + +https://anypoint.mulesoft.com/exchange/org.mule.examples/fhir-r4-medicationadministration-library/[MedicationAdministration] + +https://anypoint.mulesoft.com/exchange/org.mule.examples/fhir-r4-medicationdispense-library/[MedicationDispense] + +https://anypoint.mulesoft.com/exchange/org.mule.examples/fhir-r4-medicationstatement-library/[MedicationStatement] + +https://anypoint.mulesoft.com/exchange/org.mule.examples/fhir-r4-medication-library/[Medication] + +https://anypoint.mulesoft.com/exchange/org.mule.examples/fhir-r4-medicationknowledge-library/[MedicationKnowledge] + +https://anypoint.mulesoft.com/exchange/org.mule.examples/fhir-r4-immunization-library/[Immunization] + +https://anypoint.mulesoft.com/exchange/org.mule.examples/fhir-r4-immunizationevaluation-library/[ImmunizationEvaluation] + +https://anypoint.mulesoft.com/exchange/org.mule.examples/fhir-r4-immunizationrecommendation-library/[ImmunizationRecommendation] +| https://anypoint.mulesoft.com/exchange/org.mule.examples/fhir-r4-medicationrequest-api/[MedicationRequest] + +https://anypoint.mulesoft.com/exchange/org.mule.examples/fhir-r4-medicationadministration-api/[MedicationAdministration] + +https://anypoint.mulesoft.com/exchange/org.mule.examples/fhir-r4-medicationdispense-api/[MedicationDispense] + +https://anypoint.mulesoft.com/exchange/org.mule.examples/fhir-r4-medicationstatement-api/[MedicationStatement] + +https://anypoint.mulesoft.com/exchange/org.mule.examples/fhir-r4-medication-api/[Medication] + +https://anypoint.mulesoft.com/exchange/org.mule.examples/fhir-r4-medicationknowledge-api/[MedicationKnowledge] + +https://anypoint.mulesoft.com/exchange/org.mule.examples/fhir-r4-immunization-api/[Immunization] + +https://anypoint.mulesoft.com/exchange/org.mule.examples/fhir-r4-immunizationevaluation-api/[ImmunizationEvaluation] + +https://anypoint.mulesoft.com/exchange/org.mule.examples/fhir-r4-immunizationrecommendation-api/[ImmunizationRecommendation] .^| Clinical - Care Provision -| https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fhir-r4-careplan-library/[CarePlan] + -https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fhir-r4-careteam-library/[CareTeam] + -https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fhir-r4-goal-library/[Goal] + -https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fhir-r4-servicerequest-library/[ServiceRequest] + -https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fhir-r4-nutritionorder-library/[NutritionOrder] + -https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fhir-r4-visionprescription-library/[VisionPrescription] + -https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fhir-r4-riskassessment-library/[RiskAssessment] + -https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fhir-r4-requestgroup-library/[RequestGroup] -| https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fhir-r4-careplan-api/[CarePlan] + -https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fhir-r4-careteam-api/[CareTeam] + -https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fhir-r4-goal-api/[Goal] + -https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fhir-r4-servicerequest-api/[ServiceRequest] + -https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fhir-r4-nutritionorder-api/[NutritionOrder] + -https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fhir-r4-visionprescription-api/[VisionPrescription] + -https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fhir-r4-riskassessment-api/[RiskAssessment] + -https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fhir-r4-requestgroup-api/[RequestGroup] +| https://anypoint.mulesoft.com/exchange/org.mule.examples/fhir-r4-careplan-library/[CarePlan] + +https://anypoint.mulesoft.com/exchange/org.mule.examples/fhir-r4-careteam-library/[CareTeam] + +https://anypoint.mulesoft.com/exchange/org.mule.examples/fhir-r4-goal-library/[Goal] + +https://anypoint.mulesoft.com/exchange/org.mule.examples/fhir-r4-servicerequest-library/[ServiceRequest] + +https://anypoint.mulesoft.com/exchange/org.mule.examples/fhir-r4-nutritionorder-library/[NutritionOrder] + +https://anypoint.mulesoft.com/exchange/org.mule.examples/fhir-r4-visionprescription-library/[VisionPrescription] + +https://anypoint.mulesoft.com/exchange/org.mule.examples/fhir-r4-riskassessment-library/[RiskAssessment] + +https://anypoint.mulesoft.com/exchange/org.mule.examples/fhir-r4-requestgroup-library/[RequestGroup] +| https://anypoint.mulesoft.com/exchange/org.mule.examples/fhir-r4-careplan-api/[CarePlan] + +https://anypoint.mulesoft.com/exchange/org.mule.examples/fhir-r4-careteam-api/[CareTeam] + +https://anypoint.mulesoft.com/exchange/org.mule.examples/fhir-r4-goal-api/[Goal] + +https://anypoint.mulesoft.com/exchange/org.mule.examples/fhir-r4-servicerequest-api/[ServiceRequest] + +https://anypoint.mulesoft.com/exchange/org.mule.examples/fhir-r4-nutritionorder-api/[NutritionOrder] + +https://anypoint.mulesoft.com/exchange/org.mule.examples/fhir-r4-visionprescription-api/[VisionPrescription] + +https://anypoint.mulesoft.com/exchange/org.mule.examples/fhir-r4-riskassessment-api/[RiskAssessment] + +https://anypoint.mulesoft.com/exchange/org.mule.examples/fhir-r4-requestgroup-api/[RequestGroup] .^| Clinical - Request & Response -| https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fhir-r4-communication-library/[Communication] + -https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fhir-r4-communicationrequest-library/[CommunicationRequest] + -https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fhir-r4-devicerequest-library/[DeviceRequest #] + -https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fhir-r4-deviceusestatement-library/[DeviceUseStatement] ^[u]^ + -https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fhir-r4-guidanceresponse-library/[GuidanceResponse] + -https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fhir-r4-supplyrequest-library/[SupplyRequest #] + -https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fhir-r4-supplydelivery-library/[SupplyDelivery] -| https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fhir-r4-communication-api/[Communication] + -https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fhir-r4-communicationrequest-api/[CommunicationRequest] + -https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fhir-r4-devicerequest-api/[DeviceRequest #] + -https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fhir-r4-deviceusestatement-api/[DeviceUseStatement] ^[u]^ + -https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fhir-r4-guidanceresponse-api/[GuidanceResponse] + -https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fhir-r4-supplyrequest-api/[SupplyRequest #] + -https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fhir-r4-supplydelivery-api/[SupplyDelivery] +| https://anypoint.mulesoft.com/exchange/org.mule.examples/fhir-r4-communication-library/[Communication] + +https://anypoint.mulesoft.com/exchange/org.mule.examples/fhir-r4-communicationrequest-library/[CommunicationRequest] + +https://anypoint.mulesoft.com/exchange/org.mule.examples/fhir-r4-devicerequest-library/[DeviceRequest #] + +https://anypoint.mulesoft.com/exchange/org.mule.examples/fhir-r4-deviceusestatement-library/[DeviceUseStatement] ^[u]^ + +https://anypoint.mulesoft.com/exchange/org.mule.examples/fhir-r4-guidanceresponse-library/[GuidanceResponse] + +https://anypoint.mulesoft.com/exchange/org.mule.examples/fhir-r4-supplyrequest-library/[SupplyRequest #] + +https://anypoint.mulesoft.com/exchange/org.mule.examples/fhir-r4-supplydelivery-library/[SupplyDelivery] +| https://anypoint.mulesoft.com/exchange/org.mule.examples/fhir-r4-communication-api/[Communication] + +https://anypoint.mulesoft.com/exchange/org.mule.examples/fhir-r4-communicationrequest-api/[CommunicationRequest] + +https://anypoint.mulesoft.com/exchange/org.mule.examples/fhir-r4-devicerequest-api/[DeviceRequest #] + +https://anypoint.mulesoft.com/exchange/org.mule.examples/fhir-r4-deviceusestatement-api/[DeviceUseStatement] ^[u]^ + +https://anypoint.mulesoft.com/exchange/org.mule.examples/fhir-r4-guidanceresponse-api/[GuidanceResponse] + +https://anypoint.mulesoft.com/exchange/org.mule.examples/fhir-r4-supplyrequest-api/[SupplyRequest #] + +https://anypoint.mulesoft.com/exchange/org.mule.examples/fhir-r4-supplydelivery-api/[SupplyDelivery] .^| Financial - Support -| https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fhir-r4-coverage-library/[Coverage] + -https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fhir-r4-coverageeligibilityrequest-library/[CoverageEligibilityRequest] + -https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fhir-r4-coverageeligibilityresponse-library/[CoverageEligibilityResponse] + -https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fhir-r4-enrollmentrequest-library/[EnrollmentRequest] ^[u]^ + -https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fhir-r4-enrollmentresponse-library/[EnrollmentResponse] ^[u]^ -| https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fhir-r4-coverage-api/[Coverage] + -https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fhir-r4-coverageeligibilityrequest-api/[CoverageEligibilityRequest] + -https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fhir-r4-coverageeligibilityresponse-api/[CoverageEligibilityResponse] + -https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fhir-r4-enrollmentrequest-api/[EnrollmentRequest] ^[u]^ + -https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fhir-r4-enrollmentresponse-api/[EnrollmentResponse] ^[u]^ +| https://anypoint.mulesoft.com/exchange/org.mule.examples/fhir-r4-coverage-library/[Coverage] + +https://anypoint.mulesoft.com/exchange/org.mule.examples/fhir-r4-coverageeligibilityrequest-library/[CoverageEligibilityRequest] + +https://anypoint.mulesoft.com/exchange/org.mule.examples/fhir-r4-coverageeligibilityresponse-library/[CoverageEligibilityResponse] + +https://anypoint.mulesoft.com/exchange/org.mule.examples/fhir-r4-enrollmentrequest-library/[EnrollmentRequest] ^[u]^ + +https://anypoint.mulesoft.com/exchange/org.mule.examples/fhir-r4-enrollmentresponse-library/[EnrollmentResponse] ^[u]^ +| https://anypoint.mulesoft.com/exchange/org.mule.examples/fhir-r4-coverage-api/[Coverage] + +https://anypoint.mulesoft.com/exchange/org.mule.examples/fhir-r4-coverageeligibilityrequest-api/[CoverageEligibilityRequest] + +https://anypoint.mulesoft.com/exchange/org.mule.examples/fhir-r4-coverageeligibilityresponse-api/[CoverageEligibilityResponse] + +https://anypoint.mulesoft.com/exchange/org.mule.examples/fhir-r4-enrollmentrequest-api/[EnrollmentRequest] ^[u]^ + +https://anypoint.mulesoft.com/exchange/org.mule.examples/fhir-r4-enrollmentresponse-api/[EnrollmentResponse] ^[u]^ .^| Financial - Billing -| https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fhir-r4-claim-library/[Claim] + -https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fhir-r4-claimresponse-library/[ClaimResponse] + -https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fhir-r4-invoice-library/[Invoice] -| https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fhir-r4-claim-api/[Claim] + -https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fhir-r4-claimresponse-api/[ClaimResponse] + -https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fhir-r4-invoice-api/[Invoice] - -.^| Financial - Payment | https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fhir-r4-paymentnotice-library/[PaymentNotice] + -https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fhir-r4-paymentreconciliation-library/[PaymentReconcilliation] -| https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fhir-r4-paymentnotice-api/[PaymentNotice] + -https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fhir-r4-paymentreconciliation-api/[PaymentReconcilliation] - -.^| Financial - General | https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fhir-r4-account-library/[Account] + -https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fhir-r4-chargeitem-library/[ChargeItem] + -https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fhir-r4-chargeitemdefinition-library/[ChargeItemDefinition] + -https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fhir-r4-contract-library/[Contract] + -https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fhir-r4-explanationofbenefit-library/[ExplanationOfBenefit] + -https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fhir-r4-insuranceplan-library/[InsurancePlan] -| https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fhir-r4-account-api/[Account] + -https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fhir-r4-chargeitem-api/[ChargeItem] + -https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fhir-r4-chargeitemdefinition-api/[ChargeItemDefinition] + -https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fhir-r4-contract-api/[Contract] + -https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fhir-r4-explanationofbenefit-api/[ExplanationOfBenefit] + -https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fhir-r4-insuranceplan-api/[InsurancePlan] - -.^| Specialized - Public Health & Research | https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fhir-r4-researchstudy-library/[ResearchStudy] + -https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fhir-r4-researchsubject-library/[ResearchSubject] -| https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fhir-r4-researchstudy-api/[ResearchStudy] + -https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fhir-r4-researchsubject-api/[ResearchSubject] - -.^| Specialized - Definitional Artifacts | https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fhir-r4-activitydefinition-library/[ActivityDefinition] + -https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fhir-r4-devicedefinition-library/[DeviceDefinition] + -https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fhir-r4-eventdefinition-library/[EventDefinition] + -https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fhir-r4-observationdefinition-library/[ObservationDefinition] ^[u]^ + -https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fhir-r4-plandefinition-library/[PlanDefinition] + -https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fhir-r4-questionnaire-library/[Questionnaire] + -https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fhir-r4-specimendefinition-library/[SpecimenDefinition] -| https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fhir-r4-activitydefinition-api/[ActivityDefinition] + -https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fhir-r4-devicedefinition-api/[DeviceDefinition] + -https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fhir-r4-eventdefinition-api/[EventDefinition] + -https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fhir-r4-observationdefinition-api/[ObservationDefinition] ^[u]^ + -https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fhir-r4-plandefinition-api/[PlanDefinition] + -https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fhir-r4-questionnaire-api/[Questionnaire] + -https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fhir-r4-specimendefinition-api/[SpecimenDefinition] - -.^| Specialized - Evidence Based Medicine | https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fhir-r4-researchdefinition-library/[ResearchDefinition] + -https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fhir-r4-researchelementdefinition-library/[ResearchElementDefinition] + -https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fhir-r4-evidence-library/[Evidence] + -https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fhir-r4-evidencevariable-library/[EvidenceVariable] + -https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fhir-r4-effectevidencesynthesis-library/[EffectEvidenceSynthesis] + -https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fhir-r4-riskevidencesynthesis-library/[RiskEvidenceSynthesis] -| https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fhir-r4-researchdefinition-api/[ResearchDefinition] + -https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fhir-r4-researchelementdefinition-api/[ResearchElementDefinition] + -https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fhir-r4-evidence-api/[Evidence] + -https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fhir-r4-evidencevariable-api/[EvidenceVariable] + -https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fhir-r4-effectevidencesynthesis-api/[EffectEvidenceSynthesis] + -https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fhir-r4-riskevidencesynthesis-api/[RiskEvidenceSynthesis] - -.^| Specialized - Quality Reporting & Testing | https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fhir-r4-measure-library/[Measure] + -https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fhir-r4-measurereport-library/[MeasureReport] + -https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fhir-r4-testscript-library/[TestScript] + -https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fhir-r4-testreport-library/[TestReport] -| https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fhir-r4-measure-api/[Measure] + -https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fhir-r4-measurereport-api/[MeasureReport] + -https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fhir-r4-testscript-api/[TestScript] + -https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fhir-r4-testreport-api/[TestReport] - -.^| Specialized - Medication Definition | https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fhir-r4-medicinalproduct-library/[MedicinalProduct] ^[u]^ + -https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fhir-r4-medicinalproductauthorization-library/[MedicinalProductAuthorization] ^[u]^ + -https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fhir-r4-medicinalproductcontraindication-library/[MedicinalProductContraindication] + -https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fhir-r4-medicinalproductindication-library/[MedicinalProductIndication] + -https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fhir-r4-medicinalproductingredient-library/[MedicinalProductIngredient] ^[u]^ + -https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fhir-r4-medicinalproductinteraction-library/[MedicinalProductInteraction] + -https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fhir-r4-medicinalproductmanufactured-library/[MedicinalProductManufactured] + -https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fhir-r4-medicinalproductpackaged-library/[MedicinalProductPackaged] ^[u]^ + -https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fhir-r4-medicinalproductpharmaceutical-library/[MedicinalProductPharmaceutical] ^[u]^ + -https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fhir-r4-medicinalproductundesirableeffect-library/[MedicinalProductUndesirableEffect] + -https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fhir-r4-substancenucleicacid-library/[SubstanceNucleicAcid] + -https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fhir-r4-substancepolymer-library/[SubstancePolymer] ^[u]^ + -https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fhir-r4-substanceprotein-library/[SubstanceProtein] + -https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fhir-r4-substancereferenceinformation-library/[SubstanceReferenceInformation] ^[u]^ + -https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fhir-r4-substancespecification-library/[SubstanceSpecification] ^[u]^ + -https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fhir-r4-substancesourcematerial-library/[SubstanceSourceMaterial] -| https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fhir-r4-medicinalproduct-api/[MedicinalProduct] ^[u]^ + -https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fhir-r4-medicinalproductauthorization-api/[MedicinalProductAuthorization] ^[u]^ + -https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fhir-r4-medicinalproductcontraindication-api/[MedicinalProductContraindication] + -https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fhir-r4-medicinalproductindication-api/[MedicinalProductIndication] + -https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fhir-r4-medicinalproductingredient-api/[MedicinalProductIngredient] ^[u]^ + -https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fhir-r4-medicinalproductinteraction-api/[MedicinalProductInteraction] + -https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fhir-r4-medicinalproductmanufactured-api/[MedicinalProductManufactured] + -https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fhir-r4-medicinalproductpackaged-api/[MedicinalProductPackaged] ^[u]^ + -https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fhir-r4-medicinalproductpharmaceutical-api/[MedicinalProductPharmaceutical] ^[u]^ + -https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fhir-r4-medicinalproductundesirableeffect-api/[MedicinalProductUndesirableEffect] + -https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fhir-r4-substancenucleicacid-api/[SubstanceNucleicAcid] + -https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fhir-r4-substancepolymer-api/[SubstancePolymer] ^[u]^ + -https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fhir-r4-substanceprotein-api/[SubstanceProtein] + -https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fhir-r4-substancereferenceinformation-api/[SubstanceReferenceInformation] ^[u]^ + -https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fhir-r4-substancespecification-api/[SubstanceSpecification] ^[u]^ + -https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fhir-r4-substancesourcematerial-api/[SubstanceSourceMaterial] +| https://anypoint.mulesoft.com/exchange/org.mule.examples/fhir-r4-claim-library/[Claim] + +https://anypoint.mulesoft.com/exchange/org.mule.examples/fhir-r4-claimresponse-library/[ClaimResponse] + +https://anypoint.mulesoft.com/exchange/org.mule.examples/fhir-r4-invoice-library/[Invoice] +| https://anypoint.mulesoft.com/exchange/org.mule.examples/fhir-r4-claim-api/[Claim] + +https://anypoint.mulesoft.com/exchange/org.mule.examples/fhir-r4-claimresponse-api/[ClaimResponse] + +https://anypoint.mulesoft.com/exchange/org.mule.examples/fhir-r4-invoice-api/[Invoice] + +.^| Financial - Payment | https://anypoint.mulesoft.com/exchange/org.mule.examples/fhir-r4-paymentnotice-library/[PaymentNotice] + +https://anypoint.mulesoft.com/exchange/org.mule.examples/fhir-r4-paymentreconciliation-library/[PaymentReconcilliation] +| https://anypoint.mulesoft.com/exchange/org.mule.examples/fhir-r4-paymentnotice-api/[PaymentNotice] + +https://anypoint.mulesoft.com/exchange/org.mule.examples/fhir-r4-paymentreconciliation-api/[PaymentReconcilliation] + +.^| Financial - General | https://anypoint.mulesoft.com/exchange/org.mule.examples/fhir-r4-account-library/[Account] + +https://anypoint.mulesoft.com/exchange/org.mule.examples/fhir-r4-chargeitem-library/[ChargeItem] + +https://anypoint.mulesoft.com/exchange/org.mule.examples/fhir-r4-chargeitemdefinition-library/[ChargeItemDefinition] + +https://anypoint.mulesoft.com/exchange/org.mule.examples/fhir-r4-contract-library/[Contract] + +https://anypoint.mulesoft.com/exchange/org.mule.examples/fhir-r4-explanationofbenefit-library/[ExplanationOfBenefit] + +https://anypoint.mulesoft.com/exchange/org.mule.examples/fhir-r4-insuranceplan-library/[InsurancePlan] +| https://anypoint.mulesoft.com/exchange/org.mule.examples/fhir-r4-account-api/[Account] + +https://anypoint.mulesoft.com/exchange/org.mule.examples/fhir-r4-chargeitem-api/[ChargeItem] + +https://anypoint.mulesoft.com/exchange/org.mule.examples/fhir-r4-chargeitemdefinition-api/[ChargeItemDefinition] + +https://anypoint.mulesoft.com/exchange/org.mule.examples/fhir-r4-contract-api/[Contract] + +https://anypoint.mulesoft.com/exchange/org.mule.examples/fhir-r4-explanationofbenefit-api/[ExplanationOfBenefit] + +https://anypoint.mulesoft.com/exchange/org.mule.examples/fhir-r4-insuranceplan-api/[InsurancePlan] + +.^| Specialized - Public Health & Research | https://anypoint.mulesoft.com/exchange/org.mule.examples/fhir-r4-researchstudy-library/[ResearchStudy] + +https://anypoint.mulesoft.com/exchange/org.mule.examples/fhir-r4-researchsubject-library/[ResearchSubject] +| https://anypoint.mulesoft.com/exchange/org.mule.examples/fhir-r4-researchstudy-api/[ResearchStudy] + +https://anypoint.mulesoft.com/exchange/org.mule.examples/fhir-r4-researchsubject-api/[ResearchSubject] + +.^| Specialized - Definitional Artifacts | https://anypoint.mulesoft.com/exchange/org.mule.examples/fhir-r4-activitydefinition-library/[ActivityDefinition] + +https://anypoint.mulesoft.com/exchange/org.mule.examples/fhir-r4-devicedefinition-library/[DeviceDefinition] + +https://anypoint.mulesoft.com/exchange/org.mule.examples/fhir-r4-eventdefinition-library/[EventDefinition] + +https://anypoint.mulesoft.com/exchange/org.mule.examples/fhir-r4-observationdefinition-library/[ObservationDefinition] ^[u]^ + +https://anypoint.mulesoft.com/exchange/org.mule.examples/fhir-r4-plandefinition-library/[PlanDefinition] + +https://anypoint.mulesoft.com/exchange/org.mule.examples/fhir-r4-questionnaire-library/[Questionnaire] + +https://anypoint.mulesoft.com/exchange/org.mule.examples/fhir-r4-specimendefinition-library/[SpecimenDefinition] +| https://anypoint.mulesoft.com/exchange/org.mule.examples/fhir-r4-activitydefinition-api/[ActivityDefinition] + +https://anypoint.mulesoft.com/exchange/org.mule.examples/fhir-r4-devicedefinition-api/[DeviceDefinition] + +https://anypoint.mulesoft.com/exchange/org.mule.examples/fhir-r4-eventdefinition-api/[EventDefinition] + +https://anypoint.mulesoft.com/exchange/org.mule.examples/fhir-r4-observationdefinition-api/[ObservationDefinition] ^[u]^ + +https://anypoint.mulesoft.com/exchange/org.mule.examples/fhir-r4-plandefinition-api/[PlanDefinition] + +https://anypoint.mulesoft.com/exchange/org.mule.examples/fhir-r4-questionnaire-api/[Questionnaire] + +https://anypoint.mulesoft.com/exchange/org.mule.examples/fhir-r4-specimendefinition-api/[SpecimenDefinition] + +.^| Specialized - Evidence Based Medicine | https://anypoint.mulesoft.com/exchange/org.mule.examples/fhir-r4-researchdefinition-library/[ResearchDefinition] + +https://anypoint.mulesoft.com/exchange/org.mule.examples/fhir-r4-researchelementdefinition-library/[ResearchElementDefinition] + +https://anypoint.mulesoft.com/exchange/org.mule.examples/fhir-r4-evidence-library/[Evidence] + +https://anypoint.mulesoft.com/exchange/org.mule.examples/fhir-r4-evidencevariable-library/[EvidenceVariable] + +https://anypoint.mulesoft.com/exchange/org.mule.examples/fhir-r4-effectevidencesynthesis-library/[EffectEvidenceSynthesis] + +https://anypoint.mulesoft.com/exchange/org.mule.examples/fhir-r4-riskevidencesynthesis-library/[RiskEvidenceSynthesis] +| https://anypoint.mulesoft.com/exchange/org.mule.examples/fhir-r4-researchdefinition-api/[ResearchDefinition] + +https://anypoint.mulesoft.com/exchange/org.mule.examples/fhir-r4-researchelementdefinition-api/[ResearchElementDefinition] + +https://anypoint.mulesoft.com/exchange/org.mule.examples/fhir-r4-evidence-api/[Evidence] + +https://anypoint.mulesoft.com/exchange/org.mule.examples/fhir-r4-evidencevariable-api/[EvidenceVariable] + +https://anypoint.mulesoft.com/exchange/org.mule.examples/fhir-r4-effectevidencesynthesis-api/[EffectEvidenceSynthesis] + +https://anypoint.mulesoft.com/exchange/org.mule.examples/fhir-r4-riskevidencesynthesis-api/[RiskEvidenceSynthesis] + +.^| Specialized - Quality Reporting & Testing | https://anypoint.mulesoft.com/exchange/org.mule.examples/fhir-r4-measure-library/[Measure] + +https://anypoint.mulesoft.com/exchange/org.mule.examples/fhir-r4-measurereport-library/[MeasureReport] + +https://anypoint.mulesoft.com/exchange/org.mule.examples/fhir-r4-testscript-library/[TestScript] + +https://anypoint.mulesoft.com/exchange/org.mule.examples/fhir-r4-testreport-library/[TestReport] +| https://anypoint.mulesoft.com/exchange/org.mule.examples/fhir-r4-measure-api/[Measure] + +https://anypoint.mulesoft.com/exchange/org.mule.examples/fhir-r4-measurereport-api/[MeasureReport] + +https://anypoint.mulesoft.com/exchange/org.mule.examples/fhir-r4-testscript-api/[TestScript] + +https://anypoint.mulesoft.com/exchange/org.mule.examples/fhir-r4-testreport-api/[TestReport] + +.^| Specialized - Medication Definition | https://anypoint.mulesoft.com/exchange/org.mule.examples/fhir-r4-medicinalproduct-library/[MedicinalProduct] ^[u]^ + +https://anypoint.mulesoft.com/exchange/org.mule.examples/fhir-r4-medicinalproductauthorization-library/[MedicinalProductAuthorization] ^[u]^ + +https://anypoint.mulesoft.com/exchange/org.mule.examples/fhir-r4-medicinalproductcontraindication-library/[MedicinalProductContraindication] + +https://anypoint.mulesoft.com/exchange/org.mule.examples/fhir-r4-medicinalproductindication-library/[MedicinalProductIndication] + +https://anypoint.mulesoft.com/exchange/org.mule.examples/fhir-r4-medicinalproductingredient-library/[MedicinalProductIngredient] ^[u]^ + +https://anypoint.mulesoft.com/exchange/org.mule.examples/fhir-r4-medicinalproductinteraction-library/[MedicinalProductInteraction] + +https://anypoint.mulesoft.com/exchange/org.mule.examples/fhir-r4-medicinalproductmanufactured-library/[MedicinalProductManufactured] + +https://anypoint.mulesoft.com/exchange/org.mule.examples/fhir-r4-medicinalproductpackaged-library/[MedicinalProductPackaged] ^[u]^ + +https://anypoint.mulesoft.com/exchange/org.mule.examples/fhir-r4-medicinalproductpharmaceutical-library/[MedicinalProductPharmaceutical] ^[u]^ + +https://anypoint.mulesoft.com/exchange/org.mule.examples/fhir-r4-medicinalproductundesirableeffect-library/[MedicinalProductUndesirableEffect] + +https://anypoint.mulesoft.com/exchange/org.mule.examples/fhir-r4-substancenucleicacid-library/[SubstanceNucleicAcid] + +https://anypoint.mulesoft.com/exchange/org.mule.examples/fhir-r4-substancepolymer-library/[SubstancePolymer] ^[u]^ + +https://anypoint.mulesoft.com/exchange/org.mule.examples/fhir-r4-substanceprotein-library/[SubstanceProtein] + +https://anypoint.mulesoft.com/exchange/org.mule.examples/fhir-r4-substancereferenceinformation-library/[SubstanceReferenceInformation] ^[u]^ + +https://anypoint.mulesoft.com/exchange/org.mule.examples/fhir-r4-substancespecification-library/[SubstanceSpecification] ^[u]^ + +https://anypoint.mulesoft.com/exchange/org.mule.examples/fhir-r4-substancesourcematerial-library/[SubstanceSourceMaterial] +| https://anypoint.mulesoft.com/exchange/org.mule.examples/fhir-r4-medicinalproduct-api/[MedicinalProduct] ^[u]^ + +https://anypoint.mulesoft.com/exchange/org.mule.examples/fhir-r4-medicinalproductauthorization-api/[MedicinalProductAuthorization] ^[u]^ + +https://anypoint.mulesoft.com/exchange/org.mule.examples/fhir-r4-medicinalproductcontraindication-api/[MedicinalProductContraindication] + +https://anypoint.mulesoft.com/exchange/org.mule.examples/fhir-r4-medicinalproductindication-api/[MedicinalProductIndication] + +https://anypoint.mulesoft.com/exchange/org.mule.examples/fhir-r4-medicinalproductingredient-api/[MedicinalProductIngredient] ^[u]^ + +https://anypoint.mulesoft.com/exchange/org.mule.examples/fhir-r4-medicinalproductinteraction-api/[MedicinalProductInteraction] + +https://anypoint.mulesoft.com/exchange/org.mule.examples/fhir-r4-medicinalproductmanufactured-api/[MedicinalProductManufactured] + +https://anypoint.mulesoft.com/exchange/org.mule.examples/fhir-r4-medicinalproductpackaged-api/[MedicinalProductPackaged] ^[u]^ + +https://anypoint.mulesoft.com/exchange/org.mule.examples/fhir-r4-medicinalproductpharmaceutical-api/[MedicinalProductPharmaceutical] ^[u]^ + +https://anypoint.mulesoft.com/exchange/org.mule.examples/fhir-r4-medicinalproductundesirableeffect-api/[MedicinalProductUndesirableEffect] + +https://anypoint.mulesoft.com/exchange/org.mule.examples/fhir-r4-substancenucleicacid-api/[SubstanceNucleicAcid] + +https://anypoint.mulesoft.com/exchange/org.mule.examples/fhir-r4-substancepolymer-api/[SubstancePolymer] ^[u]^ + +https://anypoint.mulesoft.com/exchange/org.mule.examples/fhir-r4-substanceprotein-api/[SubstanceProtein] + +https://anypoint.mulesoft.com/exchange/org.mule.examples/fhir-r4-substancereferenceinformation-api/[SubstanceReferenceInformation] ^[u]^ + +https://anypoint.mulesoft.com/exchange/org.mule.examples/fhir-r4-substancespecification-api/[SubstanceSpecification] ^[u]^ + +https://anypoint.mulesoft.com/exchange/org.mule.examples/fhir-r4-substancesourcematerial-api/[SubstanceSourceMaterial] |=== NOTE: @@ -364,7 +364,7 @@ This FHIR Error API policy can be used to capture error responses and format the See the following page to learn more about the FHIR Error API Policy: -* https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fhir-error-policy/[FHIR Error API Policy] +* https://anypoint.mulesoft.com/exchange/org.mule.examples/fhir-error-policy/[FHIR Error API Policy] == See Also diff --git a/healthcare/2.22/modules/ROOT/pages/fhir-r4-us-core-profiles.adoc b/healthcare/2.22/modules/ROOT/pages/fhir-r4-us-core-profiles.adoc index bd9f34445..22b48f675 100644 --- a/healthcare/2.22/modules/ROOT/pages/fhir-r4-us-core-profiles.adoc +++ b/healthcare/2.22/modules/ROOT/pages/fhir-r4-us-core-profiles.adoc @@ -2,7 +2,7 @@ The MuleSoft Accelerator for Healthcare provides a library of United States Core Data for Interoperability (USCDI) and FHIR R4 resources to help healthcare developers adhere to interoperability needs and jumpstart the development of healthcare digital transformation initiatives. -You can also use the https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fhir-error-policy/[FHIR Error API Policy] to capture error responses and format them in an FHIR OperationOutcome-compliant format, since Anypoint Platform's out-of-the-box (OOTB) policies do not provide error messages in an FHIR-compliant format. This policy can also be used with other OOTB API policies provided in Anypoint Platform, such as OAuth or JWT. +You can also use the https://anypoint.mulesoft.com/exchange/org.mule.examples/fhir-error-policy/[FHIR Error API Policy] to capture error responses and format them in an FHIR OperationOutcome-compliant format, since Anypoint Platform's out-of-the-box (OOTB) policies do not provide error messages in an FHIR-compliant format. This policy can also be used with other OOTB API policies provided in Anypoint Platform, such as OAuth or JWT. For the list of all FHIR R4 assets, please refer to xref:fhir-r4-resources.adoc[this link]. @@ -15,68 +15,68 @@ _API specifications, data types, and libraries built to meet compliance with FHI | Module | Library | API specification | Data Types -| https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fhir-r4-commons-library/[FHIR R4 Common Library] + -https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fhir-r4-resource-types-library/[Resource Types Library] + +| https://anypoint.mulesoft.com/exchange/org.mule.examples/fhir-r4-commons-library/[FHIR R4 Common Library] + +https://anypoint.mulesoft.com/exchange/org.mule.examples/fhir-r4-resource-types-library/[Resource Types Library] + | NA | Foundation -| https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fhir-r4-documentreference-library/[DocumentReference Library] -| https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fhir-r4-documentreference-api/[DocumentReference API] +| https://anypoint.mulesoft.com/exchange/org.mule.examples/fhir-r4-documentreference-library/[DocumentReference Library] +| https://anypoint.mulesoft.com/exchange/org.mule.examples/fhir-r4-documentreference-api/[DocumentReference API] | Security -| https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fhir-r4-provenance-library/[Provenance Library] -| https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fhir-r4-provenance-api/[Provenance API] +| https://anypoint.mulesoft.com/exchange/org.mule.examples/fhir-r4-provenance-library/[Provenance Library] +| https://anypoint.mulesoft.com/exchange/org.mule.examples/fhir-r4-provenance-api/[Provenance API] | Conformance -| https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fhir-r4-capabilitystatement-library/[CapabilityStatement Library] -| https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fhir-r4-capabilitystatement-api/[CapabilityStatement API] +| https://anypoint.mulesoft.com/exchange/org.mule.examples/fhir-r4-capabilitystatement-library/[CapabilityStatement Library] +| https://anypoint.mulesoft.com/exchange/org.mule.examples/fhir-r4-capabilitystatement-api/[CapabilityStatement API] | Administration -| https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fhir-r4-us-core-patient-library/[Patient Library] + -https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fhir-r4-practitioner-library/[Practitioner Library] + -https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fhir-r4-practitionerrole-library/[PractitionerRole Library] + -https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fhir-r4-device-library/[Device Library] + -https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fhir-r4-organization-library/[Organization Library] + -https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fhir-r4-location-library/[Location Library] + -https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fhir-r4-careteam-library/[CareTeam Library] + -https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fhir-r4-encounter-library/[Encounter Library] + - -| https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fhir-r4-us-core-patient-api/[Patient API*] + -https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fhir-r4-practitioner-api/[Practitioner API] + -https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fhir-r4-practitionerrole-api/[PractitionerRole API] + -https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fhir-r4-device-api/[Device API] + -https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fhir-r4-organization-api/[Organization API] + -https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fhir-r4-location-api/[Location API] + -https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fhir-r4-careteam-api/[CareTeam API] + -https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fhir-r4-encounter-api/[Encounter API] +| https://anypoint.mulesoft.com/exchange/org.mule.examples/fhir-r4-us-core-patient-library/[Patient Library] + +https://anypoint.mulesoft.com/exchange/org.mule.examples/fhir-r4-practitioner-library/[Practitioner Library] + +https://anypoint.mulesoft.com/exchange/org.mule.examples/fhir-r4-practitionerrole-library/[PractitionerRole Library] + +https://anypoint.mulesoft.com/exchange/org.mule.examples/fhir-r4-device-library/[Device Library] + +https://anypoint.mulesoft.com/exchange/org.mule.examples/fhir-r4-organization-library/[Organization Library] + +https://anypoint.mulesoft.com/exchange/org.mule.examples/fhir-r4-location-library/[Location Library] + +https://anypoint.mulesoft.com/exchange/org.mule.examples/fhir-r4-careteam-library/[CareTeam Library] + +https://anypoint.mulesoft.com/exchange/org.mule.examples/fhir-r4-encounter-library/[Encounter Library] + + +| https://anypoint.mulesoft.com/exchange/org.mule.examples/fhir-r4-us-core-patient-api/[Patient API*] + +https://anypoint.mulesoft.com/exchange/org.mule.examples/fhir-r4-practitioner-api/[Practitioner API] + +https://anypoint.mulesoft.com/exchange/org.mule.examples/fhir-r4-practitionerrole-api/[PractitionerRole API] + +https://anypoint.mulesoft.com/exchange/org.mule.examples/fhir-r4-device-api/[Device API] + +https://anypoint.mulesoft.com/exchange/org.mule.examples/fhir-r4-organization-api/[Organization API] + +https://anypoint.mulesoft.com/exchange/org.mule.examples/fhir-r4-location-api/[Location API] + +https://anypoint.mulesoft.com/exchange/org.mule.examples/fhir-r4-careteam-api/[CareTeam API] + +https://anypoint.mulesoft.com/exchange/org.mule.examples/fhir-r4-encounter-api/[Encounter API] | Clinical -| https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fhir-r4-us-core-allergyintolerance-library/[AllergyIntolerance Library] + -https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fhir-r4-careplan-library/[CarePlan Library] + -https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fhir-r4-goal-library/[Goal Library] + -https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fhir-r4-procedure-library/[Procedure Library] + -https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fhir-r4-us-core-condition-library/[Condition Library] + - -| https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fhir-r4-us-core-allergyintolerance-api/[AllergyIntolerance API*] + -https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fhir-r4-careplan-api/[CarePlan API] + -https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fhir-r4-goal-api/[Goal API] + -https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fhir-r4-procedure-api/[Procedure API] + -https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fhir-r4-us-core-condition-api/[Condition API] +| https://anypoint.mulesoft.com/exchange/org.mule.examples/fhir-r4-us-core-allergyintolerance-library/[AllergyIntolerance Library] + +https://anypoint.mulesoft.com/exchange/org.mule.examples/fhir-r4-careplan-library/[CarePlan Library] + +https://anypoint.mulesoft.com/exchange/org.mule.examples/fhir-r4-goal-library/[Goal Library] + +https://anypoint.mulesoft.com/exchange/org.mule.examples/fhir-r4-procedure-library/[Procedure Library] + +https://anypoint.mulesoft.com/exchange/org.mule.examples/fhir-r4-us-core-condition-library/[Condition Library] + + +| https://anypoint.mulesoft.com/exchange/org.mule.examples/fhir-r4-us-core-allergyintolerance-api/[AllergyIntolerance API*] + +https://anypoint.mulesoft.com/exchange/org.mule.examples/fhir-r4-careplan-api/[CarePlan API] + +https://anypoint.mulesoft.com/exchange/org.mule.examples/fhir-r4-goal-api/[Goal API] + +https://anypoint.mulesoft.com/exchange/org.mule.examples/fhir-r4-procedure-api/[Procedure API] + +https://anypoint.mulesoft.com/exchange/org.mule.examples/fhir-r4-us-core-condition-api/[Condition API] | Diagnostics -| https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fhir-r4-us-core-observation-library/[Observation Library] + -https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fhir-r4-diagnosticreport-library/[DiagnosticReport Library] -| https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fhir-r4-us-core-observation-api/[Observation API*] + -https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fhir-r4-diagnosticreport-api/[DiagnosticReport API] +| https://anypoint.mulesoft.com/exchange/org.mule.examples/fhir-r4-us-core-observation-library/[Observation Library] + +https://anypoint.mulesoft.com/exchange/org.mule.examples/fhir-r4-diagnosticreport-library/[DiagnosticReport Library] +| https://anypoint.mulesoft.com/exchange/org.mule.examples/fhir-r4-us-core-observation-api/[Observation API*] + +https://anypoint.mulesoft.com/exchange/org.mule.examples/fhir-r4-diagnosticreport-api/[DiagnosticReport API] | Medications -| https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fhir-r4-immunization-library/[Immunization Library] + -https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fhir-r4-medication-library/[Medication Library] + -https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fhir-r4-medicationrequest-library/[MedicationRequest Library] -| https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fhir-r4-immunization-api/[Immunization API] + -https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fhir-r4-medication-api/[Medication API] + -https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/fhir-r4-medicationrequest-api/[MedicationRequest API] +| https://anypoint.mulesoft.com/exchange/org.mule.examples/fhir-r4-immunization-library/[Immunization Library] + +https://anypoint.mulesoft.com/exchange/org.mule.examples/fhir-r4-medication-library/[Medication Library] + +https://anypoint.mulesoft.com/exchange/org.mule.examples/fhir-r4-medicationrequest-library/[MedicationRequest Library] +| https://anypoint.mulesoft.com/exchange/org.mule.examples/fhir-r4-immunization-api/[Immunization API] + +https://anypoint.mulesoft.com/exchange/org.mule.examples/fhir-r4-medication-api/[Medication API] + +https://anypoint.mulesoft.com/exchange/org.mule.examples/fhir-r4-medicationrequest-api/[MedicationRequest API] |=== _APIs marked with `*` have both FHIR R4 and US Core-specific Library and API specification available._ diff --git a/healthcare/2.22/modules/ROOT/pages/hl7-v2-fhir-converter.adoc b/healthcare/2.22/modules/ROOT/pages/hl7-v2-fhir-converter.adoc index 737ae28d6..d750bb00e 100644 --- a/healthcare/2.22/modules/ROOT/pages/hl7-v2-fhir-converter.adoc +++ b/healthcare/2.22/modules/ROOT/pages/hl7-v2-fhir-converter.adoc @@ -1,10 +1,10 @@ = HL7 v2 to FHIR Converter -The https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/hc-accelerator-hl7v2-to-fhir-sys-api[HL7 v2 to FHIR converter] comes with a ready to use template for HL7 v2 to FHIR conversion, which is based on the guidance provided by the https://build.fhir.org/ig/HL7/v2-to-fhir[HL7 v2 to FHIR Implementation Guide]. This template can be extended or modified to meet specific conversion requirements. +The https://anypoint.mulesoft.com/exchange/org.mule.examples/hc-accelerator-hl7v2-to-fhir-sys-api[HL7 v2 to FHIR converter] comes with a ready to use template for HL7 v2 to FHIR conversion, which is based on the guidance provided by the https://build.fhir.org/ig/HL7/v2-to-fhir[HL7 v2 to FHIR Implementation Guide]. This template can be extended or modified to meet specific conversion requirements. == Functional diagram -image:https://www.mulesoft.com/ext/solutions/draft/images/hc-hl7v2-to-fhir-usecase-diagram.png[hc-hl7v2-to-fhir-usecase-diagram.png,799,align="center"] +image:https://www.mulesoft.com/ext/solutions/images/hc-hl7v2-to-fhir-usecase-diagram.png[hc-hl7v2-to-fhir-usecase-diagram.png,799,align="center"] == Advantages diff --git a/healthcare/2.22/modules/ROOT/pages/index.adoc b/healthcare/2.22/modules/ROOT/pages/index.adoc index bc3ee64d6..e1c35f2b0 100644 --- a/healthcare/2.22/modules/ROOT/pages/index.adoc +++ b/healthcare/2.22/modules/ROOT/pages/index.adoc @@ -9,14 +9,14 @@ For solutions related to life sciences, the xref:life-sciences::index.adoc[MuleS The following describes the use cases supported by the MuleSoft Accelerator for Healthcare: -* https://www.anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/mulesoft-accelerator-for-healthcare/minor/{hls-version}/pages/Use%20case%201%20-%20Patient%20360/[Patient 360^] — This use case accelerates Patient 360 efforts by providing pre-built APIs and implementation templates to integrate critical data from EHRs with other emerging technologies and applications. This solution provides both HL7 v2 and FHIR-based capabilities to allow organizations to support a variety of use cases and realize value regardless of the industry standard that is present in their organization's ecosystem. -* https://www.anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/mulesoft-accelerator-for-healthcare/minor/{hls-version}/pages/Use%20case%202%20-%20CMS%20Interoperability/[CMS Interoperability^] — Includes assets to help you meet CMS Interoperability and Patient Access final rule. -* https://www.anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/mulesoft-accelerator-for-healthcare/minor/{hls-version}/pages/Use%20case%203%20-%20Labs%20integration/[Labs integration^] — Includes the The Electronic Laboratory Reporting (ELR) to CalREDIE implementation template, which helps you transmit laboratory reports that identify a notifiable condition to public health agencies (for example, California Department of Public Health). -* https://www.anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/mulesoft-accelerator-for-healthcare/minor/{hls-version}/pages/Use%20case%204%20-%20Appointment%20scheduling/[Appointment scheduling^] — Includes the Appointment Scheduling Process API for both Cerner and Epic, which enables call center agents to schedule, update, and cancel appointments on behalf of the patient. See the implementation template for more information. -* https://www.anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/mulesoft-accelerator-for-healthcare/minor/{hls-version}/pages/Use%20case%205%20-%20Benefits%20and%20eligibility%20verification/[Benefits and eligibility verification^] — Enables call center agents and care staff to perform real-time benefits and eligibility verification. Providers can electronically verify a patient's insurance coverage in real-time for medical treatment directly within Salesforce Health Cloud. -* https://www.anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/mulesoft-accelerator-for-healthcare/minor/{hls-version}/pages/Use%20case%206%20-%20Prior%20Authorization/[Prior Authorization^] — Includes CRD, DTR, and PAS API specifications and implementation templates to automate the prior authorization process for more immediate authorizations, leading to better outcomes and increased satisfaction for patients, providers, and payers. -* https://www.anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/mulesoft-accelerator-for-healthcare/minor/{hls-version}/pages/Use%20case%207%20-%20Population%20health%20management/[Population health management^] - Convert and surface valuable population health data into Amazon HealthLake to improve clinical outcomes. -* https://www.anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/mulesoft-accelerator-for-healthcare/minor/{hls-version}/pages/Use%20case%208%20-%20Qualified%20health%20information%20networks%20integration/[Qualified Health Information Networks Integration] - Streamline patient onboarding and remove manual data entry by integrating with external healthcare organizations to gather and ingest patient data. +* https://www.anypoint.mulesoft.com/exchange/org.mule.examples/mulesoft-accelerator-for-healthcare/minor/{hls-version}/pages/Use%20case%201%20-%20Patient%20360/[Patient 360^] — This use case accelerates Patient 360 efforts by providing pre-built APIs and implementation templates to integrate critical data from EHRs with other emerging technologies and applications. This solution provides both HL7 v2 and FHIR-based capabilities to allow organizations to support a variety of use cases and realize value regardless of the industry standard that is present in their organization's ecosystem. +* https://www.anypoint.mulesoft.com/exchange/org.mule.examples/mulesoft-accelerator-for-healthcare/minor/{hls-version}/pages/Use%20case%202%20-%20CMS%20Interoperability/[CMS Interoperability^] — Includes assets to help you meet CMS Interoperability and Patient Access final rule. +* https://www.anypoint.mulesoft.com/exchange/org.mule.examples/mulesoft-accelerator-for-healthcare/minor/{hls-version}/pages/Use%20case%203%20-%20Labs%20integration/[Labs integration^] — Includes the The Electronic Laboratory Reporting (ELR) to CalREDIE implementation template, which helps you transmit laboratory reports that identify a notifiable condition to public health agencies (for example, California Department of Public Health). +* https://www.anypoint.mulesoft.com/exchange/org.mule.examples/mulesoft-accelerator-for-healthcare/minor/{hls-version}/pages/Use%20case%204%20-%20Appointment%20scheduling/[Appointment scheduling^] — Includes the Appointment Scheduling Process API for both Cerner and Epic, which enables call center agents to schedule, update, and cancel appointments on behalf of the patient. See the implementation template for more information. +* https://www.anypoint.mulesoft.com/exchange/org.mule.examples/mulesoft-accelerator-for-healthcare/minor/{hls-version}/pages/Use%20case%205%20-%20Benefits%20and%20eligibility%20verification/[Benefits and eligibility verification^] — Enables call center agents and care staff to perform real-time benefits and eligibility verification. Providers can electronically verify a patient's insurance coverage in real-time for medical treatment directly within Salesforce Health Cloud. +* https://www.anypoint.mulesoft.com/exchange/org.mule.examples/mulesoft-accelerator-for-healthcare/minor/{hls-version}/pages/Use%20case%206%20-%20Prior%20Authorization/[Prior Authorization^] — Includes CRD, DTR, and PAS API specifications and implementation templates to automate the prior authorization process for more immediate authorizations, leading to better outcomes and increased satisfaction for patients, providers, and payers. +* https://www.anypoint.mulesoft.com/exchange/org.mule.examples/mulesoft-accelerator-for-healthcare/minor/{hls-version}/pages/Use%20case%207%20-%20Population%20health%20management/[Population health management^] - Convert and surface valuable population health data into Amazon HealthLake to improve clinical outcomes. +* https://www.anypoint.mulesoft.com/exchange/org.mule.examples/mulesoft-accelerator-for-healthcare/minor/{hls-version}/pages/Use%20case%208%20-%20Qualified%20health%20information%20networks%20integration/[Qualified Health Information Networks Integration] - Streamline patient onboarding and remove manual data entry by integrating with external healthcare organizations to gather and ingest patient data. === Use Case Agnostic Assets @@ -33,4 +33,4 @@ The following use-case agnostic assets are also available: * xref:prerequisites.adoc[Prerequisites] * xref:fhir-r4-assets.adoc[Available Assets] * xref:release-notes::accelerators/healthcare/healthcare-release-notes.adoc[Release Notes] -* https://www.anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/mulesoft-accelerator-for-healthcare/[MuleSoft Accelerator for Healthcare on Exchange^] +* https://www.anypoint.mulesoft.com/exchange/org.mule.examples/mulesoft-accelerator-for-healthcare/[MuleSoft Accelerator for Healthcare on Exchange^] diff --git a/healthcare/2.22/modules/ROOT/pages/sfdc-data-cloud-setup-guide.adoc b/healthcare/2.22/modules/ROOT/pages/sfdc-data-cloud-setup-guide.adoc index 84494a74b..0eb1a7e3e 100644 --- a/healthcare/2.22/modules/ROOT/pages/sfdc-data-cloud-setup-guide.adoc +++ b/healthcare/2.22/modules/ROOT/pages/sfdc-data-cloud-setup-guide.adoc @@ -1,7 +1,7 @@ = Salesforce Data Cloud Setup Guide :hls-version: 2.20 -The following provides guidance on Salesforce Data Cloud setup required for the https://www.anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/mulesoft-accelerator-for-healthcare/minor/{hls-version}/pages/Use%20case%207%20-%20Population%20health%20management/[Population Health Management] use case. +The following provides guidance on Salesforce Data Cloud setup required for the https://www.anypoint.mulesoft.com/exchange/org.mule.examples/mulesoft-accelerator-for-healthcare/minor/{hls-version}/pages/Use%20case%207%20-%20Population%20health%20management/[Population Health Management] use case. * <> * <> @@ -25,7 +25,7 @@ Connectors are specialized data streams that communicate with external sources t Customer Data Platform has connectors for: Marketing Cloud Email Studio, MobileConnect, MobilePush, Marketing Cloud Data Extensions, for Salesforce CRM, Ingestion API, Interaction Studio, and for data outside Salesforce via cloud storage providers. -The https://www.anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/mulesoft-accelerator-for-healthcare/minor/{hls-version}/pages/Use%20case%207%20-%20Population%20health%20management/[Population Health Management] use case uses the following connectors to ingest data into cdp: +The https://www.anypoint.mulesoft.com/exchange/org.mule.examples/mulesoft-accelerator-for-healthcare/minor/{hls-version}/pages/Use%20case%207%20-%20Population%20health%20management/[Population Health Management] use case uses the following connectors to ingest data into cdp: * Salesforce CRM - to connect data from a Salesforce Health Cloud instance to Data Cloud * Ingestion API - to connect data from external source systems like Azure, Epic, Cerner, and other EHR systems via MuleSoft's CDP connector. @@ -50,7 +50,7 @@ Follow the below steps to create connection to your Salesforce Health Cloud org. After you create your Customer Data Platform instance and set up your Salesforce Health Cloud connection, you can install standard data bundles that are powered by data kits to deploy data within Customer Data Platform. -For the https://www.anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/mulesoft-accelerator-for-healthcare/minor/{hls-version}/pages/Use%20case%207%20-%20Population%20health%20management/[Population Health Management] use case, Service Cloud bundle is installed. Refer https://help.salesforce.com/s/articleView?id=sf.c360_a_install_standard_data_bundles_powered_by_data_kits.htm&type=5[link] to install the bundle. +For the https://www.anypoint.mulesoft.com/exchange/org.mule.examples/mulesoft-accelerator-for-healthcare/minor/{hls-version}/pages/Use%20case%207%20-%20Population%20health%20management/[Population Health Management] use case, Service Cloud bundle is installed. Refer https://help.salesforce.com/s/articleView?id=sf.c360_a_install_standard_data_bundles_powered_by_data_kits.htm&type=5[link] to install the bundle. === Ingestion API @@ -63,14 +63,14 @@ Follow the steps in each section below to setup and configure ingestion API to p . In Data Cloud, select Data Cloud Setup. . Click Ingestion API. . Click New, enter a name for the API source, then click Save. On the details page for the new connector, you must upload a schema file in OpenAPI (OAS) format with a `.yaml` file extension. The schema file describes how data transferred via the API is structured. *Note:* Ingestion API schemas have set requirements - review the schema requirements before ingestion. -. Click Upload Schema and navigate to the location of the file you want to use. Select the file and click Open. For the https://www.anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/mulesoft-accelerator-for-healthcare/minor/{hls-version}/pages/Use%20case%207%20-%20Population%20health%20management/[Population Health Management] use case the schema file `mule-hls-cdp-connector-schema.yaml` is available under `/src/test/resources` of the Implementation Template https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/hls-salesforce-cdp-sys-api[HLS CDP System API]. +. Click Upload Schema and navigate to the location of the file you want to use. Select the file and click Open. For the https://www.anypoint.mulesoft.com/exchange/org.mule.examples/mulesoft-accelerator-for-healthcare/minor/{hls-version}/pages/Use%20case%207%20-%20Population%20health%20management/[Population Health Management] use case the schema file `mule-hls-cdp-connector-schema.yaml` is available under `/src/test/resources` of the Implementation Template https://anypoint.mulesoft.com/exchange/org.mule.examples/hls-salesforce-cdp-sys-api[HLS CDP System API]. . Preview all the detected objects and their attributes in your schema. . Click Save. The connector page reflects the updated status. . After the schema file is uploaded, you can create data streams to begin sending data from your source system. -For the https://www.anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/mulesoft-accelerator-for-healthcare/minor/{hls-version}/pages/Use%20case%207%20-%20Population%20health%20management/[Population Health Management] use case, the external systems Azure, Epic, Cerner, and other EHR systems contain data to be pushed to Data Cloud through MuleSoft's CDP connector using the Ingestion API. The name of the Connector used will appear under `Ingestion API` drop down while creating a new Data Stream. +For the https://www.anypoint.mulesoft.com/exchange/org.mule.examples/mulesoft-accelerator-for-healthcare/minor/{hls-version}/pages/Use%20case%207%20-%20Population%20health%20management/[Population Health Management] use case, the external systems Azure, Epic, Cerner, and other EHR systems contain data to be pushed to Data Cloud through MuleSoft's CDP connector using the Ingestion API. The name of the Connector used will appear under `Ingestion API` drop down while creating a new Data Stream. -The schema used for the https://www.anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/mulesoft-accelerator-for-healthcare/minor/{hls-version}/pages/Use%20case%207%20-%20Population%20health%20management/[Population Health Management] use case can be found in the implementation template. The following objects are added for this use case: +The schema used for the https://www.anypoint.mulesoft.com/exchange/org.mule.examples/mulesoft-accelerator-for-healthcare/minor/{hls-version}/pages/Use%20case%207%20-%20Population%20health%20management/[Population Health Management] use case can be found in the implementation template. The following objects are added for this use case: * condition * immunization @@ -116,7 +116,7 @@ To create data streams from Salesforce CRM starter bundle: Refer this https://help.salesforce.com/s/articleView?id=sf.c360_a_create_crm_starter_bundle.htm&type=5[link] to create data streams using starter bundle to begin the flow of data from a Salesforce Health Cloud data source. -For the https://www.anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/mulesoft-accelerator-for-healthcare/minor/{hls-version}/pages/Use%20case%207%20-%20Population%20health%20management/[Population Health Management] use case, data streams for Salesforce Health Cloud Account and Contact objects are created using Salesforce CRM Service bundle. +For the https://www.anypoint.mulesoft.com/exchange/org.mule.examples/mulesoft-accelerator-for-healthcare/minor/{hls-version}/pages/Use%20case%207%20-%20Population%20health%20management/[Population Health Management] use case, data streams for Salesforce Health Cloud Account and Contact objects are created using Salesforce CRM Service bundle. To create data streams from Salesforce Health Cloud data source: @@ -134,11 +134,11 @@ To add permissions for objects and their fields: Repeat these steps for all objects and fields you want to ingest into Data Cloud. Now, create data streams for the required objects by following the steps in this https://help.salesforce.com/s/articleView?id=sf.c360_a_create_crm_data_stream.htm&type=5&language=en_US[link]. -For the https://www.anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/mulesoft-accelerator-for-healthcare/minor/{hls-version}/pages/Use%20case%207%20-%20Population%20health%20management/[Population Health Management] use case, data streams for Contact Point Objects, Identifier, and ContactContactRelation are created. +For the https://www.anypoint.mulesoft.com/exchange/org.mule.examples/mulesoft-accelerator-for-healthcare/minor/{hls-version}/pages/Use%20case%207%20-%20Population%20health%20management/[Population Health Management] use case, data streams for Contact Point Objects, Identifier, and ContactContactRelation are created. === Create an Ingestion API data stream -After uploading the schema file for Ingestion API Connector, create a data stream from your source objects. For the https://www.anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/mulesoft-accelerator-for-healthcare/minor/{hls-version}/pages/Use%20case%207%20-%20Population%20health%20management/[Population Health Management] use case, data streams for condition, immunization and webEngagement are created. +After uploading the schema file for Ingestion API Connector, create a data stream from your source objects. For the https://www.anypoint.mulesoft.com/exchange/org.mule.examples/mulesoft-accelerator-for-healthcare/minor/{hls-version}/pages/Use%20case%207%20-%20Population%20health%20management/[Population Health Management] use case, data streams for condition, immunization and webEngagement are created. . In Data Cloud, select Data Streams. . In recently viewed data streams, click New. @@ -147,7 +147,7 @@ After uploading the schema file for Ingestion API Connector, create a data strea . Check the objects found in the schema you want to use and click Next. . At the New Data Stream dialog box, configure the following: ** Primary Key: A true Primary Key needs to be leveraged for Data Cloud. If one does not exist, you will need to create a Formula Field for the Primary Key. - ** Category: Choose between Profile, Engagement or Other. *Note:* For the https://www.anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/mulesoft-accelerator-for-healthcare/minor/{hls-version}/pages/Use%20case%207%20-%20Population%20health%20management/[Population Health Management] use case, the category for all the objects in the schema are Other. + ** Category: Choose between Profile, Engagement or Other. *Note:* For the https://www.anypoint.mulesoft.com/exchange/org.mule.examples/mulesoft-accelerator-for-healthcare/minor/{hls-version}/pages/Use%20case%207%20-%20Population%20health%20management/[Population Health Management] use case, the category for all the objects in the schema are Other. ** Record Modified Date: To order Profile modifications, use the Record Modified Date. *Note:* A record modified field that indicates when each incoming record was last modified is required for Engagement object types. While the field requirement is optional for Profile and Other objects, it is encouraged to provide the record modified field to ensure incoming records are processed in the right order. ** Date Time Field: Used to represent when Engagement from an external source occurred at ingestion. ** Click the `New Formula Field` (Optional). @@ -156,7 +156,7 @@ After uploading the schema file for Ingestion API Connector, create a data strea . Click Deploy. If you have only created one data stream, the data stream's record page appears. If you've created multiple data streams, the view refreshes to show all recently viewed data streams. . Wait up to one hour for your data to appear in your data stream. Map your data stream to data model objects to start using your data. -For the https://www.anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/mulesoft-accelerator-for-healthcare/minor/{hls-version}/pages/Use%20case%207%20-%20Population%20health%20management/[Population Health Management] use case, data stream is created for the objects added in schema by following the steps above. At step 6, click `New Formula field` with `Field Label` as `uniqueId` with `Formula Return` Type as `Text`. Under `Transformation Formula`, the formula is created as below for each of the object. +For the https://www.anypoint.mulesoft.com/exchange/org.mule.examples/mulesoft-accelerator-for-healthcare/minor/{hls-version}/pages/Use%20case%207%20-%20Population%20health%20management/[Population Health Management] use case, data stream is created for the objects added in schema by following the steps above. At step 6, click `New Formula field` with `Field Label` as `uniqueId` with `Formula Return` Type as `Text`. Under `Transformation Formula`, the formula is created as below for each of the object. * condition: `CONCAT(sourceField['patientMrn'],"~",sourceField['conditionCode'])` * immunization: `CONCAT(sourceField['patientMrn'],"~",sourceField['vaccineCode'],"~",sourceField['vaccineStatus'],"~",sourceField['vaccineDate'])` @@ -178,9 +178,9 @@ As part of your Connected App set up for Ingestion API, you must select the foll The MuleSoft Connector for CDP provides customers a pipeline to send data into Data Cloud. This connector works with the Data Cloud Bulk and Streaming API, depending on the operation you configure. Each API call uses a request/response pattern over an HTTPS connection. All required request headers, error handling, and HTTPS connection configurations are built into the connector. -Refer to the https://dev-docs-internal.kqa.msap.io/beta-accelerators/salesforce-cdp-connector/1.1/[CDP Connector documentation] for additional details on configuration and available operations. +Refer to the https://docs.mulesoft.com/salesforce-cdp-connector/1.1/[CDP Connector documentation] for additional details on configuration and available operations. -For the https://www.anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/mulesoft-accelerator-for-healthcare/minor/{hls-version}/pages/Use%20case%207%20-%20Population%20health%20management/[Population Health Management] use case, refer to the https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/hls-salesforce-cdp-sys-api-spec/[HLS CDP System API] specification and https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/hls-salesforce-cdp-sys-api[HLS CDP System API] implementation template assets. +For the https://www.anypoint.mulesoft.com/exchange/org.mule.examples/mulesoft-accelerator-for-healthcare/minor/{hls-version}/pages/Use%20case%207%20-%20Population%20health%20management/[Population Health Management] use case, refer to the https://anypoint.mulesoft.com/exchange/org.mule.examples/hls-salesforce-cdp-sys-api-spec/[HLS CDP System API] specification and https://anypoint.mulesoft.com/exchange/org.mule.examples/hls-salesforce-cdp-sys-api[HLS CDP System API] implementation template assets. == Data modeling and data mapping @@ -220,7 +220,7 @@ Objects in the data model created by the customer for Data Cloud implementation When mapping your party area data, complete the required fields and relationships to successfully use Identity Resolution, Segmentation, and Activation. -Default mapping exists for Account and Contact Objects if service Bundle is used to create data streams. For the https://www.anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/mulesoft-accelerator-for-healthcare/minor/{hls-version}/pages/Use%20case%207%20-%20Population%20health%20management/[Population Health Management] use case, the default mapping from Account and Contact DSOs to Contact Point DMOs are removed. Data Streams to Data Model Objects (DMO) are mapped as per the below table. +Default mapping exists for Account and Contact Objects if service Bundle is used to create data streams. For the https://www.anypoint.mulesoft.com/exchange/org.mule.examples/mulesoft-accelerator-for-healthcare/minor/{hls-version}/pages/Use%20case%207%20-%20Population%20health%20management/[Population Health Management] use case, the default mapping from Account and Contact DSOs to Contact Point DMOs are removed. Data Streams to Data Model Objects (DMO) are mapped as per the below table. |=== | Data Stream Name (DSO) | Custom Data Model Object (DMO) | Standard Data Model Object (DMO) @@ -250,7 +250,7 @@ Default mapping exists for Account and Contact Objects if service Bundle is used | |=== -For the https://www.anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/mulesoft-accelerator-for-healthcare/minor/{hls-version}/pages/Use%20case%207%20-%20Population%20health%20management/[Population Health Management] use case, below Data Mappings are created between Data Streams and DMOs/custom DMOs. +For the https://www.anypoint.mulesoft.com/exchange/org.mule.examples/mulesoft-accelerator-for-healthcare/minor/{hls-version}/pages/Use%20case%207%20-%20Population%20health%20management/[Population Health Management] use case, below Data Mappings are created between Data Streams and DMOs/custom DMOs. *Data Mappings of Account Data Stream to Account DMO* @@ -490,7 +490,7 @@ Some of the mappings are added by default from Bundle. Mapping needs to be chang | userId |=== -For the https://www.anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/mulesoft-accelerator-for-healthcare/minor/{hls-version}/pages/Use%20case%207%20-%20Population%20health%20management/[Population Health Management] use case, below DMOs and relationships needs to be maintained when Data mappings are done between Data Stream and DMOs. +For the https://www.anypoint.mulesoft.com/exchange/org.mule.examples/mulesoft-accelerator-for-healthcare/minor/{hls-version}/pages/Use%20case%207%20-%20Population%20health%20management/[Population Health Management] use case, below DMOs and relationships needs to be maintained when Data mappings are done between Data Stream and DMOs. *Data Relationships between DMOs* @@ -542,7 +542,7 @@ For the https://www.anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10 == Identity Resolution -NOTE: For the https://www.anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/mulesoft-accelerator-for-healthcare/minor/{hls-version}/pages/Use%20case%207%20-%20Population%20health%20management/[Population Health Management] use case, identity resolution rulesets were not required. +NOTE: For the https://www.anypoint.mulesoft.com/exchange/org.mule.examples/mulesoft-accelerator-for-healthcare/minor/{hls-version}/pages/Use%20case%207%20-%20Population%20health%20management/[Population Health Management] use case, identity resolution rulesets were not required. Use identity resolution to consolidate data from difference sources into a comprehensive view of your customer called a unified profile. Identity resolution uses matching and reconciliation rules to link data about people into unified profiles. Each unified profile contains all the unique contact point values from all sources. @@ -550,7 +550,7 @@ Set up identity resolution rulesets after mapping source data to data model obje == Calculated Insights -NOTE: For the https://www.anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/mulesoft-accelerator-for-healthcare/minor/{hls-version}/pages/Use%20case%207%20-%20Population%20health%20management/[Population Health Management] use case, Calculated Insights were not required. +NOTE: For the https://www.anypoint.mulesoft.com/exchange/org.mule.examples/mulesoft-accelerator-for-healthcare/minor/{hls-version}/pages/Use%20case%207%20-%20Population%20health%20management/[Population Health Management] use case, Calculated Insights were not required. The Calculated Insights feature lets you define and calculate multidimensional metrics on your entire digital state stored in Salesforce Customer Data Platform. @@ -577,7 +577,7 @@ TIP: Leave the Publish Schedule as *Don't Refresh for now*, and then fill it in Segment On: Segment On defines the target entity (object) used to build your segment. For example, you can build a segment on Unified Individual or Account or Individual. You can choose any entity marked as type Profile during ingestion. -For the https://www.anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/mulesoft-accelerator-for-healthcare/minor/{hls-version}/pages/Use%20case%207%20-%20Population%20health%20management/[Population Health Management] use case, create Segments on Individual. +For the https://www.anypoint.mulesoft.com/exchange/org.mule.examples/mulesoft-accelerator-for-healthcare/minor/{hls-version}/pages/Use%20case%207%20-%20Population%20health%20management/[Population Health Management] use case, create Segments on Individual. Example segment: @@ -615,7 +615,7 @@ For the Publish Schedule, we update it to reflect a Publish Schedule of every 12 Create activation targets to build, and activate data segments with Data Cloud. -For the https://www.anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/mulesoft-accelerator-for-healthcare/minor/{hls-version}/pages/Use%20case%207%20-%20Population%20health%20management/[Population Health Management] use case, create a Marketing Cloud Activation Target. +For the https://www.anypoint.mulesoft.com/exchange/org.mule.examples/mulesoft-accelerator-for-healthcare/minor/{hls-version}/pages/Use%20case%207%20-%20Population%20health%20management/[Population Health Management] use case, create a Marketing Cloud Activation Target. *Activation Target - Marketing Cloud:* @@ -624,8 +624,8 @@ Before creating an activation target, configure the Marketing Cloud connector in . Click Setup gear icon and then Data Cloud Setup. . Select Marketing Cloud. . Enter the Credentials to authenticate your Marketing Cloud account. You can proceed with the next step in the setup only if the authentication is successful. -. Data Source setup - this step is optional. This needs to be set up if you are planning to ingest data from Marketing Cloud into Data Cloud. *Note:* For the https://www.anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/mulesoft-accelerator-for-healthcare/minor/{hls-version}/pages/Use%20case%207%20-%20Population%20health%20management/[Population Health Management] use case, this step is skipped. -. Select Business Units to activate - this step is optional. To add or remove business units (BU), click the arrows between the two columns. *Note:* For the https://www.anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/mulesoft-accelerator-for-healthcare/minor/{hls-version}/pages/Use%20case%207%20-%20Population%20health%20management/[Population Health Management] use case, select business units to publish segments to Marketing Cloud. +. Data Source setup - this step is optional. This needs to be set up if you are planning to ingest data from Marketing Cloud into Data Cloud. *Note:* For the https://www.anypoint.mulesoft.com/exchange/org.mule.examples/mulesoft-accelerator-for-healthcare/minor/{hls-version}/pages/Use%20case%207%20-%20Population%20health%20management/[Population Health Management] use case, this step is skipped. +. Select Business Units to activate - this step is optional. To add or remove business units (BU), click the arrows between the two columns. *Note:* For the https://www.anypoint.mulesoft.com/exchange/org.mule.examples/mulesoft-accelerator-for-healthcare/minor/{hls-version}/pages/Use%20case%207%20-%20Population%20health%20management/[Population Health Management] use case, select business units to publish segments to Marketing Cloud. Create an activation target in Data Cloud to publish segments to Marketing Cloud business units. diff --git a/healthcare/2.22/modules/ROOT/pages/sfdc-health-cloud-setup-guide.adoc b/healthcare/2.22/modules/ROOT/pages/sfdc-health-cloud-setup-guide.adoc index a4876f44d..b7bac4b99 100644 --- a/healthcare/2.22/modules/ROOT/pages/sfdc-health-cloud-setup-guide.adoc +++ b/healthcare/2.22/modules/ROOT/pages/sfdc-health-cloud-setup-guide.adoc @@ -41,13 +41,13 @@ This accelerator uses MuleSoft's HL7 Connector. If you're required to use custom * Modify the message structure schema file (for example, ADT_A31.esl) to include your custom segment (or modify an existing segment to fit your needs). * Modify the basedefs.esl file to include the changes for segment definitions. -The https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/hc-accelerator-sfdc-adt-api/[implementation template^] for storing ADT messages in Salesforce Health Cloud shows an example of custom segment processing. Please check the src/main/resources/config/hl7/v2_2 folder in the implementation template. This folder has the necessary changes required to process custom segment `ZG1`. +The https://anypoint.mulesoft.com/exchange/org.mule.examples/hc-accelerator-sfdc-adt-api/[implementation template^] for storing ADT messages in Salesforce Health Cloud shows an example of custom segment processing. Please check the src/main/resources/config/hl7/v2_2 folder in the implementation template. This folder has the necessary changes required to process custom segment `ZG1`. -For additional details on HL7 Connector, please refer to the https://dev-docs-internal.kqa.msap.io/beta-accelerators/connectors/hl7/hl7-connector[documentation^]. +For additional details on HL7 Connector, please refer to the https://docs.mulesoft.com/connectors/hl7/hl7-connector[documentation^]. == Maven POM Parent -In addition to some global settings and repository references, the Maven https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/accelerator-pom-parent-src/[POM parent^] config also defines the versions of all MuleSoft connectors and modules used by applications. Refer to the https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/accelerator-pom-parent-src/[Exchange documentation^] for information on how to make changes to the POM parent file. +In addition to some global settings and repository references, the Maven https://anypoint.mulesoft.com/exchange/org.mule.examples/accelerator-pom-parent-src/[POM parent^] config also defines the versions of all MuleSoft connectors and modules used by applications. Refer to the https://anypoint.mulesoft.com/exchange/org.mule.examples/accelerator-pom-parent-src/[Exchange documentation^] for information on how to make changes to the POM parent file. == See Also diff --git a/healthcare/2.22/modules/ROOT/pages/smart-fhir-okta.adoc b/healthcare/2.22/modules/ROOT/pages/smart-fhir-okta.adoc index 293f4ce13..809023dd4 100644 --- a/healthcare/2.22/modules/ROOT/pages/smart-fhir-okta.adoc +++ b/healthcare/2.22/modules/ROOT/pages/smart-fhir-okta.adoc @@ -1,6 +1,6 @@ = SMART on FHIR with Okta -See the https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/hc-accelerator-okta-smartfhir/[Okta SMART on FHIR - Implementation Template^] asset, which walks you through how to set up a reference SMART on FHIR implementation on Anypoint Platform using Okta as the identity provider. +See the https://anypoint.mulesoft.com/exchange/org.mule.examples/hc-accelerator-okta-smartfhir/[Okta SMART on FHIR - Implementation Template^] asset, which walks you through how to set up a reference SMART on FHIR implementation on Anypoint Platform using Okta as the identity provider. The **S**ubstitutable **M**edical **A**pplications and **R**eusable **T**echnology (SMART) is a web/mobile app, which is typically embedded in EHR but can also serve as a standalone smartphone app. SMART on FHIR provides a consistent approach to security and data requirements for health applications. It also provides a workflow to securely request access to data, receive the data, and use the data. @@ -20,13 +20,13 @@ SMART on FHIR addresses the following three key aspects: Anypoint platform supports SMART on FHIR in the following ways: * Identity and access management -** Provisioning third-party https://dev-docs-internal.kqa.msap.io/beta-accelerators/access-management/configure-client-management-openid-task[OIDC client provider^] like Okta for identity management -** Out-of-the-box https://dev-docs-internal.kqa.msap.io/beta-accelerators/api-manager/2.x/policy-openid-connect[OpenID Connect token enforcement policy^] +** Provisioning third-party https://docs.mulesoft.com/access-management/configure-client-management-openid-task[OIDC client provider^] like Okta for identity management +** Out-of-the-box https://docs.mulesoft.com/api-manager/2.x/policy-openid-connect[OpenID Connect token enforcement policy^] ** Leverage OAuth provider information in the `authentication` object for custom policy * Access to the data using FHIR based APIs ** MuleSoft Accelerator for Healthcare provides FHIR R4 specifications for all the FHIR resources -** Out-of-the-box https://dev-docs-internal.kqa.msap.io/beta-accelerators/api-manager/2.x/cors-policy[cross origin resource sharing (CORS) policy^] enables cross origin data exchange. +** Out-of-the-box https://docs.mulesoft.com/api-manager/2.x/cors-policy[cross origin resource sharing (CORS) policy^] enables cross origin data exchange. == See Also diff --git a/healthcare/2.22/modules/ROOT/pages/x12-fhir-converter.adoc b/healthcare/2.22/modules/ROOT/pages/x12-fhir-converter.adoc index 354475b59..69f9d3caa 100644 --- a/healthcare/2.22/modules/ROOT/pages/x12-fhir-converter.adoc +++ b/healthcare/2.22/modules/ROOT/pages/x12-fhir-converter.adoc @@ -1,10 +1,10 @@ = X12 to FHIR Converter -The https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/hls-fhir-to-x12-sys-api/[X12 to FHIR converter^] comes with a ready to use template for https://x12.org/[X12^] to FHIR conversion. This template can be extended or modified to meet specific conversion requirements. The converter converts FHIR R4 to X12 formats and its responses from X12 to FHIR R4. +The https://anypoint.mulesoft.com/exchange/org.mule.examples/hls-fhir-to-x12-sys-api/[X12 to FHIR converter^] comes with a ready to use template for https://x12.org/[X12^] to FHIR conversion. This template can be extended or modified to meet specific conversion requirements. The converter converts FHIR R4 to X12 formats and its responses from X12 to FHIR R4. == Functional Diagram -image:https://www.mulesoft.com/ext/solutions/draft/images/hls-x12-fhir-fx-diagram.svg[X12 to FHIR converter functional diagram,900,align="center"] +image:https://www.mulesoft.com/ext/solutions/images/hls-x12-fhir-fx-diagram.svg[X12 to FHIR converter functional diagram,900,align="center"] == Advantages diff --git a/life-sciences/1.1/modules/ROOT/pages/index.adoc b/life-sciences/1.1/modules/ROOT/pages/index.adoc index ffe4663cd..b81e53282 100644 --- a/life-sciences/1.1/modules/ROOT/pages/index.adoc +++ b/life-sciences/1.1/modules/ROOT/pages/index.adoc @@ -7,8 +7,8 @@ The MuleSoft Accelerator for Life Sciences helps pharmaceuticals, medical device The following describes the use cases supported by the MuleSoft Accelerator for Life Sciences: -* https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/mulesoft-accelerator-for-life-sciences/minor/{ls-version}/pages/Use%20case%201%20-%20Clinical%20trial%20analytics/[Clinical trial analytics^] - Run more intelligent, data-driven trials with pre-built assets that surface relevant study and stakeholder information from Veeva. Easily consolidate this information into data lakes for analysis in business intelligence platforms like Tableau. -* https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/mulesoft-accelerator-for-life-sciences/minor/{ls-version}/pages/Use%20case%202%20-%20Site%20payment%20modernization/[Site payment modernization^] - Streamline the clinical trial site payment process by integrating relevant study data from CTMS systems, like Veeva, to generate and transmit payments to sites. +* https://anypoint.mulesoft.com/exchange/org.mule.examples/mulesoft-accelerator-for-life-sciences/minor/{ls-version}/pages/Use%20case%201%20-%20Clinical%20trial%20analytics/[Clinical trial analytics^] - Run more intelligent, data-driven trials with pre-built assets that surface relevant study and stakeholder information from Veeva. Easily consolidate this information into data lakes for analysis in business intelligence platforms like Tableau. +* https://anypoint.mulesoft.com/exchange/org.mule.examples/mulesoft-accelerator-for-life-sciences/minor/{ls-version}/pages/Use%20case%202%20-%20Site%20payment%20modernization/[Site payment modernization^] - Streamline the clinical trial site payment process by integrating relevant study data from CTMS systems, like Veeva, to generate and transmit payments to sites. == Other Related Solutions @@ -27,4 +27,4 @@ The following are links to related and supporting documentation: * xref:prerequisites.adoc[Prerequisites] * xref:ls-assets.adoc[Available Assets] * xref:release-notes::accelerators/life-sciences/life-sciences-release-notes.adoc[Release Notes] -* https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/mulesoft-accelerator-for-life-sciences/[MuleSoft Accelerator for Life Sciences on Exchange^] \ No newline at end of file +* https://anypoint.mulesoft.com/exchange/org.mule.examples/mulesoft-accelerator-for-life-sciences/[MuleSoft Accelerator for Life Sciences on Exchange^] \ No newline at end of file diff --git a/life-sciences/1.1/modules/ROOT/pages/ls-assets.adoc b/life-sciences/1.1/modules/ROOT/pages/ls-assets.adoc index 65ae880dd..c02ca5d82 100644 --- a/life-sciences/1.1/modules/ROOT/pages/ls-assets.adoc +++ b/life-sciences/1.1/modules/ROOT/pages/ls-assets.adoc @@ -7,28 +7,28 @@ Accelerator assets include API specifications, implementation templates, custom [cols="40,30,30",width=100%] |=== | AWS Storage System API -| https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/hls-aws-storage-sys-api-spec/[API Specification^] -| https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/hls-aws-storage-sys-api/[Implementation Template^] +| https://anypoint.mulesoft.com/exchange/org.mule.examples/hls-aws-storage-sys-api-spec/[API Specification^] +| https://anypoint.mulesoft.com/exchange/org.mule.examples/hls-aws-storage-sys-api/[Implementation Template^] | Azure Storage System API -| https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/hls-azure-storage-sys-api-spec/[API Specification^] -| https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/hls-azure-storage-sys-api/[Implementation Template^] +| https://anypoint.mulesoft.com/exchange/org.mule.examples/hls-azure-storage-sys-api-spec/[API Specification^] +| https://anypoint.mulesoft.com/exchange/org.mule.examples/hls-azure-storage-sys-api/[Implementation Template^] | Clinical Trials Tableau System API -| https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/hls-clinical-trials-tableau-sys-api-spec/[API Specification^] -| https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/hls-clinical-trials-tableau-sys-api/[Implementation Template^] +| https://anypoint.mulesoft.com/exchange/org.mule.examples/hls-clinical-trials-tableau-sys-api-spec/[API Specification^] +| https://anypoint.mulesoft.com/exchange/org.mule.examples/hls-clinical-trials-tableau-sys-api/[Implementation Template^] | SAP Accounts Payable System API -| https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/mfg-sap-accounts-payable-sys-api-spec[API Specification^] -| https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/hls-sap-accounts-payable-sys-api/[Implementation Template^] +| https://anypoint.mulesoft.com/exchange/org.mule.examples/mfg-sap-accounts-payable-sys-api-spec[API Specification^] +| https://anypoint.mulesoft.com/exchange/org.mule.examples/hls-sap-accounts-payable-sys-api/[Implementation Template^] | Veeva CDMS System API -| https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/hls-veeva-cdms-sys-api-spec[API Specification^] -| https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/hls-veeva-cdms-sys-api/[Implementation Template^] +| https://anypoint.mulesoft.com/exchange/org.mule.examples/hls-veeva-cdms-sys-api-spec[API Specification^] +| https://anypoint.mulesoft.com/exchange/org.mule.examples/hls-veeva-cdms-sys-api/[Implementation Template^] | Veeva CTMS System API -| https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/hls-veeva-ctms-sys-api-spec/[API Specification^] -| https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/hls-veeva-ctms-sys-api/[Implementation Template^] +| https://anypoint.mulesoft.com/exchange/org.mule.examples/hls-veeva-ctms-sys-api-spec/[API Specification^] +| https://anypoint.mulesoft.com/exchange/org.mule.examples/hls-veeva-ctms-sys-api/[Implementation Template^] |=== === Process APIs @@ -36,12 +36,12 @@ Accelerator assets include API specifications, implementation templates, custom [cols="40,30,30",width=100%] |=== | Clinical Trials Process API -| https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/hls-clinical-trials-prc-api-spec/[API Specification^] -| https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/hls-clinical-trials-prc-api/[Implementation Template^] +| https://anypoint.mulesoft.com/exchange/org.mule.examples/hls-clinical-trials-prc-api-spec/[API Specification^] +| https://anypoint.mulesoft.com/exchange/org.mule.examples/hls-clinical-trials-prc-api/[Implementation Template^] | Site Payments Process API | -| https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/hls-site-payments-prc-api/[Implementation Template^] +| https://anypoint.mulesoft.com/exchange/org.mule.examples/hls-site-payments-prc-api/[Implementation Template^] |=== == See Also diff --git a/manufacturing/1.3/modules/ROOT/pages/index.adoc b/manufacturing/1.3/modules/ROOT/pages/index.adoc index e6968e58b..bf6a52275 100644 --- a/manufacturing/1.3/modules/ROOT/pages/index.adoc +++ b/manufacturing/1.3/modules/ROOT/pages/index.adoc @@ -8,24 +8,24 @@ MuleSoft Accelerator for Manufacturing equips discrete and process manufacturers The following use cases are supported by the MuleSoft Accelerator for Manufacturing: -* https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/mulesoft-accelerator-for-manufacturing/minor/{mfg-version}/pages/Use%20case%201%20-%20Run-rate%20business%20management/[Run-rate business management^] — This solution seamlessly sends customer and order data from SAP into Manufacturing Cloud. It also sends product data and price lists from a PIM system into Salesforce Manufacturing Cloud. +* https://anypoint.mulesoft.com/exchange/org.mule.examples/mulesoft-accelerator-for-manufacturing/minor/{mfg-version}/pages/Use%20case%201%20-%20Run-rate%20business%20management/[Run-rate business management^] — This solution seamlessly sends customer and order data from SAP into Manufacturing Cloud. It also sends product data and price lists from a PIM system into Salesforce Manufacturing Cloud. -* https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/mulesoft-accelerator-for-manufacturing/minor/{mfg-version}/pages/Use%20case%202%20-%20Sales%20rebate%20management/[Sales rebate management^] — This solution seamlessly syncs customer and sales order data between SAP and Salesforce Manufacturing Cloud, and creates a credit memo in SAP in line with program guidelines and calculations. +* https://anypoint.mulesoft.com/exchange/org.mule.examples/mulesoft-accelerator-for-manufacturing/minor/{mfg-version}/pages/Use%20case%202%20-%20Sales%20rebate%20management/[Sales rebate management^] — This solution seamlessly syncs customer and sales order data between SAP and Salesforce Manufacturing Cloud, and creates a credit memo in SAP in line with program guidelines and calculations. -* https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/mulesoft-accelerator-for-manufacturing/minor/{mfg-version}/pages/Use%20case%203%20-%20Total%20productive%20maintenance/[Total productive maintenance^] - This solution seamlessly aggregates factory floor equipment data, like temperature and vibration, into a data visualization tool. This data visualization tool can model the data, and a business user can pre-define business criteria to trigger equipment maintenance work orders in a servicing case management system. +* https://anypoint.mulesoft.com/exchange/org.mule.examples/mulesoft-accelerator-for-manufacturing/minor/{mfg-version}/pages/Use%20case%203%20-%20Total%20productive%20maintenance/[Total productive maintenance^] - This solution seamlessly aggregates factory floor equipment data, like temperature and vibration, into a data visualization tool. This data visualization tool can model the data, and a business user can pre-define business criteria to trigger equipment maintenance work orders in a servicing case management system. === Shared Use Cases -The following use cases provided by the https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/mulesoft-accelerator-for-sap/[MuleSoft Accelerator for SAP^] are also leveraged by this accelerator: +The following use cases provided by the https://anypoint.mulesoft.com/exchange/org.mule.examples/mulesoft-accelerator-for-sap/[MuleSoft Accelerator for SAP^] are also leveraged by this accelerator: -* https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/mulesoft-accelerator-for-sap/minor/{sap-version}/pages/Use%20case%202%20-%20Procure-to-pay/[Procure-to-pay^] - Streamline your procure-to-pay process with pre-built APIs, implementation templates, and connectors to seamlessly move supplier, invoice, and goods receipt data. -* https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/mulesoft-accelerator-for-sap/minor/{sap-version}/pages/Use%20case%203a%20-%20Quote-to-cash%20-%20Salesforce%20and%20SAP%20S4HANA/[Quote-to-cash: Salesforce and SAP S/4HANA^] - Sync order, inventory, and customer data from opportunity to close between Salesforce Sales Cloud (including CPQ) and SAP S/4HANA. -* https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/mulesoft-accelerator-for-sap/minor/{sap-version}/pages/Use%20case%203b%20-%20Quote-to-cash%20-%20B2B%20EDI/[Quote-to-cash: B2B EDI^] - Enable the sales order/purchase order and post-purchase order transaction flows between businesses, with one business serving as the buyer and the other as the supplier. -* https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/mulesoft-accelerator-for-sap/minor/{sap-version}/pages/Use%20case%204%20-%20Real-time%20and%20bulk%20data%20lakes%20integration/[Real-time and bulk data lakes integration^] - Send sales order, inventory, and customer information from source systems to common data lake storage repositories. +* https://anypoint.mulesoft.com/exchange/org.mule.examples/mulesoft-accelerator-for-sap/minor/{sap-version}/pages/Use%20case%202%20-%20Procure-to-pay/[Procure-to-pay^] - Streamline your procure-to-pay process with pre-built APIs, implementation templates, and connectors to seamlessly move supplier, invoice, and goods receipt data. +* https://anypoint.mulesoft.com/exchange/org.mule.examples/mulesoft-accelerator-for-sap/minor/{sap-version}/pages/Use%20case%203a%20-%20Quote-to-cash%20-%20Salesforce%20and%20SAP%20S4HANA/[Quote-to-cash: Salesforce and SAP S/4HANA^] - Sync order, inventory, and customer data from opportunity to close between Salesforce Sales Cloud (including CPQ) and SAP S/4HANA. +* https://anypoint.mulesoft.com/exchange/org.mule.examples/mulesoft-accelerator-for-sap/minor/{sap-version}/pages/Use%20case%203b%20-%20Quote-to-cash%20-%20B2B%20EDI/[Quote-to-cash: B2B EDI^] - Enable the sales order/purchase order and post-purchase order transaction flows between businesses, with one business serving as the buyer and the other as the supplier. +* https://anypoint.mulesoft.com/exchange/org.mule.examples/mulesoft-accelerator-for-sap/minor/{sap-version}/pages/Use%20case%204%20-%20Real-time%20and%20bulk%20data%20lakes%20integration/[Real-time and bulk data lakes integration^] - Send sales order, inventory, and customer information from source systems to common data lake storage repositories. == See Also * xref:accelerators-home::getting-started.adoc[Getting Started Guide] * xref:prerequisites.adoc[Prerequisites] * xref:release-notes.adoc[Release Notes] -* https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/mulesoft-accelerator-for-manufacturing/[MuleSoft Accelerator for Manufacturing on Exchange^] +* https://anypoint.mulesoft.com/exchange/org.mule.examples/mulesoft-accelerator-for-manufacturing/[MuleSoft Accelerator for Manufacturing on Exchange^] diff --git a/manufacturing/1.3/modules/ROOT/pages/mfg-assets.adoc b/manufacturing/1.3/modules/ROOT/pages/mfg-assets.adoc index c3a379d0d..83c38503b 100644 --- a/manufacturing/1.3/modules/ROOT/pages/mfg-assets.adoc +++ b/manufacturing/1.3/modules/ROOT/pages/mfg-assets.adoc @@ -7,56 +7,56 @@ Accelerator assets include API specifications, implementation templates, custom [cols="40,30,30",width=100%] |=== | MFG Salesforce Customers System API -| https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/accelerator-salesforce-customers-sys-api/[API Specification^] -| https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/mfg-salesforce-customers-sys-api/[Implementation Template^] +| https://anypoint.mulesoft.com/exchange/org.mule.examples/accelerator-salesforce-customers-sys-api/[API Specification^] +| https://anypoint.mulesoft.com/exchange/org.mule.examples/mfg-salesforce-customers-sys-api/[Implementation Template^] | MFG Salesforce Manufacture System API -| https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/mfg-salesforce-manufacture-sys-api-spec/[API Specification^] -| https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/mfg-salesforce-manufacture-sys-api/[Implementation Template^] +| https://anypoint.mulesoft.com/exchange/org.mule.examples/mfg-salesforce-manufacture-sys-api-spec/[API Specification^] +| https://anypoint.mulesoft.com/exchange/org.mule.examples/mfg-salesforce-manufacture-sys-api/[Implementation Template^] | MFG Salesforce Orders System API -| https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/mfg-salesforce-orders-sys-api-spec/[API Specification^] -| https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/mfg-salesforce-orders-sys-api/[Implementation Template^] +| https://anypoint.mulesoft.com/exchange/org.mule.examples/mfg-salesforce-orders-sys-api-spec/[API Specification^] +| https://anypoint.mulesoft.com/exchange/org.mule.examples/mfg-salesforce-orders-sys-api/[Implementation Template^] | MFG Salesforce Products System API -| https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/mfg-salesforce-products-sys-api-spec/[API Specification^] -| https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/mfg-salesforce-products-sys-api/[Implementation Template^] +| https://anypoint.mulesoft.com/exchange/org.mule.examples/mfg-salesforce-products-sys-api-spec/[API Specification^] +| https://anypoint.mulesoft.com/exchange/org.mule.examples/mfg-salesforce-products-sys-api/[Implementation Template^] | MFG SAP S/4HANA Customers System API -| https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/accelerator-saphana-customers-sys-api/[API Specification^] -| https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/mfg-saphana-customers-sys-api/[Implementation Template^] +| https://anypoint.mulesoft.com/exchange/org.mule.examples/accelerator-saphana-customers-sys-api/[API Specification^] +| https://anypoint.mulesoft.com/exchange/org.mule.examples/mfg-saphana-customers-sys-api/[Implementation Template^] | MFG SAP S/4HANA Orders System API -| https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/accelerator-saphana-orders-sys-api/[API Specification^] -| https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/mfg-saphana-orders-sys-api/[Implementation Template^] +| https://anypoint.mulesoft.com/exchange/org.mule.examples/accelerator-saphana-orders-sys-api/[API Specification^] +| https://anypoint.mulesoft.com/exchange/org.mule.examples/mfg-saphana-orders-sys-api/[Implementation Template^] | Manufacturing MDM System API -| https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/accelerator-mdm-sys-api/[API Specification^] -| https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/mfg-mdm-sys-api/[Implementation Template^] +| https://anypoint.mulesoft.com/exchange/org.mule.examples/accelerator-mdm-sys-api/[API Specification^] +| https://anypoint.mulesoft.com/exchange/org.mule.examples/mfg-mdm-sys-api/[Implementation Template^] | PIM System API -| https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/accelerator-pim-sys-api/[API Specification^] -| https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/accel-pim-sys-api/[Implementation Template^] +| https://anypoint.mulesoft.com/exchange/org.mule.examples/accelerator-pim-sys-api/[API Specification^] +| https://anypoint.mulesoft.com/exchange/org.mule.examples/accel-pim-sys-api/[Implementation Template^] | MFG Salesforce Rebate System API -| https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/mfg-salesforce-rebate-sys-api-spec/[API Specification^] -| https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/mfg-salesforce-rebate-sys-api/[Implementation Template^] +| https://anypoint.mulesoft.com/exchange/org.mule.examples/mfg-salesforce-rebate-sys-api-spec/[API Specification^] +| https://anypoint.mulesoft.com/exchange/org.mule.examples/mfg-salesforce-rebate-sys-api/[Implementation Template^] | MFG SAP S/4HANA Credit Memo System API -| https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/mfg-saphana-creditmemo-sys-api-spec/[API Specification^] -| https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/mfg-saphana-creditmemo-sys-api/[Implementation Template^] +| https://anypoint.mulesoft.com/exchange/org.mule.examples/mfg-saphana-creditmemo-sys-api-spec/[API Specification^] +| https://anypoint.mulesoft.com/exchange/org.mule.examples/mfg-saphana-creditmemo-sys-api/[Implementation Template^] | MFG OSIPI Machine Data System API -| https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/mfg-osipi-machinedata-sys-api-spec/[API Specification^] -| https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/mfg-osipi-machinedata-sys-api/[Implementation Template^] +| https://anypoint.mulesoft.com/exchange/org.mule.examples/mfg-osipi-machinedata-sys-api-spec/[API Specification^] +| https://anypoint.mulesoft.com/exchange/org.mule.examples/mfg-osipi-machinedata-sys-api/[Implementation Template^] | MFG RedShift Machine Data System API -| https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/mfg-dw-machinedata-sys-api-spec/[API Specification^] -| https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/mfg-dw-machinedata-sys-api/[Implementation Template^] +| https://anypoint.mulesoft.com/exchange/org.mule.examples/mfg-dw-machinedata-sys-api-spec/[API Specification^] +| https://anypoint.mulesoft.com/exchange/org.mule.examples/mfg-dw-machinedata-sys-api/[Implementation Template^] | MFG Salesforce Cases System API -| https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/mfg-salesforce-cases-sys-api-spec/[API Specification^] -| https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/mfg-salesforce-cases-sys-api/[Implementation Template^] +| https://anypoint.mulesoft.com/exchange/org.mule.examples/mfg-salesforce-cases-sys-api-spec/[API Specification^] +| https://anypoint.mulesoft.com/exchange/org.mule.examples/mfg-salesforce-cases-sys-api/[Implementation Template^] |=== == Process APIs @@ -64,32 +64,32 @@ Accelerator assets include API specifications, implementation templates, custom [cols="40,30,30",width=100%] |=== | MFG Bulk Load Process API -| https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/mfg-bulk-load-prc-api-spec/[API Specification^] -| https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/mfg-bulk-load-prc-api/[Implementation Template^] +| https://anypoint.mulesoft.com/exchange/org.mule.examples/mfg-bulk-load-prc-api-spec/[API Specification^] +| https://anypoint.mulesoft.com/exchange/org.mule.examples/mfg-bulk-load-prc-api/[Implementation Template^] | MFG Customers Process API -| https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/accelerator-customers-prc-api/[API Specification^] -| https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/mfg-customers-prc-api/[Implementation Template^] +| https://anypoint.mulesoft.com/exchange/org.mule.examples/accelerator-customers-prc-api/[API Specification^] +| https://anypoint.mulesoft.com/exchange/org.mule.examples/mfg-customers-prc-api/[Implementation Template^] | MFG Orders Process API -| https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/accelerator-orders-prc-api/[API Specification^] -| https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/mfg-orders-prc-api/[Implementation Template^] +| https://anypoint.mulesoft.com/exchange/org.mule.examples/accelerator-orders-prc-api/[API Specification^] +| https://anypoint.mulesoft.com/exchange/org.mule.examples/mfg-orders-prc-api/[Implementation Template^] | MFG Products Process API -| https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/accelerator-products-prc-api/[API Specification^] -| https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/mfg-products-prc-api/[Implementation Template^] +| https://anypoint.mulesoft.com/exchange/org.mule.examples/accelerator-products-prc-api/[API Specification^] +| https://anypoint.mulesoft.com/exchange/org.mule.examples/mfg-products-prc-api/[Implementation Template^] | PIM Sync Process API -| https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/accelerator-pim-sync-prc-api/[API Specification^] -| https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/accel-pim-sync-prc-api/[Implementation Template^] +| https://anypoint.mulesoft.com/exchange/org.mule.examples/accelerator-pim-sync-prc-api/[API Specification^] +| https://anypoint.mulesoft.com/exchange/org.mule.examples/accel-pim-sync-prc-api/[Implementation Template^] | MFG Rebate Process API -| https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/mfg-rebate-prc-api-spec/[API Specification^] -| https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/mfg-rebate-prc-api/[Implementation Template^] +| https://anypoint.mulesoft.com/exchange/org.mule.examples/mfg-rebate-prc-api-spec/[API Specification^] +| https://anypoint.mulesoft.com/exchange/org.mule.examples/mfg-rebate-prc-api/[Implementation Template^] | MFG Machine Data Process API -| https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/mfg-machinedata-prc-api-spec/[API Specification^] -| https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/mfg-machinedata-prc-api/[Implementation Template^] +| https://anypoint.mulesoft.com/exchange/org.mule.examples/mfg-machinedata-prc-api-spec/[API Specification^] +| https://anypoint.mulesoft.com/exchange/org.mule.examples/mfg-machinedata-prc-api/[Implementation Template^] |=== == Experience APIs @@ -97,16 +97,16 @@ Accelerator assets include API specifications, implementation templates, custom [cols="40,30,30",width=100%] |=== | MFG Bulk Load Experience API -| https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/mfg-bulk-load-exp-api-spec/[API Specification^] -| https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/mfg-bulk-load-exp-api/[Implementation Template^] +| https://anypoint.mulesoft.com/exchange/org.mule.examples/mfg-bulk-load-exp-api-spec/[API Specification^] +| https://anypoint.mulesoft.com/exchange/org.mule.examples/mfg-bulk-load-exp-api/[Implementation Template^] | MFG Salesforce Experience API -| https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/accelerator-salesforce-exp-api[API Specification^] -| https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/mfg-salesforce-exp-api/[Implementation Template^] +| https://anypoint.mulesoft.com/exchange/org.mule.examples/accelerator-salesforce-exp-api[API Specification^] +| https://anypoint.mulesoft.com/exchange/org.mule.examples/mfg-salesforce-exp-api/[Implementation Template^] | MFG Tableau Machine Data Experience API -| https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/mfg-tableau-workorders-exp-api-spec/[API Specification^] -| https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/mfg-tableau-workorders-exp-api/[Implementation Template^] +| https://anypoint.mulesoft.com/exchange/org.mule.examples/mfg-tableau-workorders-exp-api-spec/[API Specification^] +| https://anypoint.mulesoft.com/exchange/org.mule.examples/mfg-tableau-workorders-exp-api/[Implementation Template^] |=== == Listeners & Handlers @@ -114,13 +114,13 @@ Accelerator assets include API specifications, implementation templates, custom [cols="70,30",width=100%] |=== | MFG SAP Event Listener -| https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/mfg-sap-event-listener/[Implementation Template^] +| https://anypoint.mulesoft.com/exchange/org.mule.examples/mfg-sap-event-listener/[Implementation Template^] | MFG SFTP CIM Handler -| https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/mfg-sftp-cim-handler/[Implementation Template^] +| https://anypoint.mulesoft.com/exchange/org.mule.examples/mfg-sftp-cim-handler/[Implementation Template^] | MFG Salesforce Topic Listener -| https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/mfg-salesforce-topic-listener/[Implementation Template^] +| https://anypoint.mulesoft.com/exchange/org.mule.examples/mfg-salesforce-topic-listener/[Implementation Template^] |=== == Custom Components @@ -128,17 +128,17 @@ Accelerator assets include API specifications, implementation templates, custom [cols="70,30",width=100%] |=== | MFG Rebate Library -| https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/mfg-rebate-library/[Source^] +| https://anypoint.mulesoft.com/exchange/org.mule.examples/mfg-rebate-library/[Source^] |=== == Shared APIs [cols="40,30,30",width=100%] |=== -| Accelerator Email System API | https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/accelerator-email-sys-api[API Specification^] | https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/accel-email-sys-api[Implementation Template^] -| Accelerator Slack System API | https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/accelerator-slack-sys-api[API Specification^] | https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/accel-slack-sys-api[Implementation Template^] -| Accelerator SMS System API | https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/accelerator-sms-sys-api[API Specification^] | https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/accel-sms-sys-api[Implementation Template^] -| Accelerator Notifications Process API | https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/accelerator-notifications-prc-api[API Specification^] | https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/accel-notifications-prc-api/[Implementation Template^] +| Accelerator Email System API | https://anypoint.mulesoft.com/exchange/org.mule.examples/accelerator-email-sys-api[API Specification^] | https://anypoint.mulesoft.com/exchange/org.mule.examples/accel-email-sys-api[Implementation Template^] +| Accelerator Slack System API | https://anypoint.mulesoft.com/exchange/org.mule.examples/accelerator-slack-sys-api[API Specification^] | https://anypoint.mulesoft.com/exchange/org.mule.examples/accel-slack-sys-api[Implementation Template^] +| Accelerator SMS System API | https://anypoint.mulesoft.com/exchange/org.mule.examples/accelerator-sms-sys-api[API Specification^] | https://anypoint.mulesoft.com/exchange/org.mule.examples/accel-sms-sys-api[Implementation Template^] +| Accelerator Notifications Process API | https://anypoint.mulesoft.com/exchange/org.mule.examples/accelerator-notifications-prc-api[API Specification^] | https://anypoint.mulesoft.com/exchange/org.mule.examples/accel-notifications-prc-api/[Implementation Template^] |=== == Shared Components @@ -146,13 +146,13 @@ Accelerator assets include API specifications, implementation templates, custom [cols="70,30",width=100%] |=== | Accelerator Common Core -| https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/accelerator-common-core-src/[Source^] +| https://anypoint.mulesoft.com/exchange/org.mule.examples/accelerator-common-core-src/[Source^] | POM Parent -| https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/accelerator-pom-parent-src/[Source^] +| https://anypoint.mulesoft.com/exchange/org.mule.examples/accelerator-pom-parent-src/[Source^] | ID Graph Lightning Web Component -| https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/accelerator-idgraph-lwc-src/[Source^] +| https://anypoint.mulesoft.com/exchange/org.mule.examples/accelerator-idgraph-lwc-src/[Source^] |=== == See Also diff --git a/manufacturing/1.3/modules/ROOT/pages/mfg-setup-guide.adoc b/manufacturing/1.3/modules/ROOT/pages/mfg-setup-guide.adoc index 4ac151447..6f8181428 100644 --- a/manufacturing/1.3/modules/ROOT/pages/mfg-setup-guide.adoc +++ b/manufacturing/1.3/modules/ROOT/pages/mfg-setup-guide.adoc @@ -22,7 +22,7 @@ The following fields must be created in the corresponding objects. == Anypoint MQ Configuration -The Anypoint-MQ-Queues-Exchanges Postman collection in the https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/mfg-common-resources-src/[MFG Common Resources project^] will pre-create all MQ destinations required by the accelerator components. +The Anypoint-MQ-Queues-Exchanges Postman collection in the https://anypoint.mulesoft.com/exchange/org.mule.examples/mfg-common-resources-src/[MFG Common Resources project^] will pre-create all MQ destinations required by the accelerator components. The collection requires the dev environment template to be imported into your Postman workspace and assigned proper values first. The following MQ destinations will be created upon successful execution. @@ -54,7 +54,7 @@ For communication arrangement SAP_COM_0287 to replicate the sales orders pricing . Enter the *Communication arrangement* app to edit or create the arrangement. . At outbound services sections, complete with the following: -image::https://www.mulesoft.com/ext/solutions/draft/images/mfg-saphana-setup-1.png[Configure SAP_COM_0287] +image::https://www.mulesoft.com/ext/solutions/images/mfg-saphana-setup-1.png[Configure SAP_COM_0287] == Custom Fields Create the following fields in the corresponding objects for the use case: diff --git a/manufacturing/1.3/modules/ROOT/pages/release-notes.adoc b/manufacturing/1.3/modules/ROOT/pages/release-notes.adoc index 5c3f7d112..301067456 100644 --- a/manufacturing/1.3/modules/ROOT/pages/release-notes.adoc +++ b/manufacturing/1.3/modules/ROOT/pages/release-notes.adoc @@ -7,7 +7,7 @@ === Total Productive Maintenance Use Case -This release introduces the https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/mulesoft-accelerator-for-manufacturing/minor/{mfg-version}/pages/Use%20case%203%20-%20Total%20productive%20maintenance/[Total productive maintenance^] use case, which helps manufacturers to maintain factory floor equipments. +This release introduces the https://anypoint.mulesoft.com/exchange/org.mule.examples/mulesoft-accelerator-for-manufacturing/minor/{mfg-version}/pages/Use%20case%203%20-%20Total%20productive%20maintenance/[Total productive maintenance^] use case, which helps manufacturers to maintain factory floor equipments. == v1.1 @@ -15,7 +15,7 @@ This release introduces the https://anypoint.mulesoft.com/exchange/0b4cad67-8f23 === Sales Rebate Management Use Case -This release introduces the https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/mulesoft-accelerator-for-manufacturing/minor/{mfg-version}/pages/Use%20case%202%20-%20Sales%20rebate%20management/[Sales rebate management^] use case, which helps manufacturers to seamlessly manage sales rebate programs. +This release introduces the https://anypoint.mulesoft.com/exchange/org.mule.examples/mulesoft-accelerator-for-manufacturing/minor/{mfg-version}/pages/Use%20case%202%20-%20Sales%20rebate%20management/[Sales rebate management^] use case, which helps manufacturers to seamlessly manage sales rebate programs. This release also includes the following enhancements: @@ -29,7 +29,7 @@ This release also includes the following enhancements: This is the first release of the MuleSoft Accelerator for Manufacturing. -This release introduces the https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/mulesoft-accelerator-for-manufacturing/minor/{mfg-version}/pages/Use%20case%201%20-%20Run-rate%20business%20management/[Run-rate business management^] use case, which helps streamline sales agreements and account forecasts in Salesforce Manufacturing Cloud. +This release introduces the https://anypoint.mulesoft.com/exchange/org.mule.examples/mulesoft-accelerator-for-manufacturing/minor/{mfg-version}/pages/Use%20case%201%20-%20Run-rate%20business%20management/[Run-rate business management^] use case, which helps streamline sales agreements and account forecasts in Salesforce Manufacturing Cloud. == See Also diff --git a/manufacturing/1.3/modules/ROOT/pages/sftp-setup-guide.adoc b/manufacturing/1.3/modules/ROOT/pages/sftp-setup-guide.adoc index d2912adaf..06751f64a 100644 --- a/manufacturing/1.3/modules/ROOT/pages/sftp-setup-guide.adoc +++ b/manufacturing/1.3/modules/ROOT/pages/sftp-setup-guide.adoc @@ -6,7 +6,7 @@ This setup guide enables customers to upload existing customer, product, and ord _Load data to Manufacturing Cloud_ -image::https://www.mulesoft.com/ext/solutions/draft/images/mfg-data-load.png[mfg-data-load] +image::https://www.mulesoft.com/ext/solutions/images/mfg-data-load.png[mfg-data-load] === Functional Considerations diff --git a/manufacturing/1.3/modules/ROOT/pages/tableau-setup-guide.adoc b/manufacturing/1.3/modules/ROOT/pages/tableau-setup-guide.adoc index 4008acfe0..49a716c84 100644 --- a/manufacturing/1.3/modules/ROOT/pages/tableau-setup-guide.adoc +++ b/manufacturing/1.3/modules/ROOT/pages/tableau-setup-guide.adoc @@ -21,13 +21,13 @@ . Click on *File* tab, select *Import Workbook* and browse `mfg-tableau-workorders-exp-api/src/main/resources/workbook/FactoryEquipmentDashboard.twbx` file and click on the *Open* button. . Edit Amazon Redshift connection details. -image::https://www.mulesoft.com/ext/solutions/draft/images/mfg-edit-redshift.png[mfg-edit-redshift.png] +image::https://www.mulesoft.com/ext/solutions/images/mfg-edit-redshift.png[mfg-edit-redshift.png] == Steps to create work order . In the *Submit a Work Order* dialogue box, the user can manage the Priority, Machine Id and provide a Reason to submit a work order. + + - image:https://www.mulesoft.com/ext/solutions/draft/images/mfg-submit-work-order.png[mfg-submit-work-order.png] + + image:https://www.mulesoft.com/ext/solutions/images/mfg-submit-work-order.png[mfg-submit-work-order.png] + . Click on *Create Work Order* which will create a case in Service Cloud. == Steps to Publish Workbook into Tableau Online. @@ -35,7 +35,7 @@ image::https://www.mulesoft.com/ext/solutions/draft/images/mfg-edit-redshift.png . Click on *Server* and select *Publish Workbook*. . Click on *Connect*, enter email address and password to sign in. + + -image:https://www.mulesoft.com/ext/solutions/draft/images/mfg-tableau-online-publish.png[mfg-tableau-online-publish.png] + +image:https://www.mulesoft.com/ext/solutions/images/mfg-tableau-online-publish.png[mfg-tableau-online-publish.png] + + . In the *Publish Workbook to Tableau Online* window, complete the *Name* and *Description* fields. . Click on the *Publish* button. @@ -45,14 +45,14 @@ image:https://www.mulesoft.com/ext/solutions/draft/images/mfg-tableau-online-pub . Login into https://sso.online.tableau.com/public/idp/SSO[Tableau Online] . Click on *Watch* and select *Alerts* + + -image:https://www.mulesoft.com/ext/solutions/draft/images/mfg-tableau-online-alert.png[mfg-tableau-online-alert.png] + +image:https://www.mulesoft.com/ext/solutions/images/mfg-tableau-online-alert.png[mfg-tableau-online-alert.png] + + . Click on the *Create* button on the right side which opens the 'Create Alert' dialogue box. . Users can select the condition and threshold and users can provide the subject details and select the alert condition (for example, daily). . Users can provide the recipient details in the *Recipients* field and click on *Create Alert*. . An alert will be sent to the recipient. -image::https://www.mulesoft.com/ext/solutions/draft/images/mfg-email-alert.png[mfg-email-alert.png] +image::https://www.mulesoft.com/ext/solutions/images/mfg-email-alert.png[mfg-email-alert.png] == See Also diff --git a/manufacturing/1.4/modules/ROOT/pages/index.adoc b/manufacturing/1.4/modules/ROOT/pages/index.adoc index fe77f164f..a7c3dbd1a 100644 --- a/manufacturing/1.4/modules/ROOT/pages/index.adoc +++ b/manufacturing/1.4/modules/ROOT/pages/index.adoc @@ -8,24 +8,24 @@ MuleSoft Accelerator for Manufacturing equips discrete and process manufacturers The following use cases are supported by the MuleSoft Accelerator for Manufacturing: -* https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/mulesoft-accelerator-for-manufacturing/minor/{mfg-version}/pages/Use%20case%201%20-%20Account%20and%20product%20and%20order%20sync/[Account and product and order sync^] — Streamline account forecasts by connecting critical account, product, and order data from your ERP to CRM. This example will show how to accomplish this using SAP S/4HANA and Salesforce Manufacturing Cloud. +* https://anypoint.mulesoft.com/exchange/org.mule.examples/mulesoft-accelerator-for-manufacturing/minor/{mfg-version}/pages/Use%20case%201%20-%20Account%20and%20product%20and%20order%20sync/[Account and product and order sync^] — Streamline account forecasts by connecting critical account, product, and order data from your ERP to CRM. This example will show how to accomplish this using SAP S/4HANA and Salesforce Manufacturing Cloud. -* https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/mulesoft-accelerator-for-manufacturing/minor/{mfg-version}/pages/Use%20case%202%20-%20Sales%20rebate%20management/[Sales rebate management^] — This solution seamlessly syncs customer and sales order data between SAP and Salesforce Manufacturing Cloud, and creates a credit memo in SAP in line with program guidelines and calculations. +* https://anypoint.mulesoft.com/exchange/org.mule.examples/mulesoft-accelerator-for-manufacturing/minor/{mfg-version}/pages/Use%20case%202%20-%20Sales%20rebate%20management/[Sales rebate management^] — This solution seamlessly syncs customer and sales order data between SAP and Salesforce Manufacturing Cloud, and creates a credit memo in SAP in line with program guidelines and calculations. -* https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/mulesoft-accelerator-for-manufacturing/minor/{mfg-version}/pages/Use%20case%203%20-%20Total%20productive%20maintenance/[Total productive maintenance^] - This solution seamlessly aggregates factory floor equipment data, like temperature and vibration, into a data visualization tool. This data visualization tool can model the data, and a business user can pre-define business criteria to trigger equipment maintenance work orders in a servicing case management system. +* https://anypoint.mulesoft.com/exchange/org.mule.examples/mulesoft-accelerator-for-manufacturing/minor/{mfg-version}/pages/Use%20case%203%20-%20Total%20productive%20maintenance/[Total productive maintenance^] - This solution seamlessly aggregates factory floor equipment data, like temperature and vibration, into a data visualization tool. This data visualization tool can model the data, and a business user can pre-define business criteria to trigger equipment maintenance work orders in a servicing case management system. === Shared Use Cases -The following use cases provided by the https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/mulesoft-accelerator-for-sap/[MuleSoft Accelerator for SAP^] are also leveraged by this accelerator: +The following use cases provided by the https://anypoint.mulesoft.com/exchange/org.mule.examples/mulesoft-accelerator-for-sap/[MuleSoft Accelerator for SAP^] are also leveraged by this accelerator: -* https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/mulesoft-accelerator-for-sap/minor/{sap-version}/pages/Use%20case%202%20-%20Procure-to-pay/[Procure-to-pay^] - Streamline your procure-to-pay process with pre-built APIs, implementation templates, and connectors to seamlessly move supplier, invoice, and goods receipt data. -* https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/mulesoft-accelerator-for-sap/minor/{sap-version}/pages/Use%20case%203a%20-%20Quote-to-cash%20-%20Salesforce%20and%20SAP%20S4HANA/[Quote-to-cash: Salesforce and SAP S/4HANA^] - Sync order, inventory, and customer data from opportunity to close between Salesforce Sales Cloud (including CPQ) and SAP S/4HANA. -* https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/mulesoft-accelerator-for-sap/minor/{sap-version}/pages/Use%20case%203b%20-%20Quote-to-cash%20-%20B2B%20EDI/[Quote-to-cash: B2B EDI^] - Enable the sales order/purchase order and post-purchase order transaction flows between businesses, with one business serving as the buyer and the other as the supplier. -* https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/mulesoft-accelerator-for-sap/minor/{sap-version}/pages/Use%20case%204%20-%20Real-time%20and%20bulk%20data%20lakes%20integration/[Real-time and bulk data lakes integration^] - Send sales order, inventory, and customer information from source systems to common data lake storage repositories. +* https://anypoint.mulesoft.com/exchange/org.mule.examples/mulesoft-accelerator-for-sap/minor/{sap-version}/pages/Use%20case%202%20-%20Procure-to-pay/[Procure-to-pay^] - Streamline your procure-to-pay process with pre-built APIs, implementation templates, and connectors to seamlessly move supplier, invoice, and goods receipt data. +* https://anypoint.mulesoft.com/exchange/org.mule.examples/mulesoft-accelerator-for-sap/minor/{sap-version}/pages/Use%20case%203a%20-%20Quote-to-cash%20-%20Salesforce%20and%20SAP%20S4HANA/[Quote-to-cash: Salesforce and SAP S/4HANA^] - Sync order, inventory, and customer data from opportunity to close between Salesforce Sales Cloud (including CPQ) and SAP S/4HANA. +* https://anypoint.mulesoft.com/exchange/org.mule.examples/mulesoft-accelerator-for-sap/minor/{sap-version}/pages/Use%20case%203b%20-%20Quote-to-cash%20-%20B2B%20EDI/[Quote-to-cash: B2B EDI^] - Enable the sales order/purchase order and post-purchase order transaction flows between businesses, with one business serving as the buyer and the other as the supplier. +* https://anypoint.mulesoft.com/exchange/org.mule.examples/mulesoft-accelerator-for-sap/minor/{sap-version}/pages/Use%20case%204%20-%20Real-time%20and%20bulk%20data%20lakes%20integration/[Real-time and bulk data lakes integration^] - Send sales order, inventory, and customer information from source systems to common data lake storage repositories. == See Also * xref:accelerators-home::getting-started.adoc[Getting Started Guide] * xref:prerequisites.adoc[Prerequisites] * xref:release-notes::accelerators/manufacturing/manufacturing-release-notes.adoc[Release Notes] -* https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/mulesoft-accelerator-for-manufacturing/[MuleSoft Accelerator for Manufacturing on Exchange^] +* https://anypoint.mulesoft.com/exchange/org.mule.examples/mulesoft-accelerator-for-manufacturing/[MuleSoft Accelerator for Manufacturing on Exchange^] diff --git a/manufacturing/1.4/modules/ROOT/pages/mfg-assets.adoc b/manufacturing/1.4/modules/ROOT/pages/mfg-assets.adoc index c3a379d0d..83c38503b 100644 --- a/manufacturing/1.4/modules/ROOT/pages/mfg-assets.adoc +++ b/manufacturing/1.4/modules/ROOT/pages/mfg-assets.adoc @@ -7,56 +7,56 @@ Accelerator assets include API specifications, implementation templates, custom [cols="40,30,30",width=100%] |=== | MFG Salesforce Customers System API -| https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/accelerator-salesforce-customers-sys-api/[API Specification^] -| https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/mfg-salesforce-customers-sys-api/[Implementation Template^] +| https://anypoint.mulesoft.com/exchange/org.mule.examples/accelerator-salesforce-customers-sys-api/[API Specification^] +| https://anypoint.mulesoft.com/exchange/org.mule.examples/mfg-salesforce-customers-sys-api/[Implementation Template^] | MFG Salesforce Manufacture System API -| https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/mfg-salesforce-manufacture-sys-api-spec/[API Specification^] -| https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/mfg-salesforce-manufacture-sys-api/[Implementation Template^] +| https://anypoint.mulesoft.com/exchange/org.mule.examples/mfg-salesforce-manufacture-sys-api-spec/[API Specification^] +| https://anypoint.mulesoft.com/exchange/org.mule.examples/mfg-salesforce-manufacture-sys-api/[Implementation Template^] | MFG Salesforce Orders System API -| https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/mfg-salesforce-orders-sys-api-spec/[API Specification^] -| https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/mfg-salesforce-orders-sys-api/[Implementation Template^] +| https://anypoint.mulesoft.com/exchange/org.mule.examples/mfg-salesforce-orders-sys-api-spec/[API Specification^] +| https://anypoint.mulesoft.com/exchange/org.mule.examples/mfg-salesforce-orders-sys-api/[Implementation Template^] | MFG Salesforce Products System API -| https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/mfg-salesforce-products-sys-api-spec/[API Specification^] -| https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/mfg-salesforce-products-sys-api/[Implementation Template^] +| https://anypoint.mulesoft.com/exchange/org.mule.examples/mfg-salesforce-products-sys-api-spec/[API Specification^] +| https://anypoint.mulesoft.com/exchange/org.mule.examples/mfg-salesforce-products-sys-api/[Implementation Template^] | MFG SAP S/4HANA Customers System API -| https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/accelerator-saphana-customers-sys-api/[API Specification^] -| https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/mfg-saphana-customers-sys-api/[Implementation Template^] +| https://anypoint.mulesoft.com/exchange/org.mule.examples/accelerator-saphana-customers-sys-api/[API Specification^] +| https://anypoint.mulesoft.com/exchange/org.mule.examples/mfg-saphana-customers-sys-api/[Implementation Template^] | MFG SAP S/4HANA Orders System API -| https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/accelerator-saphana-orders-sys-api/[API Specification^] -| https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/mfg-saphana-orders-sys-api/[Implementation Template^] +| https://anypoint.mulesoft.com/exchange/org.mule.examples/accelerator-saphana-orders-sys-api/[API Specification^] +| https://anypoint.mulesoft.com/exchange/org.mule.examples/mfg-saphana-orders-sys-api/[Implementation Template^] | Manufacturing MDM System API -| https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/accelerator-mdm-sys-api/[API Specification^] -| https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/mfg-mdm-sys-api/[Implementation Template^] +| https://anypoint.mulesoft.com/exchange/org.mule.examples/accelerator-mdm-sys-api/[API Specification^] +| https://anypoint.mulesoft.com/exchange/org.mule.examples/mfg-mdm-sys-api/[Implementation Template^] | PIM System API -| https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/accelerator-pim-sys-api/[API Specification^] -| https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/accel-pim-sys-api/[Implementation Template^] +| https://anypoint.mulesoft.com/exchange/org.mule.examples/accelerator-pim-sys-api/[API Specification^] +| https://anypoint.mulesoft.com/exchange/org.mule.examples/accel-pim-sys-api/[Implementation Template^] | MFG Salesforce Rebate System API -| https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/mfg-salesforce-rebate-sys-api-spec/[API Specification^] -| https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/mfg-salesforce-rebate-sys-api/[Implementation Template^] +| https://anypoint.mulesoft.com/exchange/org.mule.examples/mfg-salesforce-rebate-sys-api-spec/[API Specification^] +| https://anypoint.mulesoft.com/exchange/org.mule.examples/mfg-salesforce-rebate-sys-api/[Implementation Template^] | MFG SAP S/4HANA Credit Memo System API -| https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/mfg-saphana-creditmemo-sys-api-spec/[API Specification^] -| https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/mfg-saphana-creditmemo-sys-api/[Implementation Template^] +| https://anypoint.mulesoft.com/exchange/org.mule.examples/mfg-saphana-creditmemo-sys-api-spec/[API Specification^] +| https://anypoint.mulesoft.com/exchange/org.mule.examples/mfg-saphana-creditmemo-sys-api/[Implementation Template^] | MFG OSIPI Machine Data System API -| https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/mfg-osipi-machinedata-sys-api-spec/[API Specification^] -| https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/mfg-osipi-machinedata-sys-api/[Implementation Template^] +| https://anypoint.mulesoft.com/exchange/org.mule.examples/mfg-osipi-machinedata-sys-api-spec/[API Specification^] +| https://anypoint.mulesoft.com/exchange/org.mule.examples/mfg-osipi-machinedata-sys-api/[Implementation Template^] | MFG RedShift Machine Data System API -| https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/mfg-dw-machinedata-sys-api-spec/[API Specification^] -| https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/mfg-dw-machinedata-sys-api/[Implementation Template^] +| https://anypoint.mulesoft.com/exchange/org.mule.examples/mfg-dw-machinedata-sys-api-spec/[API Specification^] +| https://anypoint.mulesoft.com/exchange/org.mule.examples/mfg-dw-machinedata-sys-api/[Implementation Template^] | MFG Salesforce Cases System API -| https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/mfg-salesforce-cases-sys-api-spec/[API Specification^] -| https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/mfg-salesforce-cases-sys-api/[Implementation Template^] +| https://anypoint.mulesoft.com/exchange/org.mule.examples/mfg-salesforce-cases-sys-api-spec/[API Specification^] +| https://anypoint.mulesoft.com/exchange/org.mule.examples/mfg-salesforce-cases-sys-api/[Implementation Template^] |=== == Process APIs @@ -64,32 +64,32 @@ Accelerator assets include API specifications, implementation templates, custom [cols="40,30,30",width=100%] |=== | MFG Bulk Load Process API -| https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/mfg-bulk-load-prc-api-spec/[API Specification^] -| https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/mfg-bulk-load-prc-api/[Implementation Template^] +| https://anypoint.mulesoft.com/exchange/org.mule.examples/mfg-bulk-load-prc-api-spec/[API Specification^] +| https://anypoint.mulesoft.com/exchange/org.mule.examples/mfg-bulk-load-prc-api/[Implementation Template^] | MFG Customers Process API -| https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/accelerator-customers-prc-api/[API Specification^] -| https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/mfg-customers-prc-api/[Implementation Template^] +| https://anypoint.mulesoft.com/exchange/org.mule.examples/accelerator-customers-prc-api/[API Specification^] +| https://anypoint.mulesoft.com/exchange/org.mule.examples/mfg-customers-prc-api/[Implementation Template^] | MFG Orders Process API -| https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/accelerator-orders-prc-api/[API Specification^] -| https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/mfg-orders-prc-api/[Implementation Template^] +| https://anypoint.mulesoft.com/exchange/org.mule.examples/accelerator-orders-prc-api/[API Specification^] +| https://anypoint.mulesoft.com/exchange/org.mule.examples/mfg-orders-prc-api/[Implementation Template^] | MFG Products Process API -| https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/accelerator-products-prc-api/[API Specification^] -| https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/mfg-products-prc-api/[Implementation Template^] +| https://anypoint.mulesoft.com/exchange/org.mule.examples/accelerator-products-prc-api/[API Specification^] +| https://anypoint.mulesoft.com/exchange/org.mule.examples/mfg-products-prc-api/[Implementation Template^] | PIM Sync Process API -| https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/accelerator-pim-sync-prc-api/[API Specification^] -| https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/accel-pim-sync-prc-api/[Implementation Template^] +| https://anypoint.mulesoft.com/exchange/org.mule.examples/accelerator-pim-sync-prc-api/[API Specification^] +| https://anypoint.mulesoft.com/exchange/org.mule.examples/accel-pim-sync-prc-api/[Implementation Template^] | MFG Rebate Process API -| https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/mfg-rebate-prc-api-spec/[API Specification^] -| https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/mfg-rebate-prc-api/[Implementation Template^] +| https://anypoint.mulesoft.com/exchange/org.mule.examples/mfg-rebate-prc-api-spec/[API Specification^] +| https://anypoint.mulesoft.com/exchange/org.mule.examples/mfg-rebate-prc-api/[Implementation Template^] | MFG Machine Data Process API -| https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/mfg-machinedata-prc-api-spec/[API Specification^] -| https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/mfg-machinedata-prc-api/[Implementation Template^] +| https://anypoint.mulesoft.com/exchange/org.mule.examples/mfg-machinedata-prc-api-spec/[API Specification^] +| https://anypoint.mulesoft.com/exchange/org.mule.examples/mfg-machinedata-prc-api/[Implementation Template^] |=== == Experience APIs @@ -97,16 +97,16 @@ Accelerator assets include API specifications, implementation templates, custom [cols="40,30,30",width=100%] |=== | MFG Bulk Load Experience API -| https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/mfg-bulk-load-exp-api-spec/[API Specification^] -| https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/mfg-bulk-load-exp-api/[Implementation Template^] +| https://anypoint.mulesoft.com/exchange/org.mule.examples/mfg-bulk-load-exp-api-spec/[API Specification^] +| https://anypoint.mulesoft.com/exchange/org.mule.examples/mfg-bulk-load-exp-api/[Implementation Template^] | MFG Salesforce Experience API -| https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/accelerator-salesforce-exp-api[API Specification^] -| https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/mfg-salesforce-exp-api/[Implementation Template^] +| https://anypoint.mulesoft.com/exchange/org.mule.examples/accelerator-salesforce-exp-api[API Specification^] +| https://anypoint.mulesoft.com/exchange/org.mule.examples/mfg-salesforce-exp-api/[Implementation Template^] | MFG Tableau Machine Data Experience API -| https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/mfg-tableau-workorders-exp-api-spec/[API Specification^] -| https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/mfg-tableau-workorders-exp-api/[Implementation Template^] +| https://anypoint.mulesoft.com/exchange/org.mule.examples/mfg-tableau-workorders-exp-api-spec/[API Specification^] +| https://anypoint.mulesoft.com/exchange/org.mule.examples/mfg-tableau-workorders-exp-api/[Implementation Template^] |=== == Listeners & Handlers @@ -114,13 +114,13 @@ Accelerator assets include API specifications, implementation templates, custom [cols="70,30",width=100%] |=== | MFG SAP Event Listener -| https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/mfg-sap-event-listener/[Implementation Template^] +| https://anypoint.mulesoft.com/exchange/org.mule.examples/mfg-sap-event-listener/[Implementation Template^] | MFG SFTP CIM Handler -| https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/mfg-sftp-cim-handler/[Implementation Template^] +| https://anypoint.mulesoft.com/exchange/org.mule.examples/mfg-sftp-cim-handler/[Implementation Template^] | MFG Salesforce Topic Listener -| https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/mfg-salesforce-topic-listener/[Implementation Template^] +| https://anypoint.mulesoft.com/exchange/org.mule.examples/mfg-salesforce-topic-listener/[Implementation Template^] |=== == Custom Components @@ -128,17 +128,17 @@ Accelerator assets include API specifications, implementation templates, custom [cols="70,30",width=100%] |=== | MFG Rebate Library -| https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/mfg-rebate-library/[Source^] +| https://anypoint.mulesoft.com/exchange/org.mule.examples/mfg-rebate-library/[Source^] |=== == Shared APIs [cols="40,30,30",width=100%] |=== -| Accelerator Email System API | https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/accelerator-email-sys-api[API Specification^] | https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/accel-email-sys-api[Implementation Template^] -| Accelerator Slack System API | https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/accelerator-slack-sys-api[API Specification^] | https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/accel-slack-sys-api[Implementation Template^] -| Accelerator SMS System API | https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/accelerator-sms-sys-api[API Specification^] | https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/accel-sms-sys-api[Implementation Template^] -| Accelerator Notifications Process API | https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/accelerator-notifications-prc-api[API Specification^] | https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/accel-notifications-prc-api/[Implementation Template^] +| Accelerator Email System API | https://anypoint.mulesoft.com/exchange/org.mule.examples/accelerator-email-sys-api[API Specification^] | https://anypoint.mulesoft.com/exchange/org.mule.examples/accel-email-sys-api[Implementation Template^] +| Accelerator Slack System API | https://anypoint.mulesoft.com/exchange/org.mule.examples/accelerator-slack-sys-api[API Specification^] | https://anypoint.mulesoft.com/exchange/org.mule.examples/accel-slack-sys-api[Implementation Template^] +| Accelerator SMS System API | https://anypoint.mulesoft.com/exchange/org.mule.examples/accelerator-sms-sys-api[API Specification^] | https://anypoint.mulesoft.com/exchange/org.mule.examples/accel-sms-sys-api[Implementation Template^] +| Accelerator Notifications Process API | https://anypoint.mulesoft.com/exchange/org.mule.examples/accelerator-notifications-prc-api[API Specification^] | https://anypoint.mulesoft.com/exchange/org.mule.examples/accel-notifications-prc-api/[Implementation Template^] |=== == Shared Components @@ -146,13 +146,13 @@ Accelerator assets include API specifications, implementation templates, custom [cols="70,30",width=100%] |=== | Accelerator Common Core -| https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/accelerator-common-core-src/[Source^] +| https://anypoint.mulesoft.com/exchange/org.mule.examples/accelerator-common-core-src/[Source^] | POM Parent -| https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/accelerator-pom-parent-src/[Source^] +| https://anypoint.mulesoft.com/exchange/org.mule.examples/accelerator-pom-parent-src/[Source^] | ID Graph Lightning Web Component -| https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/accelerator-idgraph-lwc-src/[Source^] +| https://anypoint.mulesoft.com/exchange/org.mule.examples/accelerator-idgraph-lwc-src/[Source^] |=== == See Also diff --git a/manufacturing/1.4/modules/ROOT/pages/mfg-setup-guide.adoc b/manufacturing/1.4/modules/ROOT/pages/mfg-setup-guide.adoc index 4ac151447..6f8181428 100644 --- a/manufacturing/1.4/modules/ROOT/pages/mfg-setup-guide.adoc +++ b/manufacturing/1.4/modules/ROOT/pages/mfg-setup-guide.adoc @@ -22,7 +22,7 @@ The following fields must be created in the corresponding objects. == Anypoint MQ Configuration -The Anypoint-MQ-Queues-Exchanges Postman collection in the https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/mfg-common-resources-src/[MFG Common Resources project^] will pre-create all MQ destinations required by the accelerator components. +The Anypoint-MQ-Queues-Exchanges Postman collection in the https://anypoint.mulesoft.com/exchange/org.mule.examples/mfg-common-resources-src/[MFG Common Resources project^] will pre-create all MQ destinations required by the accelerator components. The collection requires the dev environment template to be imported into your Postman workspace and assigned proper values first. The following MQ destinations will be created upon successful execution. @@ -54,7 +54,7 @@ For communication arrangement SAP_COM_0287 to replicate the sales orders pricing . Enter the *Communication arrangement* app to edit or create the arrangement. . At outbound services sections, complete with the following: -image::https://www.mulesoft.com/ext/solutions/draft/images/mfg-saphana-setup-1.png[Configure SAP_COM_0287] +image::https://www.mulesoft.com/ext/solutions/images/mfg-saphana-setup-1.png[Configure SAP_COM_0287] == Custom Fields Create the following fields in the corresponding objects for the use case: diff --git a/manufacturing/1.4/modules/ROOT/pages/sftp-setup-guide.adoc b/manufacturing/1.4/modules/ROOT/pages/sftp-setup-guide.adoc index d2912adaf..06751f64a 100644 --- a/manufacturing/1.4/modules/ROOT/pages/sftp-setup-guide.adoc +++ b/manufacturing/1.4/modules/ROOT/pages/sftp-setup-guide.adoc @@ -6,7 +6,7 @@ This setup guide enables customers to upload existing customer, product, and ord _Load data to Manufacturing Cloud_ -image::https://www.mulesoft.com/ext/solutions/draft/images/mfg-data-load.png[mfg-data-load] +image::https://www.mulesoft.com/ext/solutions/images/mfg-data-load.png[mfg-data-load] === Functional Considerations diff --git a/manufacturing/1.4/modules/ROOT/pages/tableau-setup-guide.adoc b/manufacturing/1.4/modules/ROOT/pages/tableau-setup-guide.adoc index 4008acfe0..49a716c84 100644 --- a/manufacturing/1.4/modules/ROOT/pages/tableau-setup-guide.adoc +++ b/manufacturing/1.4/modules/ROOT/pages/tableau-setup-guide.adoc @@ -21,13 +21,13 @@ . Click on *File* tab, select *Import Workbook* and browse `mfg-tableau-workorders-exp-api/src/main/resources/workbook/FactoryEquipmentDashboard.twbx` file and click on the *Open* button. . Edit Amazon Redshift connection details. -image::https://www.mulesoft.com/ext/solutions/draft/images/mfg-edit-redshift.png[mfg-edit-redshift.png] +image::https://www.mulesoft.com/ext/solutions/images/mfg-edit-redshift.png[mfg-edit-redshift.png] == Steps to create work order . In the *Submit a Work Order* dialogue box, the user can manage the Priority, Machine Id and provide a Reason to submit a work order. + + - image:https://www.mulesoft.com/ext/solutions/draft/images/mfg-submit-work-order.png[mfg-submit-work-order.png] + + image:https://www.mulesoft.com/ext/solutions/images/mfg-submit-work-order.png[mfg-submit-work-order.png] + . Click on *Create Work Order* which will create a case in Service Cloud. == Steps to Publish Workbook into Tableau Online. @@ -35,7 +35,7 @@ image::https://www.mulesoft.com/ext/solutions/draft/images/mfg-edit-redshift.png . Click on *Server* and select *Publish Workbook*. . Click on *Connect*, enter email address and password to sign in. + + -image:https://www.mulesoft.com/ext/solutions/draft/images/mfg-tableau-online-publish.png[mfg-tableau-online-publish.png] + +image:https://www.mulesoft.com/ext/solutions/images/mfg-tableau-online-publish.png[mfg-tableau-online-publish.png] + + . In the *Publish Workbook to Tableau Online* window, complete the *Name* and *Description* fields. . Click on the *Publish* button. @@ -45,14 +45,14 @@ image:https://www.mulesoft.com/ext/solutions/draft/images/mfg-tableau-online-pub . Login into https://sso.online.tableau.com/public/idp/SSO[Tableau Online] . Click on *Watch* and select *Alerts* + + -image:https://www.mulesoft.com/ext/solutions/draft/images/mfg-tableau-online-alert.png[mfg-tableau-online-alert.png] + +image:https://www.mulesoft.com/ext/solutions/images/mfg-tableau-online-alert.png[mfg-tableau-online-alert.png] + + . Click on the *Create* button on the right side which opens the 'Create Alert' dialogue box. . Users can select the condition and threshold and users can provide the subject details and select the alert condition (for example, daily). . Users can provide the recipient details in the *Recipients* field and click on *Create Alert*. . An alert will be sent to the recipient. -image::https://www.mulesoft.com/ext/solutions/draft/images/mfg-email-alert.png[mfg-email-alert.png] +image::https://www.mulesoft.com/ext/solutions/images/mfg-email-alert.png[mfg-email-alert.png] == See Also diff --git a/modules/ROOT/pages/accel/shared-assets.adoc b/modules/ROOT/pages/accel/shared-assets.adoc index e1ed09a47..40963e8e7 100644 --- a/modules/ROOT/pages/accel/shared-assets.adoc +++ b/modules/ROOT/pages/accel/shared-assets.adoc @@ -32,7 +32,7 @@ The following APIs are used by multiple accelerators to access and manage data i ==== US Exchange:: + -:anypoint-url: anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873 +:anypoint-url: anypoint.mulesoft.com/exchange/org.mule.examples include::_partials/system-apis-fragment.adoc[] EU Exchange:: @@ -54,7 +54,7 @@ The following APIs represent the reusable business processes that are leveraged ==== US Exchange:: + -:anypoint-url: anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873 +:anypoint-url: anypoint.mulesoft.com/exchange/org.mule.examples include::_partials/process-apis-fragment.adoc[] EU Exchange:: @@ -76,7 +76,7 @@ The following APIs provide tailor-made endpoints for specific applications to co ==== US Exchange:: + -:anypoint-url: anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873 +:anypoint-url: anypoint.mulesoft.com/exchange/org.mule.examples include::_partials/experience-apis-fragment.adoc[] EU Exchange:: @@ -98,7 +98,7 @@ The following applications provide key integrations but do not expose any APIs a ==== US Exchange:: + -:anypoint-url: anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873 +:anypoint-url: anypoint.mulesoft.com/exchange/org.mule.examples include::_partials/integrations-fragment.adoc[] EU Exchange:: @@ -120,7 +120,7 @@ The following non-application components are also used by multiple accelerators. ==== US Exchange:: + -:anypoint-url: anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873 +:anypoint-url: anypoint.mulesoft.com/exchange/org.mule.examples include::_partials/shared-components-fragment.adoc[] EU Exchange:: diff --git a/retail/2.7/modules/ROOT/pages/index.adoc b/retail/2.7/modules/ROOT/pages/index.adoc index 507af9f9b..ecb25a4a8 100644 --- a/retail/2.7/modules/ROOT/pages/index.adoc +++ b/retail/2.7/modules/ROOT/pages/index.adoc @@ -7,19 +7,19 @@ MuleSoft Accelerator for Retail empowers retail IT teams to unlock data from sys The following use cases are supported by the MuleSoft Accelerator for Manufacturing: -* https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/mulesoft-accelerator-for-retail/minor/{retail-version}/pages/Use%20case%201%20-%20Customer%20profile%20sync/[Customer profile sync^] - The Customer profile sync use case enables retail developers to create a customer 360 view by unlocking customer data from disparate systems. +* https://anypoint.mulesoft.com/exchange/org.mule.examples/mulesoft-accelerator-for-retail/minor/{retail-version}/pages/Use%20case%201%20-%20Customer%20profile%20sync/[Customer profile sync^] - The Customer profile sync use case enables retail developers to create a customer 360 view by unlocking customer data from disparate systems. -* https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/mulesoft-accelerator-for-retail/minor/{retail-version}/pages/Use%20case%202%20-%20Sales%20order%20sync/[Sales order sync^] - The Sales order sync use case enables retail developers to create and update sales orders across relevant applications. +* https://anypoint.mulesoft.com/exchange/org.mule.examples/mulesoft-accelerator-for-retail/minor/{retail-version}/pages/Use%20case%202%20-%20Sales%20order%20sync/[Sales order sync^] - The Sales order sync use case enables retail developers to create and update sales orders across relevant applications. -* https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/mulesoft-accelerator-for-retail/minor/{retail-version}/pages/Use%20case%203%20-%20Product%20sync/[Product sync^] - The Product sync use case enables retail developers to update product details in Salsify across relevant applications. +* https://anypoint.mulesoft.com/exchange/org.mule.examples/mulesoft-accelerator-for-retail/minor/{retail-version}/pages/Use%20case%203%20-%20Product%20sync/[Product sync^] - The Product sync use case enables retail developers to update product details in Salsify across relevant applications. -* https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/mulesoft-accelerator-for-retail/minor/{retail-version}/pages/Use%20case%204%20-%20Real-time%20inventory%20management/[Real-time inventory management^] - The Real-time inventory management use case enables customers to make an informed decision of their online purchase based on real-time inventory of a product in nearby stores. +* https://anypoint.mulesoft.com/exchange/org.mule.examples/mulesoft-accelerator-for-retail/minor/{retail-version}/pages/Use%20case%204%20-%20Real-time%20inventory%20management/[Real-time inventory management^] - The Real-time inventory management use case enables customers to make an informed decision of their online purchase based on real-time inventory of a product in nearby stores. -* https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/mulesoft-accelerator-for-retail/minor/{retail-version}/pages/Use%20case%205%20-%20Deliver%20relevancy%20with%20CDP/[Deliver relevancy with CDP^] - The Deliver relevancy with CDP use case enables retail developers to combine customer profile data in a standardized format. +* https://anypoint.mulesoft.com/exchange/org.mule.examples/mulesoft-accelerator-for-retail/minor/{retail-version}/pages/Use%20case%205%20-%20Deliver%20relevancy%20with%20CDP/[Deliver relevancy with CDP^] - The Deliver relevancy with CDP use case enables retail developers to combine customer profile data in a standardized format. == See Also * xref:accelerators-home::getting-started.adoc[Getting Started Guide] * xref:prerequisites.adoc[Prerequisites] * xref:release-notes::accelerators/retail/retail-release-notes.adoc[Release Notes] -* https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/mulesoft-accelerator-for-retail/[MuleSoft Accelerator for Retail on Exchange^] +* https://anypoint.mulesoft.com/exchange/org.mule.examples/mulesoft-accelerator-for-retail/[MuleSoft Accelerator for Retail on Exchange^] diff --git a/retail/2.7/modules/ROOT/pages/rcg-assets.adoc b/retail/2.7/modules/ROOT/pages/rcg-assets.adoc index b24864e70..df2f098bc 100644 --- a/retail/2.7/modules/ROOT/pages/rcg-assets.adoc +++ b/retail/2.7/modules/ROOT/pages/rcg-assets.adoc @@ -7,76 +7,76 @@ Accelerator assets include API specifications, implementation templates, custom [cols="40,30,30",width=100%] |=== | B2B Commerce System API -| https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/rcg-b2b-commerce-sys-api-spec/[API Specification^] -| https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/rcg-b2b-commerce-sys-api/[Implementation Template^] +| https://anypoint.mulesoft.com/exchange/org.mule.examples/rcg-b2b-commerce-sys-api-spec/[API Specification^] +| https://anypoint.mulesoft.com/exchange/org.mule.examples/rcg-b2b-commerce-sys-api/[Implementation Template^] | B2C Commerce System API -| https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/rcg-b2c-commerce-sys-api-spec/[API Specification^] -| https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/rcg-b2c-commerce-sys-api[Implementation Template^] +| https://anypoint.mulesoft.com/exchange/org.mule.examples/rcg-b2c-commerce-sys-api-spec/[API Specification^] +| https://anypoint.mulesoft.com/exchange/org.mule.examples/rcg-b2c-commerce-sys-api[Implementation Template^] | B2C Customers System API -| https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/rcg-b2c-customers-sys-api-spec/[API Specification^] -| https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/rcg-b2c-customers-sys-api/[Implementation Template^] +| https://anypoint.mulesoft.com/exchange/org.mule.examples/rcg-b2c-customers-sys-api-spec/[API Specification^] +| https://anypoint.mulesoft.com/exchange/org.mule.examples/rcg-b2c-customers-sys-api/[Implementation Template^] | MDM System API -| https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/rcg-mdm-sys-api-spec/[API Specification^] -| https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/rcg-mdm-sys-api/[Implementation Template^] +| https://anypoint.mulesoft.com/exchange/org.mule.examples/rcg-mdm-sys-api-spec/[API Specification^] +| https://anypoint.mulesoft.com/exchange/org.mule.examples/rcg-mdm-sys-api/[Implementation Template^] | RCG Salsify Products System API -| https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/rcg-salsify-products-sys-api-spec/[API Specification^] -| https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/rcg-salsify-products-sys-api/[Implementation Template^] +| https://anypoint.mulesoft.com/exchange/org.mule.examples/rcg-salsify-products-sys-api-spec/[API Specification^] +| https://anypoint.mulesoft.com/exchange/org.mule.examples/rcg-salsify-products-sys-api/[Implementation Template^] | RCG Azure Cosmos DB System API -| https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/rcg-azure-sys-api-spec/[API Specification^] -| https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/rcg-azure-sys-api/[Implementation Template^] +| https://anypoint.mulesoft.com/exchange/org.mule.examples/rcg-azure-sys-api-spec/[API Specification^] +| https://anypoint.mulesoft.com/exchange/org.mule.examples/rcg-azure-sys-api/[Implementation Template^] | RCG B2C Commerce System API -| https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/rcg-b2c-commerce-sys-api-spec/[API Specification^] -| https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/rcg-b2c-commerce-sys-api/[Implementation Template^] +| https://anypoint.mulesoft.com/exchange/org.mule.examples/rcg-b2c-commerce-sys-api-spec/[API Specification^] +| https://anypoint.mulesoft.com/exchange/org.mule.examples/rcg-b2c-commerce-sys-api/[Implementation Template^] | RCG Marketo System API -| https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/rcg-marketo-system-api-spec/[API Specification^] -| https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/rcg-marketo-system-api/[Implementation Template^] +| https://anypoint.mulesoft.com/exchange/org.mule.examples/rcg-marketo-system-api-spec/[API Specification^] +| https://anypoint.mulesoft.com/exchange/org.mule.examples/rcg-marketo-system-api/[Implementation Template^] | RCG Salesforce CDP System API -| https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/rcg-salesforce-cdp-sys-api-spec/[API Specification^] -| https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/rcg-salesforce-cdp-sys-api/[Implementation Template^] +| https://anypoint.mulesoft.com/exchange/org.mule.examples/rcg-salesforce-cdp-sys-api-spec/[API Specification^] +| https://anypoint.mulesoft.com/exchange/org.mule.examples/rcg-salesforce-cdp-sys-api/[Implementation Template^] | RCG Snowflake System API -| https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/rcg-snowflake-sys-api-spec/[API Specification^] -| https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/rcg-snowflake-sys-api/[Implementation Template^] +| https://anypoint.mulesoft.com/exchange/org.mule.examples/rcg-snowflake-sys-api-spec/[API Specification^] +| https://anypoint.mulesoft.com/exchange/org.mule.examples/rcg-snowflake-sys-api/[Implementation Template^] | Salesforce Customers System API -| https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/rcg-salesforce-customers-sys-api-spec/[API Specification^] -| https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/rcg-salesforce-customers-sys-api/[Implementation Template^] +| https://anypoint.mulesoft.com/exchange/org.mule.examples/rcg-salesforce-customers-sys-api-spec/[API Specification^] +| https://anypoint.mulesoft.com/exchange/org.mule.examples/rcg-salesforce-customers-sys-api/[Implementation Template^] | Salesforce Marketing System API -| https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/rcg-salesforce-marketing-sys-api-spec/[API Specification^] -| https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/rcg-salesforce-marketing-sys-api/[Implementation Template^] +| https://anypoint.mulesoft.com/exchange/org.mule.examples/rcg-salesforce-marketing-sys-api-spec/[API Specification^] +| https://anypoint.mulesoft.com/exchange/org.mule.examples/rcg-salesforce-marketing-sys-api/[Implementation Template^] | Salesforce Orders System API -| https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/rcg-salesforce-orders-sys-api-spec/[API Specification^] -| https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/rcg-salesforce-orders-sys-api/[Implementation Template^] +| https://anypoint.mulesoft.com/exchange/org.mule.examples/rcg-salesforce-orders-sys-api-spec/[API Specification^] +| https://anypoint.mulesoft.com/exchange/org.mule.examples/rcg-salesforce-orders-sys-api/[Implementation Template^] | SAP ECC Customers System API -| https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/rcg-sapecc-customers-sys-api-spec/[API Specification^] -| https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/rcg-sapecc-customers-sys-api/[Implementation Template^] +| https://anypoint.mulesoft.com/exchange/org.mule.examples/rcg-sapecc-customers-sys-api-spec/[API Specification^] +| https://anypoint.mulesoft.com/exchange/org.mule.examples/rcg-sapecc-customers-sys-api/[Implementation Template^] | SAP S/4HANA Customers System API -| https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/rcg-saphana-customers-sys-api-spec/[API Specification^] -| https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/rcg-saphana-customers-sys-api/[Implementation Template^] +| https://anypoint.mulesoft.com/exchange/org.mule.examples/rcg-saphana-customers-sys-api-spec/[API Specification^] +| https://anypoint.mulesoft.com/exchange/org.mule.examples/rcg-saphana-customers-sys-api/[Implementation Template^] | SAP S/4HANA Orders System API -| https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/accelerator-saphana-orders-sys-api/[API Specification^] -| https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/rcg-saphana-orders-sys-api/[Implementation Template^] +| https://anypoint.mulesoft.com/exchange/org.mule.examples/accelerator-saphana-orders-sys-api/[API Specification^] +| https://anypoint.mulesoft.com/exchange/org.mule.examples/rcg-saphana-orders-sys-api/[Implementation Template^] | SAP S/4HANA Product Availability System API -| https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/accelerator-saphana-productavailability-sys-api/[API Specification^] -| https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/accel-saphana-productavailability-sys-api/[Implementation Template^] +| https://anypoint.mulesoft.com/exchange/org.mule.examples/accelerator-saphana-productavailability-sys-api/[API Specification^] +| https://anypoint.mulesoft.com/exchange/org.mule.examples/accel-saphana-productavailability-sys-api/[Implementation Template^] | SAP S/4HANA Products System API -| https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/rcg-saphana-products-sys-api-spec/[API Specification^] -| https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/rcg-saphana-products-sys-api/[Implementation Template^] +| https://anypoint.mulesoft.com/exchange/org.mule.examples/rcg-saphana-products-sys-api-spec/[API Specification^] +| https://anypoint.mulesoft.com/exchange/org.mule.examples/rcg-saphana-products-sys-api/[Implementation Template^] |=== == Process APIs @@ -84,40 +84,40 @@ Accelerator assets include API specifications, implementation templates, custom [cols="40,30,30",width=100%] |=== | Customers Process API -| https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/rcg-customers-prc-api-spec/[API Specification^] -| https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/rcg-customers-prc-api/[Implementation Template^] +| https://anypoint.mulesoft.com/exchange/org.mule.examples/rcg-customers-prc-api-spec/[API Specification^] +| https://anypoint.mulesoft.com/exchange/org.mule.examples/rcg-customers-prc-api/[Implementation Template^] | ERP Customers Process API -| https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/rcg-erp-customers-prc-api-spec/[API Specification^] -| https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/rcg-erp-customers-prc-api/[Implementation Template^] +| https://anypoint.mulesoft.com/exchange/org.mule.examples/rcg-erp-customers-prc-api-spec/[API Specification^] +| https://anypoint.mulesoft.com/exchange/org.mule.examples/rcg-erp-customers-prc-api/[Implementation Template^] | ERP Orders Process API -| https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/rcg-erp-orders-prc-api-spec/[API Specification^] -| https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/rcg-erp-orders-prc-api/[Implementation Template^] +| https://anypoint.mulesoft.com/exchange/org.mule.examples/rcg-erp-orders-prc-api-spec/[API Specification^] +| https://anypoint.mulesoft.com/exchange/org.mule.examples/rcg-erp-orders-prc-api/[Implementation Template^] | Inventory Process API -| https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/rcg-inventory-prc-api-spec/[API Specification^] -| https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/rcg-inventory-prc-api/[Implementation Template^] +| https://anypoint.mulesoft.com/exchange/org.mule.examples/rcg-inventory-prc-api-spec/[API Specification^] +| https://anypoint.mulesoft.com/exchange/org.mule.examples/rcg-inventory-prc-api/[Implementation Template^] | Orders Process API -| https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/rcg-orders-prc-api-spec/[API Specification^] -| https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/rcg-orders-prc-api/[Implementation Template^] +| https://anypoint.mulesoft.com/exchange/org.mule.examples/rcg-orders-prc-api-spec/[API Specification^] +| https://anypoint.mulesoft.com/exchange/org.mule.examples/rcg-orders-prc-api/[Implementation Template^] | Products Process API -| https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/rcg-products-prc-api-spec/[API Specification^] -| https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/rcg-products-prc-api/[Implementation Template^] +| https://anypoint.mulesoft.com/exchange/org.mule.examples/rcg-products-prc-api-spec/[API Specification^] +| https://anypoint.mulesoft.com/exchange/org.mule.examples/rcg-products-prc-api/[Implementation Template^] | RCG Customer Data Platform Process API -| https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/rcg-cdp-prc-api-spec/[API Specification^] -| https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/rcg-cdp-prc-api/[Implementation Template^] +| https://anypoint.mulesoft.com/exchange/org.mule.examples/rcg-cdp-prc-api-spec/[API Specification^] +| https://anypoint.mulesoft.com/exchange/org.mule.examples/rcg-cdp-prc-api/[Implementation Template^] | RCG DataLake Process API -| https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/rcg-datalake-prc-api-spec/[API Specification^] -| https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/rcg-datalake-prc-api/[Implementation Template^] +| https://anypoint.mulesoft.com/exchange/org.mule.examples/rcg-datalake-prc-api-spec/[API Specification^] +| https://anypoint.mulesoft.com/exchange/org.mule.examples/rcg-datalake-prc-api/[Implementation Template^] | RCG Marketing Process API -| https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/rcg-marketing-prc-api-spec/[API Specification^] -| https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/rcg-marketing-prc-api/[Implementation Template^] +| https://anypoint.mulesoft.com/exchange/org.mule.examples/rcg-marketing-prc-api-spec/[API Specification^] +| https://anypoint.mulesoft.com/exchange/org.mule.examples/rcg-marketing-prc-api/[Implementation Template^] |=== == Experience APIs @@ -125,12 +125,12 @@ Accelerator assets include API specifications, implementation templates, custom [cols="40,30,30",width=100%] |=== | B2C Commerce Experience API -| https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/rcg-b2c-commerce-exp-api-spec/[API Specification^] -| https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/rcg-b2c-commerce-exp-api[Implementation Template^] +| https://anypoint.mulesoft.com/exchange/org.mule.examples/rcg-b2c-commerce-exp-api-spec/[API Specification^] +| https://anypoint.mulesoft.com/exchange/org.mule.examples/rcg-b2c-commerce-exp-api[Implementation Template^] | Salesforce Experience API -| https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/rcg-salesforce-exp-api-spec/[API Specification^] -| https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/rcg-salesforce-exp-api/[Implementation Template^] +| https://anypoint.mulesoft.com/exchange/org.mule.examples/rcg-salesforce-exp-api-spec/[API Specification^] +| https://anypoint.mulesoft.com/exchange/org.mule.examples/rcg-salesforce-exp-api/[Implementation Template^] |=== == Listeners & Handlers @@ -138,16 +138,16 @@ Accelerator assets include API specifications, implementation templates, custom [cols="70,30",width=100%] |=== | Salesforce Marketing Listener -| https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/rcg-salesforce-marketing-listener/[Implementation Template^] +| https://anypoint.mulesoft.com/exchange/org.mule.examples/rcg-salesforce-marketing-listener/[Implementation Template^] | Salesforce Topic Listener -| https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/rcg-salesforce-topic-listener/[Implementation Template^] +| https://anypoint.mulesoft.com/exchange/org.mule.examples/rcg-salesforce-topic-listener/[Implementation Template^] | SAP Event Listener -| https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/rcg-sap-event-listener/[Implementation Template^] +| https://anypoint.mulesoft.com/exchange/org.mule.examples/rcg-sap-event-listener/[Implementation Template^] | Salsify Channel Listener -| https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/rcg-salsify-channel-listener/[Implementation Template^] +| https://anypoint.mulesoft.com/exchange/org.mule.examples/rcg-salsify-channel-listener/[Implementation Template^] |=== === Custom Components @@ -155,29 +155,29 @@ Accelerator assets include API specifications, implementation templates, custom [cols="70,30",width=100%] |=== | B2C Commerce Instore Pickup Cartridge -| https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/rcg-b2c-commerce-instore-pickup-cartridge-src/[Source^] +| https://anypoint.mulesoft.com/exchange/org.mule.examples/rcg-b2c-commerce-instore-pickup-cartridge-src/[Source^] | B2C Commerce Sync Cartridge -| https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/rcg-b2c-commerce-sync-cartridge-src/[Source^] +| https://anypoint.mulesoft.com/exchange/org.mule.examples/rcg-b2c-commerce-sync-cartridge-src/[Source^] | ID Graph Lightning Web Component -| https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/accelerator-idgraph-lwc-src[Source^] +| https://anypoint.mulesoft.com/exchange/org.mule.examples/accelerator-idgraph-lwc-src[Source^] | POM Parent -| https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/accelerator-pom-parent-src/[Source^] +| https://anypoint.mulesoft.com/exchange/org.mule.examples/accelerator-pom-parent-src/[Source^] | Product Availability Lightning Web Component -| https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/accelerator-productavailability-lwc-src/[Source^] +| https://anypoint.mulesoft.com/exchange/org.mule.examples/accelerator-productavailability-lwc-src/[Source^] |=== == Shared APIs [cols="40,30,30",width=100%] |=== -| Accelerator Email System API | https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/accelerator-email-sys-api[API Specification^] | https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/accel-email-sys-api[Implementation Template^] -| Accelerator Slack System API | https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/accelerator-slack-sys-api[API Specification^] | https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/accel-slack-sys-api[Implementation Template^] -| Accelerator SMS System API | https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/accelerator-sms-sys-api[API Specification^] | https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/accel-sms-sys-api[Implementation Template^] -| Accelerator Notifications Process API | https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/accelerator-notifications-prc-api[API Specification^] | https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/accel-notifications-prc-api/[Implementation Template^] +| Accelerator Email System API | https://anypoint.mulesoft.com/exchange/org.mule.examples/accelerator-email-sys-api[API Specification^] | https://anypoint.mulesoft.com/exchange/org.mule.examples/accel-email-sys-api[Implementation Template^] +| Accelerator Slack System API | https://anypoint.mulesoft.com/exchange/org.mule.examples/accelerator-slack-sys-api[API Specification^] | https://anypoint.mulesoft.com/exchange/org.mule.examples/accel-slack-sys-api[Implementation Template^] +| Accelerator SMS System API | https://anypoint.mulesoft.com/exchange/org.mule.examples/accelerator-sms-sys-api[API Specification^] | https://anypoint.mulesoft.com/exchange/org.mule.examples/accel-sms-sys-api[Implementation Template^] +| Accelerator Notifications Process API | https://anypoint.mulesoft.com/exchange/org.mule.examples/accelerator-notifications-prc-api[API Specification^] | https://anypoint.mulesoft.com/exchange/org.mule.examples/accel-notifications-prc-api/[Implementation Template^] |=== == Shared Components @@ -185,13 +185,13 @@ Accelerator assets include API specifications, implementation templates, custom [cols="70,30",width=100%] |=== | Accelerator Common Core -| https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/accelerator-common-core-src/[Source^] +| https://anypoint.mulesoft.com/exchange/org.mule.examples/accelerator-common-core-src/[Source^] | POM Parent -| https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/accelerator-pom-parent-src/[Source^] +| https://anypoint.mulesoft.com/exchange/org.mule.examples/accelerator-pom-parent-src/[Source^] | ID Graph Lightning Web Component -| https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/accelerator-idgraph-lwc-src/[Source^] +| https://anypoint.mulesoft.com/exchange/org.mule.examples/accelerator-idgraph-lwc-src/[Source^] |=== == See Also diff --git a/retail/2.7/modules/ROOT/pages/sap-custom-bapi-setup-guide.adoc b/retail/2.7/modules/ROOT/pages/sap-custom-bapi-setup-guide.adoc index 1a7f2a872..b137b7833 100644 --- a/retail/2.7/modules/ROOT/pages/sap-custom-bapi-setup-guide.adoc +++ b/retail/2.7/modules/ROOT/pages/sap-custom-bapi-setup-guide.adoc @@ -5,7 +5,7 @@ The following provides guidance on how to use the custom BAPI code (for example, `ZBAPI_CUSTOMER_V3`) for your SAP instance. [NOTE] -You must complete the following instructions before deploying the https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/mulesoft-accelerator-for-retail/minor/{retail-version}/pages/Use%20case%201%20-%20Customer%20profile%20sync/[Customer profile sync from SAP^] use case. +You must complete the following instructions before deploying the https://anypoint.mulesoft.com/exchange/org.mule.examples/mulesoft-accelerator-for-retail/minor/{retail-version}/pages/Use%20case%201%20-%20Customer%20profile%20sync/[Customer profile sync from SAP^] use case. == BAPI custom objects @@ -61,7 +61,7 @@ You must create the following ABAP objects in order to use this custom BAPI, whi | Object | How to create | `Z_MASTER_ID` -| image:https://www.mulesoft.com/ext/solutions/draft/images/sfc-retail-com-bapi_01.png[sfc-retail-com-bapi_01.png,599] +| image:https://www.mulesoft.com/ext/solutions/images/sfc-retail-com-bapi_01.png[sfc-retail-com-bapi_01.png,599] |=== [[creating-structures]] @@ -72,19 +72,19 @@ You must create the following ABAP objects in order to use this custom BAPI, whi | Object | How to create | `ZSTR_PERSON` -| image:https://www.mulesoft.com/ext/solutions/draft/images/retail-2.2-bapi-01.1.png[retail-2.2-bapi-01.1.png,599] +| image:https://www.mulesoft.com/ext/solutions/images/retail-2.2-bapi-01.1.png[retail-2.2-bapi-01.1.png,599] | `ZSTR_ORGANIZATION` -| image:https://www.mulesoft.com/ext/solutions/draft/images/retail-2.2-bapi-01.2.png[retail-2.2-bapi-01.2.png,599] +| image:https://www.mulesoft.com/ext/solutions/images/retail-2.2-bapi-01.2.png[retail-2.2-bapi-01.2.png,599] | `ZSTR_GROUP` -| image:https://www.mulesoft.com/ext/solutions/draft/images/retail-2.2-bapi-01.3.png[retail-2.2-bapi-01.3.png,599] +| image:https://www.mulesoft.com/ext/solutions/images/retail-2.2-bapi-01.3.png[retail-2.2-bapi-01.3.png,599] | `ZES_CUSTOMER` -| image:https://www.mulesoft.com/ext/solutions/draft/images/retail-2.2-bapi-01.4.png[retail-2.2-bapi-01.4.png,599] +| image:https://www.mulesoft.com/ext/solutions/images/retail-2.2-bapi-01.4.png[retail-2.2-bapi-01.4.png,599] | `ZES_CONTROLDATA` -| image:https://www.mulesoft.com/ext/solutions/draft/images/retail-2.2-bapi-01.5.png[retail-2.2-bapi-01.5.png,599] +| image:https://www.mulesoft.com/ext/solutions/images/retail-2.2-bapi-01.5.png[retail-2.2-bapi-01.5.png,599] |=== [[creating-table-types]] @@ -95,7 +95,7 @@ You must create the following ABAP objects in order to use this custom BAPI, whi | Object | How to create | `ZTY_CUSTOMER` -| image:https://www.mulesoft.com/ext/solutions/draft/images/sfc-retail-com-bapi_05.png[sfc-retail-com-bapi_05.png,599] +| image:https://www.mulesoft.com/ext/solutions/images/sfc-retail-com-bapi_05.png[sfc-retail-com-bapi_05.png,599] |=== [[creating-transparent-tables]] @@ -106,7 +106,7 @@ You must create the following ABAP objects in order to use this custom BAPI, whi | Object | How to create | `ZTT_CUSTOMER` -| image:https://www.mulesoft.com/ext/solutions/draft/images/retail-2.2-bapi-05.1.png[retail-2.2-bapi-05.1.png,599] +| image:https://www.mulesoft.com/ext/solutions/images/retail-2.2-bapi-05.1.png[retail-2.2-bapi-05.1.png,599] |=== {blank} @@ -123,91 +123,91 @@ You must create the following ABAP objects in order to use this custom BAPI, whi . Create the function group "ZFG_CUSTOMER_V3". . Create the function module "ZBAPI_CUSTOMER_V3", using "Remote-enable module" as processing type: + -image:https://www.mulesoft.com/ext/solutions/draft/images/sfc-retail-com-bapi_06.png[sfc-retail-com-bapi_06.png,599] +image:https://www.mulesoft.com/ext/solutions/images/sfc-retail-com-bapi_06.png[sfc-retail-com-bapi_06.png,599] . Complete the import parameters with the following: + -image:https://www.mulesoft.com/ext/solutions/draft/images/sfc-retail-com-bapi_07.png[sfc-retail-com-bapi_07.png,599] +image:https://www.mulesoft.com/ext/solutions/images/sfc-retail-com-bapi_07.png[sfc-retail-com-bapi_07.png,599] . Complete the export parameters with the following: + -image:https://www.mulesoft.com/ext/solutions/draft/images/sfc-retail-com-bapi_08.png[sfc-retail-com-bapi_08.png,599] +image:https://www.mulesoft.com/ext/solutions/images/sfc-retail-com-bapi_08.png[sfc-retail-com-bapi_08.png,599] . Copy and paste the code from "ZBAPI_CUSTOMER_V3.txt". . Create the function module "ZBAPI_CUSTOMER_CREATE_V3": + -image:https://www.mulesoft.com/ext/solutions/draft/images/sfc-retail-com-bapi_09.png[sfc-retail-com-bapi_09.png,399] +image:https://www.mulesoft.com/ext/solutions/images/sfc-retail-com-bapi_09.png[sfc-retail-com-bapi_09.png,399] . Complete the import parameters with the following: + -image:https://www.mulesoft.com/ext/solutions/draft/images/retail-2.2-bapi-09.1.png[retail-2.2-bapi-09.1.png,599] +image:https://www.mulesoft.com/ext/solutions/images/retail-2.2-bapi-09.1.png[retail-2.2-bapi-09.1.png,599] . Complete the export parameters with the following: + -image:https://www.mulesoft.com/ext/solutions/draft/images/sfc-retail-com-bapi_11.png[sfc-retail-com-bapi_11.png,599] +image:https://www.mulesoft.com/ext/solutions/images/sfc-retail-com-bapi_11.png[sfc-retail-com-bapi_11.png,599] . Copy and paste the code from "ZBAPI_CUSTOMER_CREATE_V3.txt". . Create the function module "ZBAPI_CUSTOMER_CUSTOM_FLDS_V3": + -image:https://www.mulesoft.com/ext/solutions/draft/images/sfc-retail-com-bapi_15.png[sfc-retail-com-bapi_15.png,599] +image:https://www.mulesoft.com/ext/solutions/images/sfc-retail-com-bapi_15.png[sfc-retail-com-bapi_15.png,599] . Complete the import parameters with the following: + -image:https://www.mulesoft.com/ext/solutions/draft/images/retail-2.2-bapi-15.1.png[retail-2.2-bapi-15.1.png,399] +image:https://www.mulesoft.com/ext/solutions/images/retail-2.2-bapi-15.1.png[retail-2.2-bapi-15.1.png,399] . Copy and paste the code from "ZBAPI_CUSTOMER_CUSTOM_FIELDS_V3.txt". . Create the function module "ZBAPI_CUSTOMER_UPDATE_V3": + -image:https://www.mulesoft.com/ext/solutions/draft/images/sfc-retail-com-bapi_12.png[sfc-retail-com-bapi_12.png,599] +image:https://www.mulesoft.com/ext/solutions/images/sfc-retail-com-bapi_12.png[sfc-retail-com-bapi_12.png,599] . Complete the import parameters with the following: + -image:https://www.mulesoft.com/ext/solutions/draft/images/retail-2.2-bapi-12.1.png[retail-2.2-bapi-12.1.png,599] +image:https://www.mulesoft.com/ext/solutions/images/retail-2.2-bapi-12.1.png[retail-2.2-bapi-12.1.png,599] . Complete the export parameters with the following: + -image:https://www.mulesoft.com/ext/solutions/draft/images/retail-2.2-bapi-12.2.png[retail-2.2-bapi-12.2.png,599] +image:https://www.mulesoft.com/ext/solutions/images/retail-2.2-bapi-12.2.png[retail-2.2-bapi-12.2.png,599] . Copy and paste the code from "ZBAPI_CUSTOMER_UPDATE_V3.txt". . Create the function module "ZBAPI_QUERY_V3", using "Remote-enable module" as processing type: + -image:https://www.mulesoft.com/ext/solutions/draft/images/sfc-retail-com-bapi_36.png[sfc-retail-com-bapi_36.png,599] +image:https://www.mulesoft.com/ext/solutions/images/sfc-retail-com-bapi_36.png[sfc-retail-com-bapi_36.png,599] . Complete the import parameters with the following: + -image:https://www.mulesoft.com/ext/solutions/draft/images/retail-2.2-bapi-36.1.png[retail-2.2-bapi-36.1.png,399] +image:https://www.mulesoft.com/ext/solutions/images/retail-2.2-bapi-36.1.png[retail-2.2-bapi-36.1.png,399] . Complete the export parameters with the following: + -image:https://www.mulesoft.com/ext/solutions/draft/images/sfc-retail-com-bapi_22.png[sfc-retail-com-bapi_22.png,399] +image:https://www.mulesoft.com/ext/solutions/images/sfc-retail-com-bapi_22.png[sfc-retail-com-bapi_22.png,399] . Copy and paste the code from "ZBAPI_QUERY_V3.txt". . Create the function module "ZBAPI_CONTROL_DATA_V3": + -image:https://www.mulesoft.com/ext/solutions/draft/images/sfc-retail-com-bapi_21.png[sfc-retail-com-bapi_21.png,599] +image:https://www.mulesoft.com/ext/solutions/images/sfc-retail-com-bapi_21.png[sfc-retail-com-bapi_21.png,599] . Complete the import parameters with the following: + -image:https://www.mulesoft.com/ext/solutions/draft/images/sfc-retail-com-bapi_24.png[sfc-retail-com-bapi_24.png,599] +image:https://www.mulesoft.com/ext/solutions/images/sfc-retail-com-bapi_24.png[sfc-retail-com-bapi_24.png,599] . Complete the export parameters with the following: + -image:https://www.mulesoft.com/ext/solutions/draft/images/sfc-retail-com-bapi_19.png[sfc-retail-com-bapi_19.png,599] +image:https://www.mulesoft.com/ext/solutions/images/sfc-retail-com-bapi_19.png[sfc-retail-com-bapi_19.png,599] . Copy the source code from "ZBAPI_CONTROL_DATA_V3.txt". . Activate the entire function group by right-clicking on it in the tree and then selecting "Activate": + -image:https://www.mulesoft.com/ext/solutions/draft/images/sfc-retail-com-bapi_35.png[sfc-retail-com-bapi_35.png,301] +image:https://www.mulesoft.com/ext/solutions/images/sfc-retail-com-bapi_35.png[sfc-retail-com-bapi_35.png,301] . Create the function group "ZFG_CUSTOMER2". . Create the function module "ZBAPI_ADDR_QUERY", using "Remote-enable module" as processing type: + -image:https://www.mulesoft.com/ext/solutions/draft/images/sfc-retail-com-bapi_17.png[sfc-retail-com-bapi_17.png,599] +image:https://www.mulesoft.com/ext/solutions/images/sfc-retail-com-bapi_17.png[sfc-retail-com-bapi_17.png,599] . Complete the import parameters with the following: + -image:https://www.mulesoft.com/ext/solutions/draft/images/sfc-retail-com-bapi_20.png[sfc-retail-com-bapi_20.png,599] +image:https://www.mulesoft.com/ext/solutions/images/sfc-retail-com-bapi_20.png[sfc-retail-com-bapi_20.png,599] . Complete the export parameters with the following: + -image:https://www.mulesoft.com/ext/solutions/draft/images/sfc-retail-com-bapi_22.png[sfc-retail-com-bapi_22.png,399] +image:https://www.mulesoft.com/ext/solutions/images/sfc-retail-com-bapi_22.png[sfc-retail-com-bapi_22.png,399] . Copy and paste the code from "ZBAPI_ADDR_QUERY.txt". . Create the function module "ZBAPI_CONTROL_DATA" using the import parameters as follows: + -image:https://www.mulesoft.com/ext/solutions/draft/images/retail-2.2-bapi-22.1.png[retail-2.2-bapi-22.1.png,599] +image:https://www.mulesoft.com/ext/solutions/images/retail-2.2-bapi-22.1.png[retail-2.2-bapi-22.1.png,599] . Use the export parameters as in the following: + -image:https://www.mulesoft.com/ext/solutions/draft/images/retail-2.2-bapi-22.2.png[retail-2.2-bapi-22.2.png,599] +image:https://www.mulesoft.com/ext/solutions/images/retail-2.2-bapi-22.2.png[retail-2.2-bapi-22.2.png,599] . Copy the source code from "ZBAPI_CONTROL_DATA.txt". . Activate the entire function group by right-clicking on it in the tree and selecting 'Activate': + -image:https://www.mulesoft.com/ext/solutions/draft/images/retail-2.2-bapi-22.3.png[retail-2.2-bapi-22.3.png,301] +image:https://www.mulesoft.com/ext/solutions/images/retail-2.2-bapi-22.3.png[retail-2.2-bapi-22.3.png,301] . Complete the following: . Create a customer group ZSME (*Logistics - General\->Business Partner\->Customer\->Control\->Define and Assign Customer Number Ranges*) . Create a partner group ZSME (*Cross-Application Components\->SAP Business Partner\->Business Partner\->Basic Settings\->Number Ranges and Settings*) from the transaction SPRO . Synchronize them from the same transaction (*Cross-Application Components\->Master Data Synchronization\->Customer/Vendor Integration\->Business Partner Settings\->Settings for Customer Integration\->Assign Keys\->Define Number Assignment for Direction BP to Customer*) + -image:https://www.mulesoft.com/ext/solutions/draft/images/retail-2.2-bapi-22.4.png[retail-2.2-bapi-22.4.png,599] +image:https://www.mulesoft.com/ext/solutions/images/retail-2.2-bapi-22.4.png[retail-2.2-bapi-22.4.png,599] ==== *More ZBAPI modules* @@ -222,52 +222,52 @@ To create ABAP custom objects, groups, and modules: . Create the same dictionary objects created for the BAPI `ZBAPI_CUSTOMER` using the following structure/table type: + -image:https://www.mulesoft.com/ext/solutions/draft/images/retail-2.2-bapi-51.png[retail-2.2-bapi-51.png,599] -image:https://www.mulesoft.com/ext/solutions/draft/images/retail-2.2-bapi-52.png[retail-2.2-bapi-52.png,599] +image:https://www.mulesoft.com/ext/solutions/images/retail-2.2-bapi-51.png[retail-2.2-bapi-51.png,599] +image:https://www.mulesoft.com/ext/solutions/images/retail-2.2-bapi-52.png[retail-2.2-bapi-52.png,599] . Create the function group `ZFG_CUSTOMER2`. . Create the function module `ZBAPI_ADDR_QUERY` using 'Remote-enable module' as the processing type: + -image:https://www.mulesoft.com/ext/solutions/draft/images/retail-2.2-bapi-53.png[retail-2.2-bapi-53.png,599] +image:https://www.mulesoft.com/ext/solutions/images/retail-2.2-bapi-53.png[retail-2.2-bapi-53.png,599] . Complete the import parameters with the following: + -image:https://www.mulesoft.com/ext/solutions/draft/images/retail-2.2-bapi-54.png[retail-2.2-bapi-54.png,599] +image:https://www.mulesoft.com/ext/solutions/images/retail-2.2-bapi-54.png[retail-2.2-bapi-54.png,599] . Complete the export parameters with the following: + -image:https://www.mulesoft.com/ext/solutions/draft/images/retail-2.2-bapi-55.png[retail-2.2-bapi-55.png,399] +image:https://www.mulesoft.com/ext/solutions/images/retail-2.2-bapi-55.png[retail-2.2-bapi-55.png,399] . Copy and paste the code from 'ZBAPI_ADDR_QUERY.txt'. . Create the function module `ZBAPI_ADDR_SAP` using 'Remote-enable module' as the processing type: + -image:https://www.mulesoft.com/ext/solutions/draft/images/retail-2.2-bapi-56.png[retail-2.2-bapi-56.png,599] +image:https://www.mulesoft.com/ext/solutions/images/retail-2.2-bapi-56.png[retail-2.2-bapi-56.png,599] . Complete the import parameters with the following: + -image:https://www.mulesoft.com/ext/solutions/draft/images/retail-2.2-bapi-57.png[retail-2.2-bapi-57.png,599] +image:https://www.mulesoft.com/ext/solutions/images/retail-2.2-bapi-57.png[retail-2.2-bapi-57.png,599] . Complete the export parameters with the following: + -image:https://www.mulesoft.com/ext/solutions/draft/images/retail-2.2-bapi-58.png[retail-2.2-bapi-58.png,599] +image:https://www.mulesoft.com/ext/solutions/images/retail-2.2-bapi-58.png[retail-2.2-bapi-58.png,599] . Copy and paste the code from 'ZBAPI_QUERY_SAP.txt'. . Create the function module `ZBAPI_CUST_QUERY` using 'Remote-enable module' as the processing type: + -image:https://www.mulesoft.com/ext/solutions/draft/images/retail-2.2-bapi-59.png[retail-2.2-bapi-59.png,399] +image:https://www.mulesoft.com/ext/solutions/images/retail-2.2-bapi-59.png[retail-2.2-bapi-59.png,399] . Complete the import parameters with the following: + -image:https://www.mulesoft.com/ext/solutions/draft/images/retail-2.2-bapi-60.png[retail-2.2-bapi-60.png,599] +image:https://www.mulesoft.com/ext/solutions/images/retail-2.2-bapi-60.png[retail-2.2-bapi-60.png,599] . Complete the export parameters with the following: + -image:https://www.mulesoft.com/ext/solutions/draft/images/retail-2.2-bapi-61.png[retail-2.2-bapi-61.png,599] +image:https://www.mulesoft.com/ext/solutions/images/retail-2.2-bapi-61.png[retail-2.2-bapi-61.png,599] . Copy and paste the code from 'ZBAPI_CUST_QUERY.txt'. . Create the function module `ZBAPI_CUSTOMER_CD` using 'Remote-enable module' as the processing type: + -image:https://www.mulesoft.com/ext/solutions/draft/images/retail-2.2-bapi-62.png[retail-2.2-bapi-62.png,399] +image:https://www.mulesoft.com/ext/solutions/images/retail-2.2-bapi-62.png[retail-2.2-bapi-62.png,399] . Complete the import parameters with the following: + -image:https://www.mulesoft.com/ext/solutions/draft/images/retail-2.2-bapi-63.png[retail-2.2-bapi-63.png,599] +image:https://www.mulesoft.com/ext/solutions/images/retail-2.2-bapi-63.png[retail-2.2-bapi-63.png,599] . Complete the export parameters with the following: + -image:https://www.mulesoft.com/ext/solutions/draft/images/retail-2.2-bapi-64.png[retail-2.2-bapi-64.png,599] +image:https://www.mulesoft.com/ext/solutions/images/retail-2.2-bapi-64.png[retail-2.2-bapi-64.png,599] . Copy and paste the code from 'ZBAPI_CUSTOMER_CD.txt'. . Activate the entire function group by right-clicking on it in the tree and selecting 'Activate': + -image:https://www.mulesoft.com/ext/solutions/draft/images/retail-2.2-bapi-65.png[retail-2.2-bapi-65.png,301] +image:https://www.mulesoft.com/ext/solutions/images/retail-2.2-bapi-65.png[retail-2.2-bapi-65.png,301] == See Also diff --git a/retail/2.7/modules/ROOT/pages/sap-s4hana-setup-guide.adoc b/retail/2.7/modules/ROOT/pages/sap-s4hana-setup-guide.adoc index b4b27a925..e6295f815 100644 --- a/retail/2.7/modules/ROOT/pages/sap-s4hana-setup-guide.adoc +++ b/retail/2.7/modules/ROOT/pages/sap-s4hana-setup-guide.adoc @@ -10,24 +10,24 @@ To make the necessary configurations in S/4HANA: . Create a *Communication System* in the corresponding Fiori app. This communication system represents the external system that will consume the S/4HANA Cloud SOAP service. In this example, it's named `COM_0009_SOAP_OUT`: + + -image:https://www.mulesoft.com/ext/solutions/draft/images/retail-sap-s4hana-setup-guide-01.png[retail-sap-s4hana-setup-guide-01.png,799] +image:https://www.mulesoft.com/ext/solutions/images/retail-sap-s4hana-setup-guide-01.png[retail-sap-s4hana-setup-guide-01.png,799] . For the 'Business System' name, use the same name of the System ID. . In the 'Host Name' field, enter the hostname of the Mule application deployed on Cloudhub (if you don't have it yet, you can enter a mock URL and then modify it later): + + -image:https://www.mulesoft.com/ext/solutions/draft/images/retail-sap-s4hana-setup-guide-02.png[retail-sap-s4hana-setup-guide-02.png,799] + +image:https://www.mulesoft.com/ext/solutions/images/retail-sap-s4hana-setup-guide-02.png[retail-sap-s4hana-setup-guide-02.png,799] + + . Create a user that will be used to connect to the Cloud Hub app for sending product information in the outbound scenario (this is necessary even though the Mule application does not validate the user; we used any user for outbound): + + -image:https://www.mulesoft.com/ext/solutions/draft/images/retail-sap-s4hana-setup-guide-03.png[retail-sap-s4hana-setup-guide-03.png,799] + +image:https://www.mulesoft.com/ext/solutions/images/retail-sap-s4hana-setup-guide-03.png[retail-sap-s4hana-setup-guide-03.png,799] + + . Use the *Communication Arrangement* Fiori app to create a new Communication Arrangement: + + -image:https://www.mulesoft.com/ext/solutions/draft/images/retail-sap-s4hana-setup-guide-04.png[retail-sap-s4hana-setup-guide-04.png,799] + +image:https://www.mulesoft.com/ext/solutions/images/retail-sap-s4hana-setup-guide-04.png[retail-sap-s4hana-setup-guide-04.png,799] + + . Create a new *Communication Arrangement*, select the communication scenario "SAP_COM_0009", and then define a specific name for the arrangement, "SAP_COM_0009_SOAP". . In the *Communication System* field, select the Communication System created in the previous step: + + -image:https://www.mulesoft.com/ext/solutions/draft/images/retail-sap-s4hana-setup-guide-05.png[retail-sap-s4hana-setup-guide-05.png,799] + +image:https://www.mulesoft.com/ext/solutions/images/retail-sap-s4hana-setup-guide-05.png[retail-sap-s4hana-setup-guide-05.png,799] + + . For outbound communication, select the previously-created user and configure the *Product Master - Replicate from SAP S/4HANA Cloud to Client* and include the following settings. Make sure to note the Path (`/sap/bc/srt/scs/sap/productmdmbulkreplicaterequest`) because we will use this path to configure the Mule application SOAP endpoint: ** Set the *Service status* to *Active* @@ -35,11 +35,11 @@ image:https://www.mulesoft.com/ext/solutions/draft/images/retail-sap-s4hana-setu ** Replication model = `I (Initial)` ** The Output Mode = `D (Direct)` + + -image:https://www.mulesoft.com/ext/solutions/draft/images/retail-sap-s4hana-setup-guide-06.png[retail-sap-s4hana-setup-guide-06.png,799] + +image:https://www.mulesoft.com/ext/solutions/images/retail-sap-s4hana-setup-guide-06.png[retail-sap-s4hana-setup-guide-06.png,799] + + -image:https://www.mulesoft.com/ext/solutions/draft/images/retail-sap-s4hana-setup-guide-07.png[retail-sap-s4hana-setup-guide-07.png,799] + +image:https://www.mulesoft.com/ext/solutions/images/retail-sap-s4hana-setup-guide-07.png[retail-sap-s4hana-setup-guide-07.png,799] + + -image:https://www.mulesoft.com/ext/solutions/draft/images/retail-sap-s4hana-setup-guide-08.png[retail-sap-s4hana-setup-guide-08.png,799] + +image:https://www.mulesoft.com/ext/solutions/images/retail-sap-s4hana-setup-guide-08.png[retail-sap-s4hana-setup-guide-08.png,799] + + . Save it. All configurations at S/4HANA Cloud side are finished and you will be able to download the WSDL that contains the metadata to import into the S/4HANA Cloud SOAP Connector into the Mule application. @@ -49,38 +49,38 @@ The following example describes how to create a Mule application using the Outbo . Create a Mule project and add the appropriate connector from Exchange to the Mule Palette: + + -image:https://www.mulesoft.com/ext/solutions/draft/images/retail-sap-s4hana-setup-guide-09.png[retail-sap-s4hana-setup-guide-09.png,799] + +image:https://www.mulesoft.com/ext/solutions/images/retail-sap-s4hana-setup-guide-09.png[retail-sap-s4hana-setup-guide-09.png,799] + + . Add and configure the *Outbound Message Listener* to the canvas: + + -image:https://www.mulesoft.com/ext/solutions/draft/images/retail-sap-s4hana-setup-guide-10.png[retail-sap-s4hana-setup-guide-10.png,799] + +image:https://www.mulesoft.com/ext/solutions/images/retail-sap-s4hana-setup-guide-10.png[retail-sap-s4hana-setup-guide-10.png,799] + + . Add the corresponding WSDL path to the WSDL you downloaded from S/4HANA Cloud and create the HTTP listener configuration: + + -image:https://www.mulesoft.com/ext/solutions/draft/images/retail-sap-s4hana-setup-guide-11.png[retail-sap-s4hana-setup-guide-11.png,799] + +image:https://www.mulesoft.com/ext/solutions/images/retail-sap-s4hana-setup-guide-11.png[retail-sap-s4hana-setup-guide-11.png,799] + + -image:https://www.mulesoft.com/ext/solutions/draft/images/retail-sap-s4hana-setup-guide-12.png[retail-sap-s4hana-setup-guide-12.png,799] + +image:https://www.mulesoft.com/ext/solutions/images/retail-sap-s4hana-setup-guide-12.png[retail-sap-s4hana-setup-guide-12.png,799] + + _Note: we are using no authentication on the Mule Application, so we used the Insecure option for the Trust Store Configuration. In the Keystore configuration, we used a test Keystore, which is mandatory for HTTPS communication:_ + + -image:https://www.mulesoft.com/ext/solutions/draft/images/retail-sap-s4hana-setup-guide-13.png[retail-sap-s4hana-setup-guide-13.png,799] + +image:https://www.mulesoft.com/ext/solutions/images/retail-sap-s4hana-setup-guide-13.png[retail-sap-s4hana-setup-guide-13.png,799] + + . Select the Message type that the connector expects to receive from SAP (the connector reads the metadata from the WSDL we configured): + + -image:https://www.mulesoft.com/ext/solutions/draft/images/retail-sap-s4hana-setup-guide-14.png[retail-sap-s4hana-setup-guide-14.png,799] + +image:https://www.mulesoft.com/ext/solutions/images/retail-sap-s4hana-setup-guide-14.png[retail-sap-s4hana-setup-guide-14.png,799] + + . On the Responses tab, use the status Code "202" and the Reason-Phrase "Accepted" because we want to send the same status that S/4HANA Cloud will send if the service invocation results OK. No payload will be returned as a response - just the `Status` code and `Reason-phrase`: + + -image:https://www.mulesoft.com/ext/solutions/draft/images/retail-sap-s4hana-setup-guide-15.png[retail-sap-s4hana-setup-guide-15.png,799] + +image:https://www.mulesoft.com/ext/solutions/images/retail-sap-s4hana-setup-guide-15.png[retail-sap-s4hana-setup-guide-15.png,799] + + . Use a *Logger* component to log the inbound XML payload: + + -image:https://www.mulesoft.com/ext/solutions/draft/images/retail-sap-s4hana-setup-guide-16.png[retail-sap-s4hana-setup-guide-16.png,799] + +image:https://www.mulesoft.com/ext/solutions/images/retail-sap-s4hana-setup-guide-16.png[retail-sap-s4hana-setup-guide-16.png,799] + + _The Mule flow should look like the following:_ + + -image:https://www.mulesoft.com/ext/solutions/draft/images/retail-sap-s4hana-setup-guide-17.png[retail-sap-s4hana-setup-guide-17.png,399] + +image:https://www.mulesoft.com/ext/solutions/images/retail-sap-s4hana-setup-guide-17.png[retail-sap-s4hana-setup-guide-17.png,399] + + . Deploy the application to Cloudhub. You're now ready to test the scenario. @@ -90,35 +90,35 @@ To test the scenario: . Create the following. You only need to create a material in the corresponding Fiori app of S/4HANA Cloud: + + -image:https://www.mulesoft.com/ext/solutions/draft/images/retail-sap-s4hana-setup-guide-18.png[retail-sap-s4hana-setup-guide-18.png,599] + +image:https://www.mulesoft.com/ext/solutions/images/retail-sap-s4hana-setup-guide-18.png[retail-sap-s4hana-setup-guide-18.png,599] + + -image:https://www.mulesoft.com/ext/solutions/draft/images/retail-sap-s4hana-setup-guide-19.png[retail-sap-s4hana-setup-guide-19.png,799] + +image:https://www.mulesoft.com/ext/solutions/images/retail-sap-s4hana-setup-guide-19.png[retail-sap-s4hana-setup-guide-19.png,799] + + -image:https://www.mulesoft.com/ext/solutions/draft/images/retail-sap-s4hana-setup-guide-20.png[retail-sap-s4hana-setup-guide-20.png,799] + +image:https://www.mulesoft.com/ext/solutions/images/retail-sap-s4hana-setup-guide-20.png[retail-sap-s4hana-setup-guide-20.png,799] + + -image:https://www.mulesoft.com/ext/solutions/draft/images/retail-sap-s4hana-setup-guide-21.png[retail-sap-s4hana-setup-guide-21.png,799] + +image:https://www.mulesoft.com/ext/solutions/images/retail-sap-s4hana-setup-guide-21.png[retail-sap-s4hana-setup-guide-21.png,799] + + _After you save the new material, you should see the following confirmation in S/4HANA Cloud:_ + + -image:https://www.mulesoft.com/ext/solutions/draft/images/retail-sap-s4hana-setup-guide-22.png[retail-sap-s4hana-setup-guide-22.png,399] + +image:https://www.mulesoft.com/ext/solutions/images/retail-sap-s4hana-setup-guide-22.png[retail-sap-s4hana-setup-guide-22.png,399] + + _The following shows the XML message received at the Mule application at the Runtime Manager on Cloudhub:_ + + -image:https://www.mulesoft.com/ext/solutions/draft/images/retail-sap-s4hana-setup-guide-23.png[retail-sap-s4hana-setup-guide-23.png,799] + +image:https://www.mulesoft.com/ext/solutions/images/retail-sap-s4hana-setup-guide-23.png[retail-sap-s4hana-setup-guide-23.png,799] + + . See the sent message in the Message Dashboard Fiori Application: + + -image:https://www.mulesoft.com/ext/solutions/draft/images/retail-sap-s4hana-setup-guide-24.png[retail-sap-s4hana-setup-guide-24.png,799] + +image:https://www.mulesoft.com/ext/solutions/images/retail-sap-s4hana-setup-guide-24.png[retail-sap-s4hana-setup-guide-24.png,799] + + . Select the date: + + -image:https://www.mulesoft.com/ext/solutions/draft/images/retail-sap-s4hana-setup-guide-25.png[retail-sap-s4hana-setup-guide-25.png,399] + +image:https://www.mulesoft.com/ext/solutions/images/retail-sap-s4hana-setup-guide-25.png[retail-sap-s4hana-setup-guide-25.png,399] + + . Search under *CMD:Product Integration - /CMDPR → Product Replication to Client via Service - PRDREQ_OUT/00001 namespace*: + + -image:https://www.mulesoft.com/ext/solutions/draft/images/retail-sap-s4hana-setup-guide-26.png[retail-sap-s4hana-setup-guide-26.png,799] + +image:https://www.mulesoft.com/ext/solutions/images/retail-sap-s4hana-setup-guide-26.png[retail-sap-s4hana-setup-guide-26.png,799] + + -image:https://www.mulesoft.com/ext/solutions/draft/images/retail-sap-s4hana-setup-guide-27.png[retail-sap-s4hana-setup-guide-27.png,799] +image:https://www.mulesoft.com/ext/solutions/images/retail-sap-s4hana-setup-guide-27.png[retail-sap-s4hana-setup-guide-27.png,799] == S/4HANA customization guide diff --git a/retail/2.7/modules/ROOT/pages/sfdc-data-cloud-setup-guide.adoc b/retail/2.7/modules/ROOT/pages/sfdc-data-cloud-setup-guide.adoc index e67313693..fc0ae1e29 100644 --- a/retail/2.7/modules/ROOT/pages/sfdc-data-cloud-setup-guide.adoc +++ b/retail/2.7/modules/ROOT/pages/sfdc-data-cloud-setup-guide.adoc @@ -8,7 +8,7 @@ The following provides guidance on Salesforce Data Cloud setup required for the . Click the Setup icon and then `Data Cloud Setup`. If you don't see this option, either refresh your page or log out and back in with your admin user credentials. . Click `Get Started`. Setup can take a few minutes. Your Data Cloud instance is considered as successfully set up if you see a green tick mark for all the steps. If not, correct the issue and finish the setup. -image::https://www.mulesoft.com/ext/solutions/draft/images/rcg-cdp-setup-cdp-provisioning.png[rcg-cdp-setup-cdp-provisioning.png,599] +image::https://www.mulesoft.com/ext/solutions/images/rcg-cdp-setup-cdp-provisioning.png[rcg-cdp-setup-cdp-provisioning.png,599] == Connect Data @@ -212,7 +212,7 @@ Anypoint Connector for Salesforce CDP (Data Cloud Connector) provides customers This connector works with the Data Cloud Bulk and Streaming API, depending on the operation you configure. Each API call uses a request/response pattern over an HTTPS connection. All required request headers, error handling, and HTTPS connection configurations are built into the connector. -Refer to this https://dev-docs-internal.kqa.msap.io/beta-accelerators/salesforce-cdp-connector/1.0/[link] for details on configuration and operations for Data Cloud Connector. +Refer to this https://docs.mulesoft.com/salesforce-cdp-connector/1.0/[link] for details on configuration and operations for Data Cloud Connector. For the "Personalization with CDP" use case, refer CDP System API specification and implementation template. @@ -242,11 +242,11 @@ For the "Personalization with CDP" use case, we mapped to Custom DMO for our Mul ==== Data Mapping -image::https://www.mulesoft.com/ext/solutions/draft/images/rcg-cdp-setup-custom-dmo-webengagement.png[rcg-cdp-setup-custom-dmo-webengagement.png,599] +image::https://www.mulesoft.com/ext/solutions/images/rcg-cdp-setup-custom-dmo-webengagement.png[rcg-cdp-setup-custom-dmo-webengagement.png,599] ==== Data Relationships -image::https://www.mulesoft.com/ext/solutions/draft/images/rcg-cdp-setup-webengagement-data-relationships.png[rcg-cdp-setup-webengagement-data-relationships.png,599] +image::https://www.mulesoft.com/ext/solutions/images/rcg-cdp-setup-webengagement-data-relationships.png[rcg-cdp-setup-webengagement-data-relationships.png,599] == Identity Resolution @@ -261,9 +261,9 @@ Access Identity Resolution from Data Cloud after mapping entities to the CIM. En For the `Personalization with CDP` use case, we are leveraging the Fuzzy Name and Normalized Email Match Rule; leveraging Fuzzy First Name, Exact Last Name, and Normalized Email Address. -image:https://www.mulesoft.com/ext/solutions/draft/images/rcg-cdp-setup-identity-match-rules.png[rcg-cdp-setup-identity-match-rules.png,599] +image:https://www.mulesoft.com/ext/solutions/images/rcg-cdp-setup-identity-match-rules.png[rcg-cdp-setup-identity-match-rules.png,599] -image:https://www.mulesoft.com/ext/solutions/draft/images/rcg-cdp-setup-identity-match-rules-criteria.png[rcg-cdp-setup-identity-match-rules-criteria.png,599] +image:https://www.mulesoft.com/ext/solutions/images/rcg-cdp-setup-identity-match-rules-criteria.png[rcg-cdp-setup-identity-match-rules-criteria.png,599] To create your Identity Resolution Rules, follow the steps below: @@ -303,7 +303,7 @@ Segment On: Segment On defines the target entity (object) used to build your seg For the "Personalization with CDP" use case, we have created a few Segments. All Segments that we have created have been segmented on Unified Individual. For this segment, we wanted to create an audience wherein there were no Web Page Views in the last 365 Days. We grabbed updated Date from our Attribute Library and dragged it to the canvas. And for the operator we selected "Greater Than Last Number of Days" and entered "365" for the number of days. In the *Publish Schedule* field, we select a schedule of every 24 hours. -image::https://www.mulesoft.com/ext/solutions/draft/images/rcg-cdp-setup-segment-nowebpageviews.png[rcg-cdp-setup-segment-nowebpageviews.png,599] +image::https://www.mulesoft.com/ext/solutions/images/rcg-cdp-setup-segment-nowebpageviews.png[rcg-cdp-setup-segment-nowebpageviews.png,599] === Activation Targets @@ -423,7 +423,7 @@ For the "Personalization with CDP" use case, we created Calculated Insights to g Once created, Calculated Insights are available in the Attribute Library. You can also confirm and validate Calculated Insights via Data Explorer. -image::https://www.mulesoft.com/ext/solutions/draft/images/rcg-cdp-setup-calculated-insights.png[rcg-cdp-setup-calculated-insights.png,399] +image::https://www.mulesoft.com/ext/solutions/images/rcg-cdp-setup-calculated-insights.png[rcg-cdp-setup-calculated-insights.png,399] == See Also diff --git a/retail/3.0/modules/ROOT/pages/index.adoc b/retail/3.0/modules/ROOT/pages/index.adoc index 1bfd24162..51a266690 100644 --- a/retail/3.0/modules/ROOT/pages/index.adoc +++ b/retail/3.0/modules/ROOT/pages/index.adoc @@ -7,19 +7,19 @@ MuleSoft Accelerator for Retail empowers retail IT teams to unlock data from sys The following use cases are supported by the MuleSoft Accelerator for Retail: -* https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/mulesoft-accelerator-for-retail/minor/{retail-version}/pages/Use%20case%201%20-%20Customer%20profile%20sync/[Customer profile sync^] - The Customer profile sync use case enables retail developers to create a customer 360 view by unlocking customer data from disparate systems. +* https://anypoint.mulesoft.com/exchange/org.mule.examples/mulesoft-accelerator-for-retail/minor/{retail-version}/pages/Use%20case%201%20-%20Customer%20profile%20sync/[Customer profile sync^] - The Customer profile sync use case enables retail developers to create a customer 360 view by unlocking customer data from disparate systems. -* https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/mulesoft-accelerator-for-retail/minor/{retail-version}/pages/Use%20case%202%20-%20Sales%20order%20sync/[Sales order sync^] - The Sales order sync use case enables retail developers to create and update sales orders across relevant applications. +* https://anypoint.mulesoft.com/exchange/org.mule.examples/mulesoft-accelerator-for-retail/minor/{retail-version}/pages/Use%20case%202%20-%20Sales%20order%20sync/[Sales order sync^] - The Sales order sync use case enables retail developers to create and update sales orders across relevant applications. -* https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/mulesoft-accelerator-for-retail/minor/{retail-version}/pages/Use%20case%203%20-%20Product%20sync/[Product sync^] - The Product sync use case enables retail developers to update product details in Salsify across relevant applications. +* https://anypoint.mulesoft.com/exchange/org.mule.examples/mulesoft-accelerator-for-retail/minor/{retail-version}/pages/Use%20case%203%20-%20Product%20sync/[Product sync^] - The Product sync use case enables retail developers to update product details in Salsify across relevant applications. -* https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/mulesoft-accelerator-for-retail/minor/{retail-version}/pages/Use%20case%204%20-%20Real-time%20inventory%20management/[Real-time inventory management^] - The Real-time inventory management use case enables customers to make an informed decision of their online purchase based on real-time inventory of a product in nearby stores. +* https://anypoint.mulesoft.com/exchange/org.mule.examples/mulesoft-accelerator-for-retail/minor/{retail-version}/pages/Use%20case%204%20-%20Real-time%20inventory%20management/[Real-time inventory management^] - The Real-time inventory management use case enables customers to make an informed decision of their online purchase based on real-time inventory of a product in nearby stores. -* https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/mulesoft-accelerator-for-retail/minor/{retail-version}/pages/Use%20case%205%20-%20Deliver%20relevancy%20with%20CDP/[Deliver relevancy with CDP^] - The Deliver relevancy with CDP use case enables retail developers to combine customer profile data in a standardized format. +* https://anypoint.mulesoft.com/exchange/org.mule.examples/mulesoft-accelerator-for-retail/minor/{retail-version}/pages/Use%20case%205%20-%20Deliver%20relevancy%20with%20CDP/[Deliver relevancy with CDP^] - The Deliver relevancy with CDP use case enables retail developers to combine customer profile data in a standardized format. == See Also * xref:accelerators-home::getting-started.adoc[Getting Started Guide] * xref:prerequisites.adoc[Prerequisites] * xref:release-notes::accelerators/retail/retail-release-notes.adoc[Release Notes] -* https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/mulesoft-accelerator-for-retail/[MuleSoft Accelerator for Retail on Exchange^] +* https://anypoint.mulesoft.com/exchange/org.mule.examples/mulesoft-accelerator-for-retail/[MuleSoft Accelerator for Retail on Exchange^] diff --git a/retail/3.0/modules/ROOT/pages/rcg-assets.adoc b/retail/3.0/modules/ROOT/pages/rcg-assets.adoc index b24864e70..df2f098bc 100644 --- a/retail/3.0/modules/ROOT/pages/rcg-assets.adoc +++ b/retail/3.0/modules/ROOT/pages/rcg-assets.adoc @@ -7,76 +7,76 @@ Accelerator assets include API specifications, implementation templates, custom [cols="40,30,30",width=100%] |=== | B2B Commerce System API -| https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/rcg-b2b-commerce-sys-api-spec/[API Specification^] -| https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/rcg-b2b-commerce-sys-api/[Implementation Template^] +| https://anypoint.mulesoft.com/exchange/org.mule.examples/rcg-b2b-commerce-sys-api-spec/[API Specification^] +| https://anypoint.mulesoft.com/exchange/org.mule.examples/rcg-b2b-commerce-sys-api/[Implementation Template^] | B2C Commerce System API -| https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/rcg-b2c-commerce-sys-api-spec/[API Specification^] -| https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/rcg-b2c-commerce-sys-api[Implementation Template^] +| https://anypoint.mulesoft.com/exchange/org.mule.examples/rcg-b2c-commerce-sys-api-spec/[API Specification^] +| https://anypoint.mulesoft.com/exchange/org.mule.examples/rcg-b2c-commerce-sys-api[Implementation Template^] | B2C Customers System API -| https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/rcg-b2c-customers-sys-api-spec/[API Specification^] -| https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/rcg-b2c-customers-sys-api/[Implementation Template^] +| https://anypoint.mulesoft.com/exchange/org.mule.examples/rcg-b2c-customers-sys-api-spec/[API Specification^] +| https://anypoint.mulesoft.com/exchange/org.mule.examples/rcg-b2c-customers-sys-api/[Implementation Template^] | MDM System API -| https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/rcg-mdm-sys-api-spec/[API Specification^] -| https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/rcg-mdm-sys-api/[Implementation Template^] +| https://anypoint.mulesoft.com/exchange/org.mule.examples/rcg-mdm-sys-api-spec/[API Specification^] +| https://anypoint.mulesoft.com/exchange/org.mule.examples/rcg-mdm-sys-api/[Implementation Template^] | RCG Salsify Products System API -| https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/rcg-salsify-products-sys-api-spec/[API Specification^] -| https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/rcg-salsify-products-sys-api/[Implementation Template^] +| https://anypoint.mulesoft.com/exchange/org.mule.examples/rcg-salsify-products-sys-api-spec/[API Specification^] +| https://anypoint.mulesoft.com/exchange/org.mule.examples/rcg-salsify-products-sys-api/[Implementation Template^] | RCG Azure Cosmos DB System API -| https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/rcg-azure-sys-api-spec/[API Specification^] -| https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/rcg-azure-sys-api/[Implementation Template^] +| https://anypoint.mulesoft.com/exchange/org.mule.examples/rcg-azure-sys-api-spec/[API Specification^] +| https://anypoint.mulesoft.com/exchange/org.mule.examples/rcg-azure-sys-api/[Implementation Template^] | RCG B2C Commerce System API -| https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/rcg-b2c-commerce-sys-api-spec/[API Specification^] -| https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/rcg-b2c-commerce-sys-api/[Implementation Template^] +| https://anypoint.mulesoft.com/exchange/org.mule.examples/rcg-b2c-commerce-sys-api-spec/[API Specification^] +| https://anypoint.mulesoft.com/exchange/org.mule.examples/rcg-b2c-commerce-sys-api/[Implementation Template^] | RCG Marketo System API -| https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/rcg-marketo-system-api-spec/[API Specification^] -| https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/rcg-marketo-system-api/[Implementation Template^] +| https://anypoint.mulesoft.com/exchange/org.mule.examples/rcg-marketo-system-api-spec/[API Specification^] +| https://anypoint.mulesoft.com/exchange/org.mule.examples/rcg-marketo-system-api/[Implementation Template^] | RCG Salesforce CDP System API -| https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/rcg-salesforce-cdp-sys-api-spec/[API Specification^] -| https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/rcg-salesforce-cdp-sys-api/[Implementation Template^] +| https://anypoint.mulesoft.com/exchange/org.mule.examples/rcg-salesforce-cdp-sys-api-spec/[API Specification^] +| https://anypoint.mulesoft.com/exchange/org.mule.examples/rcg-salesforce-cdp-sys-api/[Implementation Template^] | RCG Snowflake System API -| https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/rcg-snowflake-sys-api-spec/[API Specification^] -| https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/rcg-snowflake-sys-api/[Implementation Template^] +| https://anypoint.mulesoft.com/exchange/org.mule.examples/rcg-snowflake-sys-api-spec/[API Specification^] +| https://anypoint.mulesoft.com/exchange/org.mule.examples/rcg-snowflake-sys-api/[Implementation Template^] | Salesforce Customers System API -| https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/rcg-salesforce-customers-sys-api-spec/[API Specification^] -| https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/rcg-salesforce-customers-sys-api/[Implementation Template^] +| https://anypoint.mulesoft.com/exchange/org.mule.examples/rcg-salesforce-customers-sys-api-spec/[API Specification^] +| https://anypoint.mulesoft.com/exchange/org.mule.examples/rcg-salesforce-customers-sys-api/[Implementation Template^] | Salesforce Marketing System API -| https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/rcg-salesforce-marketing-sys-api-spec/[API Specification^] -| https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/rcg-salesforce-marketing-sys-api/[Implementation Template^] +| https://anypoint.mulesoft.com/exchange/org.mule.examples/rcg-salesforce-marketing-sys-api-spec/[API Specification^] +| https://anypoint.mulesoft.com/exchange/org.mule.examples/rcg-salesforce-marketing-sys-api/[Implementation Template^] | Salesforce Orders System API -| https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/rcg-salesforce-orders-sys-api-spec/[API Specification^] -| https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/rcg-salesforce-orders-sys-api/[Implementation Template^] +| https://anypoint.mulesoft.com/exchange/org.mule.examples/rcg-salesforce-orders-sys-api-spec/[API Specification^] +| https://anypoint.mulesoft.com/exchange/org.mule.examples/rcg-salesforce-orders-sys-api/[Implementation Template^] | SAP ECC Customers System API -| https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/rcg-sapecc-customers-sys-api-spec/[API Specification^] -| https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/rcg-sapecc-customers-sys-api/[Implementation Template^] +| https://anypoint.mulesoft.com/exchange/org.mule.examples/rcg-sapecc-customers-sys-api-spec/[API Specification^] +| https://anypoint.mulesoft.com/exchange/org.mule.examples/rcg-sapecc-customers-sys-api/[Implementation Template^] | SAP S/4HANA Customers System API -| https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/rcg-saphana-customers-sys-api-spec/[API Specification^] -| https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/rcg-saphana-customers-sys-api/[Implementation Template^] +| https://anypoint.mulesoft.com/exchange/org.mule.examples/rcg-saphana-customers-sys-api-spec/[API Specification^] +| https://anypoint.mulesoft.com/exchange/org.mule.examples/rcg-saphana-customers-sys-api/[Implementation Template^] | SAP S/4HANA Orders System API -| https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/accelerator-saphana-orders-sys-api/[API Specification^] -| https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/rcg-saphana-orders-sys-api/[Implementation Template^] +| https://anypoint.mulesoft.com/exchange/org.mule.examples/accelerator-saphana-orders-sys-api/[API Specification^] +| https://anypoint.mulesoft.com/exchange/org.mule.examples/rcg-saphana-orders-sys-api/[Implementation Template^] | SAP S/4HANA Product Availability System API -| https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/accelerator-saphana-productavailability-sys-api/[API Specification^] -| https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/accel-saphana-productavailability-sys-api/[Implementation Template^] +| https://anypoint.mulesoft.com/exchange/org.mule.examples/accelerator-saphana-productavailability-sys-api/[API Specification^] +| https://anypoint.mulesoft.com/exchange/org.mule.examples/accel-saphana-productavailability-sys-api/[Implementation Template^] | SAP S/4HANA Products System API -| https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/rcg-saphana-products-sys-api-spec/[API Specification^] -| https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/rcg-saphana-products-sys-api/[Implementation Template^] +| https://anypoint.mulesoft.com/exchange/org.mule.examples/rcg-saphana-products-sys-api-spec/[API Specification^] +| https://anypoint.mulesoft.com/exchange/org.mule.examples/rcg-saphana-products-sys-api/[Implementation Template^] |=== == Process APIs @@ -84,40 +84,40 @@ Accelerator assets include API specifications, implementation templates, custom [cols="40,30,30",width=100%] |=== | Customers Process API -| https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/rcg-customers-prc-api-spec/[API Specification^] -| https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/rcg-customers-prc-api/[Implementation Template^] +| https://anypoint.mulesoft.com/exchange/org.mule.examples/rcg-customers-prc-api-spec/[API Specification^] +| https://anypoint.mulesoft.com/exchange/org.mule.examples/rcg-customers-prc-api/[Implementation Template^] | ERP Customers Process API -| https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/rcg-erp-customers-prc-api-spec/[API Specification^] -| https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/rcg-erp-customers-prc-api/[Implementation Template^] +| https://anypoint.mulesoft.com/exchange/org.mule.examples/rcg-erp-customers-prc-api-spec/[API Specification^] +| https://anypoint.mulesoft.com/exchange/org.mule.examples/rcg-erp-customers-prc-api/[Implementation Template^] | ERP Orders Process API -| https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/rcg-erp-orders-prc-api-spec/[API Specification^] -| https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/rcg-erp-orders-prc-api/[Implementation Template^] +| https://anypoint.mulesoft.com/exchange/org.mule.examples/rcg-erp-orders-prc-api-spec/[API Specification^] +| https://anypoint.mulesoft.com/exchange/org.mule.examples/rcg-erp-orders-prc-api/[Implementation Template^] | Inventory Process API -| https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/rcg-inventory-prc-api-spec/[API Specification^] -| https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/rcg-inventory-prc-api/[Implementation Template^] +| https://anypoint.mulesoft.com/exchange/org.mule.examples/rcg-inventory-prc-api-spec/[API Specification^] +| https://anypoint.mulesoft.com/exchange/org.mule.examples/rcg-inventory-prc-api/[Implementation Template^] | Orders Process API -| https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/rcg-orders-prc-api-spec/[API Specification^] -| https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/rcg-orders-prc-api/[Implementation Template^] +| https://anypoint.mulesoft.com/exchange/org.mule.examples/rcg-orders-prc-api-spec/[API Specification^] +| https://anypoint.mulesoft.com/exchange/org.mule.examples/rcg-orders-prc-api/[Implementation Template^] | Products Process API -| https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/rcg-products-prc-api-spec/[API Specification^] -| https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/rcg-products-prc-api/[Implementation Template^] +| https://anypoint.mulesoft.com/exchange/org.mule.examples/rcg-products-prc-api-spec/[API Specification^] +| https://anypoint.mulesoft.com/exchange/org.mule.examples/rcg-products-prc-api/[Implementation Template^] | RCG Customer Data Platform Process API -| https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/rcg-cdp-prc-api-spec/[API Specification^] -| https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/rcg-cdp-prc-api/[Implementation Template^] +| https://anypoint.mulesoft.com/exchange/org.mule.examples/rcg-cdp-prc-api-spec/[API Specification^] +| https://anypoint.mulesoft.com/exchange/org.mule.examples/rcg-cdp-prc-api/[Implementation Template^] | RCG DataLake Process API -| https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/rcg-datalake-prc-api-spec/[API Specification^] -| https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/rcg-datalake-prc-api/[Implementation Template^] +| https://anypoint.mulesoft.com/exchange/org.mule.examples/rcg-datalake-prc-api-spec/[API Specification^] +| https://anypoint.mulesoft.com/exchange/org.mule.examples/rcg-datalake-prc-api/[Implementation Template^] | RCG Marketing Process API -| https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/rcg-marketing-prc-api-spec/[API Specification^] -| https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/rcg-marketing-prc-api/[Implementation Template^] +| https://anypoint.mulesoft.com/exchange/org.mule.examples/rcg-marketing-prc-api-spec/[API Specification^] +| https://anypoint.mulesoft.com/exchange/org.mule.examples/rcg-marketing-prc-api/[Implementation Template^] |=== == Experience APIs @@ -125,12 +125,12 @@ Accelerator assets include API specifications, implementation templates, custom [cols="40,30,30",width=100%] |=== | B2C Commerce Experience API -| https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/rcg-b2c-commerce-exp-api-spec/[API Specification^] -| https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/rcg-b2c-commerce-exp-api[Implementation Template^] +| https://anypoint.mulesoft.com/exchange/org.mule.examples/rcg-b2c-commerce-exp-api-spec/[API Specification^] +| https://anypoint.mulesoft.com/exchange/org.mule.examples/rcg-b2c-commerce-exp-api[Implementation Template^] | Salesforce Experience API -| https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/rcg-salesforce-exp-api-spec/[API Specification^] -| https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/rcg-salesforce-exp-api/[Implementation Template^] +| https://anypoint.mulesoft.com/exchange/org.mule.examples/rcg-salesforce-exp-api-spec/[API Specification^] +| https://anypoint.mulesoft.com/exchange/org.mule.examples/rcg-salesforce-exp-api/[Implementation Template^] |=== == Listeners & Handlers @@ -138,16 +138,16 @@ Accelerator assets include API specifications, implementation templates, custom [cols="70,30",width=100%] |=== | Salesforce Marketing Listener -| https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/rcg-salesforce-marketing-listener/[Implementation Template^] +| https://anypoint.mulesoft.com/exchange/org.mule.examples/rcg-salesforce-marketing-listener/[Implementation Template^] | Salesforce Topic Listener -| https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/rcg-salesforce-topic-listener/[Implementation Template^] +| https://anypoint.mulesoft.com/exchange/org.mule.examples/rcg-salesforce-topic-listener/[Implementation Template^] | SAP Event Listener -| https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/rcg-sap-event-listener/[Implementation Template^] +| https://anypoint.mulesoft.com/exchange/org.mule.examples/rcg-sap-event-listener/[Implementation Template^] | Salsify Channel Listener -| https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/rcg-salsify-channel-listener/[Implementation Template^] +| https://anypoint.mulesoft.com/exchange/org.mule.examples/rcg-salsify-channel-listener/[Implementation Template^] |=== === Custom Components @@ -155,29 +155,29 @@ Accelerator assets include API specifications, implementation templates, custom [cols="70,30",width=100%] |=== | B2C Commerce Instore Pickup Cartridge -| https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/rcg-b2c-commerce-instore-pickup-cartridge-src/[Source^] +| https://anypoint.mulesoft.com/exchange/org.mule.examples/rcg-b2c-commerce-instore-pickup-cartridge-src/[Source^] | B2C Commerce Sync Cartridge -| https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/rcg-b2c-commerce-sync-cartridge-src/[Source^] +| https://anypoint.mulesoft.com/exchange/org.mule.examples/rcg-b2c-commerce-sync-cartridge-src/[Source^] | ID Graph Lightning Web Component -| https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/accelerator-idgraph-lwc-src[Source^] +| https://anypoint.mulesoft.com/exchange/org.mule.examples/accelerator-idgraph-lwc-src[Source^] | POM Parent -| https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/accelerator-pom-parent-src/[Source^] +| https://anypoint.mulesoft.com/exchange/org.mule.examples/accelerator-pom-parent-src/[Source^] | Product Availability Lightning Web Component -| https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/accelerator-productavailability-lwc-src/[Source^] +| https://anypoint.mulesoft.com/exchange/org.mule.examples/accelerator-productavailability-lwc-src/[Source^] |=== == Shared APIs [cols="40,30,30",width=100%] |=== -| Accelerator Email System API | https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/accelerator-email-sys-api[API Specification^] | https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/accel-email-sys-api[Implementation Template^] -| Accelerator Slack System API | https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/accelerator-slack-sys-api[API Specification^] | https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/accel-slack-sys-api[Implementation Template^] -| Accelerator SMS System API | https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/accelerator-sms-sys-api[API Specification^] | https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/accel-sms-sys-api[Implementation Template^] -| Accelerator Notifications Process API | https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/accelerator-notifications-prc-api[API Specification^] | https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/accel-notifications-prc-api/[Implementation Template^] +| Accelerator Email System API | https://anypoint.mulesoft.com/exchange/org.mule.examples/accelerator-email-sys-api[API Specification^] | https://anypoint.mulesoft.com/exchange/org.mule.examples/accel-email-sys-api[Implementation Template^] +| Accelerator Slack System API | https://anypoint.mulesoft.com/exchange/org.mule.examples/accelerator-slack-sys-api[API Specification^] | https://anypoint.mulesoft.com/exchange/org.mule.examples/accel-slack-sys-api[Implementation Template^] +| Accelerator SMS System API | https://anypoint.mulesoft.com/exchange/org.mule.examples/accelerator-sms-sys-api[API Specification^] | https://anypoint.mulesoft.com/exchange/org.mule.examples/accel-sms-sys-api[Implementation Template^] +| Accelerator Notifications Process API | https://anypoint.mulesoft.com/exchange/org.mule.examples/accelerator-notifications-prc-api[API Specification^] | https://anypoint.mulesoft.com/exchange/org.mule.examples/accel-notifications-prc-api/[Implementation Template^] |=== == Shared Components @@ -185,13 +185,13 @@ Accelerator assets include API specifications, implementation templates, custom [cols="70,30",width=100%] |=== | Accelerator Common Core -| https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/accelerator-common-core-src/[Source^] +| https://anypoint.mulesoft.com/exchange/org.mule.examples/accelerator-common-core-src/[Source^] | POM Parent -| https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/accelerator-pom-parent-src/[Source^] +| https://anypoint.mulesoft.com/exchange/org.mule.examples/accelerator-pom-parent-src/[Source^] | ID Graph Lightning Web Component -| https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/accelerator-idgraph-lwc-src/[Source^] +| https://anypoint.mulesoft.com/exchange/org.mule.examples/accelerator-idgraph-lwc-src/[Source^] |=== == See Also diff --git a/retail/3.0/modules/ROOT/pages/sap-custom-bapi-setup-guide.adoc b/retail/3.0/modules/ROOT/pages/sap-custom-bapi-setup-guide.adoc index 7611ac3ae..c5b529059 100644 --- a/retail/3.0/modules/ROOT/pages/sap-custom-bapi-setup-guide.adoc +++ b/retail/3.0/modules/ROOT/pages/sap-custom-bapi-setup-guide.adoc @@ -5,7 +5,7 @@ The following provides guidance on how to use the custom BAPI code (for example, `ZBAPI_CUSTOMER_V3`) for your SAP instance. [NOTE] -You must complete the following instructions before deploying the https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/mulesoft-accelerator-for-retail/minor/{retail-version}/pages/Use%20case%201%20-%20Customer%20profile%20sync/[Customer profile sync from SAP^] use case. +You must complete the following instructions before deploying the https://anypoint.mulesoft.com/exchange/org.mule.examples/mulesoft-accelerator-for-retail/minor/{retail-version}/pages/Use%20case%201%20-%20Customer%20profile%20sync/[Customer profile sync from SAP^] use case. == BAPI custom objects @@ -61,7 +61,7 @@ You must create the following ABAP objects in order to use this custom BAPI, whi | Object | How to create | `Z_MASTER_ID` -| image:https://www.mulesoft.com/ext/solutions/draft/images/sfc-retail-com-bapi_01.png[sfc-retail-com-bapi_01.png,599] +| image:https://www.mulesoft.com/ext/solutions/images/sfc-retail-com-bapi_01.png[sfc-retail-com-bapi_01.png,599] |=== [[creating-structures]] @@ -72,19 +72,19 @@ You must create the following ABAP objects in order to use this custom BAPI, whi | Object | How to create | `ZSTR_PERSON` -| image:https://www.mulesoft.com/ext/solutions/draft/images/retail-2.2-bapi-01.1.png[retail-2.2-bapi-01.1.png,599] +| image:https://www.mulesoft.com/ext/solutions/images/retail-2.2-bapi-01.1.png[retail-2.2-bapi-01.1.png,599] | `ZSTR_ORGANIZATION` -| image:https://www.mulesoft.com/ext/solutions/draft/images/retail-2.2-bapi-01.2.png[retail-2.2-bapi-01.2.png,599] +| image:https://www.mulesoft.com/ext/solutions/images/retail-2.2-bapi-01.2.png[retail-2.2-bapi-01.2.png,599] | `ZSTR_GROUP` -| image:https://www.mulesoft.com/ext/solutions/draft/images/retail-2.2-bapi-01.3.png[retail-2.2-bapi-01.3.png,599] +| image:https://www.mulesoft.com/ext/solutions/images/retail-2.2-bapi-01.3.png[retail-2.2-bapi-01.3.png,599] | `ZES_CUSTOMER` -| image:https://www.mulesoft.com/ext/solutions/draft/images/retail-2.2-bapi-01.4.png[retail-2.2-bapi-01.4.png,599] +| image:https://www.mulesoft.com/ext/solutions/images/retail-2.2-bapi-01.4.png[retail-2.2-bapi-01.4.png,599] | `ZES_CONTROLDATA` -| image:https://www.mulesoft.com/ext/solutions/draft/images/retail-2.2-bapi-01.5.png[retail-2.2-bapi-01.5.png,599] +| image:https://www.mulesoft.com/ext/solutions/images/retail-2.2-bapi-01.5.png[retail-2.2-bapi-01.5.png,599] |=== [[creating-table-types]] @@ -95,7 +95,7 @@ You must create the following ABAP objects in order to use this custom BAPI, whi | Object | How to create | `ZTY_CUSTOMER` -| image:https://www.mulesoft.com/ext/solutions/draft/images/sfc-retail-com-bapi_05.png[sfc-retail-com-bapi_05.png,599] +| image:https://www.mulesoft.com/ext/solutions/images/sfc-retail-com-bapi_05.png[sfc-retail-com-bapi_05.png,599] |=== [[creating-transparent-tables]] @@ -106,7 +106,7 @@ You must create the following ABAP objects in order to use this custom BAPI, whi | Object | How to create | `ZTT_CUSTOMER` -| image:https://www.mulesoft.com/ext/solutions/draft/images/retail-2.2-bapi-05.1.png[retail-2.2-bapi-05.1.png,599] +| image:https://www.mulesoft.com/ext/solutions/images/retail-2.2-bapi-05.1.png[retail-2.2-bapi-05.1.png,599] |=== {blank} @@ -123,91 +123,91 @@ You must create the following ABAP objects in order to use this custom BAPI, whi . Create the function group "ZFG_CUSTOMER_V3". . Create the function module "ZBAPI_CUSTOMER_V3", using "Remote-enable module" as processing type: + -image:https://www.mulesoft.com/ext/solutions/draft/images/sfc-retail-com-bapi_06.png[sfc-retail-com-bapi_06.png,599] +image:https://www.mulesoft.com/ext/solutions/images/sfc-retail-com-bapi_06.png[sfc-retail-com-bapi_06.png,599] . Complete the import parameters with the following: + -image:https://www.mulesoft.com/ext/solutions/draft/images/sfc-retail-com-bapi_07.png[sfc-retail-com-bapi_07.png,599] +image:https://www.mulesoft.com/ext/solutions/images/sfc-retail-com-bapi_07.png[sfc-retail-com-bapi_07.png,599] . Complete the export parameters with the following: + -image:https://www.mulesoft.com/ext/solutions/draft/images/sfc-retail-com-bapi_08.png[sfc-retail-com-bapi_08.png,599] +image:https://www.mulesoft.com/ext/solutions/images/sfc-retail-com-bapi_08.png[sfc-retail-com-bapi_08.png,599] . Copy and paste the code from "ZBAPI_CUSTOMER_V3.txt". . Create the function module "ZBAPI_CUSTOMER_CREATE_V3": + -image:https://www.mulesoft.com/ext/solutions/draft/images/sfc-retail-com-bapi_09.png[sfc-retail-com-bapi_09.png,399] +image:https://www.mulesoft.com/ext/solutions/images/sfc-retail-com-bapi_09.png[sfc-retail-com-bapi_09.png,399] . Complete the import parameters with the following: + -image:https://www.mulesoft.com/ext/solutions/draft/images/retail-2.2-bapi-09.1.png[retail-2.2-bapi-09.1.png,599] +image:https://www.mulesoft.com/ext/solutions/images/retail-2.2-bapi-09.1.png[retail-2.2-bapi-09.1.png,599] . Complete the export parameters with the following: + -image:https://www.mulesoft.com/ext/solutions/draft/images/sfc-retail-com-bapi_11.png[sfc-retail-com-bapi_11.png,599] +image:https://www.mulesoft.com/ext/solutions/images/sfc-retail-com-bapi_11.png[sfc-retail-com-bapi_11.png,599] . Copy and paste the code from "ZBAPI_CUSTOMER_CREATE_V3.txt". . Create the function module "ZBAPI_CUSTOMER_CUSTOM_FLDS_V3": + -image:https://www.mulesoft.com/ext/solutions/draft/images/sfc-retail-com-bapi_15.png[sfc-retail-com-bapi_15.png,599] +image:https://www.mulesoft.com/ext/solutions/images/sfc-retail-com-bapi_15.png[sfc-retail-com-bapi_15.png,599] . Complete the import parameters with the following: + -image:https://www.mulesoft.com/ext/solutions/draft/images/retail-2.2-bapi-15.1.png[retail-2.2-bapi-15.1.png,399] +image:https://www.mulesoft.com/ext/solutions/images/retail-2.2-bapi-15.1.png[retail-2.2-bapi-15.1.png,399] . Copy and paste the code from "ZBAPI_CUSTOMER_CUSTOM_FIELDS_V3.txt". . Create the function module "ZBAPI_CUSTOMER_UPDATE_V3": + -image:https://www.mulesoft.com/ext/solutions/draft/images/sfc-retail-com-bapi_12.png[sfc-retail-com-bapi_12.png,599] +image:https://www.mulesoft.com/ext/solutions/images/sfc-retail-com-bapi_12.png[sfc-retail-com-bapi_12.png,599] . Complete the import parameters with the following: + -image:https://www.mulesoft.com/ext/solutions/draft/images/retail-2.2-bapi-12.1.png[retail-2.2-bapi-12.1.png,599] +image:https://www.mulesoft.com/ext/solutions/images/retail-2.2-bapi-12.1.png[retail-2.2-bapi-12.1.png,599] . Complete the export parameters with the following: + -image:https://www.mulesoft.com/ext/solutions/draft/images/retail-2.2-bapi-12.2.png[retail-2.2-bapi-12.2.png,599] +image:https://www.mulesoft.com/ext/solutions/images/retail-2.2-bapi-12.2.png[retail-2.2-bapi-12.2.png,599] . Copy and paste the code from "ZBAPI_CUSTOMER_UPDATE_V3.txt". . Create the function module "ZBAPI_QUERY_V3", using "Remote-enable module" as processing type: + -image:https://www.mulesoft.com/ext/solutions/draft/images/sfc-retail-com-bapi_36.png[sfc-retail-com-bapi_36.png,599] +image:https://www.mulesoft.com/ext/solutions/images/sfc-retail-com-bapi_36.png[sfc-retail-com-bapi_36.png,599] . Complete the import parameters with the following: + -image:https://www.mulesoft.com/ext/solutions/draft/images/retail-2.2-bapi-36.1.png[retail-2.2-bapi-36.1.png,399] +image:https://www.mulesoft.com/ext/solutions/images/retail-2.2-bapi-36.1.png[retail-2.2-bapi-36.1.png,399] . Complete the export parameters with the following: + -image:https://www.mulesoft.com/ext/solutions/draft/images/sfc-retail-com-bapi_22.png[sfc-retail-com-bapi_22.png,399] +image:https://www.mulesoft.com/ext/solutions/images/sfc-retail-com-bapi_22.png[sfc-retail-com-bapi_22.png,399] . Copy and paste the code from "ZBAPI_QUERY_V3.txt". . Create the function module "ZBAPI_CONTROL_DATA_V3": + -image:https://www.mulesoft.com/ext/solutions/draft/images/sfc-retail-com-bapi_21.png[sfc-retail-com-bapi_21.png,599] +image:https://www.mulesoft.com/ext/solutions/images/sfc-retail-com-bapi_21.png[sfc-retail-com-bapi_21.png,599] . Complete the import parameters with the following: + -image:https://www.mulesoft.com/ext/solutions/draft/images/sfc-retail-com-bapi_24.png[sfc-retail-com-bapi_24.png,599] +image:https://www.mulesoft.com/ext/solutions/images/sfc-retail-com-bapi_24.png[sfc-retail-com-bapi_24.png,599] . Complete the export parameters with the following: + -image:https://www.mulesoft.com/ext/solutions/draft/images/sfc-retail-com-bapi_19.png[sfc-retail-com-bapi_19.png,599] +image:https://www.mulesoft.com/ext/solutions/images/sfc-retail-com-bapi_19.png[sfc-retail-com-bapi_19.png,599] . Copy the source code from "ZBAPI_CONTROL_DATA_V3.txt". . Activate the entire function group by right-clicking on it in the tree and then selecting "Activate": + -image:https://www.mulesoft.com/ext/solutions/draft/images/sfc-retail-com-bapi_35.png[sfc-retail-com-bapi_35.png,301] +image:https://www.mulesoft.com/ext/solutions/images/sfc-retail-com-bapi_35.png[sfc-retail-com-bapi_35.png,301] . Create the function group "ZFG_CUSTOMER2". . Create the function module "ZBAPI_ADDR_QUERY", using "Remote-enable module" as processing type: + -image:https://www.mulesoft.com/ext/solutions/draft/images/sfc-retail-com-bapi_17.png[sfc-retail-com-bapi_17.png,599] +image:https://www.mulesoft.com/ext/solutions/images/sfc-retail-com-bapi_17.png[sfc-retail-com-bapi_17.png,599] . Complete the import parameters with the following: + -image:https://www.mulesoft.com/ext/solutions/draft/images/sfc-retail-com-bapi_20.png[sfc-retail-com-bapi_20.png,599] +image:https://www.mulesoft.com/ext/solutions/images/sfc-retail-com-bapi_20.png[sfc-retail-com-bapi_20.png,599] . Complete the export parameters with the following: + -image:https://www.mulesoft.com/ext/solutions/draft/images/sfc-retail-com-bapi_22.png[sfc-retail-com-bapi_22.png,399] +image:https://www.mulesoft.com/ext/solutions/images/sfc-retail-com-bapi_22.png[sfc-retail-com-bapi_22.png,399] . Copy and paste the code from "ZBAPI_ADDR_QUERY.txt". . Create the function module "ZBAPI_CONTROL_DATA" using the import parameters as follows: + -image:https://www.mulesoft.com/ext/solutions/draft/images/retail-2.2-bapi-22.1.png[retail-2.2-bapi-22.1.png,599] +image:https://www.mulesoft.com/ext/solutions/images/retail-2.2-bapi-22.1.png[retail-2.2-bapi-22.1.png,599] . Use the export parameters as in the following: + -image:https://www.mulesoft.com/ext/solutions/draft/images/retail-2.2-bapi-22.2.png[retail-2.2-bapi-22.2.png,599] +image:https://www.mulesoft.com/ext/solutions/images/retail-2.2-bapi-22.2.png[retail-2.2-bapi-22.2.png,599] . Copy the source code from "ZBAPI_CONTROL_DATA.txt". . Activate the entire function group by right-clicking on it in the tree and selecting 'Activate': + -image:https://www.mulesoft.com/ext/solutions/draft/images/retail-2.2-bapi-22.3.png[retail-2.2-bapi-22.3.png,301] +image:https://www.mulesoft.com/ext/solutions/images/retail-2.2-bapi-22.3.png[retail-2.2-bapi-22.3.png,301] . Complete the following: . Create a customer group ZSME (*Logistics - General\->Business Partner\->Customer\->Control\->Define and Assign Customer Number Ranges*) . Create a partner group ZSME (*Cross-Application Components\->SAP Business Partner\->Business Partner\->Basic Settings\->Number Ranges and Settings*) from the transaction SPRO . Synchronize them from the same transaction (*Cross-Application Components\->Master Data Synchronization\->Customer/Vendor Integration\->Business Partner Settings\->Settings for Customer Integration\->Assign Keys\->Define Number Assignment for Direction BP to Customer*) + -image:https://www.mulesoft.com/ext/solutions/draft/images/retail-2.2-bapi-22.4.png[retail-2.2-bapi-22.4.png,599] +image:https://www.mulesoft.com/ext/solutions/images/retail-2.2-bapi-22.4.png[retail-2.2-bapi-22.4.png,599] ==== *More ZBAPI modules* @@ -222,52 +222,52 @@ To create ABAP custom objects, groups, and modules: . Create the same dictionary objects created for the BAPI `ZBAPI_CUSTOMER` using the following structure/table type: + -image:https://www.mulesoft.com/ext/solutions/draft/images/retail-2.2-bapi-51.png[retail-2.2-bapi-51.png,599] -image:https://www.mulesoft.com/ext/solutions/draft/images/retail-2.2-bapi-52.png[retail-2.2-bapi-52.png,599] +image:https://www.mulesoft.com/ext/solutions/images/retail-2.2-bapi-51.png[retail-2.2-bapi-51.png,599] +image:https://www.mulesoft.com/ext/solutions/images/retail-2.2-bapi-52.png[retail-2.2-bapi-52.png,599] . Create the function group `ZFG_CUSTOMER2`. . Create the function module `ZBAPI_ADDR_QUERY` using 'Remote-enable module' as the processing type: + -image:https://www.mulesoft.com/ext/solutions/draft/images/retail-2.2-bapi-53.png[retail-2.2-bapi-53.png,599] +image:https://www.mulesoft.com/ext/solutions/images/retail-2.2-bapi-53.png[retail-2.2-bapi-53.png,599] . Complete the import parameters with the following: + -image:https://www.mulesoft.com/ext/solutions/draft/images/retail-2.2-bapi-54.png[retail-2.2-bapi-54.png,599] +image:https://www.mulesoft.com/ext/solutions/images/retail-2.2-bapi-54.png[retail-2.2-bapi-54.png,599] . Complete the export parameters with the following: + -image:https://www.mulesoft.com/ext/solutions/draft/images/retail-2.2-bapi-55.png[retail-2.2-bapi-55.png,399] +image:https://www.mulesoft.com/ext/solutions/images/retail-2.2-bapi-55.png[retail-2.2-bapi-55.png,399] . Copy and paste the code from 'ZBAPI_ADDR_QUERY.txt'. . Create the function module `ZBAPI_ADDR_SAP` using 'Remote-enable module' as the processing type: + -image:https://www.mulesoft.com/ext/solutions/draft/images/retail-2.2-bapi-56.png[retail-2.2-bapi-56.png,599] +image:https://www.mulesoft.com/ext/solutions/images/retail-2.2-bapi-56.png[retail-2.2-bapi-56.png,599] . Complete the import parameters with the following: + -image:https://www.mulesoft.com/ext/solutions/draft/images/retail-2.2-bapi-57.png[retail-2.2-bapi-57.png,599] +image:https://www.mulesoft.com/ext/solutions/images/retail-2.2-bapi-57.png[retail-2.2-bapi-57.png,599] . Complete the export parameters with the following: + -image:https://www.mulesoft.com/ext/solutions/draft/images/retail-2.2-bapi-58.png[retail-2.2-bapi-58.png,599] +image:https://www.mulesoft.com/ext/solutions/images/retail-2.2-bapi-58.png[retail-2.2-bapi-58.png,599] . Copy and paste the code from 'ZBAPI_QUERY_SAP.txt'. . Create the function module `ZBAPI_CUST_QUERY` using 'Remote-enable module' as the processing type: + -image:https://www.mulesoft.com/ext/solutions/draft/images/retail-2.2-bapi-59.png[retail-2.2-bapi-59.png,399] +image:https://www.mulesoft.com/ext/solutions/images/retail-2.2-bapi-59.png[retail-2.2-bapi-59.png,399] . Complete the import parameters with the following: + -image:https://www.mulesoft.com/ext/solutions/draft/images/retail-2.2-bapi-60.png[retail-2.2-bapi-60.png,599] +image:https://www.mulesoft.com/ext/solutions/images/retail-2.2-bapi-60.png[retail-2.2-bapi-60.png,599] . Complete the export parameters with the following: + -image:https://www.mulesoft.com/ext/solutions/draft/images/retail-2.2-bapi-61.png[retail-2.2-bapi-61.png,599] +image:https://www.mulesoft.com/ext/solutions/images/retail-2.2-bapi-61.png[retail-2.2-bapi-61.png,599] . Copy and paste the code from 'ZBAPI_CUST_QUERY.txt'. . Create the function module `ZBAPI_CUSTOMER_CD` using 'Remote-enable module' as the processing type: + -image:https://www.mulesoft.com/ext/solutions/draft/images/retail-2.2-bapi-62.png[retail-2.2-bapi-62.png,399] +image:https://www.mulesoft.com/ext/solutions/images/retail-2.2-bapi-62.png[retail-2.2-bapi-62.png,399] . Complete the import parameters with the following: + -image:https://www.mulesoft.com/ext/solutions/draft/images/retail-2.2-bapi-63.png[retail-2.2-bapi-63.png,599] +image:https://www.mulesoft.com/ext/solutions/images/retail-2.2-bapi-63.png[retail-2.2-bapi-63.png,599] . Complete the export parameters with the following: + -image:https://www.mulesoft.com/ext/solutions/draft/images/retail-2.2-bapi-64.png[retail-2.2-bapi-64.png,599] +image:https://www.mulesoft.com/ext/solutions/images/retail-2.2-bapi-64.png[retail-2.2-bapi-64.png,599] . Copy and paste the code from 'ZBAPI_CUSTOMER_CD.txt'. . Activate the entire function group by right-clicking on it in the tree and selecting 'Activate': + -image:https://www.mulesoft.com/ext/solutions/draft/images/retail-2.2-bapi-65.png[retail-2.2-bapi-65.png,301] +image:https://www.mulesoft.com/ext/solutions/images/retail-2.2-bapi-65.png[retail-2.2-bapi-65.png,301] == See Also diff --git a/retail/3.0/modules/ROOT/pages/sap-s4hana-setup-guide.adoc b/retail/3.0/modules/ROOT/pages/sap-s4hana-setup-guide.adoc index b4b27a925..e6295f815 100644 --- a/retail/3.0/modules/ROOT/pages/sap-s4hana-setup-guide.adoc +++ b/retail/3.0/modules/ROOT/pages/sap-s4hana-setup-guide.adoc @@ -10,24 +10,24 @@ To make the necessary configurations in S/4HANA: . Create a *Communication System* in the corresponding Fiori app. This communication system represents the external system that will consume the S/4HANA Cloud SOAP service. In this example, it's named `COM_0009_SOAP_OUT`: + + -image:https://www.mulesoft.com/ext/solutions/draft/images/retail-sap-s4hana-setup-guide-01.png[retail-sap-s4hana-setup-guide-01.png,799] +image:https://www.mulesoft.com/ext/solutions/images/retail-sap-s4hana-setup-guide-01.png[retail-sap-s4hana-setup-guide-01.png,799] . For the 'Business System' name, use the same name of the System ID. . In the 'Host Name' field, enter the hostname of the Mule application deployed on Cloudhub (if you don't have it yet, you can enter a mock URL and then modify it later): + + -image:https://www.mulesoft.com/ext/solutions/draft/images/retail-sap-s4hana-setup-guide-02.png[retail-sap-s4hana-setup-guide-02.png,799] + +image:https://www.mulesoft.com/ext/solutions/images/retail-sap-s4hana-setup-guide-02.png[retail-sap-s4hana-setup-guide-02.png,799] + + . Create a user that will be used to connect to the Cloud Hub app for sending product information in the outbound scenario (this is necessary even though the Mule application does not validate the user; we used any user for outbound): + + -image:https://www.mulesoft.com/ext/solutions/draft/images/retail-sap-s4hana-setup-guide-03.png[retail-sap-s4hana-setup-guide-03.png,799] + +image:https://www.mulesoft.com/ext/solutions/images/retail-sap-s4hana-setup-guide-03.png[retail-sap-s4hana-setup-guide-03.png,799] + + . Use the *Communication Arrangement* Fiori app to create a new Communication Arrangement: + + -image:https://www.mulesoft.com/ext/solutions/draft/images/retail-sap-s4hana-setup-guide-04.png[retail-sap-s4hana-setup-guide-04.png,799] + +image:https://www.mulesoft.com/ext/solutions/images/retail-sap-s4hana-setup-guide-04.png[retail-sap-s4hana-setup-guide-04.png,799] + + . Create a new *Communication Arrangement*, select the communication scenario "SAP_COM_0009", and then define a specific name for the arrangement, "SAP_COM_0009_SOAP". . In the *Communication System* field, select the Communication System created in the previous step: + + -image:https://www.mulesoft.com/ext/solutions/draft/images/retail-sap-s4hana-setup-guide-05.png[retail-sap-s4hana-setup-guide-05.png,799] + +image:https://www.mulesoft.com/ext/solutions/images/retail-sap-s4hana-setup-guide-05.png[retail-sap-s4hana-setup-guide-05.png,799] + + . For outbound communication, select the previously-created user and configure the *Product Master - Replicate from SAP S/4HANA Cloud to Client* and include the following settings. Make sure to note the Path (`/sap/bc/srt/scs/sap/productmdmbulkreplicaterequest`) because we will use this path to configure the Mule application SOAP endpoint: ** Set the *Service status* to *Active* @@ -35,11 +35,11 @@ image:https://www.mulesoft.com/ext/solutions/draft/images/retail-sap-s4hana-setu ** Replication model = `I (Initial)` ** The Output Mode = `D (Direct)` + + -image:https://www.mulesoft.com/ext/solutions/draft/images/retail-sap-s4hana-setup-guide-06.png[retail-sap-s4hana-setup-guide-06.png,799] + +image:https://www.mulesoft.com/ext/solutions/images/retail-sap-s4hana-setup-guide-06.png[retail-sap-s4hana-setup-guide-06.png,799] + + -image:https://www.mulesoft.com/ext/solutions/draft/images/retail-sap-s4hana-setup-guide-07.png[retail-sap-s4hana-setup-guide-07.png,799] + +image:https://www.mulesoft.com/ext/solutions/images/retail-sap-s4hana-setup-guide-07.png[retail-sap-s4hana-setup-guide-07.png,799] + + -image:https://www.mulesoft.com/ext/solutions/draft/images/retail-sap-s4hana-setup-guide-08.png[retail-sap-s4hana-setup-guide-08.png,799] + +image:https://www.mulesoft.com/ext/solutions/images/retail-sap-s4hana-setup-guide-08.png[retail-sap-s4hana-setup-guide-08.png,799] + + . Save it. All configurations at S/4HANA Cloud side are finished and you will be able to download the WSDL that contains the metadata to import into the S/4HANA Cloud SOAP Connector into the Mule application. @@ -49,38 +49,38 @@ The following example describes how to create a Mule application using the Outbo . Create a Mule project and add the appropriate connector from Exchange to the Mule Palette: + + -image:https://www.mulesoft.com/ext/solutions/draft/images/retail-sap-s4hana-setup-guide-09.png[retail-sap-s4hana-setup-guide-09.png,799] + +image:https://www.mulesoft.com/ext/solutions/images/retail-sap-s4hana-setup-guide-09.png[retail-sap-s4hana-setup-guide-09.png,799] + + . Add and configure the *Outbound Message Listener* to the canvas: + + -image:https://www.mulesoft.com/ext/solutions/draft/images/retail-sap-s4hana-setup-guide-10.png[retail-sap-s4hana-setup-guide-10.png,799] + +image:https://www.mulesoft.com/ext/solutions/images/retail-sap-s4hana-setup-guide-10.png[retail-sap-s4hana-setup-guide-10.png,799] + + . Add the corresponding WSDL path to the WSDL you downloaded from S/4HANA Cloud and create the HTTP listener configuration: + + -image:https://www.mulesoft.com/ext/solutions/draft/images/retail-sap-s4hana-setup-guide-11.png[retail-sap-s4hana-setup-guide-11.png,799] + +image:https://www.mulesoft.com/ext/solutions/images/retail-sap-s4hana-setup-guide-11.png[retail-sap-s4hana-setup-guide-11.png,799] + + -image:https://www.mulesoft.com/ext/solutions/draft/images/retail-sap-s4hana-setup-guide-12.png[retail-sap-s4hana-setup-guide-12.png,799] + +image:https://www.mulesoft.com/ext/solutions/images/retail-sap-s4hana-setup-guide-12.png[retail-sap-s4hana-setup-guide-12.png,799] + + _Note: we are using no authentication on the Mule Application, so we used the Insecure option for the Trust Store Configuration. In the Keystore configuration, we used a test Keystore, which is mandatory for HTTPS communication:_ + + -image:https://www.mulesoft.com/ext/solutions/draft/images/retail-sap-s4hana-setup-guide-13.png[retail-sap-s4hana-setup-guide-13.png,799] + +image:https://www.mulesoft.com/ext/solutions/images/retail-sap-s4hana-setup-guide-13.png[retail-sap-s4hana-setup-guide-13.png,799] + + . Select the Message type that the connector expects to receive from SAP (the connector reads the metadata from the WSDL we configured): + + -image:https://www.mulesoft.com/ext/solutions/draft/images/retail-sap-s4hana-setup-guide-14.png[retail-sap-s4hana-setup-guide-14.png,799] + +image:https://www.mulesoft.com/ext/solutions/images/retail-sap-s4hana-setup-guide-14.png[retail-sap-s4hana-setup-guide-14.png,799] + + . On the Responses tab, use the status Code "202" and the Reason-Phrase "Accepted" because we want to send the same status that S/4HANA Cloud will send if the service invocation results OK. No payload will be returned as a response - just the `Status` code and `Reason-phrase`: + + -image:https://www.mulesoft.com/ext/solutions/draft/images/retail-sap-s4hana-setup-guide-15.png[retail-sap-s4hana-setup-guide-15.png,799] + +image:https://www.mulesoft.com/ext/solutions/images/retail-sap-s4hana-setup-guide-15.png[retail-sap-s4hana-setup-guide-15.png,799] + + . Use a *Logger* component to log the inbound XML payload: + + -image:https://www.mulesoft.com/ext/solutions/draft/images/retail-sap-s4hana-setup-guide-16.png[retail-sap-s4hana-setup-guide-16.png,799] + +image:https://www.mulesoft.com/ext/solutions/images/retail-sap-s4hana-setup-guide-16.png[retail-sap-s4hana-setup-guide-16.png,799] + + _The Mule flow should look like the following:_ + + -image:https://www.mulesoft.com/ext/solutions/draft/images/retail-sap-s4hana-setup-guide-17.png[retail-sap-s4hana-setup-guide-17.png,399] + +image:https://www.mulesoft.com/ext/solutions/images/retail-sap-s4hana-setup-guide-17.png[retail-sap-s4hana-setup-guide-17.png,399] + + . Deploy the application to Cloudhub. You're now ready to test the scenario. @@ -90,35 +90,35 @@ To test the scenario: . Create the following. You only need to create a material in the corresponding Fiori app of S/4HANA Cloud: + + -image:https://www.mulesoft.com/ext/solutions/draft/images/retail-sap-s4hana-setup-guide-18.png[retail-sap-s4hana-setup-guide-18.png,599] + +image:https://www.mulesoft.com/ext/solutions/images/retail-sap-s4hana-setup-guide-18.png[retail-sap-s4hana-setup-guide-18.png,599] + + -image:https://www.mulesoft.com/ext/solutions/draft/images/retail-sap-s4hana-setup-guide-19.png[retail-sap-s4hana-setup-guide-19.png,799] + +image:https://www.mulesoft.com/ext/solutions/images/retail-sap-s4hana-setup-guide-19.png[retail-sap-s4hana-setup-guide-19.png,799] + + -image:https://www.mulesoft.com/ext/solutions/draft/images/retail-sap-s4hana-setup-guide-20.png[retail-sap-s4hana-setup-guide-20.png,799] + +image:https://www.mulesoft.com/ext/solutions/images/retail-sap-s4hana-setup-guide-20.png[retail-sap-s4hana-setup-guide-20.png,799] + + -image:https://www.mulesoft.com/ext/solutions/draft/images/retail-sap-s4hana-setup-guide-21.png[retail-sap-s4hana-setup-guide-21.png,799] + +image:https://www.mulesoft.com/ext/solutions/images/retail-sap-s4hana-setup-guide-21.png[retail-sap-s4hana-setup-guide-21.png,799] + + _After you save the new material, you should see the following confirmation in S/4HANA Cloud:_ + + -image:https://www.mulesoft.com/ext/solutions/draft/images/retail-sap-s4hana-setup-guide-22.png[retail-sap-s4hana-setup-guide-22.png,399] + +image:https://www.mulesoft.com/ext/solutions/images/retail-sap-s4hana-setup-guide-22.png[retail-sap-s4hana-setup-guide-22.png,399] + + _The following shows the XML message received at the Mule application at the Runtime Manager on Cloudhub:_ + + -image:https://www.mulesoft.com/ext/solutions/draft/images/retail-sap-s4hana-setup-guide-23.png[retail-sap-s4hana-setup-guide-23.png,799] + +image:https://www.mulesoft.com/ext/solutions/images/retail-sap-s4hana-setup-guide-23.png[retail-sap-s4hana-setup-guide-23.png,799] + + . See the sent message in the Message Dashboard Fiori Application: + + -image:https://www.mulesoft.com/ext/solutions/draft/images/retail-sap-s4hana-setup-guide-24.png[retail-sap-s4hana-setup-guide-24.png,799] + +image:https://www.mulesoft.com/ext/solutions/images/retail-sap-s4hana-setup-guide-24.png[retail-sap-s4hana-setup-guide-24.png,799] + + . Select the date: + + -image:https://www.mulesoft.com/ext/solutions/draft/images/retail-sap-s4hana-setup-guide-25.png[retail-sap-s4hana-setup-guide-25.png,399] + +image:https://www.mulesoft.com/ext/solutions/images/retail-sap-s4hana-setup-guide-25.png[retail-sap-s4hana-setup-guide-25.png,399] + + . Search under *CMD:Product Integration - /CMDPR → Product Replication to Client via Service - PRDREQ_OUT/00001 namespace*: + + -image:https://www.mulesoft.com/ext/solutions/draft/images/retail-sap-s4hana-setup-guide-26.png[retail-sap-s4hana-setup-guide-26.png,799] + +image:https://www.mulesoft.com/ext/solutions/images/retail-sap-s4hana-setup-guide-26.png[retail-sap-s4hana-setup-guide-26.png,799] + + -image:https://www.mulesoft.com/ext/solutions/draft/images/retail-sap-s4hana-setup-guide-27.png[retail-sap-s4hana-setup-guide-27.png,799] +image:https://www.mulesoft.com/ext/solutions/images/retail-sap-s4hana-setup-guide-27.png[retail-sap-s4hana-setup-guide-27.png,799] == S/4HANA customization guide diff --git a/retail/3.0/modules/ROOT/pages/sfdc-customization-guide.adoc b/retail/3.0/modules/ROOT/pages/sfdc-customization-guide.adoc index 1eb487e32..44bf6eb9c 100644 --- a/retail/3.0/modules/ROOT/pages/sfdc-customization-guide.adoc +++ b/retail/3.0/modules/ROOT/pages/sfdc-customization-guide.adoc @@ -36,7 +36,7 @@ The following objects must be created === Create a Custom Object via Apex Script -An Apex class called `CustomObjectUtility` and `MetadataService` are used to create a custom object programmatically. The source can be found on https://anypoint.mulesoft.com/exchange/997d5e99-287f-4f68-bc95-ed435d7c5797/accelerator-common-resources-src[Common Resources project] and https://github.com/financialforcedev/apex-mdapi/blob/master/apex-mdapi/src/classes/MetadataService.cls[MetadataService] respectively. Download the project and follow the steps below. +An Apex class called `CustomObjectUtility` and `MetadataService` are used to create a custom object programmatically. The source can be found on https://anypoint.mulesoft.com/exchange/org.mule.examples/accelerator-common-resources-src[Common Resources project] and https://github.com/financialforcedev/apex-mdapi/blob/master/apex-mdapi/src/classes/MetadataService.cls[MetadataService] respectively. Download the project and follow the steps below. 1. Click on the Salesforce Setup icon and select `Developer Console` to open a new console window. 1. Go to `File > New > Apex class` and create a new class named `CustomObjectUtility`. diff --git a/retail/3.0/modules/ROOT/pages/sfdc-data-cloud-setup-guide.adoc b/retail/3.0/modules/ROOT/pages/sfdc-data-cloud-setup-guide.adoc index e67313693..fc0ae1e29 100644 --- a/retail/3.0/modules/ROOT/pages/sfdc-data-cloud-setup-guide.adoc +++ b/retail/3.0/modules/ROOT/pages/sfdc-data-cloud-setup-guide.adoc @@ -8,7 +8,7 @@ The following provides guidance on Salesforce Data Cloud setup required for the . Click the Setup icon and then `Data Cloud Setup`. If you don't see this option, either refresh your page or log out and back in with your admin user credentials. . Click `Get Started`. Setup can take a few minutes. Your Data Cloud instance is considered as successfully set up if you see a green tick mark for all the steps. If not, correct the issue and finish the setup. -image::https://www.mulesoft.com/ext/solutions/draft/images/rcg-cdp-setup-cdp-provisioning.png[rcg-cdp-setup-cdp-provisioning.png,599] +image::https://www.mulesoft.com/ext/solutions/images/rcg-cdp-setup-cdp-provisioning.png[rcg-cdp-setup-cdp-provisioning.png,599] == Connect Data @@ -212,7 +212,7 @@ Anypoint Connector for Salesforce CDP (Data Cloud Connector) provides customers This connector works with the Data Cloud Bulk and Streaming API, depending on the operation you configure. Each API call uses a request/response pattern over an HTTPS connection. All required request headers, error handling, and HTTPS connection configurations are built into the connector. -Refer to this https://dev-docs-internal.kqa.msap.io/beta-accelerators/salesforce-cdp-connector/1.0/[link] for details on configuration and operations for Data Cloud Connector. +Refer to this https://docs.mulesoft.com/salesforce-cdp-connector/1.0/[link] for details on configuration and operations for Data Cloud Connector. For the "Personalization with CDP" use case, refer CDP System API specification and implementation template. @@ -242,11 +242,11 @@ For the "Personalization with CDP" use case, we mapped to Custom DMO for our Mul ==== Data Mapping -image::https://www.mulesoft.com/ext/solutions/draft/images/rcg-cdp-setup-custom-dmo-webengagement.png[rcg-cdp-setup-custom-dmo-webengagement.png,599] +image::https://www.mulesoft.com/ext/solutions/images/rcg-cdp-setup-custom-dmo-webengagement.png[rcg-cdp-setup-custom-dmo-webengagement.png,599] ==== Data Relationships -image::https://www.mulesoft.com/ext/solutions/draft/images/rcg-cdp-setup-webengagement-data-relationships.png[rcg-cdp-setup-webengagement-data-relationships.png,599] +image::https://www.mulesoft.com/ext/solutions/images/rcg-cdp-setup-webengagement-data-relationships.png[rcg-cdp-setup-webengagement-data-relationships.png,599] == Identity Resolution @@ -261,9 +261,9 @@ Access Identity Resolution from Data Cloud after mapping entities to the CIM. En For the `Personalization with CDP` use case, we are leveraging the Fuzzy Name and Normalized Email Match Rule; leveraging Fuzzy First Name, Exact Last Name, and Normalized Email Address. -image:https://www.mulesoft.com/ext/solutions/draft/images/rcg-cdp-setup-identity-match-rules.png[rcg-cdp-setup-identity-match-rules.png,599] +image:https://www.mulesoft.com/ext/solutions/images/rcg-cdp-setup-identity-match-rules.png[rcg-cdp-setup-identity-match-rules.png,599] -image:https://www.mulesoft.com/ext/solutions/draft/images/rcg-cdp-setup-identity-match-rules-criteria.png[rcg-cdp-setup-identity-match-rules-criteria.png,599] +image:https://www.mulesoft.com/ext/solutions/images/rcg-cdp-setup-identity-match-rules-criteria.png[rcg-cdp-setup-identity-match-rules-criteria.png,599] To create your Identity Resolution Rules, follow the steps below: @@ -303,7 +303,7 @@ Segment On: Segment On defines the target entity (object) used to build your seg For the "Personalization with CDP" use case, we have created a few Segments. All Segments that we have created have been segmented on Unified Individual. For this segment, we wanted to create an audience wherein there were no Web Page Views in the last 365 Days. We grabbed updated Date from our Attribute Library and dragged it to the canvas. And for the operator we selected "Greater Than Last Number of Days" and entered "365" for the number of days. In the *Publish Schedule* field, we select a schedule of every 24 hours. -image::https://www.mulesoft.com/ext/solutions/draft/images/rcg-cdp-setup-segment-nowebpageviews.png[rcg-cdp-setup-segment-nowebpageviews.png,599] +image::https://www.mulesoft.com/ext/solutions/images/rcg-cdp-setup-segment-nowebpageviews.png[rcg-cdp-setup-segment-nowebpageviews.png,599] === Activation Targets @@ -423,7 +423,7 @@ For the "Personalization with CDP" use case, we created Calculated Insights to g Once created, Calculated Insights are available in the Attribute Library. You can also confirm and validate Calculated Insights via Data Explorer. -image::https://www.mulesoft.com/ext/solutions/draft/images/rcg-cdp-setup-calculated-insights.png[rcg-cdp-setup-calculated-insights.png,399] +image::https://www.mulesoft.com/ext/solutions/images/rcg-cdp-setup-calculated-insights.png[rcg-cdp-setup-calculated-insights.png,399] == See Also diff --git a/retail/3.1/modules/ROOT/pages/index.adoc b/retail/3.1/modules/ROOT/pages/index.adoc index d10977f41..3192771ad 100644 --- a/retail/3.1/modules/ROOT/pages/index.adoc +++ b/retail/3.1/modules/ROOT/pages/index.adoc @@ -7,17 +7,17 @@ MuleSoft Accelerator for Retail empowers retail IT teams to unlock data from sys The following use cases are supported by the MuleSoft Accelerator for Retail: -* https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/mulesoft-accelerator-for-retail/minor/{retail-version}/pages/Use%20case%201%20-%20Customer%20profile%20sync/[Customer profile sync^] - The Customer profile sync use case enables retail developers to create a customer 360 view by unlocking customer data from disparate systems. +* https://anypoint.mulesoft.com/exchange/org.mule.examples/mulesoft-accelerator-for-retail/minor/{retail-version}/pages/Use%20case%201%20-%20Customer%20profile%20sync/[Customer profile sync^] - The Customer profile sync use case enables retail developers to create a customer 360 view by unlocking customer data from disparate systems. -* https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/mulesoft-accelerator-for-retail/minor/{retail-version}/pages/Use%20case%202%20-%20Sales%20order%20sync/[Sales order sync^] - The Sales order sync use case enables retail developers to create and update sales orders across relevant applications. +* https://anypoint.mulesoft.com/exchange/org.mule.examples/mulesoft-accelerator-for-retail/minor/{retail-version}/pages/Use%20case%202%20-%20Sales%20order%20sync/[Sales order sync^] - The Sales order sync use case enables retail developers to create and update sales orders across relevant applications. -* https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/mulesoft-accelerator-for-retail/minor/{retail-version}/pages/Use%20case%203%20-%20Product%20sync/[Product sync^] - The Product sync use case enables retail developers to update product details in Salsify across relevant applications. +* https://anypoint.mulesoft.com/exchange/org.mule.examples/mulesoft-accelerator-for-retail/minor/{retail-version}/pages/Use%20case%203%20-%20Product%20sync/[Product sync^] - The Product sync use case enables retail developers to update product details in Salsify across relevant applications. -* https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/mulesoft-accelerator-for-retail/minor/{retail-version}/pages/Use%20case%204%20-%20Real-time%20inventory%20management/[Real-time inventory management^] - The Real-time inventory management use case enables customers to make an informed decision of their online purchase based on real-time inventory of a product in nearby stores. +* https://anypoint.mulesoft.com/exchange/org.mule.examples/mulesoft-accelerator-for-retail/minor/{retail-version}/pages/Use%20case%204%20-%20Real-time%20inventory%20management/[Real-time inventory management^] - The Real-time inventory management use case enables customers to make an informed decision of their online purchase based on real-time inventory of a product in nearby stores. -* https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/mulesoft-accelerator-for-retail/minor/{retail-version}/pages/Use%20case%205%20-%20Deliver%20relevancy%20with%20CDP/[Deliver relevancy with CDP^] - The Deliver relevancy with CDP use case enables retail developers to combine customer profile data in a standardized format. +* https://anypoint.mulesoft.com/exchange/org.mule.examples/mulesoft-accelerator-for-retail/minor/{retail-version}/pages/Use%20case%205%20-%20Deliver%20relevancy%20with%20CDP/[Deliver relevancy with CDP^] - The Deliver relevancy with CDP use case enables retail developers to combine customer profile data in a standardized format. -* https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/mulesoft-accelerator-for-retail/minor/{retail-version}/pages/Use%20case%206%20-%20POS%20integration/[POS Integration^] - The Point of Sale (POS) Integration use case enables retail developers to leverage pre-built integrations to connect order and loyalty data from POS systems to Salesforce Loyalty Management and Data Cloud. +* https://anypoint.mulesoft.com/exchange/org.mule.examples/mulesoft-accelerator-for-retail/minor/{retail-version}/pages/Use%20case%206%20-%20POS%20integration/[POS Integration^] - The Point of Sale (POS) Integration use case enables retail developers to leverage pre-built integrations to connect order and loyalty data from POS systems to Salesforce Loyalty Management and Data Cloud. @@ -27,4 +27,4 @@ The following use cases are supported by the MuleSoft Accelerator for Retail: * xref:accelerators-home::getting-started.adoc[Getting Started Guide] * xref:prerequisites.adoc[Prerequisites] * xref:release-notes::accelerators/retail/retail-release-notes.adoc[Release Notes] -* https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/mulesoft-accelerator-for-retail/[MuleSoft Accelerator for Retail on Exchange^] +* https://anypoint.mulesoft.com/exchange/org.mule.examples/mulesoft-accelerator-for-retail/[MuleSoft Accelerator for Retail on Exchange^] diff --git a/retail/3.1/modules/ROOT/pages/rcg-assets.adoc b/retail/3.1/modules/ROOT/pages/rcg-assets.adoc index f1877950c..09fd8d0aa 100644 --- a/retail/3.1/modules/ROOT/pages/rcg-assets.adoc +++ b/retail/3.1/modules/ROOT/pages/rcg-assets.adoc @@ -7,80 +7,80 @@ Accelerator assets include API specifications, implementation templates, custom [cols="40,30,30",width=100%] |=== | B2B Commerce System API -| https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/rcg-b2b-commerce-sys-api-spec/[API Specification^] -| https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/rcg-b2b-commerce-sys-api/[Implementation Template^] +| https://anypoint.mulesoft.com/exchange/org.mule.examples/rcg-b2b-commerce-sys-api-spec/[API Specification^] +| https://anypoint.mulesoft.com/exchange/org.mule.examples/rcg-b2b-commerce-sys-api/[Implementation Template^] | B2C Commerce System API -| https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/rcg-b2c-commerce-sys-api-spec/[API Specification^] -| https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/rcg-b2c-commerce-sys-api[Implementation Template^] +| https://anypoint.mulesoft.com/exchange/org.mule.examples/rcg-b2c-commerce-sys-api-spec/[API Specification^] +| https://anypoint.mulesoft.com/exchange/org.mule.examples/rcg-b2c-commerce-sys-api[Implementation Template^] | B2C Customers System API -| https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/rcg-b2c-customers-sys-api-spec/[API Specification^] -| https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/rcg-b2c-customers-sys-api/[Implementation Template^] +| https://anypoint.mulesoft.com/exchange/org.mule.examples/rcg-b2c-customers-sys-api-spec/[API Specification^] +| https://anypoint.mulesoft.com/exchange/org.mule.examples/rcg-b2c-customers-sys-api/[Implementation Template^] | MDM System API -| https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/rcg-mdm-sys-api-spec/[API Specification^] -| https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/rcg-mdm-sys-api/[Implementation Template^] +| https://anypoint.mulesoft.com/exchange/org.mule.examples/rcg-mdm-sys-api-spec/[API Specification^] +| https://anypoint.mulesoft.com/exchange/org.mule.examples/rcg-mdm-sys-api/[Implementation Template^] | RCG Salsify Products System API -| https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/rcg-salsify-products-sys-api-spec/[API Specification^] -| https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/rcg-salsify-products-sys-api/[Implementation Template^] +| https://anypoint.mulesoft.com/exchange/org.mule.examples/rcg-salsify-products-sys-api-spec/[API Specification^] +| https://anypoint.mulesoft.com/exchange/org.mule.examples/rcg-salsify-products-sys-api/[Implementation Template^] | RCG Azure Cosmos DB System API -| https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/rcg-azure-sys-api-spec/[API Specification^] -| https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/rcg-azure-sys-api/[Implementation Template^] +| https://anypoint.mulesoft.com/exchange/org.mule.examples/rcg-azure-sys-api-spec/[API Specification^] +| https://anypoint.mulesoft.com/exchange/org.mule.examples/rcg-azure-sys-api/[Implementation Template^] | RCG B2C Commerce System API -| https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/rcg-b2c-commerce-sys-api-spec/[API Specification^] -| https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/rcg-b2c-commerce-sys-api/[Implementation Template^] +| https://anypoint.mulesoft.com/exchange/org.mule.examples/rcg-b2c-commerce-sys-api-spec/[API Specification^] +| https://anypoint.mulesoft.com/exchange/org.mule.examples/rcg-b2c-commerce-sys-api/[Implementation Template^] | RCG Marketo System API -| https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/rcg-marketo-system-api-spec/[API Specification^] -| https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/rcg-marketo-system-api/[Implementation Template^] +| https://anypoint.mulesoft.com/exchange/org.mule.examples/rcg-marketo-system-api-spec/[API Specification^] +| https://anypoint.mulesoft.com/exchange/org.mule.examples/rcg-marketo-system-api/[Implementation Template^] | RCG Salesforce Data Cloud System API -| https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/rcg-salesforce-cdp-sys-api-spec/[API Specification^] -| https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/rcg-salesforce-cdp-sys-api/[Implementation Template^] +| https://anypoint.mulesoft.com/exchange/org.mule.examples/rcg-salesforce-cdp-sys-api-spec/[API Specification^] +| https://anypoint.mulesoft.com/exchange/org.mule.examples/rcg-salesforce-cdp-sys-api/[Implementation Template^] | RCG Snowflake System API -| https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/rcg-snowflake-sys-api-spec/[API Specification^] -| https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/rcg-snowflake-sys-api/[Implementation Template^] +| https://anypoint.mulesoft.com/exchange/org.mule.examples/rcg-snowflake-sys-api-spec/[API Specification^] +| https://anypoint.mulesoft.com/exchange/org.mule.examples/rcg-snowflake-sys-api/[Implementation Template^] | Salesforce Customers System API -| https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/rcg-salesforce-customers-sys-api-spec/[API Specification^] -| https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/rcg-salesforce-customers-sys-api/[Implementation Template^] +| https://anypoint.mulesoft.com/exchange/org.mule.examples/rcg-salesforce-customers-sys-api-spec/[API Specification^] +| https://anypoint.mulesoft.com/exchange/org.mule.examples/rcg-salesforce-customers-sys-api/[Implementation Template^] | Salesforce Marketing System API -| https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/rcg-salesforce-marketing-sys-api-spec/[API Specification^] -| https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/rcg-salesforce-marketing-sys-api/[Implementation Template^] +| https://anypoint.mulesoft.com/exchange/org.mule.examples/rcg-salesforce-marketing-sys-api-spec/[API Specification^] +| https://anypoint.mulesoft.com/exchange/org.mule.examples/rcg-salesforce-marketing-sys-api/[Implementation Template^] | Salesforce Orders System API -| https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/rcg-salesforce-orders-sys-api-spec/[API Specification^] -| https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/rcg-salesforce-orders-sys-api/[Implementation Template^] +| https://anypoint.mulesoft.com/exchange/org.mule.examples/rcg-salesforce-orders-sys-api-spec/[API Specification^] +| https://anypoint.mulesoft.com/exchange/org.mule.examples/rcg-salesforce-orders-sys-api/[Implementation Template^] | SAP ECC Customers System API -| https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/rcg-sapecc-customers-sys-api-spec/[API Specification^] -| https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/rcg-sapecc-customers-sys-api/[Implementation Template^] +| https://anypoint.mulesoft.com/exchange/org.mule.examples/rcg-sapecc-customers-sys-api-spec/[API Specification^] +| https://anypoint.mulesoft.com/exchange/org.mule.examples/rcg-sapecc-customers-sys-api/[Implementation Template^] | SAP S/4HANA Customers System API -| https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/rcg-saphana-customers-sys-api-spec/[API Specification^] -| https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/rcg-saphana-customers-sys-api/[Implementation Template^] +| https://anypoint.mulesoft.com/exchange/org.mule.examples/rcg-saphana-customers-sys-api-spec/[API Specification^] +| https://anypoint.mulesoft.com/exchange/org.mule.examples/rcg-saphana-customers-sys-api/[Implementation Template^] | SAP S/4HANA Orders System API -| https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/accelerator-saphana-orders-sys-api/[API Specification^] -| https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/rcg-saphana-orders-sys-api/[Implementation Template^] +| https://anypoint.mulesoft.com/exchange/org.mule.examples/accelerator-saphana-orders-sys-api/[API Specification^] +| https://anypoint.mulesoft.com/exchange/org.mule.examples/rcg-saphana-orders-sys-api/[Implementation Template^] | SAP S/4HANA Product Availability System API -| https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/accelerator-saphana-productavailability-sys-api/[API Specification^] -| https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/accel-saphana-productavailability-sys-api/[Implementation Template^] +| https://anypoint.mulesoft.com/exchange/org.mule.examples/accelerator-saphana-productavailability-sys-api/[API Specification^] +| https://anypoint.mulesoft.com/exchange/org.mule.examples/accel-saphana-productavailability-sys-api/[Implementation Template^] | SAP S/4HANA Products System API -| https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/rcg-saphana-products-sys-api-spec/[API Specification^] -| https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/rcg-saphana-products-sys-api/[Implementation Template^] +| https://anypoint.mulesoft.com/exchange/org.mule.examples/rcg-saphana-products-sys-api-spec/[API Specification^] +| https://anypoint.mulesoft.com/exchange/org.mule.examples/rcg-saphana-products-sys-api/[Implementation Template^] | RCG Loyalty Management Cloud System API -| https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/rcg-loyalty-mgmt-cloud-sys-api-spec/[API Specification^] -| https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/rcg-loyalty-mgmt-cloud-sys-api/[Implementation Template^] +| https://anypoint.mulesoft.com/exchange/org.mule.examples/rcg-loyalty-mgmt-cloud-sys-api-spec/[API Specification^] +| https://anypoint.mulesoft.com/exchange/org.mule.examples/rcg-loyalty-mgmt-cloud-sys-api/[Implementation Template^] |=== == Process APIs @@ -88,40 +88,40 @@ Accelerator assets include API specifications, implementation templates, custom [cols="40,30,30",width=100%] |=== | Accelerator Customers Process API -| https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/accel-customers-prc-api-spec/[API Specification^] -| https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/accel-customers-prc-api/[Implementation Template^] +| https://anypoint.mulesoft.com/exchange/org.mule.examples/accel-customers-prc-api-spec/[API Specification^] +| https://anypoint.mulesoft.com/exchange/org.mule.examples/accel-customers-prc-api/[Implementation Template^] | ERP Customers Process API -| https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/rcg-erp-customers-prc-api-spec/[API Specification^] -| https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/rcg-erp-customers-prc-api/[Implementation Template^] +| https://anypoint.mulesoft.com/exchange/org.mule.examples/rcg-erp-customers-prc-api-spec/[API Specification^] +| https://anypoint.mulesoft.com/exchange/org.mule.examples/rcg-erp-customers-prc-api/[Implementation Template^] | ERP Orders Process API -| https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/rcg-erp-orders-prc-api-spec/[API Specification^] -| https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/rcg-erp-orders-prc-api/[Implementation Template^] +| https://anypoint.mulesoft.com/exchange/org.mule.examples/rcg-erp-orders-prc-api-spec/[API Specification^] +| https://anypoint.mulesoft.com/exchange/org.mule.examples/rcg-erp-orders-prc-api/[Implementation Template^] | Inventory Process API -| https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/rcg-inventory-prc-api-spec/[API Specification^] -| https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/rcg-inventory-prc-api/[Implementation Template^] +| https://anypoint.mulesoft.com/exchange/org.mule.examples/rcg-inventory-prc-api-spec/[API Specification^] +| https://anypoint.mulesoft.com/exchange/org.mule.examples/rcg-inventory-prc-api/[Implementation Template^] | Accelerator Orders Process API -| https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/accel-slsorder-sync-prc-api-spec[API Specification^] -| https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/accel-slsorder-sync-prc-api/[Implementation Template^] +| https://anypoint.mulesoft.com/exchange/org.mule.examples/accel-slsorder-sync-prc-api-spec[API Specification^] +| https://anypoint.mulesoft.com/exchange/org.mule.examples/accel-slsorder-sync-prc-api/[Implementation Template^] | Products Process API -| https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/rcg-products-prc-api-spec/[API Specification^] -| https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/rcg-products-prc-api/[Implementation Template^] +| https://anypoint.mulesoft.com/exchange/org.mule.examples/rcg-products-prc-api-spec/[API Specification^] +| https://anypoint.mulesoft.com/exchange/org.mule.examples/rcg-products-prc-api/[Implementation Template^] | RCG Customer Data Platform Process API -| https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/rcg-cdp-prc-api-spec/[API Specification^] -| https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/rcg-cdp-prc-api/[Implementation Template^] +| https://anypoint.mulesoft.com/exchange/org.mule.examples/rcg-cdp-prc-api-spec/[API Specification^] +| https://anypoint.mulesoft.com/exchange/org.mule.examples/rcg-cdp-prc-api/[Implementation Template^] | RCG DataLake Process API -| https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/rcg-datalake-prc-api-spec/[API Specification^] -| https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/rcg-datalake-prc-api/[Implementation Template^] +| https://anypoint.mulesoft.com/exchange/org.mule.examples/rcg-datalake-prc-api-spec/[API Specification^] +| https://anypoint.mulesoft.com/exchange/org.mule.examples/rcg-datalake-prc-api/[Implementation Template^] | RCG Marketing Process API -| https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/rcg-marketing-prc-api-spec/[API Specification^] -| https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/rcg-marketing-prc-api/[Implementation Template^] +| https://anypoint.mulesoft.com/exchange/org.mule.examples/rcg-marketing-prc-api-spec/[API Specification^] +| https://anypoint.mulesoft.com/exchange/org.mule.examples/rcg-marketing-prc-api/[Implementation Template^] |=== == Experience APIs @@ -129,12 +129,12 @@ Accelerator assets include API specifications, implementation templates, custom [cols="40,30,30",width=100%] |=== | B2C Commerce Experience API -| https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/rcg-b2c-commerce-exp-api-spec/[API Specification^] -| https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/rcg-b2c-commerce-exp-api[Implementation Template^] +| https://anypoint.mulesoft.com/exchange/org.mule.examples/rcg-b2c-commerce-exp-api-spec/[API Specification^] +| https://anypoint.mulesoft.com/exchange/org.mule.examples/rcg-b2c-commerce-exp-api[Implementation Template^] | Salesforce Experience API -| https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/rcg-salesforce-exp-api-spec/[API Specification^] -| https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/rcg-salesforce-exp-api/[Implementation Template^] +| https://anypoint.mulesoft.com/exchange/org.mule.examples/rcg-salesforce-exp-api-spec/[API Specification^] +| https://anypoint.mulesoft.com/exchange/org.mule.examples/rcg-salesforce-exp-api/[Implementation Template^] |=== == Listeners & Handlers @@ -142,16 +142,16 @@ Accelerator assets include API specifications, implementation templates, custom [cols="70,30",width=100%] |=== | Salesforce Marketing Listener -| https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/rcg-salesforce-marketing-listener/[Implementation Template^] +| https://anypoint.mulesoft.com/exchange/org.mule.examples/rcg-salesforce-marketing-listener/[Implementation Template^] | Salesforce Topic Listener -| https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/rcg-salesforce-topic-listener/[Implementation Template^] +| https://anypoint.mulesoft.com/exchange/org.mule.examples/rcg-salesforce-topic-listener/[Implementation Template^] | SAP Event Listener -| https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/rcg-sap-event-listener/[Implementation Template^] +| https://anypoint.mulesoft.com/exchange/org.mule.examples/rcg-sap-event-listener/[Implementation Template^] | Salsify Channel Listener -| https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/rcg-salsify-channel-listener/[Implementation Template^] +| https://anypoint.mulesoft.com/exchange/org.mule.examples/rcg-salsify-channel-listener/[Implementation Template^] |=== === Custom Components @@ -159,29 +159,29 @@ Accelerator assets include API specifications, implementation templates, custom [cols="70,30",width=100%] |=== | B2C Commerce Instore Pickup Cartridge -| https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/rcg-b2c-commerce-instore-pickup-cartridge-src/[Source^] +| https://anypoint.mulesoft.com/exchange/org.mule.examples/rcg-b2c-commerce-instore-pickup-cartridge-src/[Source^] | B2C Commerce Sync Cartridge -| https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/rcg-b2c-commerce-sync-cartridge-src/[Source^] +| https://anypoint.mulesoft.com/exchange/org.mule.examples/rcg-b2c-commerce-sync-cartridge-src/[Source^] | ID Graph Lightning Web Component -| https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/accelerator-idgraph-lwc-src[Source^] +| https://anypoint.mulesoft.com/exchange/org.mule.examples/accelerator-idgraph-lwc-src[Source^] | POM Parent -| https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/accelerator-pom-parent-src/[Source^] +| https://anypoint.mulesoft.com/exchange/org.mule.examples/accelerator-pom-parent-src/[Source^] | Product Availability Lightning Web Component -| https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/accelerator-productavailability-lwc-src/[Source^] +| https://anypoint.mulesoft.com/exchange/org.mule.examples/accelerator-productavailability-lwc-src/[Source^] |=== == Shared APIs [cols="40,30,30",width=100%] |=== -| Accelerator Email System API | https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/accelerator-email-sys-api[API Specification^] | https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/accel-email-sys-api[Implementation Template^] -| Accelerator Slack System API | https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/accelerator-slack-sys-api[API Specification^] | https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/accel-slack-sys-api[Implementation Template^] -| Accelerator SMS System API | https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/accelerator-sms-sys-api[API Specification^] | https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/accel-sms-sys-api[Implementation Template^] -| Accelerator Notifications Process API | https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/accelerator-notifications-prc-api[API Specification^] | https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/accel-notifications-prc-api/[Implementation Template^] +| Accelerator Email System API | https://anypoint.mulesoft.com/exchange/org.mule.examples/accelerator-email-sys-api[API Specification^] | https://anypoint.mulesoft.com/exchange/org.mule.examples/accel-email-sys-api[Implementation Template^] +| Accelerator Slack System API | https://anypoint.mulesoft.com/exchange/org.mule.examples/accelerator-slack-sys-api[API Specification^] | https://anypoint.mulesoft.com/exchange/org.mule.examples/accel-slack-sys-api[Implementation Template^] +| Accelerator SMS System API | https://anypoint.mulesoft.com/exchange/org.mule.examples/accelerator-sms-sys-api[API Specification^] | https://anypoint.mulesoft.com/exchange/org.mule.examples/accel-sms-sys-api[Implementation Template^] +| Accelerator Notifications Process API | https://anypoint.mulesoft.com/exchange/org.mule.examples/accelerator-notifications-prc-api[API Specification^] | https://anypoint.mulesoft.com/exchange/org.mule.examples/accel-notifications-prc-api/[Implementation Template^] |=== == Shared Components @@ -189,13 +189,13 @@ Accelerator assets include API specifications, implementation templates, custom [cols="70,30",width=100%] |=== | Accelerator Common Core -| https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/accelerator-common-core-src/[Source^] +| https://anypoint.mulesoft.com/exchange/org.mule.examples/accelerator-common-core-src/[Source^] | POM Parent -| https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/accelerator-pom-parent-src/[Source^] +| https://anypoint.mulesoft.com/exchange/org.mule.examples/accelerator-pom-parent-src/[Source^] | ID Graph Lightning Web Component -| https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/accelerator-idgraph-lwc-src/[Source^] +| https://anypoint.mulesoft.com/exchange/org.mule.examples/accelerator-idgraph-lwc-src/[Source^] |=== == See Also diff --git a/retail/3.1/modules/ROOT/pages/sap-custom-bapi-setup-guide.adoc b/retail/3.1/modules/ROOT/pages/sap-custom-bapi-setup-guide.adoc index 7611ac3ae..c5b529059 100644 --- a/retail/3.1/modules/ROOT/pages/sap-custom-bapi-setup-guide.adoc +++ b/retail/3.1/modules/ROOT/pages/sap-custom-bapi-setup-guide.adoc @@ -5,7 +5,7 @@ The following provides guidance on how to use the custom BAPI code (for example, `ZBAPI_CUSTOMER_V3`) for your SAP instance. [NOTE] -You must complete the following instructions before deploying the https://anypoint.mulesoft.com/exchange/0b4cad67-8f23-4ffe-a87f-ffd10a1f6873/mulesoft-accelerator-for-retail/minor/{retail-version}/pages/Use%20case%201%20-%20Customer%20profile%20sync/[Customer profile sync from SAP^] use case. +You must complete the following instructions before deploying the https://anypoint.mulesoft.com/exchange/org.mule.examples/mulesoft-accelerator-for-retail/minor/{retail-version}/pages/Use%20case%201%20-%20Customer%20profile%20sync/[Customer profile sync from SAP^] use case. == BAPI custom objects @@ -61,7 +61,7 @@ You must create the following ABAP objects in order to use this custom BAPI, whi | Object | How to create | `Z_MASTER_ID` -| image:https://www.mulesoft.com/ext/solutions/draft/images/sfc-retail-com-bapi_01.png[sfc-retail-com-bapi_01.png,599] +| image:https://www.mulesoft.com/ext/solutions/images/sfc-retail-com-bapi_01.png[sfc-retail-com-bapi_01.png,599] |=== [[creating-structures]] @@ -72,19 +72,19 @@ You must create the following ABAP objects in order to use this custom BAPI, whi | Object | How to create | `ZSTR_PERSON` -| image:https://www.mulesoft.com/ext/solutions/draft/images/retail-2.2-bapi-01.1.png[retail-2.2-bapi-01.1.png,599] +| image:https://www.mulesoft.com/ext/solutions/images/retail-2.2-bapi-01.1.png[retail-2.2-bapi-01.1.png,599] | `ZSTR_ORGANIZATION` -| image:https://www.mulesoft.com/ext/solutions/draft/images/retail-2.2-bapi-01.2.png[retail-2.2-bapi-01.2.png,599] +| image:https://www.mulesoft.com/ext/solutions/images/retail-2.2-bapi-01.2.png[retail-2.2-bapi-01.2.png,599] | `ZSTR_GROUP` -| image:https://www.mulesoft.com/ext/solutions/draft/images/retail-2.2-bapi-01.3.png[retail-2.2-bapi-01.3.png,599] +| image:https://www.mulesoft.com/ext/solutions/images/retail-2.2-bapi-01.3.png[retail-2.2-bapi-01.3.png,599] | `ZES_CUSTOMER` -| image:https://www.mulesoft.com/ext/solutions/draft/images/retail-2.2-bapi-01.4.png[retail-2.2-bapi-01.4.png,599] +| image:https://www.mulesoft.com/ext/solutions/images/retail-2.2-bapi-01.4.png[retail-2.2-bapi-01.4.png,599] | `ZES_CONTROLDATA` -| image:https://www.mulesoft.com/ext/solutions/draft/images/retail-2.2-bapi-01.5.png[retail-2.2-bapi-01.5.png,599] +| image:https://www.mulesoft.com/ext/solutions/images/retail-2.2-bapi-01.5.png[retail-2.2-bapi-01.5.png,599] |=== [[creating-table-types]] @@ -95,7 +95,7 @@ You must create the following ABAP objects in order to use this custom BAPI, whi | Object | How to create | `ZTY_CUSTOMER` -| image:https://www.mulesoft.com/ext/solutions/draft/images/sfc-retail-com-bapi_05.png[sfc-retail-com-bapi_05.png,599] +| image:https://www.mulesoft.com/ext/solutions/images/sfc-retail-com-bapi_05.png[sfc-retail-com-bapi_05.png,599] |=== [[creating-transparent-tables]] @@ -106,7 +106,7 @@ You must create the following ABAP objects in order to use this custom BAPI, whi | Object | How to create | `ZTT_CUSTOMER` -| image:https://www.mulesoft.com/ext/solutions/draft/images/retail-2.2-bapi-05.1.png[retail-2.2-bapi-05.1.png,599] +| image:https://www.mulesoft.com/ext/solutions/images/retail-2.2-bapi-05.1.png[retail-2.2-bapi-05.1.png,599] |=== {blank} @@ -123,91 +123,91 @@ You must create the following ABAP objects in order to use this custom BAPI, whi . Create the function group "ZFG_CUSTOMER_V3". . Create the function module "ZBAPI_CUSTOMER_V3", using "Remote-enable module" as processing type: + -image:https://www.mulesoft.com/ext/solutions/draft/images/sfc-retail-com-bapi_06.png[sfc-retail-com-bapi_06.png,599] +image:https://www.mulesoft.com/ext/solutions/images/sfc-retail-com-bapi_06.png[sfc-retail-com-bapi_06.png,599] . Complete the import parameters with the following: + -image:https://www.mulesoft.com/ext/solutions/draft/images/sfc-retail-com-bapi_07.png[sfc-retail-com-bapi_07.png,599] +image:https://www.mulesoft.com/ext/solutions/images/sfc-retail-com-bapi_07.png[sfc-retail-com-bapi_07.png,599] . Complete the export parameters with the following: + -image:https://www.mulesoft.com/ext/solutions/draft/images/sfc-retail-com-bapi_08.png[sfc-retail-com-bapi_08.png,599] +image:https://www.mulesoft.com/ext/solutions/images/sfc-retail-com-bapi_08.png[sfc-retail-com-bapi_08.png,599] . Copy and paste the code from "ZBAPI_CUSTOMER_V3.txt". . Create the function module "ZBAPI_CUSTOMER_CREATE_V3": + -image:https://www.mulesoft.com/ext/solutions/draft/images/sfc-retail-com-bapi_09.png[sfc-retail-com-bapi_09.png,399] +image:https://www.mulesoft.com/ext/solutions/images/sfc-retail-com-bapi_09.png[sfc-retail-com-bapi_09.png,399] . Complete the import parameters with the following: + -image:https://www.mulesoft.com/ext/solutions/draft/images/retail-2.2-bapi-09.1.png[retail-2.2-bapi-09.1.png,599] +image:https://www.mulesoft.com/ext/solutions/images/retail-2.2-bapi-09.1.png[retail-2.2-bapi-09.1.png,599] . Complete the export parameters with the following: + -image:https://www.mulesoft.com/ext/solutions/draft/images/sfc-retail-com-bapi_11.png[sfc-retail-com-bapi_11.png,599] +image:https://www.mulesoft.com/ext/solutions/images/sfc-retail-com-bapi_11.png[sfc-retail-com-bapi_11.png,599] . Copy and paste the code from "ZBAPI_CUSTOMER_CREATE_V3.txt". . Create the function module "ZBAPI_CUSTOMER_CUSTOM_FLDS_V3": + -image:https://www.mulesoft.com/ext/solutions/draft/images/sfc-retail-com-bapi_15.png[sfc-retail-com-bapi_15.png,599] +image:https://www.mulesoft.com/ext/solutions/images/sfc-retail-com-bapi_15.png[sfc-retail-com-bapi_15.png,599] . Complete the import parameters with the following: + -image:https://www.mulesoft.com/ext/solutions/draft/images/retail-2.2-bapi-15.1.png[retail-2.2-bapi-15.1.png,399] +image:https://www.mulesoft.com/ext/solutions/images/retail-2.2-bapi-15.1.png[retail-2.2-bapi-15.1.png,399] . Copy and paste the code from "ZBAPI_CUSTOMER_CUSTOM_FIELDS_V3.txt". . Create the function module "ZBAPI_CUSTOMER_UPDATE_V3": + -image:https://www.mulesoft.com/ext/solutions/draft/images/sfc-retail-com-bapi_12.png[sfc-retail-com-bapi_12.png,599] +image:https://www.mulesoft.com/ext/solutions/images/sfc-retail-com-bapi_12.png[sfc-retail-com-bapi_12.png,599] . Complete the import parameters with the following: + -image:https://www.mulesoft.com/ext/solutions/draft/images/retail-2.2-bapi-12.1.png[retail-2.2-bapi-12.1.png,599] +image:https://www.mulesoft.com/ext/solutions/images/retail-2.2-bapi-12.1.png[retail-2.2-bapi-12.1.png,599] . Complete the export parameters with the following: + -image:https://www.mulesoft.com/ext/solutions/draft/images/retail-2.2-bapi-12.2.png[retail-2.2-bapi-12.2.png,599] +image:https://www.mulesoft.com/ext/solutions/images/retail-2.2-bapi-12.2.png[retail-2.2-bapi-12.2.png,599] . Copy and paste the code from "ZBAPI_CUSTOMER_UPDATE_V3.txt". . Create the function module "ZBAPI_QUERY_V3", using "Remote-enable module" as processing type: + -image:https://www.mulesoft.com/ext/solutions/draft/images/sfc-retail-com-bapi_36.png[sfc-retail-com-bapi_36.png,599] +image:https://www.mulesoft.com/ext/solutions/images/sfc-retail-com-bapi_36.png[sfc-retail-com-bapi_36.png,599] . Complete the import parameters with the following: + -image:https://www.mulesoft.com/ext/solutions/draft/images/retail-2.2-bapi-36.1.png[retail-2.2-bapi-36.1.png,399] +image:https://www.mulesoft.com/ext/solutions/images/retail-2.2-bapi-36.1.png[retail-2.2-bapi-36.1.png,399] . Complete the export parameters with the following: + -image:https://www.mulesoft.com/ext/solutions/draft/images/sfc-retail-com-bapi_22.png[sfc-retail-com-bapi_22.png,399] +image:https://www.mulesoft.com/ext/solutions/images/sfc-retail-com-bapi_22.png[sfc-retail-com-bapi_22.png,399] . Copy and paste the code from "ZBAPI_QUERY_V3.txt". . Create the function module "ZBAPI_CONTROL_DATA_V3": + -image:https://www.mulesoft.com/ext/solutions/draft/images/sfc-retail-com-bapi_21.png[sfc-retail-com-bapi_21.png,599] +image:https://www.mulesoft.com/ext/solutions/images/sfc-retail-com-bapi_21.png[sfc-retail-com-bapi_21.png,599] . Complete the import parameters with the following: + -image:https://www.mulesoft.com/ext/solutions/draft/images/sfc-retail-com-bapi_24.png[sfc-retail-com-bapi_24.png,599] +image:https://www.mulesoft.com/ext/solutions/images/sfc-retail-com-bapi_24.png[sfc-retail-com-bapi_24.png,599] . Complete the export parameters with the following: + -image:https://www.mulesoft.com/ext/solutions/draft/images/sfc-retail-com-bapi_19.png[sfc-retail-com-bapi_19.png,599] +image:https://www.mulesoft.com/ext/solutions/images/sfc-retail-com-bapi_19.png[sfc-retail-com-bapi_19.png,599] . Copy the source code from "ZBAPI_CONTROL_DATA_V3.txt". . Activate the entire function group by right-clicking on it in the tree and then selecting "Activate": + -image:https://www.mulesoft.com/ext/solutions/draft/images/sfc-retail-com-bapi_35.png[sfc-retail-com-bapi_35.png,301] +image:https://www.mulesoft.com/ext/solutions/images/sfc-retail-com-bapi_35.png[sfc-retail-com-bapi_35.png,301] . Create the function group "ZFG_CUSTOMER2". . Create the function module "ZBAPI_ADDR_QUERY", using "Remote-enable module" as processing type: + -image:https://www.mulesoft.com/ext/solutions/draft/images/sfc-retail-com-bapi_17.png[sfc-retail-com-bapi_17.png,599] +image:https://www.mulesoft.com/ext/solutions/images/sfc-retail-com-bapi_17.png[sfc-retail-com-bapi_17.png,599] . Complete the import parameters with the following: + -image:https://www.mulesoft.com/ext/solutions/draft/images/sfc-retail-com-bapi_20.png[sfc-retail-com-bapi_20.png,599] +image:https://www.mulesoft.com/ext/solutions/images/sfc-retail-com-bapi_20.png[sfc-retail-com-bapi_20.png,599] . Complete the export parameters with the following: + -image:https://www.mulesoft.com/ext/solutions/draft/images/sfc-retail-com-bapi_22.png[sfc-retail-com-bapi_22.png,399] +image:https://www.mulesoft.com/ext/solutions/images/sfc-retail-com-bapi_22.png[sfc-retail-com-bapi_22.png,399] . Copy and paste the code from "ZBAPI_ADDR_QUERY.txt". . Create the function module "ZBAPI_CONTROL_DATA" using the import parameters as follows: + -image:https://www.mulesoft.com/ext/solutions/draft/images/retail-2.2-bapi-22.1.png[retail-2.2-bapi-22.1.png,599] +image:https://www.mulesoft.com/ext/solutions/images/retail-2.2-bapi-22.1.png[retail-2.2-bapi-22.1.png,599] . Use the export parameters as in the following: + -image:https://www.mulesoft.com/ext/solutions/draft/images/retail-2.2-bapi-22.2.png[retail-2.2-bapi-22.2.png,599] +image:https://www.mulesoft.com/ext/solutions/images/retail-2.2-bapi-22.2.png[retail-2.2-bapi-22.2.png,599] . Copy the source code from "ZBAPI_CONTROL_DATA.txt". . Activate the entire function group by right-clicking on it in the tree and selecting 'Activate': + -image:https://www.mulesoft.com/ext/solutions/draft/images/retail-2.2-bapi-22.3.png[retail-2.2-bapi-22.3.png,301] +image:https://www.mulesoft.com/ext/solutions/images/retail-2.2-bapi-22.3.png[retail-2.2-bapi-22.3.png,301] . Complete the following: . Create a customer group ZSME (*Logistics - General\->Business Partner\->Customer\->Control\->Define and Assign Customer Number Ranges*) . Create a partner group ZSME (*Cross-Application Components\->SAP Business Partner\->Business Partner\->Basic Settings\->Number Ranges and Settings*) from the transaction SPRO . Synchronize them from the same transaction (*Cross-Application Components\->Master Data Synchronization\->Customer/Vendor Integration\->Business Partner Settings\->Settings for Customer Integration\->Assign Keys\->Define Number Assignment for Direction BP to Customer*) + -image:https://www.mulesoft.com/ext/solutions/draft/images/retail-2.2-bapi-22.4.png[retail-2.2-bapi-22.4.png,599] +image:https://www.mulesoft.com/ext/solutions/images/retail-2.2-bapi-22.4.png[retail-2.2-bapi-22.4.png,599] ==== *More ZBAPI modules* @@ -222,52 +222,52 @@ To create ABAP custom objects, groups, and modules: . Create the same dictionary objects created for the BAPI `ZBAPI_CUSTOMER` using the following structure/table type: + -image:https://www.mulesoft.com/ext/solutions/draft/images/retail-2.2-bapi-51.png[retail-2.2-bapi-51.png,599] -image:https://www.mulesoft.com/ext/solutions/draft/images/retail-2.2-bapi-52.png[retail-2.2-bapi-52.png,599] +image:https://www.mulesoft.com/ext/solutions/images/retail-2.2-bapi-51.png[retail-2.2-bapi-51.png,599] +image:https://www.mulesoft.com/ext/solutions/images/retail-2.2-bapi-52.png[retail-2.2-bapi-52.png,599] . Create the function group `ZFG_CUSTOMER2`. . Create the function module `ZBAPI_ADDR_QUERY` using 'Remote-enable module' as the processing type: + -image:https://www.mulesoft.com/ext/solutions/draft/images/retail-2.2-bapi-53.png[retail-2.2-bapi-53.png,599] +image:https://www.mulesoft.com/ext/solutions/images/retail-2.2-bapi-53.png[retail-2.2-bapi-53.png,599] . Complete the import parameters with the following: + -image:https://www.mulesoft.com/ext/solutions/draft/images/retail-2.2-bapi-54.png[retail-2.2-bapi-54.png,599] +image:https://www.mulesoft.com/ext/solutions/images/retail-2.2-bapi-54.png[retail-2.2-bapi-54.png,599] . Complete the export parameters with the following: + -image:https://www.mulesoft.com/ext/solutions/draft/images/retail-2.2-bapi-55.png[retail-2.2-bapi-55.png,399] +image:https://www.mulesoft.com/ext/solutions/images/retail-2.2-bapi-55.png[retail-2.2-bapi-55.png,399] . Copy and paste the code from 'ZBAPI_ADDR_QUERY.txt'. . Create the function module `ZBAPI_ADDR_SAP` using 'Remote-enable module' as the processing type: + -image:https://www.mulesoft.com/ext/solutions/draft/images/retail-2.2-bapi-56.png[retail-2.2-bapi-56.png,599] +image:https://www.mulesoft.com/ext/solutions/images/retail-2.2-bapi-56.png[retail-2.2-bapi-56.png,599] . Complete the import parameters with the following: + -image:https://www.mulesoft.com/ext/solutions/draft/images/retail-2.2-bapi-57.png[retail-2.2-bapi-57.png,599] +image:https://www.mulesoft.com/ext/solutions/images/retail-2.2-bapi-57.png[retail-2.2-bapi-57.png,599] . Complete the export parameters with the following: + -image:https://www.mulesoft.com/ext/solutions/draft/images/retail-2.2-bapi-58.png[retail-2.2-bapi-58.png,599] +image:https://www.mulesoft.com/ext/solutions/images/retail-2.2-bapi-58.png[retail-2.2-bapi-58.png,599] . Copy and paste the code from 'ZBAPI_QUERY_SAP.txt'. . Create the function module `ZBAPI_CUST_QUERY` using 'Remote-enable module' as the processing type: + -image:https://www.mulesoft.com/ext/solutions/draft/images/retail-2.2-bapi-59.png[retail-2.2-bapi-59.png,399] +image:https://www.mulesoft.com/ext/solutions/images/retail-2.2-bapi-59.png[retail-2.2-bapi-59.png,399] . Complete the import parameters with the following: + -image:https://www.mulesoft.com/ext/solutions/draft/images/retail-2.2-bapi-60.png[retail-2.2-bapi-60.png,599] +image:https://www.mulesoft.com/ext/solutions/images/retail-2.2-bapi-60.png[retail-2.2-bapi-60.png,599] . Complete the export parameters with the following: + -image:https://www.mulesoft.com/ext/solutions/draft/images/retail-2.2-bapi-61.png[retail-2.2-bapi-61.png,599] +image:https://www.mulesoft.com/ext/solutions/images/retail-2.2-bapi-61.png[retail-2.2-bapi-61.png,599] . Copy and paste the code from 'ZBAPI_CUST_QUERY.txt'. . Create the function module `ZBAPI_CUSTOMER_CD` using 'Remote-enable module' as the processing type: + -image:https://www.mulesoft.com/ext/solutions/draft/images/retail-2.2-bapi-62.png[retail-2.2-bapi-62.png,399] +image:https://www.mulesoft.com/ext/solutions/images/retail-2.2-bapi-62.png[retail-2.2-bapi-62.png,399] . Complete the import parameters with the following: + -image:https://www.mulesoft.com/ext/solutions/draft/images/retail-2.2-bapi-63.png[retail-2.2-bapi-63.png,599] +image:https://www.mulesoft.com/ext/solutions/images/retail-2.2-bapi-63.png[retail-2.2-bapi-63.png,599] . Complete the export parameters with the following: + -image:https://www.mulesoft.com/ext/solutions/draft/images/retail-2.2-bapi-64.png[retail-2.2-bapi-64.png,599] +image:https://www.mulesoft.com/ext/solutions/images/retail-2.2-bapi-64.png[retail-2.2-bapi-64.png,599] . Copy and paste the code from 'ZBAPI_CUSTOMER_CD.txt'. . Activate the entire function group by right-clicking on it in the tree and selecting 'Activate': + -image:https://www.mulesoft.com/ext/solutions/draft/images/retail-2.2-bapi-65.png[retail-2.2-bapi-65.png,301] +image:https://www.mulesoft.com/ext/solutions/images/retail-2.2-bapi-65.png[retail-2.2-bapi-65.png,301] == See Also diff --git a/retail/3.1/modules/ROOT/pages/sap-s4hana-setup-guide.adoc b/retail/3.1/modules/ROOT/pages/sap-s4hana-setup-guide.adoc index b4b27a925..e6295f815 100644 --- a/retail/3.1/modules/ROOT/pages/sap-s4hana-setup-guide.adoc +++ b/retail/3.1/modules/ROOT/pages/sap-s4hana-setup-guide.adoc @@ -10,24 +10,24 @@ To make the necessary configurations in S/4HANA: . Create a *Communication System* in the corresponding Fiori app. This communication system represents the external system that will consume the S/4HANA Cloud SOAP service. In this example, it's named `COM_0009_SOAP_OUT`: + + -image:https://www.mulesoft.com/ext/solutions/draft/images/retail-sap-s4hana-setup-guide-01.png[retail-sap-s4hana-setup-guide-01.png,799] +image:https://www.mulesoft.com/ext/solutions/images/retail-sap-s4hana-setup-guide-01.png[retail-sap-s4hana-setup-guide-01.png,799] . For the 'Business System' name, use the same name of the System ID. . In the 'Host Name' field, enter the hostname of the Mule application deployed on Cloudhub (if you don't have it yet, you can enter a mock URL and then modify it later): + + -image:https://www.mulesoft.com/ext/solutions/draft/images/retail-sap-s4hana-setup-guide-02.png[retail-sap-s4hana-setup-guide-02.png,799] + +image:https://www.mulesoft.com/ext/solutions/images/retail-sap-s4hana-setup-guide-02.png[retail-sap-s4hana-setup-guide-02.png,799] + + . Create a user that will be used to connect to the Cloud Hub app for sending product information in the outbound scenario (this is necessary even though the Mule application does not validate the user; we used any user for outbound): + + -image:https://www.mulesoft.com/ext/solutions/draft/images/retail-sap-s4hana-setup-guide-03.png[retail-sap-s4hana-setup-guide-03.png,799] + +image:https://www.mulesoft.com/ext/solutions/images/retail-sap-s4hana-setup-guide-03.png[retail-sap-s4hana-setup-guide-03.png,799] + + . Use the *Communication Arrangement* Fiori app to create a new Communication Arrangement: + + -image:https://www.mulesoft.com/ext/solutions/draft/images/retail-sap-s4hana-setup-guide-04.png[retail-sap-s4hana-setup-guide-04.png,799] + +image:https://www.mulesoft.com/ext/solutions/images/retail-sap-s4hana-setup-guide-04.png[retail-sap-s4hana-setup-guide-04.png,799] + + . Create a new *Communication Arrangement*, select the communication scenario "SAP_COM_0009", and then define a specific name for the arrangement, "SAP_COM_0009_SOAP". . In the *Communication System* field, select the Communication System created in the previous step: + + -image:https://www.mulesoft.com/ext/solutions/draft/images/retail-sap-s4hana-setup-guide-05.png[retail-sap-s4hana-setup-guide-05.png,799] + +image:https://www.mulesoft.com/ext/solutions/images/retail-sap-s4hana-setup-guide-05.png[retail-sap-s4hana-setup-guide-05.png,799] + + . For outbound communication, select the previously-created user and configure the *Product Master - Replicate from SAP S/4HANA Cloud to Client* and include the following settings. Make sure to note the Path (`/sap/bc/srt/scs/sap/productmdmbulkreplicaterequest`) because we will use this path to configure the Mule application SOAP endpoint: ** Set the *Service status* to *Active* @@ -35,11 +35,11 @@ image:https://www.mulesoft.com/ext/solutions/draft/images/retail-sap-s4hana-setu ** Replication model = `I (Initial)` ** The Output Mode = `D (Direct)` + + -image:https://www.mulesoft.com/ext/solutions/draft/images/retail-sap-s4hana-setup-guide-06.png[retail-sap-s4hana-setup-guide-06.png,799] + +image:https://www.mulesoft.com/ext/solutions/images/retail-sap-s4hana-setup-guide-06.png[retail-sap-s4hana-setup-guide-06.png,799] + + -image:https://www.mulesoft.com/ext/solutions/draft/images/retail-sap-s4hana-setup-guide-07.png[retail-sap-s4hana-setup-guide-07.png,799] + +image:https://www.mulesoft.com/ext/solutions/images/retail-sap-s4hana-setup-guide-07.png[retail-sap-s4hana-setup-guide-07.png,799] + + -image:https://www.mulesoft.com/ext/solutions/draft/images/retail-sap-s4hana-setup-guide-08.png[retail-sap-s4hana-setup-guide-08.png,799] + +image:https://www.mulesoft.com/ext/solutions/images/retail-sap-s4hana-setup-guide-08.png[retail-sap-s4hana-setup-guide-08.png,799] + + . Save it. All configurations at S/4HANA Cloud side are finished and you will be able to download the WSDL that contains the metadata to import into the S/4HANA Cloud SOAP Connector into the Mule application. @@ -49,38 +49,38 @@ The following example describes how to create a Mule application using the Outbo . Create a Mule project and add the appropriate connector from Exchange to the Mule Palette: + + -image:https://www.mulesoft.com/ext/solutions/draft/images/retail-sap-s4hana-setup-guide-09.png[retail-sap-s4hana-setup-guide-09.png,799] + +image:https://www.mulesoft.com/ext/solutions/images/retail-sap-s4hana-setup-guide-09.png[retail-sap-s4hana-setup-guide-09.png,799] + + . Add and configure the *Outbound Message Listener* to the canvas: + + -image:https://www.mulesoft.com/ext/solutions/draft/images/retail-sap-s4hana-setup-guide-10.png[retail-sap-s4hana-setup-guide-10.png,799] + +image:https://www.mulesoft.com/ext/solutions/images/retail-sap-s4hana-setup-guide-10.png[retail-sap-s4hana-setup-guide-10.png,799] + + . Add the corresponding WSDL path to the WSDL you downloaded from S/4HANA Cloud and create the HTTP listener configuration: + + -image:https://www.mulesoft.com/ext/solutions/draft/images/retail-sap-s4hana-setup-guide-11.png[retail-sap-s4hana-setup-guide-11.png,799] + +image:https://www.mulesoft.com/ext/solutions/images/retail-sap-s4hana-setup-guide-11.png[retail-sap-s4hana-setup-guide-11.png,799] + + -image:https://www.mulesoft.com/ext/solutions/draft/images/retail-sap-s4hana-setup-guide-12.png[retail-sap-s4hana-setup-guide-12.png,799] + +image:https://www.mulesoft.com/ext/solutions/images/retail-sap-s4hana-setup-guide-12.png[retail-sap-s4hana-setup-guide-12.png,799] + + _Note: we are using no authentication on the Mule Application, so we used the Insecure option for the Trust Store Configuration. In the Keystore configuration, we used a test Keystore, which is mandatory for HTTPS communication:_ + + -image:https://www.mulesoft.com/ext/solutions/draft/images/retail-sap-s4hana-setup-guide-13.png[retail-sap-s4hana-setup-guide-13.png,799] + +image:https://www.mulesoft.com/ext/solutions/images/retail-sap-s4hana-setup-guide-13.png[retail-sap-s4hana-setup-guide-13.png,799] + + . Select the Message type that the connector expects to receive from SAP (the connector reads the metadata from the WSDL we configured): + + -image:https://www.mulesoft.com/ext/solutions/draft/images/retail-sap-s4hana-setup-guide-14.png[retail-sap-s4hana-setup-guide-14.png,799] + +image:https://www.mulesoft.com/ext/solutions/images/retail-sap-s4hana-setup-guide-14.png[retail-sap-s4hana-setup-guide-14.png,799] + + . On the Responses tab, use the status Code "202" and the Reason-Phrase "Accepted" because we want to send the same status that S/4HANA Cloud will send if the service invocation results OK. No payload will be returned as a response - just the `Status` code and `Reason-phrase`: + + -image:https://www.mulesoft.com/ext/solutions/draft/images/retail-sap-s4hana-setup-guide-15.png[retail-sap-s4hana-setup-guide-15.png,799] + +image:https://www.mulesoft.com/ext/solutions/images/retail-sap-s4hana-setup-guide-15.png[retail-sap-s4hana-setup-guide-15.png,799] + + . Use a *Logger* component to log the inbound XML payload: + + -image:https://www.mulesoft.com/ext/solutions/draft/images/retail-sap-s4hana-setup-guide-16.png[retail-sap-s4hana-setup-guide-16.png,799] + +image:https://www.mulesoft.com/ext/solutions/images/retail-sap-s4hana-setup-guide-16.png[retail-sap-s4hana-setup-guide-16.png,799] + + _The Mule flow should look like the following:_ + + -image:https://www.mulesoft.com/ext/solutions/draft/images/retail-sap-s4hana-setup-guide-17.png[retail-sap-s4hana-setup-guide-17.png,399] + +image:https://www.mulesoft.com/ext/solutions/images/retail-sap-s4hana-setup-guide-17.png[retail-sap-s4hana-setup-guide-17.png,399] + + . Deploy the application to Cloudhub. You're now ready to test the scenario. @@ -90,35 +90,35 @@ To test the scenario: . Create the following. You only need to create a material in the corresponding Fiori app of S/4HANA Cloud: + + -image:https://www.mulesoft.com/ext/solutions/draft/images/retail-sap-s4hana-setup-guide-18.png[retail-sap-s4hana-setup-guide-18.png,599] + +image:https://www.mulesoft.com/ext/solutions/images/retail-sap-s4hana-setup-guide-18.png[retail-sap-s4hana-setup-guide-18.png,599] + + -image:https://www.mulesoft.com/ext/solutions/draft/images/retail-sap-s4hana-setup-guide-19.png[retail-sap-s4hana-setup-guide-19.png,799] + +image:https://www.mulesoft.com/ext/solutions/images/retail-sap-s4hana-setup-guide-19.png[retail-sap-s4hana-setup-guide-19.png,799] + + -image:https://www.mulesoft.com/ext/solutions/draft/images/retail-sap-s4hana-setup-guide-20.png[retail-sap-s4hana-setup-guide-20.png,799] + +image:https://www.mulesoft.com/ext/solutions/images/retail-sap-s4hana-setup-guide-20.png[retail-sap-s4hana-setup-guide-20.png,799] + + -image:https://www.mulesoft.com/ext/solutions/draft/images/retail-sap-s4hana-setup-guide-21.png[retail-sap-s4hana-setup-guide-21.png,799] + +image:https://www.mulesoft.com/ext/solutions/images/retail-sap-s4hana-setup-guide-21.png[retail-sap-s4hana-setup-guide-21.png,799] + + _After you save the new material, you should see the following confirmation in S/4HANA Cloud:_ + + -image:https://www.mulesoft.com/ext/solutions/draft/images/retail-sap-s4hana-setup-guide-22.png[retail-sap-s4hana-setup-guide-22.png,399] + +image:https://www.mulesoft.com/ext/solutions/images/retail-sap-s4hana-setup-guide-22.png[retail-sap-s4hana-setup-guide-22.png,399] + + _The following shows the XML message received at the Mule application at the Runtime Manager on Cloudhub:_ + + -image:https://www.mulesoft.com/ext/solutions/draft/images/retail-sap-s4hana-setup-guide-23.png[retail-sap-s4hana-setup-guide-23.png,799] + +image:https://www.mulesoft.com/ext/solutions/images/retail-sap-s4hana-setup-guide-23.png[retail-sap-s4hana-setup-guide-23.png,799] + + . See the sent message in the Message Dashboard Fiori Application: + + -image:https://www.mulesoft.com/ext/solutions/draft/images/retail-sap-s4hana-setup-guide-24.png[retail-sap-s4hana-setup-guide-24.png,799] + +image:https://www.mulesoft.com/ext/solutions/images/retail-sap-s4hana-setup-guide-24.png[retail-sap-s4hana-setup-guide-24.png,799] + + . Select the date: + + -image:https://www.mulesoft.com/ext/solutions/draft/images/retail-sap-s4hana-setup-guide-25.png[retail-sap-s4hana-setup-guide-25.png,399] + +image:https://www.mulesoft.com/ext/solutions/images/retail-sap-s4hana-setup-guide-25.png[retail-sap-s4hana-setup-guide-25.png,399] + + . Search under *CMD:Product Integration - /CMDPR → Product Replication to Client via Service - PRDREQ_OUT/00001 namespace*: + + -image:https://www.mulesoft.com/ext/solutions/draft/images/retail-sap-s4hana-setup-guide-26.png[retail-sap-s4hana-setup-guide-26.png,799] + +image:https://www.mulesoft.com/ext/solutions/images/retail-sap-s4hana-setup-guide-26.png[retail-sap-s4hana-setup-guide-26.png,799] + + -image:https://www.mulesoft.com/ext/solutions/draft/images/retail-sap-s4hana-setup-guide-27.png[retail-sap-s4hana-setup-guide-27.png,799] +image:https://www.mulesoft.com/ext/solutions/images/retail-sap-s4hana-setup-guide-27.png[retail-sap-s4hana-setup-guide-27.png,799] == S/4HANA customization guide diff --git a/retail/3.1/modules/ROOT/pages/sfdc-customization-guide.adoc b/retail/3.1/modules/ROOT/pages/sfdc-customization-guide.adoc index 4c16e48ca..7a17bbd99 100644 --- a/retail/3.1/modules/ROOT/pages/sfdc-customization-guide.adoc +++ b/retail/3.1/modules/ROOT/pages/sfdc-customization-guide.adoc @@ -36,7 +36,7 @@ The following objects must be created === Create a Custom Object via Apex Script -An Apex class called `CustomObjectUtility` and `MetadataService` are used to create a custom object programmatically. The source can be found on https://anypoint.mulesoft.com/exchange/997d5e99-287f-4f68-bc95-ed435d7c5797/accelerator-common-resources-src[Common Resources project] and https://github.com/financialforcedev/apex-mdapi/blob/master/apex-mdapi/src/classes/MetadataService.cls[MetadataService] respectively. Download the project and follow the steps below. +An Apex class called `CustomObjectUtility` and `MetadataService` are used to create a custom object programmatically. The source can be found on https://anypoint.mulesoft.com/exchange/org.mule.examples/accelerator-common-resources-src[Common Resources project] and https://github.com/financialforcedev/apex-mdapi/blob/master/apex-mdapi/src/classes/MetadataService.cls[MetadataService] respectively. Download the project and follow the steps below. 1. Click on the Salesforce Setup icon and select `Developer Console` to open a new console window. 1. Go to `File > New > Apex class` and create a new class named `CustomObjectUtility`. diff --git a/retail/3.1/modules/ROOT/pages/sfdc-data-cloud-setup-guide.adoc b/retail/3.1/modules/ROOT/pages/sfdc-data-cloud-setup-guide.adoc index e67313693..fc0ae1e29 100644 --- a/retail/3.1/modules/ROOT/pages/sfdc-data-cloud-setup-guide.adoc +++ b/retail/3.1/modules/ROOT/pages/sfdc-data-cloud-setup-guide.adoc @@ -8,7 +8,7 @@ The following provides guidance on Salesforce Data Cloud setup required for the . Click the Setup icon and then `Data Cloud Setup`. If you don't see this option, either refresh your page or log out and back in with your admin user credentials. . Click `Get Started`. Setup can take a few minutes. Your Data Cloud instance is considered as successfully set up if you see a green tick mark for all the steps. If not, correct the issue and finish the setup. -image::https://www.mulesoft.com/ext/solutions/draft/images/rcg-cdp-setup-cdp-provisioning.png[rcg-cdp-setup-cdp-provisioning.png,599] +image::https://www.mulesoft.com/ext/solutions/images/rcg-cdp-setup-cdp-provisioning.png[rcg-cdp-setup-cdp-provisioning.png,599] == Connect Data @@ -212,7 +212,7 @@ Anypoint Connector for Salesforce CDP (Data Cloud Connector) provides customers This connector works with the Data Cloud Bulk and Streaming API, depending on the operation you configure. Each API call uses a request/response pattern over an HTTPS connection. All required request headers, error handling, and HTTPS connection configurations are built into the connector. -Refer to this https://dev-docs-internal.kqa.msap.io/beta-accelerators/salesforce-cdp-connector/1.0/[link] for details on configuration and operations for Data Cloud Connector. +Refer to this https://docs.mulesoft.com/salesforce-cdp-connector/1.0/[link] for details on configuration and operations for Data Cloud Connector. For the "Personalization with CDP" use case, refer CDP System API specification and implementation template. @@ -242,11 +242,11 @@ For the "Personalization with CDP" use case, we mapped to Custom DMO for our Mul ==== Data Mapping -image::https://www.mulesoft.com/ext/solutions/draft/images/rcg-cdp-setup-custom-dmo-webengagement.png[rcg-cdp-setup-custom-dmo-webengagement.png,599] +image::https://www.mulesoft.com/ext/solutions/images/rcg-cdp-setup-custom-dmo-webengagement.png[rcg-cdp-setup-custom-dmo-webengagement.png,599] ==== Data Relationships -image::https://www.mulesoft.com/ext/solutions/draft/images/rcg-cdp-setup-webengagement-data-relationships.png[rcg-cdp-setup-webengagement-data-relationships.png,599] +image::https://www.mulesoft.com/ext/solutions/images/rcg-cdp-setup-webengagement-data-relationships.png[rcg-cdp-setup-webengagement-data-relationships.png,599] == Identity Resolution @@ -261,9 +261,9 @@ Access Identity Resolution from Data Cloud after mapping entities to the CIM. En For the `Personalization with CDP` use case, we are leveraging the Fuzzy Name and Normalized Email Match Rule; leveraging Fuzzy First Name, Exact Last Name, and Normalized Email Address. -image:https://www.mulesoft.com/ext/solutions/draft/images/rcg-cdp-setup-identity-match-rules.png[rcg-cdp-setup-identity-match-rules.png,599] +image:https://www.mulesoft.com/ext/solutions/images/rcg-cdp-setup-identity-match-rules.png[rcg-cdp-setup-identity-match-rules.png,599] -image:https://www.mulesoft.com/ext/solutions/draft/images/rcg-cdp-setup-identity-match-rules-criteria.png[rcg-cdp-setup-identity-match-rules-criteria.png,599] +image:https://www.mulesoft.com/ext/solutions/images/rcg-cdp-setup-identity-match-rules-criteria.png[rcg-cdp-setup-identity-match-rules-criteria.png,599] To create your Identity Resolution Rules, follow the steps below: @@ -303,7 +303,7 @@ Segment On: Segment On defines the target entity (object) used to build your seg For the "Personalization with CDP" use case, we have created a few Segments. All Segments that we have created have been segmented on Unified Individual. For this segment, we wanted to create an audience wherein there were no Web Page Views in the last 365 Days. We grabbed updated Date from our Attribute Library and dragged it to the canvas. And for the operator we selected "Greater Than Last Number of Days" and entered "365" for the number of days. In the *Publish Schedule* field, we select a schedule of every 24 hours. -image::https://www.mulesoft.com/ext/solutions/draft/images/rcg-cdp-setup-segment-nowebpageviews.png[rcg-cdp-setup-segment-nowebpageviews.png,599] +image::https://www.mulesoft.com/ext/solutions/images/rcg-cdp-setup-segment-nowebpageviews.png[rcg-cdp-setup-segment-nowebpageviews.png,599] === Activation Targets @@ -423,7 +423,7 @@ For the "Personalization with CDP" use case, we created Calculated Insights to g Once created, Calculated Insights are available in the Attribute Library. You can also confirm and validate Calculated Insights via Data Explorer. -image::https://www.mulesoft.com/ext/solutions/draft/images/rcg-cdp-setup-calculated-insights.png[rcg-cdp-setup-calculated-insights.png,399] +image::https://www.mulesoft.com/ext/solutions/images/rcg-cdp-setup-calculated-insights.png[rcg-cdp-setup-calculated-insights.png,399] == See Also