...
- John Walker (SemanticClarity)
- Mukundan Parthasarathy (SemanticClarity)
Interested Members (add your name and organization if you may be interested in joining this FG)
...
- Remotely Accessible Patient EHR - patient expressly requests creation of a FHIR based EHR representation to be used by different Health Care providers in different (same country) locale. (This use case can evolve to support crossing national boundaries thus adding complexity)
- Consent to participate in Clinical Research (FHIR data)
- Consent to participate in a Clinical Trial. (CDISC:SDTM data (see SDTM Implementation Guide v.3.2 here))
- Specify the data and credential requirements for Patient Identity and Matching (e.g. ER visit)
Scope
Use case | Minimal mapping of FHIR r4 resources (include transitive dependencies via Referencetype properties/slots). | Comments (FHIR Profile to be identified) |
|---|---|---|
| Remotely accessible patient EHR | There are multiple use cases here, expect to start with Immunization and ImagingStudy | CDA not in scope. |
| Consent to participate in clinical research | Consent, Contract | Handling instructions: Medical treatment and Research consent directives are not explicitly modeled in R4, might require use of Contract etc. |
| Consent to participate in clinical trials | Consent, Contract | Handling instructions: Medical treatment and Research consent directives are not explicitly modeled in R4, might require use of Contract etc. |
| ER Visit/specify data and credential requirements for patient identity and matching | Consent, Contract | Handling instructions: Privacy Consent directive. |
Deliverables
- Identity and specify the base FHIR resources required to support the FG use cases above.
- OCA FHIR schema bases representing a core set of base FHIR resources to support the FG use cases.
- Specify core overlays necessary to support the FHIR-compliant OCA schema bases
- Demonstrate the correctness of structure and version between the base FHIR resource and the corresponding FHIR-compliant OCA schema base.
- Demonstrate the complete and correct mapping of data values between the base FHIR resource and the corresponding populated FHIR-compliant OCA schema base.
- Create a FHIR extensibility example, create a FHIR payload to support a selected FHIR-compliant OCA schema base.
- Specification for FHIR-compliant OCA schema base and overlay processing rules.
...
- Rich Schema Objects
- Interop with an Order Overlay
- Interop with Verifiable Credentials (VCs)
- Interoperability with the Ecosystem Foundry WG
- ToIP: Federated access model/SSI interop issues as identified
- Harmonization with general consent (e.g. Notice and Consent WG deliverables) and Domain specific (FHIR Consent model from this TF)
- W3C Data Privacy Vocabulary & Personal Data Category (ontology)
Issues and resolution
FHIR R4 support for json-ld (resolution: tbd, workaround approach needs to be finalized)