Item Number: #0008
Description
Intresys has suggested a number of expansions to court policy
Owner: Mr. James Cabral
Status: Closed
Priority: Medium
Due Date: 08 Oct 2012
Comments
Mr. James Cabral 2012-12-10 00:21 UTC
Address using a new rules language in ECF 5.0
Mr. James Cabral 2016-12-16 02:14 UTC
o Consider versioning for court policy?
o Consider use of rules language?
o See Court Policy Requirements (https://www.oasis-open.org/apps/org/workgroup/legalxml-courtfiling/download.php/49888/ECF%205.0%20Court%20Policy%20Requirements.doc)
o Sent to LegalRule TC in 2012
Some of these may be needed in multi-EFM model that some states are now planning
#1 ? Court systems need to be able to uniquely identify courts and case types hierarchically and associate court rules with any layer in the hierarchy. At a minimum, in most courts, both state and local rules of court will apply and combine. In many courts, additional rules may apply to specific court divisions (e.g. civil, criminal, traffic), specialties courts within court divisions (family court, teen court, drug court, veteran?s court) or for a specific judge and/or courtroom (e.g. common in Texas).
? only an issue in multi-EFM model
? May impact source of Policy (i.e., CRMDE rather than FRMDE)
#2 ? Courts need to be able to constrain the use of certain NIEM and ECF elements and types. To support a variety of courts and e-filing business models, NIEM and ECF are intentionally flexible and there are sometimes multiple ways of expressing the same semantic content. For instance, there are multiple roles for case participants (e.g. CaseInitiatingPartyAttorney, CaseProsecutionAttorney). Courts may choose to limit or exclude the use of certain case participants roles in specific case types.
? definitely need to address
? Use genericode multi-column code lists to support relationships
#3 ? Courts also need to be able to constrain and extend ECF beyond the capabilities of XML schema and Genericode. By automating the enforcement of court rules, the need for manual review of filings by the clerk can be reduced or eliminated. ECF 3 supported only XML schema code lists. For instance, the use of Genericode in ECF 4 has enabled hierarchical code lists. However, these mechanisms are still insufficient for expressing which documents and docket types are either required and/or permissible in certain case types.
? may be able to use genericode for now
? In part using genericode multi-column code lists to support relationships
? Others would require a rules language
#4 ? Courts need to enforce security and privacy rules. Courts often define rules for special handling of certain case types, document types or personally identifiable information (PII) due to security and privacy concerns. For instance, identifying information about minors (in juvenile abuse and neglect, delinqeuncy or dependency cases), medical records (common to malpractice cases) and wills (common to probate cases), are often protected by court rules. PII in any document or case type is often protected although the definitions or what constitutes PII differs from court to court.
? Action on specific suggestions previously submitted by Intresys:
o #1 - file requesting indigent status OR request waiver first before filing
No strong opinion, so no for now
o #2 - Judge Action vs. Court Action
No
o #3 - Fee calculations
No
Use get fees request
Could also use parameters on code tables
o #4 - Document sizes (pages)
Add MaximumAllowedAttachmentPages
o #5 - Document Types
Use parameter/column in RegisterActionDescriptionText code table
o #6 - Service
Is filer allowed to serve?
? Required
? Option
? No applicable
Need to research options/use cases
o #7 - Access to Docs
Security and access is complex
This needs more research
No expected impact on court policy
o #8 - Sealing
Combine this for further consideration with other security issues (assigned to Dallas)
o #9 - Appearance
no
o #10 - Reminders
no
o #11 - Tech side aspects
No changes to this for now
11.1 development time policy
11.2 Runtime namespace
11.3 Courts
Referenced Items
|
|
OASIS LegalXML ECF TC - efiling business configuration requirement examples-1-Serguei.docx (17K) | 2012-12-07 | Download | View Details |
|
|
OASIS LegalXML ECF TC - efiling business configuration requirement examples-dhp.docx (20K) | 2012-12-07 | Download | View Details |