Proof of Concept Project Ideas
 Share
The version of the browser you are using is no longer supported. Please upgrade to a supported browser.Dismiss

 
View only
 
 
ABCDEFGHIJKLMNOPQRSTUVWXYZAAAB
1
Joint Development Proof of Concept Project Ideas
2
3
ProjectDescriptionOrigins/ Proposed By:Project Type (ex: stds dev, spec. dev, ops or tech guidance, bp dev, req., enhancement, tool, module...)Potential Participating PartiesPlatforms/Systems Potentially AffectedHigh-Level Benefits/Relevance of Selecting as Proof of ConceptHigh-Level Challenges of Selecting as Proof of Concept (assume competing priorities are always an issue)Perceived Need/ UrgencyPerceived Funding NeedsViability as a Proof of Concept JD Project (1 - High, 2 - Medium, 3 - Low)
4
Onboarding Testing RequirementsDevelop requirements for a stand-alone testing platform for incoming HL7 messages or queriesGrantee-Developed JD User Group, ONCRequirementsNIST, ONC, All IISAllAnticipated MU 3 will likely increase onboarding need, interoperability is high priority for IIS and EHRs, AIRA's interoperability testing project can inform guidance, requirements are needed prior to tool development.Would only be able to develop requirements for the initial level of message format and content, as jurisdictionally specific requirements would still rest with programs.HighMedium - ONC or others may support, but unknown1- High
5
Data Quality ToolsDevelop tools to expand standardized approaches to DQAIRA/PHII Guidance ReportTool(s)All IIS and All VendorsAllAs volume and velocity of data increase over time, there will be a greater need to automate processes as much as possible, including data quality checks. This could include data quality checking when on-boarding a new provider, or ongoing data quality routines/processes for incoming or existing data.

Noam: DQ Tools not only need to be automated tools, they need to be better manual review technology-assisted tools for both project staff and provider organizations.
Variability in processes across IIS programs, No current standardized metrics, but guidance available through MIROW. Challenging to scope, would need to work across varied DB structures.High - data quality continues to be a significant and as of yet unstructured areaMedium - tools could be constructed independently of IIS2 - Medium
6
Immunization Forecaster InterfaceDevelop an interface to link IIS with existing forecasting optionsAIRA/PHII Guidance ReportToolAll IIS and All VendorsAllForecasters already exist as Web services from a number of implementers, but more work is needed on interfacing IIS with these services and improving testing procedures.Ambiguity of the rules, Variability across jurisdictions, Need simple, standardized interfaces between IIS and forecaster and EHR and forecaster, Standardization of forecast results versus message format, Technical issues regarding decoupling existing/embedded forecast enginesLow - will likely be minimal switching of CDS options until better testing is availableMedium - funding would likely be rolled into forecaster development costs2 - Medium
7
Onboarding Testing ToolsDevelop tool(s) for stand-alone testing platform for incoming HL7 messages or queriesGrantee-Developed JD User Group, ONCToolNIST, ONC, All IISAllCollaboratively developed tool could assist with pressure of onboarding volume, development of tool would help provide perspective on standardized onboarding processes.Onboarding testing requirements would be a precursor for this project, location for hosting and licensing may be issues, would only be able to code the initial level of message format and content, as jurisdictionally specific requirements would still rest with programs. HighMedium - ONC or others may support, but unknown3 - Low
8
Patient MatchingDevelop tools or guidelines to standardize deduplicationAIRA/PHII Guidance ReportGuidance, Tool(s)All IIS and All VendorsAllRecord de-duplication is one of the core functionalities and challenges for IIS, one which could benefit from collective analysis and documentationAside from expert panel outputs for best practices and test cases, no standards exist to support patient deduplicationHighHigh, heavily influenced by recent AFIX BPA/IDIQ award and FOA award3 - Low
9
IIS dashboardsDevelop guidance and templates for IIS dashboards to include coverate rates, low inventory warnings, etc.AIRA/PHII Guidance ReportGuidanceAll IIS and All VendorsAllUniform dashboards would allow users to view clinic coverage reports compared to local, state, and national, as well as low inventory warnings, and last reminder/recall notification dateVariability with data structure and quality could make uniform dashboards challengingHighHigh3 - Low
10
Interface with SNS tracking systemsIntegrate IIS functions with SNS functionsAIRA/PHII Guidance ReportOps or tech guidanceImm programs with overlap with/ responsibility to SNS programsSomeThere is overlap with SNS and other preparedness activities associated with pandemic fluFew states interacting with SNS programsLowHigh3 - Low
11
SMS text-based reminder recall notificationsGuidance to support mobile phone-based reminder recall AIRA/PHII Guidance ReportGuidance, EnhancementThose IIS interested in pursuing R/R text messagingAllText messaging has potential to make R/R more effective, could also be more cost effective than mailed notices, JD process could address both functionality and security questions.Topic may not be as urgent as other more pressing topics currentlyLowHigh3 - Low
12
2D barcoding implementationSupport implementation of IIS ability to read 2D barcodesAIRA/PHII Guidance ReportEnhancementThose interested in pursuing IIS-based scanning technologyAll2D barcodes continue to be supported by pharm manufacturers, and show promise as a workflow change to improve quality and timeliness of data capture at the clinic setting. Several IIS have integrated 2D barcode scanning, and this information could be leveraged to futher expand this functionality through a JD project.Topic may not be as urgent as other more pressing topics currently. Much 2D scanning will likely use the EHR rather than the IIS as the primary point of input.LowHigh3 - Low
13
Perinatal Hepatitis B case moduleDevelop module to track Hep B casesAIRA/PHII Guidance ReportModuleThose programs leveraging their IIS for peri hep B trackingAllPeri Hep B tracking is a responsibility outlined in the IPOM, and a JD project focused on tracking Peri Hep B cases could offer models for more uniform approaches across PH.Varying levels of integration may make this project challenging. LowHigh3 - Low
14
Vaccine de-duplication algorithmsDevelop stronger guidance for vaccine level deduplicationAIRA/PHII Guidance ReportBest PracticesAllAllMIROW guidance on vax deduplication was published in 2006; a JD project to update this guidance and support implementation of these rules would be very beneficial.Variability across programs may make a JD project on this topic challenging.LowMedium3 - Low
15
Record locator service for national consumer access or a service that allows IIS to locate records in other IISDevelop requirements for national RLSAIRA/PHII Guidance ReportRequirements AllAllThis could support Interjurisdictional data exchange efforts.This project would be a substantial lift, and would have significant policy implications regarding data sharing.LowHigh3 - Low
16
Influenza public health preparedness initiativesExplore best practices for IIS supporting mass vax clinics or other flu-oriented projectsAIRA/PHII Guidance ReportBest PracticesAllAllIncreasing focus on adult vaccination suggests this could be a strong JD project. Collective development of best practices would allow broad input and leverage across programs. Link with preparedness may offer additional pathways for funding.Unless funds were readily apparent, exploration of new funds may extend the timeline of this effort. MediumHigh3 - Low
17
Consumer AccessDevelop guidelines for authentication and auditingAIRA/PHII Guidance ReportToolThose IIS interested in pursuing Consumer AccessAll but STC, where a consumer access solution already existsDemand for consumer access to health information is sweeping the country, but the accompanying privacy and security issues are not trivial. IIS, and public health generally, could benefit from consistent approaches to authentication and auditing. There are several consumer access projects being piloted across the country whose lessons could be built upon.Variability in state health data privacy laws, Variability in IIS privacy and confidentiality policies, IIS policies on consumer access, Need for authenticating users and auditing consumer accessMedium - opinion about consumer access is still mixed across the communityHigh - no clear path for how this might be funded beyond ONC's small pilot3 - Low
18
AFIX-IIS Integration SupportProvide an IIS community-wide perspective and support for AFIX-IIS implementation to achieve greater consistency
19
Interjurisdictional ExchangeSupport the development of a strategic roadmap addressing policy and technical aspects of voluntary IIS-IIS exchange.
20
IIS open source tool development and stewardshipSupport the development of governance, practical oversight, and storage of open source tools to benefit the IIS community (e.g., technical working group collectively developing DQA tool, etc.)
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
Loading...
 
 
 
Potential Projects
Projects Removed, Addressed Elsewhere
 
 
Main menu