plan_executor 1.0.2

Sign up to get free protection for your applications and to get access to all the features.
Files changed (337) hide show
  1. checksums.yaml +7 -0
  2. data/.gitignore +44 -0
  3. data/.simplecov +16 -0
  4. data/.travis.yml +13 -0
  5. data/Gemfile +26 -0
  6. data/Gemfile.lock +197 -0
  7. data/LICENSE +201 -0
  8. data/README.md +126 -0
  9. data/Rakefile +25 -0
  10. data/fixtures/daf/conformance-daf-query-responder.xml +1471 -0
  11. data/fixtures/diagnostic_order/do-100.xml +64 -0
  12. data/fixtures/diagnostic_order/do-200.xml +121 -0
  13. data/fixtures/diagnostic_order/do-300.xml +91 -0
  14. data/fixtures/diagnostic_order/do-400.xml +88 -0
  15. data/fixtures/diagnostic_report/dr-100.xml +96 -0
  16. data/fixtures/diagnostic_report/dr-200.xml +125 -0
  17. data/fixtures/diagnostic_report/dr-300.xml +132 -0
  18. data/fixtures/diagnostic_report/dr-400.xml +121 -0
  19. data/fixtures/financial/claim-example-average.xml +168 -0
  20. data/fixtures/financial/claim-example-simple.xml +67 -0
  21. data/fixtures/observation/obs-100.xml +58 -0
  22. data/fixtures/observation/obs-101.xml +58 -0
  23. data/fixtures/observation/obs-200.xml +125 -0
  24. data/fixtures/observation/obs-300.xml +106 -0
  25. data/fixtures/observation/obs-301.xml +106 -0
  26. data/fixtures/observation/obs-302.xml +106 -0
  27. data/fixtures/observation/obs-303.xml +106 -0
  28. data/fixtures/observation/obs-304.xml +106 -0
  29. data/fixtures/observation/obs-400.xml +87 -0
  30. data/fixtures/observation/obs-401.xml +95 -0
  31. data/fixtures/observation/obs-402.xml +95 -0
  32. data/fixtures/observation/obs-403.xml +84 -0
  33. data/fixtures/observation/obs-404.xml +84 -0
  34. data/fixtures/observation/obs-405.xml +83 -0
  35. data/fixtures/observation/obs-406.xml +83 -0
  36. data/fixtures/observation/obs-407.xml +70 -0
  37. data/fixtures/observation/obs-408.xml +84 -0
  38. data/fixtures/observation/obs-uslab-example5.xml +102 -0
  39. data/fixtures/order/order-100.xml +61 -0
  40. data/fixtures/order/order-200.xml +61 -0
  41. data/fixtures/order/order-300.xml +61 -0
  42. data/fixtures/order/order-400.xml +61 -0
  43. data/fixtures/order_response/ordresp-100.xml +79 -0
  44. data/fixtures/order_response/ordresp-110.xml +79 -0
  45. data/fixtures/order_response/ordresp-200.xml +79 -0
  46. data/fixtures/order_response/ordresp-210.xml +79 -0
  47. data/fixtures/order_response/ordresp-300.xml +79 -0
  48. data/fixtures/order_response/ordresp-310.xml +79 -0
  49. data/fixtures/order_response/ordresp-400.xml +79 -0
  50. data/fixtures/order_response/ordresp-410.xml +79 -0
  51. data/fixtures/organization/org-uslab-example3.xml +49 -0
  52. data/fixtures/patient/patient-example-updated.xml +140 -0
  53. data/fixtures/patient/patient-example-us-extensions(us01).xml +81 -0
  54. data/fixtures/patient/patient-example.xml +132 -0
  55. data/fixtures/patient/patient-format-example.xml +101 -0
  56. data/fixtures/patient/patient-minimal.xml +9 -0
  57. data/fixtures/patient/patient-uslab-example1.xml +44 -0
  58. data/fixtures/practitioner/pract-uslab-example1.xml +18 -0
  59. data/fixtures/practitioner/pract-uslab-example3.xml +36 -0
  60. data/fixtures/record/condition-example-f201-fever.xml +63 -0
  61. data/fixtures/record/condition-example-f205-infection.xml +20 -0
  62. data/fixtures/record/diagnosticreport-example-f201-brainct.xml +18 -0
  63. data/fixtures/record/encounter-example-f201-20130404.xml +17 -0
  64. data/fixtures/record/encounter-example-f202-20130128.xml +17 -0
  65. data/fixtures/record/observation-example-f202-temperature.xml +60 -0
  66. data/fixtures/record/organization-example-f201-aumc.xml +5 -0
  67. data/fixtures/record/organization-example-f203-bumc.xml +5 -0
  68. data/fixtures/record/patient-example-f201-roel.xml +16 -0
  69. data/fixtures/record/practitioner-example-f201-ab.xml +14 -0
  70. data/fixtures/record/procedure-example-f201-tpf.xml +23 -0
  71. data/fixtures/scheduling/appointment-simple.xml +24 -0
  72. data/fixtures/scheduling/appointmentresponse-patient-simple.xml +12 -0
  73. data/fixtures/scheduling/appointmentresponse-practitioner-simple.xml +12 -0
  74. data/fixtures/scheduling/practitioner-simple.xml +10 -0
  75. data/fixtures/scheduling/schedule-simple.xml +12 -0
  76. data/fixtures/scheduling/slot-simple.xml +10 -0
  77. data/fixtures/specimen/spec-100.xml +65 -0
  78. data/fixtures/specimen/spec-400.xml +70 -0
  79. data/fixtures/specimen/spec-uslab-example1.xml +82 -0
  80. data/fixtures/validation/observation.profile.xml +2045 -0
  81. data/fixtures/validation/observations/observation-example(example).xml +50 -0
  82. data/lib/FHIR_structure.json +529 -0
  83. data/lib/daf_resource_generator.rb +94 -0
  84. data/lib/data/fhir_structure.rb +8 -0
  85. data/lib/data/resources.rb +138 -0
  86. data/lib/executor.rb +56 -0
  87. data/lib/ext/client.rb +27 -0
  88. data/lib/ext/client_reply.rb +19 -0
  89. data/lib/plan_executor.rb +31 -0
  90. data/lib/resource_generator.rb +656 -0
  91. data/lib/tasks/tasks.rake +329 -0
  92. data/lib/tasks/templates/summary.html.erb +163 -0
  93. data/lib/test_result.rb +69 -0
  94. data/lib/tests/assertions.rb +261 -0
  95. data/lib/tests/base_test.rb +117 -0
  96. data/lib/tests/suites/argonaut_resprint_1_test.rb +260 -0
  97. data/lib/tests/suites/argonaut_resprint_2_test.rb +369 -0
  98. data/lib/tests/suites/argonaut_resprint_3_test.rb +309 -0
  99. data/lib/tests/suites/argonaut_sprint_1_test.rb +187 -0
  100. data/lib/tests/suites/argonaut_sprint_2_test.rb +115 -0
  101. data/lib/tests/suites/argonaut_sprint_3_test.rb +208 -0
  102. data/lib/tests/suites/argonaut_sprint_4_test.rb +335 -0
  103. data/lib/tests/suites/argonaut_sprint_5_test.rb +196 -0
  104. data/lib/tests/suites/argonaut_sprint_6_test.rb +243 -0
  105. data/lib/tests/suites/argonaut_sprint_7_test.rb +161 -0
  106. data/lib/tests/suites/base_suite.rb +116 -0
  107. data/lib/tests/suites/connectathon_audit_track.rb +354 -0
  108. data/lib/tests/suites/connectathon_fetch_patient_record.rb +443 -0
  109. data/lib/tests/suites/connectathon_financial_track.rb +380 -0
  110. data/lib/tests/suites/connectathon_lab_order_track.rb +239 -0
  111. data/lib/tests/suites/connectathon_patient_track.rb +364 -0
  112. data/lib/tests/suites/connectathon_profile_validation.rb +101 -0
  113. data/lib/tests/suites/connectathon_scheduling_track.rb +266 -0
  114. data/lib/tests/suites/connectathon_terminology_track.rb +242 -0
  115. data/lib/tests/suites/daf_profiles_test.rb +431 -0
  116. data/lib/tests/suites/format_test.rb +453 -0
  117. data/lib/tests/suites/history_test.rb +311 -0
  118. data/lib/tests/suites/read_test.rb +104 -0
  119. data/lib/tests/suites/resource_test.rb +553 -0
  120. data/lib/tests/suites/search_test.rb +219 -0
  121. data/lib/tests/suites/search_test_robust.rb +172 -0
  122. data/lib/tests/suites/sprinkler_search_test.rb +660 -0
  123. data/lib/tests/suites/suite_engine.rb +114 -0
  124. data/lib/tests/suites/transaction_test.rb +571 -0
  125. data/lib/tests/testscripts/base_testscript.rb +480 -0
  126. data/lib/tests/testscripts/testscript_engine.rb +81 -0
  127. data/lib/tests/testscripts/xml/Connectathon11/Track1-Patient/Client Assigned Id/track1-patient-base-client-id-json.xml +348 -0
  128. data/lib/tests/testscripts/xml/Connectathon11/Track1-Patient/Client Assigned Id/track1-patient-base-client-id-xml.xml +348 -0
  129. data/lib/tests/testscripts/xml/Connectathon11/Track1-Patient/Client Assigned Id/track1-patient-bonus-client-id-json.xml +420 -0
  130. data/lib/tests/testscripts/xml/Connectathon11/Track1-Patient/Client Assigned Id/track1-patient-bonus-client-id-xml.xml +420 -0
  131. data/lib/tests/testscripts/xml/Connectathon11/Track1-Patient/README.html +68 -0
  132. data/lib/tests/testscripts/xml/Connectathon11/Track1-Patient/Server Assigned Id/track1-patient-base-server-id-json.xml +352 -0
  133. data/lib/tests/testscripts/xml/Connectathon11/Track1-Patient/Server Assigned Id/track1-patient-base-server-id-xml.xml +352 -0
  134. data/lib/tests/testscripts/xml/Connectathon11/Track1-Patient/Server Assigned Id/track1-patient-bonus-server-id-json.xml +421 -0
  135. data/lib/tests/testscripts/xml/Connectathon11/Track1-Patient/Server Assigned Id/track1-patient-bonus-server-id-xml.xml +421 -0
  136. data/lib/tests/testscripts/xml/Connectathon11/Track1-Patient/_reference/conformance/PatientConformance.xml +34 -0
  137. data/lib/tests/testscripts/xml/Connectathon11/Track1-Patient/_reference/resources/patient-create-PeterChalmers-min.json +45 -0
  138. data/lib/tests/testscripts/xml/Connectathon11/Track1-Patient/_reference/resources/patient-create-PeterChalmers-min.xml +26 -0
  139. data/lib/tests/testscripts/xml/Connectathon11/Track1-Patient/_reference/resources/patient-create-PeterChalmers.json +100 -0
  140. data/lib/tests/testscripts/xml/Connectathon11/Track1-Patient/_reference/resources/patient-create-PeterChalmers.xml +102 -0
  141. data/lib/tests/testscripts/xml/Connectathon11/Track1-Patient/_reference/resources/patient-create-bonus-PeterChalmers-min.json +53 -0
  142. data/lib/tests/testscripts/xml/Connectathon11/Track1-Patient/_reference/resources/patient-create-bonus-PeterChalmers-min.xml +30 -0
  143. data/lib/tests/testscripts/xml/Connectathon11/Track1-Patient/_reference/resources/patient-create-bonus-PeterChalmers.json +108 -0
  144. data/lib/tests/testscripts/xml/Connectathon11/Track1-Patient/_reference/resources/patient-create-bonus-PeterChalmers.xml +108 -0
  145. data/lib/tests/testscripts/xml/Connectathon11/Track1-Patient/_reference/resources/patient-update-PeterChalmers-min.json +45 -0
  146. data/lib/tests/testscripts/xml/Connectathon11/Track1-Patient/_reference/resources/patient-update-PeterChalmers-min.xml +26 -0
  147. data/lib/tests/testscripts/xml/Connectathon11/Track1-Patient/_reference/resources/patient-update-PeterChalmers.json +100 -0
  148. data/lib/tests/testscripts/xml/Connectathon11/Track1-Patient/_reference/resources/patient-update-PeterChalmers.xml +102 -0
  149. data/lib/tests/testscripts/xml/Connectathon11/Track1-Patient/_reference/resources/patient-update-bonus1-PeterChalmers-min.json +53 -0
  150. data/lib/tests/testscripts/xml/Connectathon11/Track1-Patient/_reference/resources/patient-update-bonus1-PeterChalmers-min.xml +30 -0
  151. data/lib/tests/testscripts/xml/Connectathon11/Track1-Patient/_reference/resources/patient-update-bonus1-PeterChalmers.json +108 -0
  152. data/lib/tests/testscripts/xml/Connectathon11/Track1-Patient/_reference/resources/patient-update-bonus1-PeterChalmers.xml +107 -0
  153. data/lib/tests/testscripts/xml/Connectathon11/Track1-Patient/_reference/resources/patient-update-bonus2-PeterChalmers-min.json +53 -0
  154. data/lib/tests/testscripts/xml/Connectathon11/Track1-Patient/_reference/resources/patient-update-bonus2-PeterChalmers-min.xml +31 -0
  155. data/lib/tests/testscripts/xml/Connectathon11/Track1-Patient/_reference/resources/patient-update-bonus2-PeterChalmers.json +108 -0
  156. data/lib/tests/testscripts/xml/Connectathon11/Track1-Patient/_reference/resources/patient-update-bonus2-PeterChalmers.xml +106 -0
  157. data/lib/tests/testscripts/xml/Connectathon11/Track11-SDC/_reference/C-CDA_R2-1_CCD-ussg.xml +3414 -0
  158. data/lib/tests/testscripts/xml/Connectathon11/Track11-SDC/_reference/resources/parameters-A1-empty-on-instance.xml +9 -0
  159. data/lib/tests/testscripts/xml/Connectathon11/Track11-SDC/_reference/resources/parameters-A2-empty-by-ref.xml +15 -0
  160. data/lib/tests/testscripts/xml/Connectathon11/Track11-SDC/_reference/resources/parameters-A3-empty-by-identifier.xml +13 -0
  161. data/lib/tests/testscripts/xml/Connectathon11/Track11-SDC/_reference/resources/parameters-A4-empty-by-contained.xml +15 -0
  162. data/lib/tests/testscripts/xml/Connectathon11/Track11-SDC/_reference/resources/parameters-B1-CCDA-on-instance.xml +15 -0
  163. data/lib/tests/testscripts/xml/Connectathon11/Track11-SDC/_reference/resources/parameters-B2-CCDA-by-ref.xml +21 -0
  164. data/lib/tests/testscripts/xml/Connectathon11/Track11-SDC/_reference/resources/parameters-B3-CCDA-by-identifier.xml +19 -0
  165. data/lib/tests/testscripts/xml/Connectathon11/Track11-SDC/_reference/resources/parameters-B4-CCDA-by-contained.xml +21 -0
  166. data/lib/tests/testscripts/xml/Connectathon11/Track11-SDC/_reference/resources/questionnaire-sdc-profile-example-ussg-fht.xml +3905 -0
  167. data/lib/tests/testscripts/xml/Connectathon11/Track11-SDC/_reference/resources/questionnaireresponse-expected-ussg-fht-CCDA.xml +190 -0
  168. data/lib/tests/testscripts/xml/Connectathon11/Track11-SDC/_reference/resources/questionnaireresponse-expected-ussg-fht-empty.xml +177 -0
  169. data/lib/tests/testscripts/xml/Connectathon11/Track11-SDC/track11-sdc-prepop-xml.xml +142 -0
  170. data/lib/tests/testscripts/xml/Connectathon11/Track2-Terminology/Expand/Client Assigned Id/track2-ts-suite1-expand-client-id.xml +925 -0
  171. data/lib/tests/testscripts/xml/Connectathon11/Track2-Terminology/Expand/Client Assigned Id/track2-ts-suite2-expand-filter-client-id.xml +930 -0
  172. data/lib/tests/testscripts/xml/Connectathon11/Track2-Terminology/Expand/Server Assigned Id/track2-ts-suite1-expand-server-id.xml +953 -0
  173. data/lib/tests/testscripts/xml/Connectathon11/Track2-Terminology/Expand/Server Assigned Id/track2-ts-suite2-expand-filter-server-id.xml +958 -0
  174. data/lib/tests/testscripts/xml/Connectathon11/Track2-Terminology/Lookup/track2-ts-suite5-loinc-lookup-xml.xml +224 -0
  175. data/lib/tests/testscripts/xml/Connectathon11/Track2-Terminology/Lookup/track2-ts-suite5-snomed-lookup-xml.xml +224 -0
  176. data/lib/tests/testscripts/xml/Connectathon11/Track2-Terminology/README.html +85 -0
  177. data/lib/tests/testscripts/xml/Connectathon11/Track2-Terminology/Translate/track2-ts-suite6-translate-xml.xml +224 -0
  178. data/lib/tests/testscripts/xml/Connectathon11/Track2-Terminology/Validate-code/Client Assigned Id/track2-ts-suite3-validate-code-client-id.xml +1807 -0
  179. data/lib/tests/testscripts/xml/Connectathon11/Track2-Terminology/Validate-code/Client Assigned Id/track2-ts-suite4-validate-code-client-id.xml +714 -0
  180. data/lib/tests/testscripts/xml/Connectathon11/Track2-Terminology/Validate-code/Server Assigned Id/track2-ts-suite3-validate-code-server-id.xml +1835 -0
  181. data/lib/tests/testscripts/xml/Connectathon11/Track2-Terminology/Validate-code/Server Assigned Id/track2-ts-suite4-validate-code-server-id.xml +742 -0
  182. data/lib/tests/testscripts/xml/Connectathon11/Track2-Terminology/_reference/conformance/ConceptMapSuite6Conformance.xml +11 -0
  183. data/lib/tests/testscripts/xml/Connectathon11/Track2-Terminology/_reference/conformance/ValueSetSuite1Conformance.xml +17 -0
  184. data/lib/tests/testscripts/xml/Connectathon11/Track2-Terminology/_reference/conformance/ValueSetSuite2Conformance.xml +17 -0
  185. data/lib/tests/testscripts/xml/Connectathon11/Track2-Terminology/_reference/conformance/ValueSetSuite3Conformance.xml +14 -0
  186. data/lib/tests/testscripts/xml/Connectathon11/Track2-Terminology/_reference/conformance/ValueSetSuite4Conformance.xml +14 -0
  187. data/lib/tests/testscripts/xml/Connectathon11/Track2-Terminology/_reference/conformance/ValueSetSuite5Conformance.xml +11 -0
  188. data/lib/tests/testscripts/xml/Connectathon11/Track2-Terminology/_reference/input/extensional-case-1-input-4-2-a.xml +11 -0
  189. data/lib/tests/testscripts/xml/Connectathon11/Track2-Terminology/_reference/input/extensional-case-1-input-4-2-b.xml +11 -0
  190. data/lib/tests/testscripts/xml/Connectathon11/Track2-Terminology/_reference/input/extensional-case-1-input-4-3-a.xml +13 -0
  191. data/lib/tests/testscripts/xml/Connectathon11/Track2-Terminology/_reference/input/extensional-case-1-input-4-3-b.xml +13 -0
  192. data/lib/tests/testscripts/xml/Connectathon11/Track2-Terminology/_reference/input/extensional-case-1-input-4-4-a.xml +15 -0
  193. data/lib/tests/testscripts/xml/Connectathon11/Track2-Terminology/_reference/input/extensional-case-1-input-4-4-b.xml +15 -0
  194. data/lib/tests/testscripts/xml/Connectathon11/Track2-Terminology/_reference/input/lookup-loinc-input-5-2.xml +10 -0
  195. data/lib/tests/testscripts/xml/Connectathon11/Track2-Terminology/_reference/input/lookup-loinc-input-5-3.xml +11 -0
  196. data/lib/tests/testscripts/xml/Connectathon11/Track2-Terminology/_reference/input/lookup-snomed-input-5-2.xml +10 -0
  197. data/lib/tests/testscripts/xml/Connectathon11/Track2-Terminology/_reference/input/lookup-snomed-input-5-3.xml +11 -0
  198. data/lib/tests/testscripts/xml/Connectathon11/Track2-Terminology/_reference/input/translate-conceptmap-input-6-2.xml +14 -0
  199. data/lib/tests/testscripts/xml/Connectathon11/Track2-Terminology/_reference/input/translate-conceptmap-input-6-3.xml +15 -0
  200. data/lib/tests/testscripts/xml/Connectathon11/Track2-Terminology/_reference/output/extensional-case-1-expand-min.xml +47 -0
  201. data/lib/tests/testscripts/xml/Connectathon11/Track2-Terminology/_reference/output/extensional-case-1-filter-min.xml +23 -0
  202. data/lib/tests/testscripts/xml/Connectathon11/Track2-Terminology/_reference/output/extensional-case-2-expand-min.xml +132 -0
  203. data/lib/tests/testscripts/xml/Connectathon11/Track2-Terminology/_reference/output/extensional-case-2-filter-min.xml +38 -0
  204. data/lib/tests/testscripts/xml/Connectathon11/Track2-Terminology/_reference/output/extensional-case-3-expand-min.xml +252 -0
  205. data/lib/tests/testscripts/xml/Connectathon11/Track2-Terminology/_reference/output/extensional-case-3-filter-min.xml +58 -0
  206. data/lib/tests/testscripts/xml/Connectathon11/Track2-Terminology/_reference/output/extensional-case-4-expand-min.xml +57 -0
  207. data/lib/tests/testscripts/xml/Connectathon11/Track2-Terminology/_reference/output/extensional-case-4-filter-min.xml +28 -0
  208. data/lib/tests/testscripts/xml/Connectathon11/Track2-Terminology/_reference/output/intensional-case-1-expand-min.xml +347 -0
  209. data/lib/tests/testscripts/xml/Connectathon11/Track2-Terminology/_reference/output/intensional-case-1-filter-min.xml +33 -0
  210. data/lib/tests/testscripts/xml/Connectathon11/Track2-Terminology/_reference/output/intensional-case-2-expand-min.xml +637 -0
  211. data/lib/tests/testscripts/xml/Connectathon11/Track2-Terminology/_reference/output/intensional-case-2-filter-min.xml +33 -0
  212. data/lib/tests/testscripts/xml/Connectathon11/Track2-Terminology/_reference/output/intensional-case-3-filter-min.xml +58 -0
  213. data/lib/tests/testscripts/xml/Connectathon11/Track2-Terminology/_reference/output/lookup-loinc-min.xml +11 -0
  214. data/lib/tests/testscripts/xml/Connectathon11/Track2-Terminology/_reference/output/lookup-snomed-min.xml +11 -0
  215. data/lib/tests/testscripts/xml/Connectathon11/Track2-Terminology/_reference/output/suite3-invalid-min.xml +10 -0
  216. data/lib/tests/testscripts/xml/Connectathon11/Track2-Terminology/_reference/output/suite3-valid-min.xml +7 -0
  217. data/lib/tests/testscripts/xml/Connectathon11/Track2-Terminology/_reference/output/suite4-invalid-min.xml +10 -0
  218. data/lib/tests/testscripts/xml/Connectathon11/Track2-Terminology/_reference/output/suite4-valid-min.xml +7 -0
  219. data/lib/tests/testscripts/xml/Connectathon11/Track2-Terminology/_reference/output/translate-conceptmap-min.xml +17 -0
  220. data/lib/tests/testscripts/xml/Connectathon11/Track2-Terminology/_reference/resources/extensional-case-1.xml +55 -0
  221. data/lib/tests/testscripts/xml/Connectathon11/Track2-Terminology/_reference/resources/extensional-case-2.xml +122 -0
  222. data/lib/tests/testscripts/xml/Connectathon11/Track2-Terminology/_reference/resources/extensional-case-3.xml +222 -0
  223. data/lib/tests/testscripts/xml/Connectathon11/Track2-Terminology/_reference/resources/extensional-case-4.xml +65 -0
  224. data/lib/tests/testscripts/xml/Connectathon11/Track2-Terminology/_reference/resources/intensional-case-1.xml +31 -0
  225. data/lib/tests/testscripts/xml/Connectathon11/Track2-Terminology/_reference/resources/intensional-case-2.xml +31 -0
  226. data/lib/tests/testscripts/xml/Connectathon11/Track2-Terminology/_reference/resources/intensional-case-3.xml +31 -0
  227. data/lib/tests/testscripts/xml/Connectathon11/Track2-Terminology/_reference/resources/translate-conceptmap-case-1.xml +145 -0
  228. data/lib/tests/testscripts/xml/Connectathon11/Track3-CDS-on-FHIR/_reference/conformance/DecisionSupportServiceModule-Evaluate.xml +17 -0
  229. data/lib/tests/testscripts/xml/Connectathon11/Track3-CDS-on-FHIR/_reference/resources/ecrs-fhir-cdc-immunizations-incomplete-request-payload.xml +26 -0
  230. data/lib/tests/testscripts/xml/Connectathon11/Track3-CDS-on-FHIR/_reference/resources/ecrs-fhir-cdc-immunizations-incomplete-response-min-payload.xml +7 -0
  231. data/lib/tests/testscripts/xml/Connectathon11/Track3-CDS-on-FHIR/_reference/resources/ecrs-fhir-cdc-immunizations-incomplete-response-payload.xml +332 -0
  232. data/lib/tests/testscripts/xml/Connectathon11/Track3-CDS-on-FHIR/_reference/resources/ecrs-fhir-cdc-immunizations-malformed-request-payload.xml +28 -0
  233. data/lib/tests/testscripts/xml/Connectathon11/Track3-CDS-on-FHIR/_reference/resources/ecrs-fhir-cdc-immunizations-malformed-response-min-payload.xml +7 -0
  234. data/lib/tests/testscripts/xml/Connectathon11/Track3-CDS-on-FHIR/_reference/resources/ecrs-fhir-cdc-immunizations-malformed-response-payload.xml +20 -0
  235. data/lib/tests/testscripts/xml/Connectathon11/Track3-CDS-on-FHIR/_reference/resources/ecrs-fhir-cdc-immunizations-request-payload.xml +28 -0
  236. data/lib/tests/testscripts/xml/Connectathon11/Track3-CDS-on-FHIR/_reference/resources/ecrs-fhir-cdc-immunizations-response-min-payload.xml +7 -0
  237. data/lib/tests/testscripts/xml/Connectathon11/Track3-CDS-on-FHIR/_reference/resources/ecrs-fhir-cdc-immunizations-response-payload.xml +332 -0
  238. data/lib/tests/testscripts/xml/Connectathon11/Track3-CDS-on-FHIR/_reference/resources/ecrs-fhir-cdc-immunizations-unauthorized-request-payload.xml +28 -0
  239. data/lib/tests/testscripts/xml/Connectathon11/Track3-CDS-on-FHIR/_reference/resources/ecrs-fhir-cdc-immunizations-unauthorized-response-min-payload.xml +7 -0
  240. data/lib/tests/testscripts/xml/Connectathon11/Track3-CDS-on-FHIR/_reference/resources/ecrs-fhir-cdc-immunizations-unauthorized-response-payload.xml +8 -0
  241. data/lib/tests/testscripts/xml/Connectathon11/Track3-CDS-on-FHIR/_reference/resources/gao-assessment-request-payload.xml +176 -0
  242. data/lib/tests/testscripts/xml/Connectathon11/Track3-CDS-on-FHIR/_reference/resources/gao-assessment-response-payload-min.xml +32 -0
  243. data/lib/tests/testscripts/xml/Connectathon11/Track3-CDS-on-FHIR/_reference/resources/gao-assessment-response-payload.xml +80 -0
  244. data/lib/tests/testscripts/xml/Connectathon11/Track3-CDS-on-FHIR/track3-cds-evaluate-cdc-immunization.xml +290 -0
  245. data/lib/tests/testscripts/xml/Connectathon11/Track3-CDS-on-FHIR/track3-cds-evaluate-gao-profile.xml +110 -0
  246. data/lib/tests/testscripts/xml/Connectathon11/Track6-FHIR-Genomics/Client_Assigned_Id/TestScript_FHIR-Genomics.xml +170 -0
  247. data/lib/tests/testscripts/xml/Connectathon11/Track6-FHIR-Genomics/_reference/resources/sequence-example-1.xml +31 -0
  248. data/lib/tests/testscripts/xml/Connectathon11/Track6-FHIR-Genomics/_reference/resources/sequence-example-2.xml +31 -0
  249. data/lib/tests/testscripts/xml/Connectathon11/Track7-LabOrderLabReport/Actors.png +0 -0
  250. data/lib/tests/testscripts/xml/Connectathon11/Track7-LabOrderLabReport/Client_Assigned_Id/track7-laborder100-xml.xml +590 -0
  251. data/lib/tests/testscripts/xml/Connectathon11/Track7-LabOrderLabReport/Client_Assigned_Id/track7-laborder200-xml.xml +587 -0
  252. data/lib/tests/testscripts/xml/Connectathon11/Track7-LabOrderLabReport/Client_Assigned_Id/track7-laborder300-xml.xml +612 -0
  253. data/lib/tests/testscripts/xml/Connectathon11/Track7-LabOrderLabReport/Client_Assigned_Id/track7-laborder400-xml.xml +635 -0
  254. data/lib/tests/testscripts/xml/Connectathon11/Track7-LabOrderLabReport/Peer-to-Peer/track7-laborder100-peer2peer-xml.xml +752 -0
  255. data/lib/tests/testscripts/xml/Connectathon11/Track7-LabOrderLabReport/Thumbs.db +0 -0
  256. data/lib/tests/testscripts/xml/Connectathon11/Track7-LabOrderLabReport/_reference/conformance/LabOrderLabReport-CreateDeleteReadUpdate.xml +187 -0
  257. data/lib/tests/testscripts/xml/Connectathon11/Track7-LabOrderLabReport/_reference/conformance/html.xslt +45 -0
  258. data/lib/tests/testscripts/xml/Connectathon11/Track7-LabOrderLabReport/_reference/resources/DiagnosticOrder/do-100-update.xml +64 -0
  259. data/lib/tests/testscripts/xml/Connectathon11/Track7-LabOrderLabReport/_reference/resources/DiagnosticOrder/do-100.xml +64 -0
  260. data/lib/tests/testscripts/xml/Connectathon11/Track7-LabOrderLabReport/_reference/resources/DiagnosticOrder/do-200-update.xml +121 -0
  261. data/lib/tests/testscripts/xml/Connectathon11/Track7-LabOrderLabReport/_reference/resources/DiagnosticOrder/do-200.xml +121 -0
  262. data/lib/tests/testscripts/xml/Connectathon11/Track7-LabOrderLabReport/_reference/resources/DiagnosticOrder/do-300-update.xml +91 -0
  263. data/lib/tests/testscripts/xml/Connectathon11/Track7-LabOrderLabReport/_reference/resources/DiagnosticOrder/do-300.xml +91 -0
  264. data/lib/tests/testscripts/xml/Connectathon11/Track7-LabOrderLabReport/_reference/resources/DiagnosticOrder/do-400-update.xml +88 -0
  265. data/lib/tests/testscripts/xml/Connectathon11/Track7-LabOrderLabReport/_reference/resources/DiagnosticOrder/do-400.xml +88 -0
  266. data/lib/tests/testscripts/xml/Connectathon11/Track7-LabOrderLabReport/_reference/resources/DiagnosticReport/dr-100.xml +96 -0
  267. data/lib/tests/testscripts/xml/Connectathon11/Track7-LabOrderLabReport/_reference/resources/DiagnosticReport/dr-200.xml +125 -0
  268. data/lib/tests/testscripts/xml/Connectathon11/Track7-LabOrderLabReport/_reference/resources/DiagnosticReport/dr-300.xml +132 -0
  269. data/lib/tests/testscripts/xml/Connectathon11/Track7-LabOrderLabReport/_reference/resources/DiagnosticReport/dr-400.xml +121 -0
  270. data/lib/tests/testscripts/xml/Connectathon11/Track7-LabOrderLabReport/_reference/resources/Observation/obs-100.xml +58 -0
  271. data/lib/tests/testscripts/xml/Connectathon11/Track7-LabOrderLabReport/_reference/resources/Observation/obs-101.xml +58 -0
  272. data/lib/tests/testscripts/xml/Connectathon11/Track7-LabOrderLabReport/_reference/resources/Observation/obs-200.xml +125 -0
  273. data/lib/tests/testscripts/xml/Connectathon11/Track7-LabOrderLabReport/_reference/resources/Observation/obs-300.xml +106 -0
  274. data/lib/tests/testscripts/xml/Connectathon11/Track7-LabOrderLabReport/_reference/resources/Observation/obs-301.xml +106 -0
  275. data/lib/tests/testscripts/xml/Connectathon11/Track7-LabOrderLabReport/_reference/resources/Observation/obs-302.xml +106 -0
  276. data/lib/tests/testscripts/xml/Connectathon11/Track7-LabOrderLabReport/_reference/resources/Observation/obs-303.xml +106 -0
  277. data/lib/tests/testscripts/xml/Connectathon11/Track7-LabOrderLabReport/_reference/resources/Observation/obs-304.xml +106 -0
  278. data/lib/tests/testscripts/xml/Connectathon11/Track7-LabOrderLabReport/_reference/resources/Observation/obs-400.xml +87 -0
  279. data/lib/tests/testscripts/xml/Connectathon11/Track7-LabOrderLabReport/_reference/resources/Observation/obs-401.xml +95 -0
  280. data/lib/tests/testscripts/xml/Connectathon11/Track7-LabOrderLabReport/_reference/resources/Observation/obs-402.xml +95 -0
  281. data/lib/tests/testscripts/xml/Connectathon11/Track7-LabOrderLabReport/_reference/resources/Observation/obs-403.xml +84 -0
  282. data/lib/tests/testscripts/xml/Connectathon11/Track7-LabOrderLabReport/_reference/resources/Observation/obs-404.xml +84 -0
  283. data/lib/tests/testscripts/xml/Connectathon11/Track7-LabOrderLabReport/_reference/resources/Observation/obs-405.xml +83 -0
  284. data/lib/tests/testscripts/xml/Connectathon11/Track7-LabOrderLabReport/_reference/resources/Observation/obs-406.xml +83 -0
  285. data/lib/tests/testscripts/xml/Connectathon11/Track7-LabOrderLabReport/_reference/resources/Observation/obs-407.xml +70 -0
  286. data/lib/tests/testscripts/xml/Connectathon11/Track7-LabOrderLabReport/_reference/resources/Observation/obs-408.xml +84 -0
  287. data/lib/tests/testscripts/xml/Connectathon11/Track7-LabOrderLabReport/_reference/resources/Observation/obs-uslab-example5.xml +102 -0
  288. data/lib/tests/testscripts/xml/Connectathon11/Track7-LabOrderLabReport/_reference/resources/Order/order-100.xml +61 -0
  289. data/lib/tests/testscripts/xml/Connectathon11/Track7-LabOrderLabReport/_reference/resources/Order/order-200.xml +61 -0
  290. data/lib/tests/testscripts/xml/Connectathon11/Track7-LabOrderLabReport/_reference/resources/Order/order-300.xml +61 -0
  291. data/lib/tests/testscripts/xml/Connectathon11/Track7-LabOrderLabReport/_reference/resources/Order/order-400.xml +61 -0
  292. data/lib/tests/testscripts/xml/Connectathon11/Track7-LabOrderLabReport/_reference/resources/OrderResponse/ordresp-100.xml +79 -0
  293. data/lib/tests/testscripts/xml/Connectathon11/Track7-LabOrderLabReport/_reference/resources/OrderResponse/ordresp-110.xml +79 -0
  294. data/lib/tests/testscripts/xml/Connectathon11/Track7-LabOrderLabReport/_reference/resources/OrderResponse/ordresp-200.xml +79 -0
  295. data/lib/tests/testscripts/xml/Connectathon11/Track7-LabOrderLabReport/_reference/resources/OrderResponse/ordresp-210.xml +79 -0
  296. data/lib/tests/testscripts/xml/Connectathon11/Track7-LabOrderLabReport/_reference/resources/OrderResponse/ordresp-300.xml +79 -0
  297. data/lib/tests/testscripts/xml/Connectathon11/Track7-LabOrderLabReport/_reference/resources/OrderResponse/ordresp-310.xml +79 -0
  298. data/lib/tests/testscripts/xml/Connectathon11/Track7-LabOrderLabReport/_reference/resources/OrderResponse/ordresp-400.xml +79 -0
  299. data/lib/tests/testscripts/xml/Connectathon11/Track7-LabOrderLabReport/_reference/resources/OrderResponse/ordresp-410.xml +79 -0
  300. data/lib/tests/testscripts/xml/Connectathon11/Track7-LabOrderLabReport/_reference/resources/Organization/org-uslab-example3.xml +49 -0
  301. data/lib/tests/testscripts/xml/Connectathon11/Track7-LabOrderLabReport/_reference/resources/Patient/patient-uslab-example1.xml +44 -0
  302. data/lib/tests/testscripts/xml/Connectathon11/Track7-LabOrderLabReport/_reference/resources/Practitioner/pract-uslab-example1.xml +18 -0
  303. data/lib/tests/testscripts/xml/Connectathon11/Track7-LabOrderLabReport/_reference/resources/Practitioner/pract-uslab-example3.xml +36 -0
  304. data/lib/tests/testscripts/xml/Connectathon11/Track7-LabOrderLabReport/_reference/resources/Specimen/Thumbs.db +0 -0
  305. data/lib/tests/testscripts/xml/Connectathon11/Track7-LabOrderLabReport/_reference/resources/Specimen/spec-100.xml +65 -0
  306. data/lib/tests/testscripts/xml/Connectathon11/Track7-LabOrderLabReport/_reference/resources/Specimen/spec-400.xml +70 -0
  307. data/lib/tests/testscripts/xml/Connectathon11/Track7-LabOrderLabReport/_reference/resources/Specimen/spec-uslab-example1.xml +82 -0
  308. data/lib/tests/testscripts/xml/Connectathon11/Track7-LabOrderLabReport/_reference/resources/Testscript 1 Document.txt +122 -0
  309. data/lib/tests/testscripts/xml/Connectathon11/Track7-LabOrderLabReport/_reference/resources/Testscript 2 Document.txt +103 -0
  310. data/lib/tests/testscripts/xml/Connectathon11/Track7-LabOrderLabReport/_reference/resources/Testscript 3 Document.txt +201 -0
  311. data/lib/tests/testscripts/xml/Connectathon11/Track7-LabOrderLabReport/_reference/resources/Testscript 4 Document.txt +310 -0
  312. data/lib/tests/testscripts/xml/Connectathon11/Track9-Patch/_reference/conformance/MedicationStatementCreate.xml +11 -0
  313. data/lib/tests/testscripts/xml/Connectathon11/Track9-Patch/_reference/conformance/PatientSearchType.xml +15 -0
  314. data/lib/tests/testscripts/xml/Connectathon11/Track9-Patch/_reference/resources/medicationstatement-create.json +39 -0
  315. data/lib/tests/testscripts/xml/Connectathon11/Track9-Patch/_reference/resources/medicationstatement-patch.json +3 -0
  316. data/lib/tests/testscripts/xml/Connectathon11/Track9-Patch/track9-patch-medicationstatement-json-if-match.xml +321 -0
  317. data/lib/tests/testscripts/xml/Connectathon11/Track9-Patch/track9-patch-medicationstatement-json.xml +303 -0
  318. data/lib/tests/testscripts/xml/Connectathon11/Track9-Patch/track9-patch-peer2peer-patient-json.xml +235 -0
  319. data/plan_executor.gemspec +14 -0
  320. data/test/fixtures/diagnostic_bundle.xml +51 -0
  321. data/test/fixtures/lab_results_bundle.xml +49 -0
  322. data/test/fixtures/observation_bundle.json +61 -0
  323. data/test/fixtures/testscript-example.xml +202 -0
  324. data/test/fixtures/testscript-history.xml +143 -0
  325. data/test/fixtures/testscript-readtest.xml +272 -0
  326. data/test/fixtures/testscript-search.xml +282 -0
  327. data/test/fixtures/testscript-update.xml +147 -0
  328. data/test/fixtures/vital_signs_bundle.xml +117 -0
  329. data/test/test_helper.rb +8 -0
  330. data/test/unit/argonaut_sprint6_test.rb +31 -0
  331. data/test/unit/argonaut_sprint7_test.rb +21 -0
  332. data/test/unit/basic_test.rb +27 -0
  333. data/test/unit/fetch_patient_record_test.rb +357 -0
  334. data/test/unit/financial_test.rb +41 -0
  335. data/test/unit/fixtures_test.rb +45 -0
  336. data/test/unit/metadata_test.rb +33 -0
  337. metadata +394 -0
@@ -0,0 +1,79 @@
1
+ <?xml version="1.0" encoding="UTF-8"?>
2
+ <OrderResponse xmlns="http://hl7.org/fhir">
3
+ <id value="ordresp-300"/>
4
+ <text>
5
+ <status value="generated"/>
6
+ <div xmlns="http://www.w3.org/1999/xhtml">
7
+ <p>
8
+ <b>Generated Narrative with Details</b>
9
+ </p>
10
+ <p>
11
+ <b>id</b>: ordresp-300</p>
12
+ <p>
13
+ <b>identifier</b>: FILL = ordresp-300</p>
14
+ <p>
15
+ <b>request</b>:
16
+ <a href="Order/order-300">Order/order-300</a>
17
+ </p>
18
+ <p>
19
+ <b>date</b>: 12/15/2015 7:36:25 AM</p>
20
+ <p>
21
+ <b>who</b>:
22
+ <a href="Organization/org-uslab-example3">Acme Labs</a>
23
+ </p>
24
+ <p>
25
+ <b>orderStatus</b>: accepted</p>
26
+ </div>
27
+ </text>
28
+ <identifier>
29
+ <type>
30
+ <coding>
31
+ <code value="http://hl7.org/fhir/identifier-type"/>
32
+ <display value="FILL"/>
33
+ </coding>
34
+ </type>
35
+ <system value="http://lis.acmelabs.org/identifiers"/>
36
+ <value value="ordresp-300"/>
37
+ </identifier>
38
+ <!--
39
+ this should be a response to the example request,
40
+ but we don't yet have all the resource types in
41
+ place to make this happen
42
+
43
+ So for now, although the Order message referred to
44
+ here contains a prescription resource, this example
45
+ response contains lab reports
46
+ -->
47
+ <request>
48
+ <reference value="Order/order-300"/>
49
+ </request>
50
+ <date value="2015-12-15T07:36:25Z"/>
51
+ <!-- made by the lab -->
52
+ <who>
53
+ <reference value="Organization/org-uslab-example3"/>
54
+ <display value="Acme Labs"/>
55
+ </who>
56
+ <!--
57
+ there's a loose relationship between the status of
58
+ the order, and status information on the fulfillment
59
+ resources. For instance, in the case of a lab, it probably
60
+ wouldn't make sense to claim that the response is anything
61
+ but completed when the report is marked as "final" (as it is
62
+ in this case). However due to the diversity of business
63
+ practices in the order/fulfillment cycle, there's no formal
64
+ rules about what is allowed
65
+ -->
66
+ <orderStatus value="accepted"/>
67
+ <!--
68
+ the lab report that the lab provides as a token of its
69
+ fulfillment for this order
70
+
71
+ In the case of a lab order, the report is usually the real/only
72
+ outcome. However in a case such as a medication administration,
73
+ the actual administration is the fulfillment - the MedicationAdministration
74
+ resource is only a token of the fulfillment of the order
75
+ -->
76
+ <!--<fulfillment>
77
+ <reference value="DiagnosticReport/101"/>
78
+ </fulfillment>-->
79
+ </OrderResponse>
@@ -0,0 +1,79 @@
1
+ <?xml version="1.0" encoding="UTF-8"?>
2
+ <OrderResponse xmlns="http://hl7.org/fhir">
3
+ <id value="ordresp-310"/>
4
+ <text>
5
+ <status value="generated"/>
6
+ <div xmlns="http://www.w3.org/1999/xhtml">
7
+ <p>
8
+ <b>Generated Narrative with Details</b>
9
+ </p>
10
+ <p>
11
+ <b>id</b>: ordresp-310</p>
12
+ <p>
13
+ <b>identifier</b>: FILL = ordresp-310</p>
14
+ <p>
15
+ <b>request</b>:
16
+ <a href="Order/order-300">Order/order-300</a>
17
+ </p>
18
+ <p>
19
+ <b>date</b>: 12/15/2015 7:36:25 AM</p>
20
+ <p>
21
+ <b>who</b>:
22
+ <a href="Organization/org-uslab-example3">Acme Labs</a>
23
+ </p>
24
+ <p>
25
+ <b>orderStatus</b>: completed</p>
26
+ </div>
27
+ </text>
28
+ <identifier>
29
+ <type>
30
+ <coding>
31
+ <code value="http://hl7.org/fhir/identifier-type"/>
32
+ <display value="FILL"/>
33
+ </coding>
34
+ </type>
35
+ <system value="http://lis.acmelabs.org/identifiers"/>
36
+ <value value="ordresp-310"/>
37
+ </identifier>
38
+ <!--
39
+ this should be a response to the example request,
40
+ but we don't yet have all the resource types in
41
+ place to make this happen
42
+
43
+ So for now, although the Order message referred to
44
+ here contains a prescription resource, this example
45
+ response contains lab reports
46
+ -->
47
+ <request>
48
+ <reference value="Order/order-300"/>
49
+ </request>
50
+ <date value="2015-12-15T07:36:25Z"/>
51
+ <!-- made by the lab -->
52
+ <who>
53
+ <reference value="Organization/org-uslab-example3"/>
54
+ <display value="Acme Labs"/>
55
+ </who>
56
+ <!--
57
+ there's a loose relationship between the status of
58
+ the order, and status information on the fulfillment
59
+ resources. For instance, in the case of a lab, it probably
60
+ wouldn't make sense to claim that the response is anything
61
+ but completed when the report is marked as "final" (as it is
62
+ in this case). However due to the diversity of business
63
+ practices in the order/fulfillment cycle, there's no formal
64
+ rules about what is allowed
65
+ -->
66
+ <orderStatus value="completed"/>
67
+ <!--
68
+ the lab report that the lab provides as a token of its
69
+ fulfillment for this order
70
+
71
+ In the case of a lab order, the report is usually the real/only
72
+ outcome. However in a case such as a medication administration,
73
+ the actual administration is the fulfillment - the MedicationAdministration
74
+ resource is only a token of the fulfillment of the order
75
+ -->
76
+ <!--<fulfillment>
77
+ <reference value="DiagnosticReport/101"/>
78
+ </fulfillment>-->
79
+ </OrderResponse>
@@ -0,0 +1,79 @@
1
+ <?xml version="1.0" encoding="UTF-8"?>
2
+ <OrderResponse xmlns="http://hl7.org/fhir">
3
+ <id value="ordresp-400"/>
4
+ <text>
5
+ <status value="generated"/>
6
+ <div xmlns="http://www.w3.org/1999/xhtml">
7
+ <p>
8
+ <b>Generated Narrative with Details</b>
9
+ </p>
10
+ <p>
11
+ <b>id</b>: ordresp-400</p>
12
+ <p>
13
+ <b>identifier</b>: FILL = ordresp-400</p>
14
+ <p>
15
+ <b>request</b>:
16
+ <a href="Order/order-400">Order/order-400</a>
17
+ </p>
18
+ <p>
19
+ <b>date</b>: 12/15/2015 7:36:25 AM</p>
20
+ <p>
21
+ <b>who</b>:
22
+ <a href="Organization/org-uslab-example3">Acme Labs</a>
23
+ </p>
24
+ <p>
25
+ <b>orderStatus</b>: accepted</p>
26
+ </div>
27
+ </text>
28
+ <identifier>
29
+ <type>
30
+ <coding>
31
+ <code value="http://hl7.org/fhir/identifier-type"/>
32
+ <display value="FILL"/>
33
+ </coding>
34
+ </type>
35
+ <system value="http://lis.acmelabs.org/identifiers"/>
36
+ <value value="ordresp-400"/>
37
+ </identifier>
38
+ <!--
39
+ this should be a response to the example request,
40
+ but we don't yet have all the resource types in
41
+ place to make this happen
42
+
43
+ So for now, although the Order message referred to
44
+ here contains a prescription resource, this example
45
+ response contains lab reports
46
+ -->
47
+ <request>
48
+ <reference value="Order/order-400"/>
49
+ </request>
50
+ <date value="2015-12-15T07:36:25Z"/>
51
+ <!-- made by the lab -->
52
+ <who>
53
+ <reference value="Organization/org-uslab-example3"/>
54
+ <display value="Acme Labs"/>
55
+ </who>
56
+ <!--
57
+ there's a loose relationship between the status of
58
+ the order, and status information on the fulfillment
59
+ resources. For instance, in the case of a lab, it probably
60
+ wouldn't make sense to claim that the response is anything
61
+ but completed when the report is marked as "final" (as it is
62
+ in this case). However due to the diversity of business
63
+ practices in the order/fulfillment cycle, there's no formal
64
+ rules about what is allowed
65
+ -->
66
+ <orderStatus value="accepted"/>
67
+ <!--
68
+ the lab report that the lab provides as a token of its
69
+ fulfillment for this order
70
+
71
+ In the case of a lab order, the report is usually the real/only
72
+ outcome. However in a case such as a medication administration,
73
+ the actual administration is the fulfillment - the MedicationAdministration
74
+ resource is only a token of the fulfillment of the order
75
+ -->
76
+ <!--<fulfillment>
77
+ <reference value="DiagnosticReport/101"/>
78
+ </fulfillment>-->
79
+ </OrderResponse>
@@ -0,0 +1,79 @@
1
+ <?xml version="1.0" encoding="UTF-8"?>
2
+ <OrderResponse xmlns="http://hl7.org/fhir">
3
+ <id value="ordresp-410"/>
4
+ <text>
5
+ <status value="generated"/>
6
+ <div xmlns="http://www.w3.org/1999/xhtml">
7
+ <p>
8
+ <b>Generated Narrative with Details</b>
9
+ </p>
10
+ <p>
11
+ <b>id</b>: ordresp-410</p>
12
+ <p>
13
+ <b>identifier</b>: FILL = ordresp-410</p>
14
+ <p>
15
+ <b>request</b>:
16
+ <a href="Order/order-400">Order/order-400</a>
17
+ </p>
18
+ <p>
19
+ <b>date</b>: 12/15/2015 7:36:25 AM</p>
20
+ <p>
21
+ <b>who</b>:
22
+ <a href="Organization/org-uslab-example3">Acme Labs</a>
23
+ </p>
24
+ <p>
25
+ <b>orderStatus</b>: completed</p>
26
+ </div>
27
+ </text>
28
+ <identifier>
29
+ <type>
30
+ <coding>
31
+ <code value="http://hl7.org/fhir/identifier-type"/>
32
+ <display value="FILL"/>
33
+ </coding>
34
+ </type>
35
+ <system value="http://lis.acmelabs.org/identifiers"/>
36
+ <value value="ordresp-410"/>
37
+ </identifier>
38
+ <!--
39
+ this should be a response to the example request,
40
+ but we don't yet have all the resource types in
41
+ place to make this happen
42
+
43
+ So for now, although the Order message referred to
44
+ here contains a prescription resource, this example
45
+ response contains lab reports
46
+ -->
47
+ <request>
48
+ <reference value="Order/order-400"/>
49
+ </request>
50
+ <date value="2015-12-15T07:36:25Z"/>
51
+ <!-- made by the lab -->
52
+ <who>
53
+ <reference value="Organization/org-uslab-example3"/>
54
+ <display value="Acme Labs"/>
55
+ </who>
56
+ <!--
57
+ there's a loose relationship between the status of
58
+ the order, and status information on the fulfillment
59
+ resources. For instance, in the case of a lab, it probably
60
+ wouldn't make sense to claim that the response is anything
61
+ but completed when the report is marked as "final" (as it is
62
+ in this case). However due to the diversity of business
63
+ practices in the order/fulfillment cycle, there's no formal
64
+ rules about what is allowed
65
+ -->
66
+ <orderStatus value="completed"/>
67
+ <!--
68
+ the lab report that the lab provides as a token of its
69
+ fulfillment for this order
70
+
71
+ In the case of a lab order, the report is usually the real/only
72
+ outcome. However in a case such as a medication administration,
73
+ the actual administration is the fulfillment - the MedicationAdministration
74
+ resource is only a token of the fulfillment of the order
75
+ -->
76
+ <!--<fulfillment>
77
+ <reference value="DiagnosticReport/101"/>
78
+ </fulfillment>-->
79
+ </OrderResponse>
@@ -0,0 +1,49 @@
1
+ <?xml version="1.0" encoding="UTF-8"?>
2
+ <Organization xmlns="http://hl7.org/fhir">
3
+ <id value="org-uslab-example3"/>
4
+ <text>
5
+ <status value="generated"/>
6
+ <div xmlns="http://www.w3.org/1999/xhtml">
7
+ <p>
8
+ <b>Generated Narrative with Details</b>
9
+ </p>
10
+ <p>
11
+ <b>id</b>: org-uslab-example3</p>
12
+ <p>
13
+ <b>identifier</b>: 01D1111111 (official)</p>
14
+ <p>
15
+ <b>name</b>: Acme Labs</p>
16
+ <p>
17
+ <b>address</b>: Firstcare Way Building 2 Harrisburg PA 42043 USA (work)</p>
18
+ </div>
19
+ </text>
20
+ <identifier>
21
+ <use value="official"/>
22
+ <system value="http://www.cms.gov/Regulations-and-Guidance/Legislation/CLIA/index.html"/>
23
+ <!-- CLIA -->
24
+ <value value="01D1111111"/>
25
+ </identifier>
26
+ <name value="Acme Labs"/>
27
+ <address>
28
+ <!-- EH extension for us county -->
29
+ <extension url="http://hl7.org/fhir/StructureDefinition/us-core-county">
30
+ <valueString value="42043"/>
31
+ </extension>
32
+ <use value="work"/>
33
+ <line value="Firstcare Way"/>
34
+ <line value="Building 2"/>
35
+ <city value="Harrisburg"/>
36
+ <state value="PA"/>
37
+ <postalCode value="42043"/>
38
+ <country value="USA"/>
39
+ </address>
40
+ <contact>
41
+ <name>
42
+ <family value="House"/>
43
+ <given value="Gregory"/>
44
+ <given value="F"/>
45
+ <prefix value="Dr"/>
46
+ <suffix value="PhD"/>
47
+ </name>
48
+ </contact>
49
+ </Organization>
@@ -0,0 +1,44 @@
1
+ <?xml version="1.0" encoding="UTF-8"?><Patient xmlns="http://hl7.org/fhir">
2
+ <id value="patient-uslab-example1"/>
3
+ <text><status value="generated"/><div xmlns="http://www.w3.org/1999/xhtml"><p><b>Generated Narrative with Details</b></p><p><b>id</b>: patient-uslab-example1</p><p><b>identifier</b>: 18547545 (USUAL)</p><p><b>name</b>: Todd G. Lerr (OFFICIAL)</p><p><b>gender</b>: male</p><p><b>birthDate</b>: Jun 7, 2012</p><p><b>deceased</b>: false</p><p><b>address</b>: 123 North 102nd Street Apt 4d Harrisburg PA 17102 USA (HOME)</p></div></text><extension url="http://hl7.org/fhir/StructureDefinition/us-core-race">
4
+ <valueCodeableConcept>
5
+ <coding>
6
+ <code value="2106-3"/>
7
+ </coding>
8
+ </valueCodeableConcept>
9
+ </extension>
10
+ <extension url="http://hl7.org/fhir/StructureDefinition/us-core-ethnicity">
11
+ <valueCodeableConcept>
12
+ <coding>
13
+ <code value="2135-2"/>
14
+ </coding>
15
+ </valueCodeableConcept>
16
+ </extension>
17
+ <!-- EH: limit to single identifier that orderer can match to patient system can be URL -->
18
+ <identifier>
19
+ <use value="usual"/>
20
+ <system value="urn:oid:2.16.840.1.113883.3.72.5.30.2"/>
21
+ <value value="18547545"/>
22
+ </identifier>
23
+ <!-- name use limited to official and anonymous -->
24
+ <name>
25
+ <use value="official"/>
26
+ <family value="Lerr"/>
27
+ <given value="Todd"/>
28
+ <given value="G."/>
29
+ <suffix value="Jr"/>
30
+ </name>
31
+ <!-- use FHIR code system for male / female -->
32
+ <gender value="male"/>
33
+ <birthDate value="2012-06-07"/>
34
+ <deceasedBoolean value="false"/>
35
+ <address>
36
+ <use value="home"/>
37
+ <line value="123 North 102nd Street"/>
38
+ <line value="Apt 4d"/>
39
+ <city value="Harrisburg"/>
40
+ <state value="PA"/>
41
+ <postalCode value="17102"/>
42
+ <country value="USA"/>
43
+ </address>
44
+ </Patient>
@@ -0,0 +1,18 @@
1
+ <?xml version="1.0" encoding="UTF-8"?><Practitioner xmlns="http://hl7.org/fhir">
2
+ <id value="pract-uslab-example1"/>
3
+ <text><status value="generated"/><div xmlns="http://www.w3.org/1999/xhtml"><p><b>Generated Narrative with Details</b></p><p><b>id</b>: pract-uslab-example1</p><p><b>identifier</b>: 4444444445 (OFFICIAL)</p><p><b>name</b>: Leanard T Bloodraw </p><p><b>telecom</b>: ph: (555)7771234 ext.11</p></div></text><identifier>
4
+ <use value="official"/>
5
+ <system value="http://hl7.org/fhir/sid/us-npi"/> <!-- NPI -->
6
+ <value value="4444444445"/>
7
+ </identifier>
8
+ <name>
9
+ <family value="Bloodraw"/>
10
+ <given value="Leanard"/>
11
+ <given value="T"/>
12
+ <suffix value="Jr"/>
13
+ </name>
14
+ <telecom>
15
+ <system value="phone"/>
16
+ <value value="(555)7771234 ext.11"/>
17
+ </telecom>
18
+ </Practitioner>
@@ -0,0 +1,36 @@
1
+ <?xml version="1.0" encoding="UTF-8"?>
2
+ <Practitioner xmlns="http://hl7.org/fhir">
3
+ <id value="pract-uslab-example3"/>
4
+ <text>
5
+ <status value="generated"/>
6
+ <div xmlns="http://www.w3.org/1999/xhtml">
7
+ <p>
8
+ <b>Generated Narrative with Details</b>
9
+ </p>
10
+ <p>
11
+ <b>id</b>: pract-uslab-example3</p>
12
+ <p>
13
+ <b>identifier</b>: 1234567893 (official)</p>
14
+ <p>
15
+ <b>name</b>: Gregory F House </p>
16
+ <p>
17
+ <b>telecom</b>: ph: 555 777 1234 11</p>
18
+ </div>
19
+ </text>
20
+ <identifier>
21
+ <use value="official"/>
22
+ <system value="http://hl7.org/fhir/sid/us-npi"/>
23
+ <!-- NPI -->
24
+ <value value="1234567893"/>
25
+ </identifier>
26
+ <name>
27
+ <family value="House"/>
28
+ <given value="Gregory"/>
29
+ <given value="F"/>
30
+ <suffix value="PhD"/>
31
+ </name>
32
+ <telecom>
33
+ <system value="phone"/>
34
+ <value value="555 777 1234 11"/>
35
+ </telecom>
36
+ </Practitioner>
@@ -0,0 +1,65 @@
1
+ <?xml version="1.0" encoding="UTF-8"?>
2
+ <Specimen xmlns="http://hl7.org/fhir">
3
+ <id value="spec-100"/>
4
+ <text>
5
+ <status value="generated"/>
6
+ <div xmlns="http://www.w3.org/1999/xhtml">
7
+ <p>
8
+ <b>Generated Narrative with Details</b>
9
+ </p>
10
+ <p>
11
+ <b>id</b>: spec-100</p>
12
+ <p>
13
+ <b>type</b>: Platelet-free plasma
14
+ <span style="background: LightGoldenRodYellow ">(Details : {SNOMED CT code "708048008" := "708048008", given as "Plasma specimen with citrate"}; {http://ehr.goodhealthclinic.org/specimens/type code "PFP" := "PFP", given as "Platelet Free Plasma"})</span>
15
+ </p>
16
+ <p>
17
+ <b>subject</b>:
18
+ <a href="Patient/patient-uslab-example1">Todd Lerr</a>
19
+ </p>
20
+ <p>
21
+ <b>accessionIdentifier</b>: spec-100 (official)</p>
22
+ </div>
23
+ </text>
24
+ <!--Assume no specimen placer ID for now <identifier> <use value="official"/> <system value="http://ehr.goodhealthclinic.org/identifiers/specimen"/> <value value="spec-100"/> </identifier>-->
25
+ <!--Filler ID moved to accsession number-->
26
+ <!-- Type is a loosely defined field because there is such a lot of variation in how it is used. The principal variation is how much information that could be represented elsewhere is also represented here. For instance, here's some possible types: lithium heparin plasma (+ .container.additive) (e.g. SNOMED CT 446272009) transfusion bag of blood (+ container.type) Peritoneal lavage (+ collection.bodySite) If the type includes other fields, it would be normal not to populate the other fields Note that this practice is so widespread that it's pointless to try and stop it :( -->
27
+ <!-- choice of SNOMED CT concept code... -->
28
+ <type>
29
+ <coding>
30
+ <system value="http://snomed.info/sct"/>
31
+ <!-- EH: Note to balloters - lots of choices for whole blood I chose this. -->
32
+ <code value="708048008"/>
33
+ <display value="Plasma specimen with citrate"/>
34
+ </coding>
35
+ <!-- and or local code -->
36
+ <coding>
37
+ <system value="http://ehr.goodhealthclinic.org/specimens/type"/>
38
+ <code value="PFP"/>
39
+ <display value="Platelet Free Plasma"/>
40
+ </coding>
41
+ <text value="Platelet-free plasma"/>
42
+ </type>
43
+ <!-- Patient is required from core -->
44
+ <subject>
45
+ <reference value="Patient/patient-uslab-example1"/>
46
+ <display value="Todd Lerr"/>
47
+ </subject>
48
+ <!-- accession identifier - e.g. assigned by the labaratory when it is received. This is common, unlike specimen identifier -->
49
+ <accessionIdentifier>
50
+ <use value="official"/>
51
+ <system value="http://lis.acmelabs.org/identifiers/accession"/>
52
+ <value value="spec-100"/>
53
+ </accessionIdentifier>
54
+ <collection>
55
+ <!-- the time of collection is required. Usually a point in time, but can be a period (collectedPeriod) if it's a timed collection (e.g. a 24 hour urine) Should be same a effective times in obs and dr-->
56
+ <collectedDateTime value="2014-12-05"/>
57
+ <!-- <bodySite>-->
58
+ <!-- choice of SNOMED CT concept code... -->
59
+ <!--<coding> <system value="http://snomed.info/sct"/>-->
60
+ <!-- EH: Note to balloters - this is to demonstrate use of source for body site not really needed for blood draw. -->
61
+ <!--<code value="53120007"/> <display value="Arm"/> </coding>-->
62
+ <!-- and or local code -->
63
+ <!--<coding> <system value="http://ehr.goodhealthclinic.org"/> <code value="ARM"/> <display value="Arm"/> </coding> <text value="Drawn from Arm"/> </bodySite>-->
64
+ </collection>
65
+ </Specimen>
@@ -0,0 +1,70 @@
1
+ <?xml version="1.0" encoding="UTF-8"?>
2
+ <Specimen xmlns="http://hl7.org/fhir">
3
+ <id value="spec-400"/>
4
+ <text>
5
+ <status value="generated"/>
6
+ <div xmlns="http://www.w3.org/1999/xhtml">
7
+ <p>
8
+ <b>Generated Narrative with Details</b>
9
+ </p>
10
+ <p>
11
+ <b>id</b>: spec-400</p>
12
+ <p>
13
+ <b>type</b>: Stool specimen
14
+ <span style="background: LightGoldenRodYellow ">(Details : {SNOMED CT code "119339001" := "119339001", given as "Stool specimen"})</span>
15
+ </p>
16
+ <p>
17
+ <b>subject</b>:
18
+ <a href="Patient/patient-uslab-example1">Todd Lerr</a>
19
+ </p>
20
+ <p>
21
+ <b>accessionIdentifier</b>: 21041205000001 (official)</p>
22
+ </div>
23
+ </text>
24
+ <!-- a specimen identifier - e.g. assigned when the specimen was taken by the orderer/placer use the accession number for the filling lab -->
25
+ <!-- Placer ID -->
26
+ <!-- Filler ID moved to accsession number
27
+ <identifier>
28
+ <use value="official"></use>
29
+ <label value="Filler Specimen ID"></label>
30
+ <system value="http://lis.acmelabs.org/identifiers/specimen"/>
31
+ <value value="SID456"/>
32
+ </identifier>
33
+ -->
34
+ <!--
35
+ Type is a loosely defined field because there is such a lot of variation in how it is used.
36
+ The principal variation is how much information that could be represented elsewhere is also
37
+ represented here. For instance, here's some possible types:
38
+ lithium heparin plasma (+ .container.additive) (e.g. SNOMED CT 446272009)
39
+ transfusion bag of blood (+ container.type)
40
+ Peritoneal lavage (+ collection.bodySite)
41
+ If the type includes other fields, it would be normal not to populate the other fields
42
+
43
+ Note that this practice is so widespread that it's pointless to try and stop it :( -->
44
+ <!-- choice of SNOMED CT concept code... -->
45
+ <type>
46
+ <coding>
47
+ <system value="http://snomed.info/sct"/>
48
+ <code value="119339001"/>
49
+ <display value="Stool specimen"/>
50
+ </coding>
51
+ <text value="Stool specimen"/>
52
+ </type>
53
+ <!-- Patient is required from core -->
54
+ <subject>
55
+ <reference value="Patient/patient-uslab-example1"/>
56
+ <display value="Todd Lerr"/>
57
+ </subject>
58
+ <!-- accession identifier - e.g. assigned by the labaratory when it is received.
59
+ This is common, unlike specimen identifier -->
60
+ <accessionIdentifier>
61
+ <use value="official"/>
62
+ <system value="http://lis.acmelabs.org/identifiers/accession"/>
63
+ <value value="21041205000001"/>
64
+ </accessionIdentifier>
65
+ <collection>
66
+ <!-- the time of collection is required. Usually a point in time, but can be a period
67
+ (collectedPeriod) if it's a timed collection (e.g. a 24 hour urine) -->
68
+ <collectedDateTime value="2014-12-05"/>
69
+ </collection>
70
+ </Specimen>