| Quality Checks |
| Publisher Version: | IG Publisher Version: v1.2.22 |
| Publication Code: | vulcan-schedule . PackageId = hl7.fhir.uv.vulcan-schedule, Canonical = http://hl7.org/fhir/uv/vulcan-schedule |
| Realm Check for UV: | |
| Publication Request: |
| package-id | hl7.fhir.uv.vulcan-schedule |
| version | 1.0.0-ballot |
| path | http://hl7.org/fhir/uv/vulcan-schedule/2023Jan |
| milestone | false |
| status | ballot |
| sequence | STU1 |
| desc | This is the ballot version of the first release in the STU1 sequence. |
| category | Research |
| title | Clinical Study Schedule of Activities |
| introduction | Every research study has a number of activities that must be performed. Typically this is described in the study protocol as a succession of activities with a permissible interval between each one. For a specific Research Subject this is converted to a plan with actual dates. As the events occur a record is built up of the execution of the study for that specific subject. Less often thought about is the wider set of activities that go toward designing a study and setting it up. The mechanics of representation will be essentially the same but the consumers of the data are more likely to be the Sponsor or Agent for the Sponsor managing the study. This set of activities is likely to be completely independent of any patient record. Currently each software package used in the study holds its own representation of that schedule. This leads to repeated entry of the schedule frequently leading to differences in naming for a given event and omission of other events. Management and reporting of data during a study and subsequent aggregation of data are made more difficult. CTMS software packages that hold their own representation of a Study/Protocol schedule would ideally integrate with EHRs as well as other CTMS. This guide provides a set of FHIR Profiles that will allow for a schedule of activities of a clinical study to be represented using FHIR resources. It is currently restricted to the initial definition of the activities and uses the Workflow Definition resources. It provides some guidance on how to convert from the ODM-XML format to FHIR. Future iterations of the guide may include the actual implementation of the schedule and thus use the Event resources. This means of using FHIR to represent a structured schedule of activities enables interoperability between CTMS and EHRs when the subject/patient scheduling for protocol/study defined activities is initiated. |
| ci-build | http://build.fhir.org/ig/HL7/Vulcan-schedule-ig |
This IG has never been published  |
| Supressed Messages: | 2 Suppressed Issues
|
| Dependency Checks: | | Package | Version | FHIR | Canonical | Web Base | Comment |
|---|
  hl7.fhir.uv.vulcan-schedule | 1.0.0-ballot | R4 | http://hl7.org/fhir/uv/vulcan-schedule | | |
 hl7.terminology.r4 | 5.0.0 M | R4 | http://terminology.hl7.org | http://terminology.hl7.org/5.0.0 | |
Templates: hl7.vulcan.template#current -> hl7.fhir.template#current -> hl7.base.template#current -> fhir.base.template#current |
| Dependent IGs: | no references |
| Global Profiles: | (none declared) |
| HTA Analysis: | no Non-HL7 references found |
| R5 Dependencies: | (none) |
| Modifier Extensions: | (none) |
| Previous Version Comparison: | Unable to compare with previous version: Unable to find version history at http://hl7.org/fhir/uv/vulcan-schedule (Problem #1 with package-list.json at http://hl7.org/fhir/uv/vulcan-schedule: Invalid HTTP response 404 from http://hl7.org/fhir/uv/vulcan-schedule/package-list.json?nocache=1670184438696 (Not Found) (content in c:\temp\fhir-http-2.log)) |
| IPA Comparison: | n/a |
| Summary: | errors = 0, warn = 0, info = 0, broken links = 0 |