New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Document registry #32

Closed

clemens-msupply opened this issue May 23, 2022 · 1 comment

Assignees

Labels

back-end feature: programs

Contributor

clemens-msupply commented May 23, 2022 •

edited

Loading

For each store we need to know:

Which programs are available
Which document are associated with a program
Which schema a document should use
How document are related

This information can be stored in the following three tables:

document_registry: Defines how a document can be used (context) and what the default schema is
document_hierarchy: Defines how documents are connected, e.g. which encounter is possible for a certain program

clemens-msupply added feature: programs back-end labels

clemens-msupply mentioned this issue

32 document registry #121

Merged

clemens-msupply self-assigned this

clemens-msupply mentioned this issue

Add children node to the document registry node #162

Merged

Contributor Author

clemens-msupply commented Jul 22, 2022

document_hierarchy is not implemented since not needed right now

clemens-msupply closed this as completed

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment