PHTT 9/30/2014 Digging into SDC DRAFT Version 1

Clinical Care / EHRPublic Health Use PH Trigger Codes Record DX/Problem In EHR Asynchronous Core, “Initial” Case Message (C- CDA) and communication to reporter Decision Support Rules Decision Support Engine Parse PHA Preparedness Uses Form Creation PH Surveillance System Clinical “Notification” Creation Pre-Population Respond to Queued Clinical “Notification” With URL Reporter Continue process with Web-Based, Pre-Populated Report Form Storage Provider Pre-populated web form page PH System SDC transactions or web surveillance system over SOAP or eventually FHIR For future consideration

Design Patterns Model – View – Control

A model is an object representing data or even activity, e.g. a database table or even some plant-floor production-machine process. A view is some form of visualization of the state of the model. A controller offers facilities to change the state of the model.

Source Materials Structured Data Capture – Trial Implementation

Terms Glossary TermDefinition Form A form with data entry fields that will be filled out by an end user or provider. Form RepositoryAn authoritative source for forms. SDC Form DefinitionA standardized set of attributes describing the semantics and syntax of a form design so that it may be rendered consistently in any suitable information system and can be validated using SDC Schema. Based on ISO/IEC with SDC extensions. This is not a fillable form.

More terms (the transaction, from PH to Reporter) Glossary TermDefinition SDC HTML Package A collection of files that contains an HTML form instance derived from an SDC Form Definition, along with (optional) mapping information, (optional) administrative information, and (optional) supplemental data. The package is represented in SDC Content modules and may also be persisted as a collection of files. The HTML form instance is a fillable form. SDC XML PackageA collection of XML data, meeting the SDC Schema, that includes the particular SDC Form Definition represented as a set of standardized XML elements, along with mapping information, administrative information including submission and compliance instructions, and (optional) supplemental data. The package is represented in SDC Content modules and may also be persisted as a collection of files.

The transaction from PH to Reporter Glossary TermDefinition Enhanced Form Repository A form repository with capability to pre-populate form with the data received from the Form Filler.

Contrast and Compare SCD XML PACKAGE and SDC HTML Package In Common – mapping information – administrative information – supplemental data Differ by – SDC HTMP Package contains an HTML form instance derived from an SDC Form Definition A “ready to go” fillable form – SDC XML Package SDC Form Definition represented as a set of standardized XML elements It is not a fillable form. The EHR requires the capability of transforming SDC XML Package into a fillable form.

More Terms Loading data in the form automatically Glossary TermDefinition Pre-population When an Enhanced Form Repository fills in form fields using data sent by the Form Filler (note: an actor, in our case the provider and the EHR on behalf of provider) along with the retrieve request. The initial case message contained data and the data is placed into the form as part of the initial request process. So it is in the form before the point where the EHR prepares to display. Auto-populationWhen an EHR system automatically fills in form fields with data that are already available within the system’s database. At the point when the EHR displays a form it obtains data from the EHR based on mapping information. Pre-population is performed by a Form Manager, before being returned the form to the EHR. Auto-population is performed by the EHR after it receives the form package.

The transaction from PH to Reporter Glossary TermDefinition Pre-population When an Enhanced Form Repository fills in form fields using data sent by the Form Filler (an actor, the EHR on behalf of provider) along with the retrieve request. The initial case message contained data and the data is placed into the form as part of the initial request process. So it is in the form before at the point where the EHR prepares to display. Auto-populationWhen an EHR system automatically fills in form fields with data that are already available within the system’s database. At the point when the EHR displays a form it obtains data from the EHR based on mapping information. Pre-population is performed by a Form Manager, before being returned the form to the EHR. Auto-population is performed by the EHR after it receives the form package.

One more option: SDC URL FORM? A URL is returned. The URL points to a location that will “present” your form. Pre-population may have occurred. Auto-population is out of scope (technically possible, not a way you want to go!) Note: The spec refers to URL and URI. For our work it does not matter, it should be referring to URL.

and why are you discussing this? Impacts implementations – Who are our potential controllers? The EHR A web browser Some other system Flexibility – The same form could be presented through any of our controllers Usability - Look and feel/user experience – When the EHR is the controller look and feel is under control of the program

Clinical Care / EHRPublic Health Use PH Trigger Codes Record DX/Problem In EHR Asynchronous Core, “Initial” Case Message (C- CDA) and communication to reporter Decision Support Rules Decision Support Engine Parse PHA Preparedness Uses Form Creation PH Surveillance System Clinical “Notification” Creation Pre-Population Respond to Queued Clinical “Notification” With URL Reporter Continue process with Web-Based, Pre-Populated Report Form Storage Provider Pre-populated web form page PH System SDC transactions or web surveillance system over SOAP or eventually FHIR For future consideration

Questions Answers Discussion