Specifications include, but are not limited to: EFSP Responsibilities. At no cost to the COURT, the EFSP must: 1. Conform its FAMDE application to: a. The COURT’s adaptation to the OASIS LegalXML Electronic Court Filing (ECF) 4.01 XML schema and technical specifications. b. Current and future data‐driven COURT e‐filing XML extension schema and technical specifications based on the OASIS LegalXML Electronic Court Filing (ECF) 4.01 or higher standard. NOTE: The COURT’s most current extension schema version is 2.3. c. The COURT’s Court Policy service. NOTE: The COURT may, within the contract period, implement an OASIS LegalXML ECF 4.01 GetPolicy service, which the EFSP will be required to support. An appropriate lead time will be afforded the EFSP to conform its FAMDE to the OASIS LegalXML ECF Court Policy service. d. The COURT’s adaptation of the ECF Legal Service MDE for providing electronic secondary service. 2. At the COURT’s direction, perform XML schema validation in the COURT’s integrated development, test, and production e‐filing system environments. 3. Only to use XML elements identified within the COURT’s e‐filing specifications documents. 4. Provide a separate: a. Development system that integrates with the COURT’s integrated development e‐ filing system environment (aka DEVTEST), including [simulated] payment processing, for full round‐trip testing purposes. b. Test system that integrates with the COURT’s test e‐filing system environment (aka TEST), including [simulated] payment processing, for User Acceptance Testing (UAT), pre‐production testing, and EFSP FAMDE certification testing. c. Production system that integrates with the COURT’s production e‐filing system environment (aka PROD), including payment processing for day‐to‐day operations. 5. Exchange OASIS LegalXML ECF and COURT conformant request‐response messages based on the following operations: a. ReviewFiling i. Case type specific schema (e.g., Appellate, Civil, Criminal) ii. CoreFilingMessage iii. PaymentMessage b. GetCase c. GetDocument d. GetFeesCalculation e. NotifyFilingReviewComplete f. MessageReceiptMessage 6. Integrate with COURT e‐filing system’s equivalent to the OASIS LegalXML ECF GetPolicy service. (see 1.c of this section) 7. Include data‐populated COURT forms, based on COURT‐provided forms templates, in e‐ filed submissions, as required. NOTE: COURT forms templates ensure file and issuance stamps can be added by COURT Clerk review and case management systems in a clear and unobstructed manner. 8. Fully integrate and test its FAMDE application in the COURT e‐filing TEST environment within six (6) months of the COURT notifying the EFSP when a new or changes to the COURT e‐filing XML schema and/or technical specification is announced. 9. Provide Fully Qualified Domain Names (FQDN) for its DEVTEST, TEST, and PROD systems (sending MDE). 10. Gain access to the COURT’s DEVTEST environment, when necessary, with COURT‐ specified VPN services.
