NIEM Executive Briefing TRAINING.

NIEM Executive Briefing TRAINING

Why Niem?

Why NIEM? Problem Lack of standards leads to a decreased level of information sharing and increased costs associated with information exchange development. Solution The National Information Exchange Model (NIEM) NIEM is a federal, state, local, tribal and private initiative to increase information sharing between organizations. NIEM includes a data model from which organizations can establish information sharing specifications. NIEM adoption leads to cost avoidance, enhanced mission capabilities and low total cost of ownership.

Identification of large scale, complex processes
Creation of the standardized exchange Governance and adoption of the exchange Selection based on number of stakeholders and potential for reuse Complexity increases with numbers of entities involved Benefit increases with numbers of implementations

What is Niem?

Niem IS… Community Technical Framework Support Framework
NIEM is a community-driven, government-wide, standards-based approach to exchanging information. Diverse communities can collectively leverage NIEM to increase efficiencies and improve decision-making. It is available to everyone, including both public and private organizations. NIEM includes a data model, governance, training, tools, technical support services, and an active community to assist users in adopting a standards-based approach to exchanging data. Community Technical Framework Support Framework Formal Governance Processes Online Repositories Mission-Oriented Domains Self-Managing Domain Stewards Data Model XML Design Rules Development Methodology Predefined Deliverables (IEPD) Tools for Development and Discovery Established Training Program Implementation Support Help Desk & Knowledge Center There are three different aspects to the value of NIEM: community involvement, a technical framework that helps define data structures, and a support framework that helps from an implementation perspective. NIEM is available to everyone. The NIEM community spans federal, state, local, tribal, international, and private sector entities. It is this diverse group of people who drives NIEM forward. NIEM was built by the community, for the community. Community: Information exchange partners have a business need to come together to exchange information and NIEM is the mechanism that allows them to do so. NIEM provides formalized governance that allows self-organized, self-managed communities to proactively address their specific needs. This ensures information exchanges are flexible and adaptable over time. NIEM governance provides rigor in defining rules for information exchange, while at the same time encouraging diverse communities to define their own data requirements. Technical Framework: NIEM consists of a technical framework, which is what most people associate with NIEM. This includes a data model–the common vocabulary, rules and methodologies around the creation and use of the data model, and a standardized exchange development approach which can be repeated and reused by everyone. Support Framework: NIEM provides extensive support for information exchange. This includes tools to support development, discovery, and reuse of information exchanges. In addition, there is training available, technical support through a help desk, and a searchable online knowledgebase.

COMMONLY FORMATTED DATA
Standardizing Data Scope-of-NIEM COMMONLY FORMATTED DATA LEGACY DATABASES INTERFACE INTERFACE LEGACY DATABASES Translation NIEM intentionally does not address standardizing data inside legacy systems. NIEM serves as a translation layer (providing a common understanding) between and across disparate systems.

Repeatable, Reusable Process
How niem works Common Language (Community-driven Data Model) Repeatable, Reusable Process (Information Exchange Development Lifecycle) There are two concepts that can be used to help illustrate NIEM. The data model is the collective representation of the communities that leverage NIEM. This is where NIEM provides a consistent set of data definitions and a structure to define the relationships between them. The diverse communities that leverage NIEM collaboratively govern the data model. The NIEM Information Exchange Development Lifecycle, commonly referred to as the Information Exchange Package Documentation (IEPD) Lifecycle provides a repeatable, reusable process for using NIEM to define information exchange. Built and governed by the business users at federal, state, local, tribal, international, and private sectors

model overview Words are to a dictionary as elements are to a data model. Think of the NIEM data model as a mature and stable data dictionary of agreed-upon terms, definitions, and formats independent of how information is stored in individual agency systems. The data model consists of two sets of closely related vocabularies: NIEM core and individual NIEM domains. Now, let’s take a look at the NIEM data model. Words are to a dictionary as elements are to a data model. The NIEM data model provides common, agreed-upon terms, definitions, and formats independent of how information is stored in individual systems. It consists of two related vocabularies, NIEM core and individual NIEM domains. NIEM core consists of data elements that are commonly understood across domains. It’s governed jointly by all NIEM domains. A NIEM domain represents both the governance and model content oriented around a community’s business needs. A NIEM domain manages their portion of the NIEM data model and works with other NIEM domains to collaboratively identify areas of overlapping interest. As a community member of NIEM, your involvement could span one or more NIEM domains. You also don’t need to be aligned to a formal NIEM domain to use NIEM, as NIEM’s core elements are universal and applicable to many or all. Future domains are added by NIEM as necessary, based on an established business need. What are the NIEM data components? NIEM core NIEM domains

The data components The data model consists of two sets of closely related vocabularies: NIEM core and individual NIEM domains. NIEM core includes data elements commonly understood across all NIEM domains, such as person, activity, location, and item. NIEM domains contain mission-specific data components that build upon NIEM core concepts. Let’s take a look at a basic example of the NIEM core and the NIEM domain relationship. All domains would agree that a person has a name and date of birth—commonly agreed-upon characteristics of a person. Some communities have a business need to extend the definition of a person based on their information exchange requirements. For example, within the Justice community, they need the flexibility to extend Person to capture additional information of a Subject, who may be involved or suspected of being involved in an incident or criminal activity. In addition, a name and date of birth are not sufficient to identify a Subject. They also may require biometric identifiers such as fingerprints, scars, or tattoos to verify their identity. Another commonly used core element is Activity. For example, the Emergency Management Domain may need to extend Activity such as an alarm event to include additional identifiers such as dispatch agency and response action, to create context.

Basic overview: Niem in action
NIEM is not a system or database; it does not specify how to transmit or store data. NIEM is a standard way of defining the contents of messages being exchanged. It’s important to note that NIEM is NOT a system, database, software, or the actual exchange of information. Rather, NIEM provides the common vocabulary so that organizations can speak the same language to quickly and effectively exchange meaningful data. NIEM is the standard way of defining the contents of messages being exchanged. For example, two organizations identify the need to exchange information. Their information, though similar, is defined differently. Both organizations have a concept of a person’s last name. One refers to it as “last name” while the other refers to it as “surname”—the same concept, but different defining term. Using NIEM, the organizations are able to come together to agree on a common vocabulary. When additional organizations need to be added to the information exchange, the initial NIEM exchange can be reused, saving time and money. This allows diverse communities to collectively leverage a common vocabulary and exchange development tools irrespective of technologies, increasing both efficiencies and improving decision-making.

NIEM is not… Not only Federal government
Includes state, local, and tribal Includes vertical, horizontal, and diagonal exchanges Not a replacement for interagency agreements NIEM provides a framework for building exchanges within those agreements Not a database schema Not just a data dictionary Not a programming language

True or False? Knowledge Check NIEM is not a data model.
NIEM is community-driven. Future NIEM domains are added based on established business needs. NIEM specifies how you must transmit and store your data.

HOW NIEM GOT STARTED

The beginning of NIEm: part 1
To understand how NIEM began watch this short video. Note to instructor: Play video to class Direct video file is available (if needed) Please click play to begin.

The beginning of niem: Part 2
Parallel to work that was being done within the justice community, was the stand-up of the U.S. Department of Homeland Security—which was also beginning to work toward data standardization. Collaborative efforts by the justice and homeland security communities—to produce a set of common, well-defined data elements for data exchange development and harmonization—led to the beginnings of NIEM. Coinciding with the Justice community’s work to standardize data was the stand-up of the U.S. Department of Homeland Security—which was also beginning to work toward data standardization. Collaborative efforts by the Justice and homeland security communities to produce a set of common, well-defined data elements for data exchange development and harmonization led to the beginnings of NIEM.

To Recap: History of niem
Started by a handful of organizations supporting state and local government, NIEM is a community-driven, government-wide, standards-based approach to exchanging information. Diverse communities can collectively leverage NIEM to increase efficiencies and improve decision-making. Built upon GJXDM's success and lessons learned, NIEM was launched in April 2005 by DHS and DOJ. HHS joined as the third primary sponsor in 2010. By joining forces to overcome the challenges of information exchange across government boundaries, a grassroots effort called the Global Justice Information Sharing Initiative was established. The Department of Homeland Security (DHS) was established November 25, 2002. The Global Justice XML Data Model (GJXDM) was announced in April 2003. NIEM continues to mature with new communities and partners… Started by a handful of organizations supporting state and local government, NIEM is a community-driven, government-wide, standards-based approach to exchanging information. Diverse communities can collectively leverage NIEM to increase efficiencies and improve decision-making.

SAMPLING OF INFORMATION SHARING EVOLUTION
OCT 2001 DEC 2004 2004 to 2005 2007 MAY 2012 Critical Infrastructure Protection in the Information Age Intelligence Reform and Terrorism Prevention Act Sharing of Terrorism Related Information The National Strategy for Information Sharing Federal Information Technology Shared Services Strategy Homeland Security Act Homeland Security Information Sharing Implementing Recommendations of the 911 Commission Act DOD Information Sharing Strategy National Strategy for Trusted Identities in Cyberspace NOV 2002 JULY 2003 2007 2007 APRIL 2011 Legislative Act Executive Order

True or False? Knowledge Check
NIEM is only used by federal government. NIEM can be used government-wide. U.S. state and local organizations needed something to overcome the challenges of exchanging information across boundaries—this led to what is now NIEM. Statement 1: False Statement 2: True Statement 3: True

HOW NIEM Works

Please click play to begin.
NIEM Simplified Note to Instructor: Play video to class. Direct video file is available (if needed). Please click play to begin.

Who uses niem?

Interactive Map on NIEM.gov
Who uses niem? Interactive Map on NIEM.gov NIEM.gov/map NIEM is in the public domain and available for any agency or organization to use. We can track use of NIEM across the majority of federal agencies and 50 states, as well as internationally. Often, the NIEM program does not know who is using it unless we hear someone talking about it! “Are You NIEMified?” is a community-building campaign to track NIEM adoption. NIEM is available to any agency or organization. We can track use of NIEM across the majority of federal agencies and 50 states, as well as internationally. Often, the NIEM Program Office doesn’t know who’s using NIEM unless we hear them talking about it! “Are you NIEM-ified?” is a community building campaign used to track NIEM adoption. Visit the Interactive Map at NIEM.gov/map to learn more. NIEMified (adjective): Indicating an entity such as a project or organization that has implemented a NIEM-based exchange to advance their mission.

NIEM’s Benefits & Impacts

NIEM Provides… Which Leads To Collaboration Consistency Development
Support Brings stakeholders together through reuse and community engagement Provides a standardized framework and mature governance Supplies tools to aid in discovery and creation of exchanges Provides technical assistance and training Which Leads To Lower Development Costs Collaboration: NIEM provides a forum for collaboration to accelerate information exchange development and reuse. Consistency: NIEM provides a common vocabulary, standardized framework and mature governance that promotes re-use and consistency of structure and documentation across stakeholders. Development: NIEM provides tools to support development, discovery, and re-use of information exchanges. Support: NIEM provides support in the form of training, a helpdesk, governance processes, and technical assistance to help answer NIEM related questions. In addition, NIEM is driven by a large, diverse, and actively engaged stakeholder community that can offer support for issues ranging from governance to exchange development. All of this is in support of efforts to lower the barrier to NIEM understanding and adoption. In addition, NIEM is driven by a large, diverse, and actively engaged stakeholder community that can offer support for issues ranging from governance to exchange development Each of these concepts leads to benefits, such as enhanced mission capabilities and organizational cost avoidance from reduced development and maintenance costs. Specifically: Lower Development Cost: Organizations that implement NIEM can leverage a repeatable process to shorten exchange development time. In addition, previously developed exchanges can be completely or partially reused as accelerators for development. Enhanced Mission Capabilities: By increasing interoperability between organizations, NIEM can help agencies enhance services across key mission and function areas. Common Vocabulary: NIEM helps to eliminate confusion associated with different data definitions across organizations by providing a consistent set of definitions for everyone to use. Reduced Maintenance Costs: Organizations can reduce maintenance costs by reusing common data exchange objects and messages; by utilizing standardized processes, development, and implementation methodologies; and by leveraging economies of scale savings realized by shared governance, training, and technical assistance. Enhanced Mission Capabilities Common Vocabulary Reduced Maintenance Costs

NIEM: A place to start Source A Source B Rocket Spaceship
NIEM provides a common vocabulary as well as information exchange development tools and guidelines that diverse communities collectively leverage to increase efficiencies and improve decision-making. Whether you are a police chief, port security director, financial regulator, child welfare worker, or physician—anyone who has a complex problem to solve that crosses organizational, sector, function, and/or geographic boundaries—you need information. However, much of it could be maintained by other organizations. We need a way for our disparate computer systems to “speak the same language.” For example, if I say “rocket” and you say “spaceship,” we may mean the same thing, but we don’t have a way to tell our computer systems to treat these words as having the same meaning. NIEM provides a consistent starting point. NIEM provides a common vocabulary as well as information exchange development tools and guidelines that diverse communities collectively leverage to increase efficiencies and improve decision-making. Whether you are a police chief, port security director, financial regulator, child welfare worker, or physician—anyone who has a complex problem to solve that crosses organizational, sector, function, and/or geographic boundaries—you need information. However, much of it could be maintained by other organizations. We need a way for disparate computer systems to “speak the same language.” For example, if I say “rocket” and you say “spaceship,” we may mean the same thing, but we don’t have a way to tell our computer systems to treat these words as having the same meaning. Rocket Source A Spaceship Source B

Benefit: Common Language
Organization A Organization B When using NIEM, you only need to “speak” two languages—your own and NIEM. When developing information exchanges, agreeing to a common set of data elements and definitions is a frequent challenge. NIEM was built to address this challenge. For example: a previous data exchange included four partner organizations. As one of the four partner organizations, you would have had to connect to three different systems and negotiate a common language between them. Now, it’s just your language and NIEM. NIEM provides this common vocabulary, thus a place to start—saving time and money. NIEM: Common Language Let’s take a look at a benefit of NIEM: Common Language. When using NIEM, you only need to “speak” two languages—your own and NIEM. When developing information exchanges, agreeing to a common set of data elements and definitions is a frequent challenge. NIEM was built to address this challenge. For example, a previous data exchange included four partner organizations. As one of the four partner organizations, you would have had to connect to three different systems and negotiate a common language between them. Now, it’s just your language and NIEM. NIEM provides this common vocabulary, thus a place to start—saving time and money. Organization C Organization D

Benefit: Interoperability
NIEM provides a consistent starting point for creating information exchanges so that the sender and receiver of information share a common, unambiguous understanding of the meaning of that information. This ensures that information is understood and carries the same consistent meaning across various communities, irrespective of technologies, allowing interoperability to occur. Interoperability is a characteristic of information systems that use NIEM to exchange information—NIEM allows for the quick and easy addition of exchange partners, irrespective of technologies being used. Another benefit of NIEM is interoperability. NIEM provides a consistent starting point for creating information exchanges, so the sender and receiver of information share a common, unambiguous understanding of the meaning of that information. This ensures that information is understood and carries the same consistent meaning across various communities, irrespective of technologies, allowing interoperability to occur. Interoperability is a characteristic of information systems that use NIEM to exchange information—NIEM allows for the quick and easy addition of exchange partners, regardless of technologies being used.

Benefit: Community collaboration
Mission challenges and opportunities are too large for any one organization, sector, unit, or nation to take on alone—they must be addressed collaboratively. NIEM is a data model used to facilitate information exchange among partners in various disciplines, government-wide. With NIEM, information exchange partners come together to identify what data needs to be exchanged, then agree to exchange that data in a standards-conformant manner. The use of NIEM accelerates collaboration in and across communities. Mission challenges and opportunities are too large for any one organization, sector, unit, or nation to take on alone—they must be addressed collaboratively. NIEM is a national data model used to facilitate information exchange among partners in various disciplines, government-wide. It’s about achieving interoperability: partners coming together to identify what data needs to be exchanged, then agreeing to exchange that data in a standards-conformant manner. The use of NIEM accelerates collaboration in and across communities. For example, each jurisdiction has a different definition of a warrant. Collaboratively, the Justice community came together to define the minimum requirements for a warrant. This exchange can then be used verbatim or with modification based on local requirements. This helps to drive consistency of implementation nationwide, which enables the seamless exchange of warrant data regardless of location, variation of format, and how the data is stored. Note to instructor: Map and Search Warrant image correlates to the below example. For example: each jurisdiction has a different definition of a warrant. Collaboratively, the justice community came together to define the minimum requirements for a warrant. This exchange can then be used verbatim or with modification based on local requirements. This helps to drive consistency of implementation nationwide which enables the seamless exchange of warrant data regardless of location, variation of format, and how the data is stored.

Benefit: Reuse of an exchange
Since NIEM exchange developers follow the same technical framework, they can borrow from and reuse each other’s work. Because the NIEM data model is composed of data elements that cross sectors, functions, and geographic boundaries, an exchange developed for one organizational business requirement could be “reused,” partially or fully, for a different need within or by another organization. Commonwealth of Virginia Developed an Exchange Child Welfare Information Exchange Element 1 Element 2 Element 3 Element 4 Element 5 State of New Jersey Reused the Exchange Data Specific to Child Welfare in NJ Element 6 Element 7 Element 8 x Reuse Since NIEM exchange developers follow the same technical framework, they can borrow from and reuse each other’s work. Because the NIEM data model is composed of data elements that cross sectors, functions, and geographic boundaries, an exchange developed for one organizational business requirement could be “reused,” partially or fully, for a different need within, or by another organization. This helps to reinforce the national collaborations that strengthen NIEM’s governance structure. For example, as this image shows, the Commonwealth of Virginia developed a Child Welfare Information Exchange containing specific elements. A month later, the state of New Jersey decided to reuse Virginia’s Child Welfare Exchange. They reused the exchange, taking only the elements specific to their needs and then added additional elements specific to child welfare in New Jersey. Remember, words are to a dictionary what elements are to a data model. Using this analogy, we can see how one organization—in this case, the state of New Jersey—could reuse an existing NIEM-based exchange

How is niem governed?

Domain Governance NIEM domains are communities of interest that are formally established with an executive steward to officially manage and govern a portion of the NIEM data model. NIEM domains contain mission-specific data components that build upon NIEM core concepts. NIEM domains are communities of interest that are formally established with an executive steward to officially manage and govern a portion of the NIEM data model. NIEM domains contain mission-specific data components that build upon NIEM core concepts A NIEM domain represents both the governance and model content oriented around the business needs of a community. A NIEM domain manages their portion of the NIEM data model and works with other NIEM domains to collaboratively identify areas of overlapping interest. NIEM core is governed jointly by all NIEM domains and includes elements common across many domains.

Communities of Interest
A community of interest (COI) is a group of people who share a common concern, set of problems, or interest in a topic. Within the context of NIEM, COIs come together based on a common need to exchange information in order to advance their missions—they need to have a shared vocabulary for the information they exchange. COIs can be composed of multiple NIEM domains or can be a subset of a single domain. Let’s take a look at what role communities of interest play. A community of interest (COI) is a group of people who share a common concern, set of problems, or interest in a topic. Within the context of NIEM, COIs come together based on a common need to exchange information in order to advance their missions—they need to have a shared vocabulary for the information they exchange. COIs can be composed of multiple NIEM domains or can be a subset of a single domain.

Example of a NIEM domain’s cross-jurisdictional governance structure:
NIEM Governance Example of a NIEM domain’s cross-jurisdictional governance structure: The NIEM Children, Youth, and Family Services (CYFS) domain supports timely, complete, accurate, and efficient information sharing to improve outcomes for children and youth whose circumstances make them particularly vulnerable. The following entities make up NIEM’s governing structure: NIEM Executive Steering Council (ESC) is NIEM’s decision-making body regarding membership, funding requirements, program or technical direction, personnel appointments, and other organizational decisions. NIEM Program Management Office (PMO) and Executive Director resources execute ESC’s vision of NIEM while managing the day-to-day operations of NIEM. NIEM Technical Architecture Committee (NTAC) is a national committee that defines the technical architecture associated with NIEM development and implementation. It also develops, implements, and maintains the technical specifications for the NIEM community. NIEM Business Architecture Committee (NBAC) is a national committee with membership from all NIEM domains. NBAC’s primary responsibilities include harmonization and issue resolution across NIEM core and individual domains. NIEM Domain Governance is another facet of the overall NIEM Governance Model. An example of a NIEM domain is the Children, Youth, and Family Services (CYFS) domain. This domain supports timely, complete, accurate, and efficient information sharing to improve outcomes for children and youth whose circumstances make them particularly vulnerable. Within the CYFS domain, a governance committee exists. This committee stewards the domain and brings together communities of interest to identify information sharing requirements. The CYFS communities of interest include but are not limited to: Juvenile Justice, Child Welfare, Child Support Enforcement, and Courts. End users across the communities develop and implement NIEM conformant information exchanges as well as provide information sharing requirements to the Governance Committee.

Who Steers NIEM?

NIEM DOmains Emerging Domains Agriculture Cyber Health Human Services
Current Domains Biometrics CBRN CYFS Emergency Management Immigration Infrastructure Protection Intelligence International Trade Justice Maritime MilOps Screening Emerging Domains Agriculture Cyber Health Human Services

Domain Governance Domain Executive Steward Justice
Global Justice (State & Local) Screening DHS Screening Coordination Office Immigration DHS/ICE & USCIS CBRN DHS/DNDO Maritime DOD/DON/MDA Cyber DHS/NPPD/CS&C Family Services HHS/ACFS & DOJ Emergency Management DHS/FEMA, DHS/S&T (state & local) Infrastructure Protection DHS/NPPD International Trade DHS/CBP Biometrics DHS/NPPD, DOJ/FBI, DOD, NIST *Health HHS/ONC & HHS/OCIO *Human Services HHS/ACFS & NYC/HHS *Financial (Budget, Planning, Accountability, Grants) TBD (currently HHS, OMB)

NIEM Value Proposition

Standards-Based Interoperability
U.S. National Information Sharing Programs Unifying the SBI Architecture Common Vocabulary and Extensibility - NIEM (XML) Service Oriented Architecture (SOA) – OASIS Framework and Global Reference Architecture (GRA) Federated Identity/Privilege Management N-DEx (and other FBI CJIS programs) Nationwide SAR Initiative Terrorist Screening Center Hit Confirmation Gang Information Sharing Human Trafficking

Value Proposition - Standardization
The formalization of NIEM as a standard enables: Community of Support Structured Approach NIEM Practitioners can leverage information sharing practitioners to decrease development time for exchanges and increase conformance Repeatable approach that decreases the inconsistencies and duration of development Value to Organizations: A larger community working with and developing agreed upon semantics combined with a structured approach can increase data compatibility between agencies, cost avoidance by building reusability of exchanges, and ease the development of information exchanges.

Value Proposition - Interoperability
NIEM facilitates interoperability through the use of: Common Language and Vocabulary Agnostic Implementation Eliminates confusion by providing consistency of data definitions between agencies NIEM does not dictate how agencies’ systems are implemented, but enables these systems to work together Value to Organizations: Interoperability is the ability of many diverse systems to work together. By increasing interoperability between mission areas and jurisdictions, government can enhance its services across key functional areas such as law enforcement and emergency response.

Value Proposition - Reusability
The reuse of IEPDs, in part and whole, within NIEM will: Decrease Development Time Increase Consistency Decrease the development time for information exchanges that use similar sets of data Allows practitioners to increase the level of consistency in data definitions across their information exchanges Value to Organizations: Reuse through NIEM can help organizations avoid costs associated with the development and maintenance of information exchanges, leading to an increased budget available to spend in mission areas

NIEM Success Story

ON pharmaceutical drug monitoring
NIEM Impact ON pharmaceutical drug monitoring The Standard Prescription Monitoring Information Exchange

Pharmaceutical Drug Monitoring
Prescription Drugs (15.1 million) Cocaine (5.9 mil.) Hallucinogens (4 mil.) Inhalants (2.1 mil.) Heroin (.3 mil.) NATIONWIDE DRUG ABUSE From , million Americans abused prescription drugs. That’s more than cocaine, hallucinogens, inhalants, and heroin COMBINED. During the same period, there was a 150% INCREASE in prescriptions written for controlled substances. The brand cost of 4 mg of Dilaudid is $88.94 per The street value for the same amount is $10,000. The demand is REAL.

1 in 5 teens are abusing prescription drugs to get high. 40% of teens believe that prescription drugs are safer than illegal drugs. 29% of teens believe that prescription pain relievers are not addictive. “You have young people getting pills for free from the homes of family members and friends.” - John Walters, former White House drug czar

prescription drug monitoring challenges
Lack of Resources Lack of interoperability Low utilization Difficult to use/not integrating Different access requirements

> 0 – .9% 1 – 2.9% 3 – 3.9% 4 – 7% > 19% Where CA Prescriptions Really Go Pharmaceutical drug abuse is crossing state lines as offenders realize the gap in interstate reporting. As this map shows, less than 20% of prescriptions written in California were written for California residents. There are three facets to the problem—misuse, abuse, and diversion—and three players—prescribers, dispensers, and patients. Prescription drug monitoring is the coming together of pharmacy boards, health agencies, and law enforcement to monitor drug diversion.

As diversion of prescription controlled substances and the abuse involving these drugs continues to escalate, how can we improve interstate monitoring of drug use? How do we enable prescription drug monitors to see across state lines?

Before NIEM, there was large gap in interstate reporting. As abuse and diversion escalate, law enforcement and health practitioners need a standardized, scalable solution to share patient drug history. The Standard NIEM Prescription Monitoring Program Information Exchange assists prescribers, health agencies, and law enforcement in identifying potential abuse and diversion.

What were the benefits of using NIEM?
Process provides orderly approach to reaching consensus Non-proprietary, third-party focal point Helps sharpen the focus on any issues that may frustrate achievement of the goal of information sharing Exchange partners retain control of databases Each transaction commences from non-interoperable starting point NIEM data models tend to be scalable No need for one-off, point-to-point data modeling NIEM utilizes “modern” self-describing XML NIEM tooling and support well-established

StaTuS of PDMPs The Prescription Monitoring Program uses NIEM to empower connections: 1,600,000 Prescribers 284,000 Pharmacists 73,000 Pharmacies 54 Boards of Pharmacy 18,000 Law Enforcement Agencies 11,000 Substance Addiction Treatment Programs 140 Consumer Protection Agencies This is a solution that the 50 states, Canada, and Mexico can leverage. This map identifies the status of Prescription Drug Monitoring Programs (PDMPs)

NIEM Program Updates

NIEM 3.0 NIEM 3.0 release schemas are available for use
Some tools currently work with NIEM 3.0 SSGT NIEM Wayfarer Pending NIEM 3.0 normative documents NIEM 3.0 Naming and Design Rules (NDR) NIEM Model Package Description (MPD) Specification Conformance Specification Conformance Target Attribute Specification All are being worked on furiously Effects some tool support NIEM-UML Profile

NIEM 3.0 Changes New content Existing content harmonized
Objects and references merged Augmentations improved, easier to use Code lists improved, easier to modify Support for local terminology More powerful ways to define conformance Improved infrastructure Intelligence Community Metadata Standard for Information Security Marking (IC-ISM) support

NIEM-UML Profile New way to use the NIEM No XML schema
Currently works with NIEM 2.1 NIEM 3.0 functionality is waiting on NIEM 3.0 Naming and Design Rules (NDR) release

Fed CIO Council NIEM Report & NASCIO NIEM Policy Issuance

Strategic Next Steps Increasing NIEM international adoption (Canadian and Mexican cross-border initiatives, and Europe) Broadening NIEM state & local implementations (including support through new Homeland Security grants specifications) Developing enabling standards for NIEM and the Information Sharing Environment (Object Management Group and OASIS engagement) Institutionalizing a common privacy & security framework On-boarding new and strengthening existing NIEM Domains Expanding governance to support other Federal, State, Local and International agencies

Just Part of the Picture
The National Information Exchange Model (NIEM) provides a justice standard information model for message content. NIEM does not address messaging, addressing, reliability, security, etc required for sharing information between systems. Translation Scope-of-NIEM INTERFACE LEGACY DATABASES COMMONLY FORMATTED DATA

NIEM Implementation

The iepd lifecycle Review background, assess resource impact, understand business context, and identify information exchange business scenarios Selected information exchange scenario is further elaborated to understand and document the business context and data requirements Create an exchange content model based on information exchange requirements. The Exchange Content Model is then mapped to NIEM. Create a set of exchange-specific NIEM conformant XML schemas that implement the exchange content model created for the exchange IEPD Lifecycle The IEPD lifecycle consists of six phases: Scenario Planning: During the Scenario Planning phase, you review background information related to your information exchange, assess resource impact, understand business context, and identify information exchange business scenarios. Analyze Requirements: During the Analyze Requirements phase, the selected information exchange scenario is further elaborated to understand and document the business context and data requirements. Map and Model: During the Map and Model phase, you create an exchange content model based on your information exchange requirements. The exchange content model is then mapped to the NIEM data model. Build and Validate: During the Build and Validate phase, you create a set of exchange-specific, NIEM conformant XML schemas that implement the exchange content model created for the exchange. Assemble and Document: During the Assemble and Document phase, you prepare and package all related files for the IEPD into a single, self-contained, self-documented, portable archive file. Publish and Implement: During the Publish and Implement phase, you implement the IEPD into production and publish the IEPD for search, discovery, and reuse. Prepare and package all related files for the IEPD into a single self‐contained, self-documented, portable archive file Publish the IEPD as well as implement the IEPD into production for search, discovery, and reuse

Implementing your NIEM Exchange
NIEM Does: Define XML instance document format and structure. NIEM Does Not: Define implementation specifications. Specify how a document is transmitted, but may employ encryption, Efficient XML Interchange (EXI), etc. When implementing your NIEM exchange, it is important to note the following: NIEM defines XML instance document format and structure. NIEM does NOT define implementation specifications or specify how a document is transmitted, but it may employ encryption, Efficient XML Interchange (EXI), etc.

Example: Implementing NIEM
There are many ways to implement NIEM. NIEM conformant exchanges are implemented based on business needs and vary as a result. Two common examples include: Message Queue: An organization can store NIEM conformant XML instances within a message queue during its response to a stakeholder’s information request service. Web Services: An organization can embed a NIEM conformant schema into a new or existing Web Service and perform an electronic transfer with one or more exchange partners potentially through a Service Oriented Architecture (SOA) based environment. Let’s discuss the ways to implement NIEM. NIEM conformant exchanges are implemented based on business needs and vary as a result. Two common implementation examples include: Message queue: An organization can store NIEM conformant XML instances within a message queue during its response to a stakeholder’s information request service. Web services: An organization can embed a NIEM conformant schema into a new or existing web service and perform an electronic transfer with one or more exchange partners, potentially through an Service Oriented Architecture (SOA)-based environment. Let’s discuss an SOA based implementation example.

Example: SOA Implementation
Service Oriented Architecture (SOA) is an architectural style whose goal is to achieve loose coupling among interacting software agents. Standards-Based: NIEM provides the standard for data layer interoperability among services in SOA NIEM can be used to standardize and structure the messages passed between services in SOA NIEM can decrease development time of new services in SOA through reuse of similar IEPDs Service Oriented Architecture (SOA) is an architectural style whose goal is to achieve loose coupling among interacting software agents. NIEM provides the standard for transferring information between services in service-oriented architectures. An SOA environment often uses an enterprise service bus to host the services, to control the access, and to ensure interoperability to these services. Organizations can leverage NIEM as a standard for communications within all services in their SOA environment, which increases the consistency in the implementation of services and decreases the development costs associated with services. Existing IEPDs for services in an SOA environment can be reused in the development of new services, which contributes to increased consistency and decreased developmental cost.

Considerations for Implementation
Systems on either side of the exchange can use different implementation architectures (i.e. different programming languages, operating systems) All participants in an information exchange must agree on the definition and structure for the data in the exchange—NIEM provides this standardization IEPD Lifecycle should be used to guide development of NIEM conformant information exchanges to make sure all of the necessary artifacts are created Elements already defined within NIEM should be used whenever possible; exchange elements outside of or created to fill requirements not covered in NIEM should also be reused whenever possible ARCHITECTURE CONSISTENCY DEVELOPMENT You can learn about and develop best practices in NIEM implementation by working closely with experienced NIEM practitioners. The NIEM help desk is also a resource for guidance and best practices. Considerations for implementation include: Architecture, Consistency, Development, and Reuse. Architecture: Systems on either side of the exchange can use different implementation architectures, such as different programming languages and operating systems. Consistency: All participants in an information exchange must agree on the definition and structure for the data in an exchange, and NIEM provides this standard. Development: It is imperative to use the IEPD lifecycle to guide the development of NIEM conformant information exchanges to ensure that all required artifacts are created. Reuse: Elements already defined within NIEM should be used whenever possible to save time and resources and to ensure NIEM conformance. Exchange elements outside of, or created to fill requirements not covered in NIEM should also be reused whenever possible. REUSE

Security and Privacy Security and privacy should always be key considerations when implementing an exchange. NIEM allows you to tag data with security and privacy, however, other technologies are required upon exchange implementation to enforce security and privacy rules. NIEM allows the use of metadata to describe specific requirements in regard to information security and the handling of sensitive privacy-protected information. Including this metadata allows systems that implement NIEM to automatically enforce rules that govern the use, protection, dissemination, and access controls for data being shared. This has been put to use in the Intelligence community, which established the Intelligence Community Information Security Marking (IC-ISM) as a standard for classified information. NIEM 3.0 provides support for existing versions of IC-ISM metadata attributes Slide 29: Security and Privacy Security and privacy should always be key considerations when implementing an exchange. NIEM allows you to tag data with security and privacy. However, other technologies are required upon exchange implementation to enforce security and privacy rules. NIEM allows the use of metadata to describe specific requirements in regard to information security and the handling of sensitive privacy-protected information. Including this metadata allows systems that implement NIEM to automatically enforce rules that govern the use, protection, dissemination, and access controls for data being shared. This has been put to use in the Intelligence community, which established the Intelligence Community Information Security Marking (IC-ISM) as a standard for classified information. NIEM 3.0 provides support for existing versions of IC-ISM metadata attributes Point out to participants that NIEM does not dictate how agencies handle privacy issues. They should consult with their organization’s privacy standards for additional information. Display slide 30. NIEM does not dictate how agencies handle privacy issues. Consult with your organization’s privacy standards.

Global REFERENCE ARCHITECTURE

Why the GRA…? The GRA provides a complete information sharing solution based on open standards. The GRA provides the Framework, Profiles, Guidelines, Specifications and Examples for designing and implementing an information sharing solution based on Services (SOA). No need to re-invent an information sharing architecture… Reuse the GRA as the basis for an enterprise Information Sharing Architecture

Standard System Interfaces
Existing systems are mostly custom built, use custom means for integration (non-standard). NIEM and GRA provide a standards-based alternative. GRA NIEM …

The Global Toolkit Data Technology Security Privacy Governance
A Standards Based Approaches to Information Sharing Data National Information Exchange Model (NIEM) NIEM Users’ Guide NIEM Naming and Design Rules (NDR) NIEM Conformance Information Exchange Package (IEP) Information Exchange Package Documentation (IEPD) Technology Global Reference Architecture (GRA) GRA Specifications GRA Implementation Guidelines Guidelines for Identifying and Designing Services GRA Execution Context Guidelines GRA Service Interaction Profiles Security Global Federated Identity & Privilege Management (GFIPM) GFIPM Metadata Specification GFIPM Operational Policies and Procedures GFIPM Governance Guidelines Privacy Privacy Policy Technical Framework Privacy Policy Guidelines Templates Privacy and Civil Liberties Impact Assessment Templates Governance Statement of Participation Service Level Agreements

National Information Exchange Model (NIEM)
A model that is used as a consistent baseline for creating information exchanges the sender and receiver of information share a common, unambiguous understanding of the meaning of that information. information is well understood and carries the same consistent meaning across various communities, thus allowing interoperability to occur. National Information Exchange Model (NIEM) NIEM Users’ Guide NIEM Naming and Design Rules (NDR) NIEM Conformance Information Exchange Package (IEP) Information Exchange Package Documentation (IEPD)

Global Reference Architecture (GRA)
Service Oriented Architecture Systems are “insulated” from one another, removing direct dependencies while making certain information visible. Information sharing projects follow well-established open standards whenever possible, rather than solutions proprietary to particular vendors. Adopts enterprise architecture using a common approach and a common technology infrastructure, rather than doing things on a project- or agency-specific basis. Global Reference Architecture (GRA) GRA Specifications GRA Implementation Guidelines Guidelines for Identifying and Designing Services GRA Execution Context Guidelines GRA Service Interaction Profiles

Global Federated Identity & Privilege Management (GFIPM)
GFIPM Metadata Specification GFIPM Operational Policies and Procedures GFIPM Governance Guidelines

Protection of Privacy Privacy Policy Technical Framework
Privacy Policy Guidelines Templates Privacy and Civil Liberties Impact Assessment Templates Privacy Policy Technical Framework Privacy Policy Guidelines Templates Privacy and Civil Liberties Impact Assessment Templates

Governing Information Sharing
Statement of Participation Service Level Agreements Statement of Participation Service Level Agreement(s) Federation Management

Why SOA? SOA is a style of information sharing architecture
Distinguishing Features: Keeps implementations separate (services) Open (non-proprietary) standards Formal, precise, but minimalist standards (e.g., Web Services [WS-*]) Share common services; Coordinate Services Reuse components The model is the software Separates integration logic from internal system logic Defines a standard system interface

Benefits of GRA/SOA Allow utilizing services as enterprise assets and promote service reuse. Increases interoperability between justice and non-justice agency systems. Promotes leveraging legacy systems and results in reduction of information sharing cost Facilitate service discoverability Promote consistency which leads to agility Facilitate incremental deployment which results in lower implementation risk GRA (SOA) is Business Driven

GRA Core Components An Information Sharing Architecture for System to System Communications

GRA Core Components – ARREST EXAMPLE

Service Specifications
A Service Specification can be considered a structured ‘blueprint’ for service implementation with the required (and optional) components for both business and technical analysts. The Service Specification provides all design (business and technical) requirements, functionality, standards and other information required to build the service. The GRA Service Specification Guidelines provide practical instructions on how to use the Service Specification Package and GRA conformance requirements.

For GRA more Information
GRA Framework document, Guidelines, Profiles and Specifications and other artifacts Global Justice Information Sharing Toolkit (GIST)

What this means for Milwaukee

Milwaukee Frontline with Standard Interfaces
Using Standard NIEM interfaces simplifies development Standard Interfaces w/NIEM Milwaukee Police Department FrontLine Initiative © 2014 SysLogic, Inc. Proprietary and Confidential 6/30/2014

Milwaukee Frontline – New Interfaces
Standard interfaces allow new data sources to be added New Interfaces w/NIEM Milwaukee Police Department FrontLine Initiative © 2014 SysLogic, Inc. Proprietary and Confidential 6/30/2014

Repeatable Frontline Solutions
Detroit Data Sources Systems developed to standard interfaces can be more readily shared and reused New Interfaces w/NIEM Detroit Frontline Milwaukee Police Department FrontLine Initiative © 2014 SysLogic, Inc. Proprietary and Confidential 6/30/2014

Milwaukee Frontline Next Generation
System reuse provides lifecycle benefits for lower cost and new capabilities NIEM Milwaukee Frontline V2 w/Detroit Enhancements Milwaukee Police Department FrontLine Initiative © 2014 SysLogic, Inc. Proprietary and Confidential 6/30/2014

How to get started

Evaluate Cost & Benefit
Roadmap to Adoption NIEM Engagement Process The engagement process is a self-service model that includes tools and methods for organizations to: Assess Current State Conduct a comprehensive assessment of the organization’s current information sharing environment. Evaluate Cost & Benefit Perform an analysis of qualitative and quantitative costs and benefits of NIEM adoption. Develop Roadmap Identify “quick wins” and develop a tactical action plan for sustainable NIEM adoption. Identify information exchanges where NIEM can provide the most value to the organization. Develop a tailored action plan outlining how the organization can adopt and sustainably use NIEM for information exchange. Results So how do you get started? The NIEM engagement process is a self-service model that includes tools and methods for organizations to: Assess Current State by conducting a comprehensive assessment of the organization’s current information sharing environment. Evaluate Cost & Benefit by performing an analysis of qualitative and quantitative costs and benefits of NIEM adoption. Develop a Roadmap by identifying “quick wins” and developing a tactical action plan for sustainable NIEM adoption. Results of this process include: Identifying information exchanges where NIEM can provide the most value to the organization. Developing a tailored action plan outlining how the organization can adopt and sustainably use NIEM for information exchange. Tell participants that they can get more information on the NIEM Engagement Process, at NIEM.gov/roadmaptoadoption For more information on the NIEM Engagement Process, please visit NIEM.gov/roadmaptoadoption.

For More on NIEM, Please visit
Website at Twitter at YouTube at LinkedIn at

NIEM Executive Briefing TRAINING.

Similar presentations

Presentation on theme: "NIEM Executive Briefing TRAINING."— Presentation transcript:

Similar presentations

About project

Feedback

Log in

Auth with social network:

NIEM Executive Briefing TRAINING.

Similar presentations

Presentation on theme: "NIEM Executive Briefing TRAINING."— Presentation transcript:

Similar presentations

About project

Feedback