Skip to content
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

Create blue book feature, function and application system catalogues #6

Closed
KonradHoeffner opened this issue Dec 3, 2019 · 10 comments
Closed

Create blue book feature, function and application system catalogues #6

KonradHoeffner opened this issue Dec 3, 2019 · 10 comments
Assignees
@KonradHoeffner @FranziskaJahn @ThomasPause
Labels
enhancement New feature or request
Milestone
0.1

Comments

@KonradHoeffner
Copy link
Collaborator

Page 123 in the written book second edition, table 6.7.
@KonradHoeffner KonradHoeffner added the enhancement New feature or request label Dec 3, 2019
@KonradHoeffner KonradHoeffner added this to the medfloss milestone Dec 3, 2019
@KonradHoeffner KonradHoeffner self-assigned this Dec 3, 2019
@KonradHoeffner KonradHoeffner changed the title Create blue blue feature and function catalogues Create blue book feature and function catalogues Dec 23, 2019
@KonradHoeffner
Copy link
Collaborator Author

KonradHoeffner commented Jan 20, 2020 •
edited
Loading

KonradHoeffner added a commit to hitontology/csv2rdf that referenced this issue Jan 20, 2020
@KonradHoeffner
Fix Bb Reference model catalogue name. Part of hitontology/ontology#6.
b63b1e5
KonradHoeffner added a commit that referenced this issue Jan 20, 2020
@KonradHoeffner
Fix Bb Reference model catalogue name. Part of #6.
b051e25
@ThomasPause ThomasPause added the needsDiscussion it needs some talking label Jan 23, 2020
@ThomasPause ThomasPause mentioned this issue Jan 23, 2020
Closed
@KonradHoeffner KonradHoeffner changed the title Create blue book feature and function catalogues Create blue book feature, function and application system catalogues Feb 24, 2020
@KonradHoeffner
Copy link
Collaborator Author

KonradHoeffner commented Feb 24, 2020 •
edited
Loading

One application system catalogue:
Chapters 6.4.1 till 6.4.13: each heading is a classified application system.
6.4.14 table: Each cell in the first column is also a classified application system.

@KonradHoeffner
Copy link
Collaborator Author

KonradHoeffner commented Feb 24, 2020 •
edited
Loading

https://hitontology.eu/ontology/BbOperationManagementSystemFeatureCatalogue is missing entries.
Merge all tables 6.1 to 6.13, which list single features. All into one catalogue.

@KonradHoeffner
Copy link
Collaborator Author

@FranziskaJahn: Ich habe mal nachgeforscht, der existierende Function- und Featurekatalog stammt aus dem blue book PDF manuscript von 2010 Seite 142 Tabelle 6-7: "typical supported hospital functions and related features of the operation management system".

@ThomasPause
Copy link

BB Operation Management System Feature Catalogue's extraction is ready and can be found here.

@KonradHoeffner
Copy link
Collaborator Author

KonradHoeffner commented Apr 21, 2020 •
edited
Loading

The results are online at

@KonradHoeffner
Copy link
Collaborator Author

KonradHoeffner commented Apr 21, 2020 •
edited
Loading

This was discussed in the SNIK Jour Fixe 2020-04-21.

  • The name "Blue Book Operation Management System Function Catalogue" is wrong now because an Operation Management System is an application system for medical operations (surgeries), which only applies to the original table 6.7. Rename the catalogues to "Blue Book Architecture Function/Feature/Application System Catalogue"

Each of those tables represents a different application component:

Table Application System URI
6.1 Patient Administration System https://www.snik.eu/ontology/bb/PatientAdministrationSystem
6.2 Medical Documentation System https://www.snik.eu/ontology/bb/MedicalDocumentationSystem
6.3 Nursing Management and Documentation System https://www.snik.eu/ontology/bb/NursingManagementAndDocumentationSystem
6.4 Outpatient Management System https://www.snik.eu/ontology/bb/OutpatientManagementSystem
6.5 Physician Order Entry System we only have https://www.snik.eu/ontology/bb/ComputerizedPhysicianOrderEntrySystem
6.6 Patient Data Management System https://www.snik.eu/ontology/bb/PatientDataManagementSystem
6.7 Operation Management System https://www.snik.eu/ontology/bb/OperationManagementSystem
6.8 Radiology Information System https://www.snik.eu/ontology/bb/RadiologyInformationSystem
6.9 Radiology Information System (hier müsste PACS stehen denke ich) https://www.snik.eu/ontology/bb/PictureArchivingAndCommunicationSystem
6.10 Laboratory Information System https://www.snik.eu/ontology/bb/LaboratoryInformationSystem
6.11 Enterprise Resource Planning System https://www.snik.eu/ontology/bb/EnterpriseResourcePlanningSystem
6.12 Data Warehouse System https://www.snik.eu/ontology/bb/DataWarehouseSystem
6.13 Document Archiving System https://www.snik.eu/ontology/bb/DocumentArchivingSystem

@KonradHoeffner
Copy link
Collaborator Author

KonradHoeffner commented Apr 21, 2020 •
edited
Loading

  • connect HITO to BB

When we connect HITO with BB using the HITO BB catalogue, we now create our own instances of catalogues and classified application systems, features and functions. It would be better to use BB classes directly. However:

  • in SNIK they are classes but in HITO instances
  • we need the HITO types hito:ClassifiedFeature on so on, and don't want to assign them in SNIK
  • we also need to connect XClassified to its catalogue with XClassified as the subject, so we would need to add triples to BB classes from within HITO

Due to those problems, using BB classes directly is not possible. So I will implement the following compromise:

  • add a dcterms:source column to the BB spreadsheets and prefill it with the catalogue entry suffix but BB prefix
  • create a SPARQL instance existence checker to see which ones this misses, see https://github.com/hitontology/csv2rdf/blob/master/check.py
  • try to save the misses using the SNIK Graph search or daring URL guessing, remove what is not salvageable
  • add dcterms:source support to the relevant templates in https://github.com/hitontology/csv2rdf
  • use dc:source with "Table${x}.${y}" values to note source for the features, some of which may be included in multiple tables
  • merge duplicated functions
  • merge features (keep lines though, just align the URIs)
  • update the result in bb.rdf
  • review bb.rdf by Konrad
  • split the values of the "super" column in the subfeature template
  • upload the new version of HITO to the SPARQL endpoint
  • review of the results by Konrad
  • test the catalogues in the instance generator

@KonradHoeffner KonradHoeffner mentioned this issue Apr 21, 2020
Open
KonradHoeffner added a commit to hitontology/csv2rdf that referenced this issue Apr 22, 2020
@KonradHoeffner
Support dcterms:source and dc:source for issue hitontology/ontology#6.
428a689
KonradHoeffner added a commit that referenced this issue Apr 22, 2020
@KonradHoeffner
Improve blue book catalogue for issue #6.
fac7e70
@KonradHoeffner
Copy link
Collaborator Author

Removed the task to create SKOS links between SNIK and HITO BB catalogue entries because fac7e70 adds links via dcterms:source instead.

@KonradHoeffner KonradHoeffner mentioned this issue Jan 26, 2021
Closed
1 task
@KonradHoeffner
Copy link
Collaborator Author

As the catalogues are finished, close this issue. Additions are moved into issue #44.

@KonradHoeffner KonradHoeffner modified the milestones: 0.2, 0.1 Jan 28, 2021
@KonradHoeffner KonradHoeffner removed the needsDiscussion it needs some talking label May 18, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@KonradHoeffner KonradHoeffner

@FranziskaJahn FranziskaJahn

@ThomasPause ThomasPause

Labels
enhancement New feature or request
Projects
None yet
Milestone
0.1
Development

No branches or pull requests
3 participants
@KonradHoeffner @FranziskaJahn @ThomasPause