openhie / case-reporting

case-reportingImplementation Guide

Case Reporting IG

This is the OpenHIE Case Reporting Implementation Guide.

Publication

This ImplementationGuide is published in the following locations:

Continuous Build: https://openhie.github.io/case-reporting/branches/intro-page
Canonical / permanent URL:

Issues

Issues and change requests are managed here:

Issues: https://github.com/openhie/case-reporting/issues
Kanban board: https://github.com/openhie/case-reporting/projects/10612176
Project board: https://github.com/orgs/openhie/projects/2/views/1?visibleFields=%5B%22Title%22%2C%22Assignees%22%2C%22Status%22%2C%22Repository%22%5D

case-reporting's Issues

add a data models page

Confirm if Transactions are OK

extension pagecontrol is not visible

extension pagecontrol is not visible

Document: OPENHIE.FHIR.CASEREPORTING\Case Reporting Questionnaire - JSON Representation - FHIR v4.0.1
Section: : Case Reporting Questionnaire - JSON Representation
Organization: JCT
Mail:

Add an introduction to the home page

Add an introduction to the home page - focused on generic case reporting.
“This IG is a common architecture IG, without any specific content focus…

Simple architecture (CRSubmitter, Transformer, Repository)

The overarching IG is based on the FHIR questionnaire only. Add other input options e.g. full bundles of resources (not only the questionnaire)

Consider including monitoring content in this generic case reporting IG

Add some usage workflows

Example scenarios?
Should we put APIs either here or in transactions section?
This is where we put the APIs together.

Add draft/proposed use cases - then we’ll see more details and structure are needed for the HIV-specific IG

Add the example usage workflows - one for each option (FHIR Bundle, FHIRQuestionnaire, CSV)

Add FHIR maturity to intro

Add this to the intro

There is value to having this information in the generic IG

Breakdown of click summary that implementers can refer to for guidance

Add a "Background" page

Add an "Actors" page

Include core set of expected actions in the case reporting IG - in the transactions?

Rename "FHIR Maturity levels" in Concepts page to "FHIR readiness levels "(?)

test comment

test comment

Document: OPENHIE.FHIR.CASEREPORTING\L1: OpenHIE Case Reporting - FHIR v4.0.1
Section: L1: OpenHIE Case Reporting
Organization: jct
Mail:

test comment

**test comment **

Document: OPENHIE.FHIR.CASEREPORTING\L1: OpenHIE Case Reporting - FHIR v4.0.1
Section: L1: OpenHIE Case Reporting
Organization: jct
Mail: no mail

Add/rework the intro page - focused on generic case reporting.

“This IG is a common architecture IG, without any specific content focus…”

OPENHIE.FHIR.CASEREPORTING\L1: OpenHIE Case Reporting - FHIR v4.0.1 / L1: OpenHIE Case Reporting(litlfred)

Document	Section	Comment	Organization Name	Mail
OPENHIE.FHIR.CASEREPORTING\L1: OpenHIE Case Reporting - FHIR v4.0.1	L1: OpenHIE Case Reporting	top level menu items aren't clickable to referenced pages	litlfred	[email protected]

add background/references page: Reference articles ; Types of IGs and their relationships

Change the diagram in the front page

fix the arrow that should be vertical

review Credits, acknowledgements, authors

Add 2 types of transactions to IG

Questionnaire
FHIR resources

Remove non-working feedback links

Create a "How to read this IG" page

Functional requirements

Can maybe see a connection between this section, usage workflows and the transaction section - revisit in next meeting with some examples

Add sample / simple use cases

Add Personas

Short list of examples of business roles

OPENHIE.FHIR.CASEREPORTINGV\OpenHIE Case Reporting Home Page - FHIR v4.0.1 / Summary(litlfred)

Document	Section	Comment	Organization Name	Mail
OPENHIE.FHIR.CASEREPORTINGV\OpenHIE Case Reporting Home Page - FHIR v4.0.1	Summary	needs better CSS	litlfred

Clean up actors page - after architecture update

Add a security and privacy page - at least with guidelines / attention points

Add Deployment support section/page

Instructions on how resources within this IG can be demonstrated. e.g. :
Suggesting an initial set of data/dummy data that can serve to validate the IG
Instructions for rolling out a HAPI server

This section will be limited in the generic case reporting IG, which is more architectural

Gap analysis with HIV IG

Draft Security and Privacy considerations page

Complete the architecture with the 3 options - FHIR, Questionnaire, CSV

Revise COVID IG in light of the restructured Case Reporting IG

Confirm actors

Reference Implementations

Consider one reference section that is broad and covers different types of references e.g. external references such as policies and guidelines, reference implementations, upstream and downstream IGs that are referenced…

Add translation on strings and valuesets

Add translation on strings and valuesets

Document: OPENHIE.FHIR.CASEREPORTING\Case Reporting Questionnaire - JSON Representation - FHIR v4.0.1
Section: : Case Reporting Questionnaire - JSON Representation
Organization: JCT
Mail:

OPENHIE.FHIR.CASEREPORTINGV\OpenHIE Case Reporting Home Page - FHIR v4.0.1 / OpenHIE Case Reporting Home Page(litlfred)

Document	Section	Comment	Organization Name	Mail
OPENHIE.FHIR.CASEREPORTINGV\OpenHIE Case Reporting Home Page - FHIR v4.0.1	OpenHIE Case Reporting Home Page	is it possible to get the Contents box that's on the home page on some of the other high level pages (e.g. concepts.html)?	litlfred

OPENHIE.FHIR.CASEREPORTINGV\Useful Downloads - FHIR v4.0.1 / Useful Downloads(litlfred)

Document	Section	Comment	Organization Name	Mail
OPENHIE.FHIR.CASEREPORTINGV\Useful Downloads - FHIR v4.0.1	Useful Downloads	would be useful to have a link to the npm package here	litlfred

Example content - can we tag as “this is just an example to get you going”? Is it a good practice to have these?