Part 4 - Iowa Medicaid Enterprise

RFP MED-12-001 | Technical ProposalIowa Medicaid Enterprise System Service Procurement | MMIS and Core MMIS Operationsobservation identifiers, names, and codes (LOINC), as received from external data sources. Figure 7-17shows the supported code set interfaces along with the source of the dataset.Code Set Available From Code Set Available FromHCPS CMS National Drug Code by Format Federal Drug Listing Branch HFN-315ICD-9-CMNational Uniform Billing CommitteeCodesU.S. National Center forHealth StatisticsTreatment CodesNational Uniform Billing Committee Remittance Remark Codes Washington Publishing CompanyNational Drug Code First Data Bank CLIA Number CMSAmerican Dental AssociationCodes (CDT-4)American Dental Association NUBC Condition Codes National Uniform Billing CommitteeClaim Adjustment Reason Washington Publishing Company NUBC Occurrence Codes National Uniform Billing CommitteeHealth care Financing Administration(HCFA) - Code ListsDiagnosis Related Group NumberCMS NUBC Occurrence Span Codes National Uniform Billing CommitteeSuperintendent of Documents -U.S. Government Printing OfficeNUBC Value CodesCMSNational Uniform Billing CommitteeAdmission Source Code National Uniform Billing Committee UB92 Bill Type Code National Uniform Billing CommitteeAdmission Type Code National Uniform Billing Committee UB92 Facility Type Code (Two Digits) National Uniform Billing CommitteeUniform Billing Claim Form Bill Type National Uniform Billing Committee UB92 Revenue Codes National Uniform Billing CommitteePlace of Service CMS Provider Taxonomy Codes Washington Publishing CompanyPatient Status CodeNational Uniform Billing CommitteeLogical Observation Identifier Namesand Codes (LOINC)Regenstrief Institute of Health careFigure 7-17. Supported Interfaces Along with Source. The eCAMS reference business process area withreusable standard interfaces.7.13.2 Meeting and Maintaining Regulatory ComplianceRFP Section 5.13, Requirement bOur solution will provide a platform that will enable the Department to adhere to any subsequent changesin HIPAA regulations, without a major re-haul to the MMIS. eCAMS provides large, configurableoptions to adhere to ever-changing needs. Though these configurable items will need to be tested in theuser acceptance testing environment, and some new and major regulatory items may requirecustomization to MMIS, the eCAMS platform will provide the ability to adapt to the changes toregulations in a systematic way with the goal of ensuring business continuity.Team Noridian serves on the Workgroup for Electronic Data Interchange (WEDI), and the HIPAAStrategic National Implementation Process (SNIP) Transactions and Code Sets Workgroups. TeamNoridian also works directly with CMS on the Technical Advisory Group (TAG). Such involvement iscritical, allowing us to stay abreast of industry initiatives and changes, such as changes to the BusinessAssociate Agreement and security requirements due to the HITECH Act, ensuring our systems andactivities support ongoing HIPAA compliance.Team Noridian is in the process of upgrading to 5010 transactions to meet the compliance date of January1, 2012. eCAMS has the ability to load and store the ICD-10-PCS code set in the database. The referencebusiness process area in eCAMS is responsible for maintaining reference file data for code sets receivedfrom external data sources.eCAMS currently complies with the regulatory requirements for privacy, security, and standardtransactions including the HIPAA Security, HIPAA Administrative and Simplification Provisions forPrivacy and Security, the HITECH provisions, the Department's Information Technology Security Policy,the Department's privacy policies, and all stated and federal requirements to ensure the privacy andsecurity of the Department's Medicaid data.7 | 60