Data Format. The Contractor shall provide data to the DMHA in a format designated by the DARMHA manual that includes, but may not be limited to, data and computations of the ANSA (Adult Needs and Strengths Assessment), CANS (Child and Adolescent Needs and Strengths) or other instrument for provider assessment of individual functional impairment required by the State.
Data Format. Registry Operator may change the format of the Data from time to time, in a manner that will not materially change the content of the Data (but which may affect other aspects of the content of the file, including, without limitation, comments, spacing and ordering), provided that the format will be compliant with standard Master File format as originally defined in XXX 0000, Section 5. Registry Operator will provide notice via Registry Operator’s website not less than sixty (60) days prior to any such change.
Data Format. File layouts must provide for “fixed-width” fields using the ASCII character set. Delimited data is also acceptable, provided that FMC’s consent to the delimiter must be obtained. If comma-delimited fields are being submitted, then all text fields must be enclosed in double quotes.
Data Format. Submeter MDMA must satisfy PG&E’s EV Submetering Pilot Phase 1 Data Reporting and Transfer Requirements, attached hereto as Attachment 2.
Data Format. Any data to be imported must be given to CircuiTree personnel in one of the following formats: Comma separated file, Excel spreadsheet, Access data file, Microsoft SQL backup file, or other formats to be approved by Company on a case-by- case basis.
Data Format. All parties to this MOA will commit to acceptance of the Minimum Data Elements (MDE), a format developed and agreed to by the ICLN Network Coordinating Group, as a common format to enable transmission of data among network program offices, as necessary, during the conduct of a joint response within the ICLN environment. Decisions on the specific data to be exchanged via the MDE format will be determined by the parties to this MOA at the time of a joint incident response and documented in the ISDSA. The data exchanged will be in compliance with all applicable laws and regulations, especially those addressing privacy, and with policies of the D/As participating in the joint response. Any data exchanged under this MOA, where the transferring D/A does not own or possess unlimited intellectual property rights over such data, will be marked with appropriate restrictions prior to such transfer. Data Quality Reconciliation of data duplicates, discrepancies, or other quality issues will be in accordance with the process agreed upon and documented in the ISDSA.
Data Format. The Contractor must submit encounter and subcapitation data electronically over POSNet using file transfer protocol (FTP). Subcapitation data reporting currently being submitted via paper reports will, at a future date, be required to be transmitted electronically. Encounter data files must be provided in ASCII text format using the appropriate format for the five different record types.
Data Format. Seller shall provide complete and properly formatted Subscriber data as specifically set forth on Exhibit D.
Data Format. Contractor agrees to submit data in an electronic or tape format that conforms to the State's specifications. The precise nature of these specifications is included in the Encounter Data Business Design including updates and associated HIPAA companion guides.
Data Format. The CHC-MCO must submit Encounter Data to the Department pursuant to protocols to be established by the Department.
