Example for filled in form

Hi Vojtech,

Short question, but it needs a long answer.

Currently, this GitHub site is just for “milestone” Schema copies and test forms that we used for the pilot.

To answer your question, you can find partially completed SDC XML (using the SDCSubmitForm Schema) on the California Cancer Registry (CCR) Form Receiver endpointhttps://sdcpilot.azurewebsites.net/SDCFormView.aspx?ID=188. This is the same site that was shown in today’s demo. As you saw on the demo, the CCR site is using an older xslt for HTML rendering, and may not work correctly. We plan to fix it soon.

Here is a snippet of the web site for orientation. [cid:image003.png@01D240F0.749BC520]

If you click this linkhttps://sdcpilot.azurewebsites.net/SDCFormView.aspx?ID=173 from the same page (transaction ID 173, from Cancer Care Ontario), it will show a partially completed form as HTML. This is its XMLhttps://sdcpilot.azurewebsites.net/SDCFormViewRaw.aspx?ID=173 inside the SOAP/RFD wrapper. The XML is the current long form version of SDCSubmitForm. We plan to introduce more compact versions (e.g., lightweight XML, JSON, ProtoBuf, MessagePack, etc.) later if needed.

In the sample, you can see that, for selected answer choices, we set @selected=”true” [cid:image004.jpg@01D24100.D8ABF840]

and for fill-in responses, the Response is populated according to the form’s datatype, in the @val attribute. [cid:image007.jpg@01D24100.D8ABF840] All W3C data types are supported, including base64Binary, and a few others like literal HTML and XML responses. This allows the form responses to be directly validated against the SDC Schema.

Re your question about multiple patients: Ordinarily, the RFD wrapper protocol handles only one patient at a time. We have a draft Schema for sending multiple SDC documents on the same patient, but we temporarily removed it to focus on basics. We have not yet discussed sending documents on multiple patients, but that should be straightforward, and we certainly have very active use cases for that. But, if FHIR takes it on, we may decide to stuff a FHIR pipe with multiple patients’ IHE SDC payloads. In fact, for some use cases (simple forms), we may wish to use an IHE SDC form to generate lightweight FHIR QuestionnaireResponse instances and use the FHIR pipe to transport them. In fact, some people are working on IHE SDC using a SMART on FHIR approach. At this point, I prefer to leave the field open for experimentation, and not insist on an IHE-only transport model.

On another topic: I have to apologize for not having a very good documentation set at this point, but we plan to improve it after the next IHE Connectathon. Suggestions for improvements are definitely welcome.

The best place to find documentation is the IHE website (http://ihe.net/uploadedfiles/documents/qrph/ihe_qrph_suppl_sdc.pdf), and the new ONC Tech Lab website: https://oncprojectracking.healthit.gov/wiki/display/TechLabSC/SDC+IHE+Profile . More documentation is provided directly inside the Schema files and the HTML Schema documentation set (see below).

There is a lot of active SDC material not present on the new pilot GitHub repo, but you can find it on the Google Drive repohttps://drive.google.com/drive/folders/0B8uz5ZospJR5WUJQX0RtRVIzVmM. I pasted a lightly edited version of an earlier email below. It contains some important SDC links and instructions for testing SDC. Let me know if you have any trouble, and I’ll be glad to help. Some of these files are latest stable copies of code that is under active development for the Connectathon. For the CAP team, we have a separate svn repo for that, and we periodically update the Google site with new versions. At this point, the GitHub repo is only updated when we reach a new Schema milestone. I imagine that may change in 2017, to include more refined demo apps, documentation, sample forms and other artifacts.

Older email pasted below:

I posted the iteration14 Form Filler zipped folder in its present incomplete state. You can download it here: SDC Form Filler (CAP) iteration14.ziphttps://drive.google.com/open?id=0B_l1k9QvLvueeTZ0MUgtdGE3ZjQ The zip file should be unzipped in any suitable location on a windows computer (Windows 7 +) that has .NET Framework 4 installed. All the source code is provided, and the executable file is here: iteration14\DesktopClient\DesktopClient\bin\Debug\DesktopClient.exe. Just double click the file to run it.

This is the version we used for pilot testing in Las Vegas. It handles only SDC XML form design templates, but does not yet handle HTML or URL requests. It connects to the DCG pilot Form Manager,https://formmanager.dcgroupinc.com/SdcFormManager/home which apparently does not yet provide endpoints in the RequestFormResponse XML. The DCG FM provides a list of available forms in a JSON string. This list is loaded into the FF tool combo box on startup. This version of the form filler is directed to the CCR endpointhttps://sdcpilot.azurewebsites.net/ for SubmitForm submissions. There is an App.config file where the form list JSON node, Form Manager RetrieveForm node, and SubmitForm endpoint node can be changed.

This version has primitive methods for saving and reloading from disk, as well as loading from a FM and saving to endpoints. The saved file is named response.xml and it may be found here: iteration14\DesktopClient\DesktopClient\bin\Debug\forms\ response.xml. The xslt, css style sheet, and supporting files are found here as well.

When a template is saved to local disk, the screen displays a simple synoptic report based upon the answered questions. After the template is submitted to the (CCR) endpoint, the screen will show the endpoint’s SubmitFormResponse XML response.

Multiple repeating sections are supported, but not extensively tested. Repeating data may be saved, reloaded from disk, and re-edited any number of times, followed by submission of the data to the CCR endpoint, if desired.

The xslt needs some work. In particular, it does not properly render OtherText (now called Property), but instead just dumps the text to raw HTML. Also, the namespace has not been updated to urn:ihe:qrph:sdc:2016. This xslt version does not directly write the SDC XML with instance guids into the HTML page, due to a technical problem that we hope to resolve soon. Instead, the .NET application code (which wraps the browser control) writes the XML with initial instance guids directly into the HTML.

This version also does not handle demographic forms or FormDesign instance metadata, which would be needed in real patient transactions. We hope to address all of these issues before the Connectathon.

Here is a screen shot of the application: [cid:image002.png@01D240E9.D63EE750]

You can access the DCG Form Manager here: https://formmanager.dcgroupinc.com/SdcFormManager/home You can access the CCR log page here: https://sdcpilot.azurewebsites.net/ (It may take a while to load or refresh, because of the many log files not displayed.)

Schema docs (but not for the latest Schema) for this version: https://drive.google.com/file/d/0B_l1k9QvLvueZTFKbVpOcE5ueVU/view?usp=sharing Schemas for this version (not the latest): https://drive.google.com/open?id=0B_l1k9QvLvueRUxVTmVVczl6YWs

Please let me know if you have any difficulties, suggestions, bug reports etc. There will be future updates soon, as described above, to make the tool suitable for more advanced testing at the IHE Connectathon. Once that is ready and working, we will consider making it available on GitHub as well.

--Rich

Richard Moldwin, M.D., Ph.D. Lead Physician Informaticist College of American Pathologists 325 Waukegan Rd, Northfield, IL 60093 | rmoldwin@cap.orgmailto:rmoldwin@cap.org Tel: 847-983-0085|Cell: 224-343-3462 Web: www.cap.org/capecchttp://www.cap.org/capecc

Confidentiality Notice: This e-mail, including any attachments is the property of the College of American Pathologists and is intended for the sole use of the intended recipient(s). It may contain information that is proprietary and confidential. Any unauthorized review, use, disclosure, or distribution is prohibited. If you are not the intended recipient, please delete this message, and reply to the sender regarding the error in a separate email.

From: Vojtech Huser [mailto:notifications@github.com] Sent: Thursday, November 17, 2016 3:35 PM To: esacinc/sdc-schema-package sdc-schema-package@noreply.github.com Subject: [esacinc/sdc-schema-package] Example for filled in form (#11)

The provided example deal with empty CRF.

Can example form with data from 1 (or multiple) patients be also provided. To facilitate adoption....

— You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHubhttps://github.com/esacinc/sdc-schema-package/issues/11, or mute the threadhttps://github.com/notifications/unsubscribe-auth/ASTnmMks1tl0JH5EQ0DaeugpLHFG-dks5q_Mh4gaJpZM4K11sy.

esacinc / sdc-schema-package

Example for filled in form #11