-
Notifications
You must be signed in to change notification settings - Fork 1
/
bb.ttl
10084 lines (8617 loc) · 533 KB
/
bb.ttl
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
132
133
134
135
136
137
138
139
140
141
142
143
144
145
146
147
148
149
150
151
152
153
154
155
156
157
158
159
160
161
162
163
164
165
166
167
168
169
170
171
172
173
174
175
176
177
178
179
180
181
182
183
184
185
186
187
188
189
190
191
192
193
194
195
196
197
198
199
200
201
202
203
204
205
206
207
208
209
210
211
212
213
214
215
216
217
218
219
220
221
222
223
224
225
226
227
228
229
230
231
232
233
234
235
236
237
238
239
240
241
242
243
244
245
246
247
248
249
250
251
252
253
254
255
256
257
258
259
260
261
262
263
264
265
266
267
268
269
270
271
272
273
274
275
276
277
278
279
280
281
282
283
284
285
286
287
288
289
290
291
292
293
294
295
296
297
298
299
300
301
302
303
304
305
306
307
308
309
310
311
312
313
314
315
316
317
318
319
320
321
322
323
324
325
326
327
328
329
330
331
332
333
334
335
336
337
338
339
340
341
342
343
344
345
346
347
348
349
350
351
352
353
354
355
356
357
358
359
360
361
362
363
364
365
366
367
368
369
370
371
372
373
374
375
376
377
378
379
380
381
382
383
384
385
386
387
388
389
390
391
392
393
394
395
396
397
398
399
400
401
402
403
404
405
406
407
408
409
410
411
412
413
414
415
416
417
418
419
420
421
422
423
424
425
426
427
428
429
430
431
432
433
434
435
436
437
438
439
440
441
442
443
444
445
446
447
448
449
450
451
452
453
454
455
456
457
458
459
460
461
462
463
464
465
466
467
468
469
470
471
472
473
474
475
476
477
478
479
480
481
482
483
484
485
486
487
488
489
490
491
492
493
494
495
496
497
498
499
500
501
502
503
504
505
506
507
508
509
510
511
512
513
514
515
516
517
518
519
520
521
522
523
524
525
526
527
528
529
530
531
532
533
534
535
536
537
538
539
540
541
542
543
544
545
546
547
548
549
550
551
552
553
554
555
556
557
558
559
560
561
562
563
564
565
566
567
568
569
570
571
572
573
574
575
576
577
578
579
580
581
582
583
584
585
586
587
588
589
590
591
592
593
594
595
596
597
598
599
600
601
602
603
604
605
606
607
608
609
610
611
612
613
614
615
616
617
618
619
620
621
622
623
624
625
626
627
628
629
630
631
632
633
634
635
636
637
638
639
640
641
642
643
644
645
646
647
648
649
650
651
652
653
654
655
656
657
658
659
660
661
662
663
664
665
666
667
668
669
670
671
672
673
674
675
676
677
678
679
680
681
682
683
684
685
686
687
688
689
690
691
692
693
694
695
696
697
698
699
700
701
702
703
704
705
706
707
708
709
710
711
712
713
714
715
716
717
718
719
720
721
722
723
724
725
726
727
728
729
730
731
732
733
734
735
736
737
738
739
740
741
742
743
744
745
746
747
748
749
750
751
752
753
754
755
756
757
758
759
760
761
762
763
764
765
766
767
768
769
770
771
772
773
774
775
776
777
778
779
780
781
782
783
784
785
786
787
788
789
790
791
792
793
794
795
796
797
798
799
800
801
802
803
804
805
806
807
808
809
810
811
812
813
814
815
816
817
818
819
820
821
822
823
824
825
826
827
828
829
830
831
832
833
834
835
836
837
838
839
840
841
842
843
844
845
846
847
848
849
850
851
852
853
854
855
856
857
858
859
860
861
862
863
864
865
866
867
868
869
870
871
872
873
874
875
876
877
878
879
880
881
882
883
884
885
886
887
888
889
890
891
892
893
894
895
896
897
898
899
900
901
902
903
904
905
906
907
908
909
910
911
912
913
914
915
916
917
918
919
920
921
922
923
924
925
926
927
928
929
930
931
932
933
934
935
936
937
938
939
940
941
942
943
944
945
946
947
948
949
950
951
952
953
954
955
956
957
958
959
960
961
962
963
964
965
966
967
968
969
970
971
972
973
974
975
976
977
978
979
980
981
982
983
984
985
986
987
988
989
990
991
992
993
994
995
996
997
998
999
1000
@base <http://www.snik.eu/ontology/> .
@prefix rdf: <http://www.w3.org/1999/02/22-rdf-syntax-ns#> .
@prefix meta: <meta/> .
@prefix bb: <bb/> .
@prefix ob: <ob/> .
@prefix ciox: <ciox/> .
@prefix he: <he/> .
@prefix it: <it/> .
@prefix it4it: <it4it/> .
@prefix owl: <http://www.w3.org/2002/07/owl#> .
@prefix xml: <http://www.w3.org/XML/1998/namespace> .
@prefix xsd: <http://www.w3.org/2001/XMLSchema#> .
@prefix rdfs: <http://www.w3.org/2000/01/rdf-schema#> .
@prefix ov: <http://open.vocab.org/terms/> .
@prefix bibo: <http://purl.org/ontology/bibo/> .
@prefix vann: <http://purl.org/vocab/vann/> .
@prefix foaf: <http://xmlns.com/foaf/0.1/> .
@prefix skos: <http://www.w3.org/2004/02/skos/core#> .
@prefix dc: <http://purl.org/dc/terms/> .
<bb>
ov:defines <bb/199993EG>, <bb/1TierArchitecture>, <bb/2PhaseCommitProtocol>, <bb/2TierArchitecture>, <bb/3LGM2>, <bb/3LGM2ApplicationComponent>, <bb/3LGM2B>, <bb/3LGM2CommunicationInterface>, <bb/3LGM2CommunicationLink>, <bb/3LGM2ComputerBasedApplicationComponent>, <bb/3LGM2DataTransmissionConnection>, <bb/3LGM2DomainLayer>, <bb/3LGM2EnterpriseFunction>, <bb/3LGM2EntityType>, <bb/3LGM2InformationProcess>, <bb/3LGM2InterlayerRelationship>, <bb/3LGM2IntralayerRelationship>, <bb/3LGM2Location>, <bb/3LGM2LogicalToolLayer>, <bb/3LGM2M>, <bb/3LGM2MCommunicationStandard>, <bb/3LGM2MMessageType>, <bb/3LGM2MessageType>, <bb/3LGM2OrganizationalSystem>, <bb/3LGM2OrganizationalUnit>, <bb/3LGM2PhysicalDataProcessingSystem>, <bb/3LGM2PhysicalToolLayer>, <bb/3LGM2ReceivingInterface>, <bb/3LGM2S>, <bb/3LGM2SInvokingInterface>, <bb/3LGM2SProvidingInterface>, <bb/3LGM2SService>, <bb/3LGM2SServiceClass>, <bb/3LGM2SendingInterface>, <bb/3LGM2SoftwareProduct>, <bb/3LGM2Support>, <bb/3LGM2Tool>, <bb/3LGM2ToolClass>, <bb/3LGM2TransmittingMedium>, <bb/3LGM2Use>, <bb/3TierArchitecture>, bb:A01, bb:A02, bb:A03, bb:AC1Style, bb:ACnStyle, bb:AccessControlManagement, bb:AccessControlSystem, bb:AccessIntegration, bb:Accuracy, bb:Acid, bb:AcquireAndImplement, bb:Activity, bb:ActivityModelingElement, bb:AdHocMonitoring, bb:Adaptability, bb:AdaptabilityOfTheHIS, bb:AdaptationCost, bb:Administration, bb:AdministrationAndAllocationOfPatientRecords, bb:AdministrationManagement, bb:AdministrationOfBusinessTripsAndFurtherTraining, bb:AdministrationOfHumanResourceMasterData, bb:AdministrativeAdmission, bb:AdministrativeDischargeAndBilling, bb:AdministrativeEntityType, bb:AdministrativeGuideline, bb:AdministrativePatientData, bb:AdministrativeStaff, bb:AdministrativeSticker, bb:AdministrativeSupport, bb:AdmissionDiagnosis, bb:AdoptionOfProjectResult, bb:Adt, bb:AnalysisAndAssessmentOfTheCurrentHISState, bb:AnnualHospitalOperatingCost, bb:AnnualITBudget, bb:ApplicationComponent, bb:ApplicationComponentStyle, bb:ApplicationHosting, bb:ApplicationPortfolio, bb:ApplicationServer, bb:ApplicationSupport, bb:Appointment, bb:AppointmentScheduling, bb:AppropriatePhysicalDataProcessingSystem, bb:Appropriateness, bb:ApprovalToAStudy, bb:ApprovalToStrategicInformationManagementPlan, bb:ArchitecturalStyle, bb:ArchitecturalStyleOfTheLogicalToolLayer, bb:ArchitecturalStyleOfThePhysicalToolLayer, bb:ArchitectureOfAnInformationSystem, bb:Archiving, bb:ArchivingOfPatientInformation, bb:ArtificialSystem, bb:Ascii, bb:AssetAccounting, bb:AsynchronousCommunication, bb:Atc, bb:Atomicity, bb:AuthenticityOfData, bb:AvailabilityOfApplicationComponents, bb:AvailabilityOfData, bb:AvailabilityOfTheApplicationComponent, bb:AvailablePhysicalDataProcessingSystem, bb:AvailableServer, bb:BPflV, bb:Backbone, bb:BalanceOfComputerBasedAndNonComputerBasedTools, bb:BalanceOfDataSecurityAndWorkingProcesses, bb:BalanceOfDocumentationQualityAndDocumentationEfforts, bb:BalanceOfFunctionalLeannessAndFunctionalRedundancy, bb:BalanceOfHomegeneityAndHeterogeneity, bb:BalancedNetwork, bb:Bar, bb:Bdsg, bb:Bed, bb:BedOccupation, bb:BehavioralPerspective, bb:Benchmarking, bb:BestOfBreedArchitecture, bb:BestPracticeBenchmark, bb:Bill, bb:BillingOfAccountableServices, bb:BloodBank, bb:BloodBankManagementSystem, bb:BodyWashing, bb:Book, bb:Bus, bb:BusinessIntelligenceSystem, bb:BusinessProcess, bb:BusinessProcessMetamodel, bb:BusinessProcessModel, bb:BusinessProcessReferenceModel, bb:BusinessReferenceModel, bb:BusinessStrategy, bb:CP1Style, bb:CPnStyle, bb:Car, bb:CardiovascularInformationSystem, bb:Case, bb:CaseMixIndex, bb:CaseStudy, bb:Catering, bb:Cchit, bb:CchitFunctionalCriterion, bb:Ccow, bb:CcowStandard, bb:Cda, bb:Cdrom, bb:Cen, bb:CentralizedComputingCenter, bb:CertifiabilityOfPhysicalDataProcessingSystems, bb:CertifiabilityOfSoftware, bb:CertifiablePhysicalDataProcessingSystem, bb:Certification, bb:CertificationByCCHIT, bb:CertificationByEuroRec, bb:CertificationByISO, bb:CertifiedPhysicalDataProcessingSystem, bb:ChangeManagement, bb:ChemotherapeuticTreatment, bb:ChiefExecutiveOfficer, bb:ChiefFinancialOfficer, bb:ChiefInformationOfficer, bb:ClassDiagram, bb:Classification, bb:ClassificationOfDiagnoses, bb:ClassificationOfProcedures, bb:Client, bb:ClientServerArchitecture, bb:ClinicalChemistryReport, bb:ClinicalDataWarehouse, bb:ClinicalDepartment, bb:ClinicalDocumentation, bb:ClinicalInformationSystem, bb:ClinicalPathway, bb:ClinicalResearch, bb:ClinicalTrial, bb:CloseToHierarchyNetwork, bb:Cluster, bb:Cobit, bb:CobitProcess, bb:CodingOfDiagnoses, bb:CodingOfDiagnosesAndProcedures, bb:CodingOfProcedures, bb:CodingSystem, bb:CommunicateDocumentsToOtherApplications, bb:CommunicateReportToOrderingUnit, bb:Communication, bb:CommunicationAbility, bb:CommunicationInterface, bb:CommunicationLink, bb:CommunicationNetwork, bb:CommunicationPattern, bb:CommunicationProtocol, bb:CommunicationServer, bb:CommunicationStandard, bb:Complaint, bb:Completeness, bb:ComponentAlignmentModelOfMartin, bb:ComputedTomography, bb:ComputerBasedApplicationComponent, bb:ComputerBasedInformationProcessing, bb:ComputerBasedInformationSystem, bb:ComputerBasedNursingForm, bb:ComputerBasedPhysicalDataProcessingSystem, bb:ComputerBasedTool, bb:ComputerNetwork, bb:ComputerSupportedInformationSystem, bb:ComputerSystem, bb:ComputerizedPhysicianOrderEntrySystem, bb:ComputingCenter, bb:ComputingCenterManager, bb:Confidentiality, bb:ConfigurationManagement, bb:ConformityWithUserExpectations, bb:ConsensusMethod, bb:Consistency, bb:Consultant, bb:ContextualIntegration, bb:ContinualServiceImprovement, bb:ContinuousHISAuditing, bb:ContinuousQualityImprovementProcess, bb:Controllability, bb:ControlledRedundancyOfData, bb:ControlledTranscriptionOfData, bb:Controlling, bb:ControllingReport, bb:ConvergingTechnologies, bb:CopperCable, bb:CorrectInformation, bb:CostAccounting, bb:CostBenefitAnalysis, bb:CostEffectivenessAnalysis, bb:CostOfTreatment, bb:CostUnit, bb:CreationOfStrategicInformationManagementPlan, bb:CreditAccounting, bb:CrossEnterpriseDocumentSharing, bb:CtScanner, bb:Customizing, bb:DB1Style, bb:DBnStyle, bb:Data, bb:DataCollectionEffort, bb:DataIntegration, bb:DataMetamodel, bb:DataModel, bb:DataProtection, bb:DataReferenceModel, bb:DataSecurity, bb:DataSecurityOfficer, bb:DataTransmissionConnection, bb:DataWarehouseSystem, bb:DatabaseServer, bb:DatabaseStyle, bb:DatabaseSystem, bb:DebtorAccounting, bb:DecisionMakingAndPatientInformation, bb:DecisionMakingPlanningAndOrganizationOfPatientTreatment, bb:DecisionSupportSystem, bb:Decomposition, bb:DecubitusProphylaxis, bb:DeductiveApproach, bb:DefinitionEN, bb:DegreeOfComputerSupport, bb:DeliverAndSupport, bb:DeliveringOfCustomerCenteredServices, bb:DelphiSurvey, bb:DepartmentOfFacilityManagement, bb:DepartmentOfQualityManagement, bb:DepartmentalSystemAdministrator, bb:DeploymentOfStrategicInformationManagementPlan, bb:DescriptionOfTheCurrentHISState, bb:DescriptionOfThePlannedHISState, bb:DesigningCustomerCenteredServices, bb:DhcpServer, bb:Diagnosis, bb:DiagnosisClass, bb:DiagnosticProcedure, bb:DiagnosticService, bb:DiagnosticStandard, bb:DialysisInformationSystem, bb:DicomFileFormat, bb:DicomMessageFormat, bb:DicomNetworkProtocol, bb:DicomService, bb:DicomStandard, bb:Diet, bb:DigitalDictationSystem, bb:DigitalImage, bb:DigitalXRay, bb:Directing, bb:DirectiveForHISConstruction, bb:DischargeSummary, bb:DiseaseManagement, bb:DnsServer, bb:DocumentArchivingSystem, bb:DocumentStandard, bb:DoubleExamination, bb:Drg, bb:DrgCalculation, bb:Drug, bb:DrugService, bb:Durability, bb:EMailCommunication, bb:EN12538, bb:EN12539, bb:EN1613, bb:EconomicAnalysis, bb:Edifact, bb:Education, bb:EducationResearch, bb:EffectivenessStudy, bb:Efficiency, bb:EfficiencyOfInformationLogistics, bb:EfqmExcellenceModel, bb:EhrStrategy, bb:ElectronicHealthRecord, bb:ElectronicPatientRecord, bb:EncryptionSoftware, bb:EnsureAccessIntegration, bb:EnsureContextualIntegration, bb:EnsureDataIntegration, bb:EnsureFunctionalIntegration, bb:EnsureIntegration, bb:EnsurePresentationIntegration, bb:EnsureProcessIntegration, bb:EnsureSemanticIntegration, bb:EnterpriseFunction, bb:EnterpriseFunctionModelingElement, bb:EnterpriseOrganizationalStructure, bb:EnterpriseResourcePlanningSystem, bb:EntityTypeModelingElement, bb:EntityTypeRelation, bb:EntityTypeRelationModelingElement, bb:ErrorTolerance, bb:EstablishAndPromoteTheStrategicInformationManagementPlan, bb:EstablishingReferentialIntegrity, bb:Ethernet, bb:EuroRec, bb:EuroRecEHRQualitySeal, bb:EuropeanNorm, bb:Evaluation, bb:EvaluationMethod, bb:Event, bb:EventCountingStudy, bb:EventDrivenProcessChain, bb:EventModelingElement, bb:Excretion, bb:ExecutionOfAQuantitativeStudy, bb:ExecutionOfAnITEvaluationStudy, bb:ExecutionOfAnOperation, bb:ExecutionOfChemotheraphy, bb:ExecutionOfClinicalTrials, bb:ExecutionOfClinicalTrialsAndExperiments, bb:ExecutionOfDiagnosticAndTherapeuticProcedures, bb:ExecutionOfDiagnosticTherapeuticAndNursingProcedures, bb:ExecutionOfIrradiation, bb:ExecutionOfLabExaminations, bb:ExecutionOfNursingProcedures, bb:ExecutionOfProphylaxis, bb:ExecutionOfRadiologicalProcedures, bb:ExperimentalStudyDesign, bb:Extent, bb:ExternalFinding, bb:FacilityAndArea, bb:FacilityManagement, bb:FailureManagement, bb:FamilyHistory, bb:FaxMachine, bb:Feature, bb:FeatureAdministrateTheMasterPatientIndex, bb:FeatureAdmitPatientsToTheWard, bb:FeatureAnalyzeData, bb:FeatureArchivePictures, bb:FeatureAssignDoctorsToPatientsOrRooms, bb:FeatureAssignOrderAndBloodSamplesToDevices, bb:FeatureAssignOrdersToModalities, bb:FeatureAssignPatientsToModalities, bb:FeatureAssignPatientsToRoomsAndBeds, bb:FeatureAssignStaffToPatientsOrOutpatientUnits, bb:FeatureAssignStaffToPatientsOrRooms, bb:FeatureAttachDigitalSignatures, bb:FeatureCalculateDosageOfDrugs, bb:FeatureCollectResultsFromDevices, bb:FeatureCommunicateDischargeInformation, bb:FeatureCommunicatePictures, bb:FeatureCreateWorklistForAGroupOfPatients, bb:FeatureCreatingARoster, bb:FeatureCreationOfRadiologyReports, bb:FeatureDisplayEarlierLabResultsOfAPatient, bb:FeatureDisplayPictures, bb:FeatureDisplayVitalParametersFromMonitoringDevices, bb:FeatureDisplayWarningMessages, bb:FeatureImportDocuments, bb:FeatureIndexDocumentContent, bb:FeatureIntegrateDataFromDifferentApplicationComponents, bb:FeatureManageModalities, bb:FeatureManageStorageFormats, bb:FeatureManageStorageMedia, bb:FeatureMergePatientInformationFromTwoRecords, bb:FeatureMessageQueuing, bb:FeatureModifyPresentationOfPictures, bb:FeatureMulticasting, bb:FeatureOfferDecisionSupportForCarePlanning, bb:FeatureOrganizePatientTransport, bb:FeaturePrepareReport, bb:FeaturePreparingStatistics, bb:FeaturePrintForms, bb:FeaturePrintReports, bb:FeaturePrintingOfLabels, bb:FeatureProvideACollectionOfInternalProcessesAndRegulations, bb:FeatureProvideAccessToArchivedInformation, bb:FeatureProvideCatalogsAndOtherMeansForCodingOfNursingDiagnosis, bb:FeatureProvideCatalogsAndOtherMeansForCodingOfNursingProcedures, bb:FeatureProvideCatalogsAndOtherMeansForCodingPatientRelatedProcedures, bb:FeatureProvideCatalogsAndOtherMeansForCodingPatientsDiagnoses, bb:FeatureProvideCatalogsAndOtherMeansForCodingRadiologicalDiagnoses, bb:FeatureProvideCatalogsAndOtherMeansForCodingRadiologicalProcedures, bb:FeatureProvideContextRelatedMedicalKnowledge, bb:FeatureProvideDrugCatalogs, bb:FeatureProvideFormsForClinicalReports, bb:FeatureProvideFormsForDocumentingClinicalProcedures, bb:FeatureProvideFormsForDocumentingDiagnosis, bb:FeatureProvideFormsForDocumentingDiagnosisAndProblems, bb:FeatureProvideFormsForDocumentingMedicalAnamnesis, bb:FeatureProvideFormsForDocumentingMedications, bb:FeatureProvideFormsForDocumentingNursingAims, bb:FeatureProvideFormsForDocumentingNursingTasks, bb:FeatureProvideFormsForDocumentingPatientsInformedConsent, bb:FeatureProvideFormsForDocumentingPerformedTasks, bb:FeatureProvideFormsForDocumentingPlannedTasks, bb:FeatureProvideFormsForDocumentingProceduresAndOutcomes, bb:FeatureProvideFormsForDocumentingTheNursingHistory, bb:FeatureProvideFormsForDocumentingTheOutcomeOfNursingTasks, bb:FeatureProvideFormsForEnteringClinicalData, bb:FeatureProvideFormsForEnteringOrUpdatingPatientAdministrativeInformation, bb:FeatureProvideFormsForPatientsInformedConsent, bb:FeatureProvideFormsForPreparingABillForThePatientInsurance, bb:FeatureProvideFormsForPreparingClinicalReports, bb:FeatureProvideFormsForPreparingOperationReports, bb:FeatureProvideFormsForWritingAReport, bb:FeatureProvideFormsForWritingATransferLetterOrDischargeReport, bb:FeatureProvideFormsForWritingTheDischargeLetterOrDischargeReport, bb:FeatureProvideFormsForWritingTheDischargeReport, bb:FeatureProvideFormsForWritingTheNursingDischargeReport, bb:FeatureProvideGuidelinesForCarePlanning, bb:FeatureProvideGuidelinesForTreatmentPlanning, bb:FeatureProvideMeansForAccountsPayable, bb:FeatureProvideMeansForAccountsReceivable, bb:FeatureProvideMeansForAssetAccounting, bb:FeatureProvideMeansForCheckInOfPatient, bb:FeatureProvideMeansForControlOfSecurityIssues, bb:FeatureProvideMeansForCostCenterAccounting, bb:FeatureProvideMeansForCostElementAccounting, bb:FeatureProvideMeansForCreatingARoster, bb:FeatureProvideMeansForCreatingOperationPlans, bb:FeatureProvideMeansForCreatingStatistics, bb:FeatureProvideMeansForDataMining, bb:FeatureProvideMeansForEditingAndGraphicallyIllustratingCollectionsOfInternalProcessesAndRegulations, bb:FeatureProvideMeansForFinalizingDocumentation, bb:FeatureProvideMeansForFinalizingNursingDocumentation, bb:FeatureProvideMeansForGeneralLedgerAccounting, bb:FeatureProvideMeansForIncidentTracking, bb:FeatureProvideMeansForInitiatingFinalBillingForOutpatientTreatment, bb:FeatureProvideMeansForInitiationOfFinalBilling, bb:FeatureProvideMeansForManagingAndMonitoringDisposal, bb:FeatureProvideMeansForManagingAppointments, bb:FeatureProvideMeansForManagingLogistics, bb:FeatureProvideMeansForManagingMedicalDevices, bb:FeatureProvideMeansForManagingOutpatientUnitsStaff, bb:FeatureProvideMeansForManagingRooms, bb:FeatureProvideMeansForManagingWardStaff, bb:FeatureProvideMeansForMinimizingAdverseDrugEvents, bb:FeatureProvideMeansForOrderManagement, bb:FeatureProvideMeansForOrderingConsumables, bb:FeatureProvideMeansForOrderingDrugs, bb:FeatureProvideMeansForOrderingDrugsMaterialsAndLaundry, bb:FeatureProvideMeansForOrderingLaundry, bb:FeatureProvideMeansForOrderingPatientTransferToOtherUnits, bb:FeatureProvideMeansForOrderingPatientTransferToWard, bb:FeatureProvideMeansForOrderingPatientTransferWithinTheInstitution, bb:FeatureProvideMeansForOrderingTransportServices, bb:FeatureProvideMeansForOrganizingCareerDevelopment, bb:FeatureProvideMeansForOrganizingRecruitment, bb:FeatureProvideMeansForOrganizingTraining, bb:FeatureProvideMeansForOverheadCostManagement, bb:FeatureProvideMeansForPerformanceEvaluation, bb:FeatureProvideMeansForPreparingACarePlan, bb:FeatureProvideMeansForPreparingHospitalWideStatistics, bb:FeatureProvideMeansForPreparingStatistics, bb:FeatureProvideMeansForPreparingWardRelatedStatistics, bb:FeatureProvideMeansForPreparingWorkSchedules, bb:FeatureProvideMeansForPreventiveMaintenance, bb:FeatureProvideMeansForProductCosting, bb:FeatureProvideMeansForRecruitingOfPatients, bb:FeatureProvideMeansForSchedulingAPatientSAppointment, bb:FeatureProvideMeansForSchedulingPatientsAppointments, bb:FeatureProvideMeansForStockKeeping, bb:FeatureProvideMeansForVerifyingCodingDoneInDepartments, bb:FeatureProvideOrdersForPatientRelatedDrugs, bb:FeatureProvideOrdersForPatientRelatedExaminations, bb:FeatureProvideRelativesWithInformationOnTheLocationOfAPatient, bb:FeatureProvideReminderForFulfillingOfLegalReportingRequirements, bb:FeatureProvisionOfPatientDataAndExaminationParameters, bb:FeatureReceiveBloodSamples, bb:FeatureReceiveOrders, bb:FeatureRegisteringPatients, bb:FeatureRetrievePatient, bb:FeatureScanDocuments, bb:FeatureScanningDocumentsFromReferringPhysicianAndOtherSources, bb:FeatureSearchForOldPictures, bb:FeatureSelectOrdersFromOrderSets, bb:FeatureServiceCombination, bb:FeatureServiceOrchestration, bb:FeatureSupportCreationOfANursingCarePlan, bb:FeatureValidateResults, bb:FeatureWorkScheduling, bb:FeatureWorkflowManagement, bb:FederatedDatabaseSchema, bb:FederatedDatabaseSystem, bb:FieldStudy, bb:FinancialAccounting, bb:FinancialAndControllingDepartment, bb:FinancialControlling, bb:FinancialResource, bb:FinancingOfHealthCare, bb:Finding, bb:FirstLevelSupport, bb:FirstStudyDesign, bb:FlexiblePhysicalDataProcessingSystem, bb:Food, bb:ForkLift, bb:Framework, bb:FulfillmentOfLawsRelevantToInformationManagement, bb:FulfillmentOfStrategicHospitalGoal, bb:FulfillmentOfTheExpectationsOfDifferentStakeholders, bb:FunctionalCoverageOfTheApplicationComponent, bb:FunctionalIntegration, bb:FunctionalLeanness, bb:FunctionalMetamodel, bb:FunctionalModel, bb:FunctionalPerspective, bb:FunctionalRedundancy, bb:FunctionalRedundancyRate, bb:Functionality, bb:FundingInstitution, bb:GeneralAdministrationDepartment, bb:GeneralPractice, bb:GeneralPractitioner, bb:GermanLaw, bb:GoalOfMedicalEducation, bb:GoalOfMedicalResearch, bb:GovernmentalAuthority, bb:HL7CDA, bb:HL7EventDescription, bb:HL7EventType, bb:HL7MessageHeader, bb:HL7MessageType, bb:HL7MessageTypeEventTypeCombination, bb:HL7PatientIdentification, bb:HL7PatientVisitInformation, bb:HL7ReceiptMessage, bb:HL7ReferenceInformationModel, bb:HL7Standard, bb:HL7Version2, bb:HL7Version3, bb:HL7Version3Message, bb:HairUndNailCare, bb:HardwareHosting, bb:HardwareVendor, bb:HarmlessPhysicalDataProcessingSystem, bb:Harmlessness, bb:HealthCareInstitution, bb:HealthCareNetwork, bb:HealthCareProfessional, bb:HealthCareRegulation, bb:HealthInformationSystem, bb:HealthInsuranceCompany, bb:HealthInsurancePortabilityAndAccountabilityAct, bb:HealthcareServicesSpecificationProject, bb:HeterogeneityOfTheHISArchitecture, bb:HeterogeneousArchitecture, bb:HisArchitecture, bb:HisBenchmarking, bb:HisBenchmarkingMethod, bb:HisBudgetPlanning, bb:HisCertificate, bb:HisCertification, bb:HisComponent, bb:HisInfrastructure, bb:HisQuality, bb:HisStakeholder, bb:HomeCareInstitution, bb:HomeOfThePatient, bb:HomogeneityOfTheHISArchitecture, bb:HomogeneousArchitecture, bb:Hospital, bb:HospitalAdministration, bb:HospitalAdministrationDepartment, bb:HospitalBilling, bb:HospitalBudget, bb:HospitalBusinessPlan, bb:HospitalCost, bb:HospitalFunction, bb:HospitalInformationSystem, bb:HospitalInformationSystemModel, bb:HospitalManagement, bb:HospitalRevenue, bb:HospitalService, bb:HospitalStaff, bb:HospitalStrategy, bb:HospitalsBoardOfDirectors, bb:HumanActor, bb:HumanResource, bb:HumanResourceManagement, bb:HumanResourcesDepartment, bb:ICD10, bb:ISO14721, bb:ISO25000SoftwareQuality, bb:ISO9001, bb:ISO9241, bb:ISO9241109, bb:ISO9241110, bb:ISO9241110UserInterfaceDesignQuality, bb:ISOIEEE11073FamilyOfStandards, bb:ISOTR22221, bb:ISOTR22222, bb:Icd, bb:Icpm, bb:Id, bb:Ihe, bb:IheActor, bb:IheConnectAThon, bb:IheContentProfile, bb:IheCrossEnterpriseDocumentSharing, bb:IheDomain, bb:IheIntegrationProfile, bb:IhePatientDemographicsQuery, bb:IheTechnicalFramework, bb:IheTransaction, bb:ImagingModality, bb:ImprovingCustomerCenteredServices, bb:IncidentAnalysis, bb:IncidentManagement, bb:IncidentTaking, bb:IndependentHealthRecordBank, bb:InductiveApproach, bb:Information, bb:InformationAndCommunicationTechnology, bb:InformationAndKnowledgeLogistics, bb:InformationDesk, bb:InformationManagement, bb:InformationManagementBoard, bb:InformationManagementCost, bb:InformationManagementDepartment, bb:InformationManagementGoal, bb:InformationManagementGuideline, bb:InformationManagementInHealthCareNetworks, bb:InformationManagementInHospitals, bb:InformationManagementOperatingCost, bb:InformationManagementOrganizationalStructure, bb:InformationManagementStaff, bb:InformationProcessing, bb:InformationProcessingModel, bb:InformationProcessingTool, bb:InformationProcessingToolModelingElement, bb:InformationStorage, bb:InformationSystem, bb:InformationSystemEffectiveness, bb:InformationSystemImprovement, bb:InformationSystemMetamodel, bb:InformationSystemModel, bb:InformationSystemSafety, bb:InformedConsent, bb:InfrastructureOfAnInformationSystem, bb:Inpatient, bb:InpatientCareInstitution, bb:InpatientEHRCertification, bb:InpatientUnit, bb:InstitutionalHealthInformationSystem, bb:IntegratedCare, bb:IntegratedCareNetwork, bb:IntegratedHIS, bb:IntegratedHealthCareDeliverySystem, bb:Integration, bb:IntegrationPlatform, bb:IntegrationTechnology, bb:Integrity, bb:IntegrityOfData, bb:InternalItService, bb:InternalQualityManagement, bb:InternalReportingSystem, bb:InternationalDICOMCommittee, bb:Interoperability, bb:IntregrationPlatform, bb:IntroductionCost, bb:IsoStandard, bb:Isolation, bb:IsoosiReferenceModel, bb:ItEvaluationStudy, bb:ItEvaluationStudyManagementAndExecution, bb:ItInvestmentJustification, bb:ItInvestmentPlanning, bb:ItService, bb:ItServiceManagement, bb:ItServiceManagementStaff, bb:ItSupport, bb:Itil, bb:ItilServiceLifecycle, bb:IuKDG, bb:JointCommission, bb:JointCommissionsCertificationProgram, bb:Jpeg, bb:KeyPerformanceIndicator, bb:KhStatV, bb:Khg, bb:Khrg, bb:Knowledge, bb:KnowledgeRetrievalAndLiteratureManagement, bb:Laboratory, bb:LaboratoryFinding, bb:LaboratoryInformationSystem, bb:LaboratoryResult, bb:LaboratoryStudy, bb:Laptop, bb:Laundry, bb:LaundryManagement, bb:Law, bb:LeannessOfInformationProcessingTools, bb:LegalRequirement, bb:Library, bb:LifeCycleManagementOfStrategicInformationManagementPlan, bb:Linear, bb:LogicalNetworkTopology, bb:LogicalOperator, bb:LogicalOperatorModelingElement, bb:LogicalToolLayer, bb:Loinc, bb:LongTermArchiving, bb:LongTermHISPlanning, bb:LooselyCoupledNetwork, bb:MagneticDisc, bb:MagneticResonanceImaging, bb:MagneticTape, bb:MailServer, bb:MainframeArchitecture, bb:MaintainabilityOfHardware, bb:MaintainabilityOfSoftware, bb:MaintainablePhysicalDataProcessingSystem, bb:MaintainableServer, bb:MaintenanceCost, bb:MakingABackup, bb:MalcolmBaldrigeNationalQualityAward, bb:ManMadeSystem, bb:Management, bb:ManagementBoardBuffer, bb:ManagementDepartment, bb:ManagementEntityType, bb:ManagementOfClinicalDepartment, bb:ManagementOfEhr, bb:ManagementOfMedicalDevices, bb:ManagementOfNonClinicalDepartment, bb:ManagementOfUserAccounts, bb:ManagementUnit, bb:MasterApplicationComponent, bb:MasterPatientIndex, bb:Material, bb:MaterialAndMedicationManagement, bb:MaterialControlling, bb:Maturity, bb:MeansOfTransport, bb:MediaCrack, bb:MedicalAdmission, bb:MedicalAnamnesis, bb:MedicalAndNursingCarePlanning, bb:MedicalAndNursingKnowledge, bb:MedicalCarePlanning, bb:MedicalDataDictionary, bb:MedicalDevice, bb:MedicalDischargeAndMedicalReportWriting, bb:MedicalDocumentationSystem, bb:MedicalErrorReport, bb:MedicalGuideline, bb:MedicalInformatician, bb:MedicalKnowledge, bb:MedicalProcedure, bb:MedicalReport, bb:MedicalService, bb:Medication, bb:MemoryStick, bb:Mesh, bb:Message, bb:MessageType, bb:Metamodel, bb:MicrobiologyReport, bb:Middleware, bb:MigrationPath, bb:MixedApproach, bb:MixedDB1DBnStyle, bb:MobileComputer, bb:MobilePhone, bb:MobilePhysicalDataProcessingSystem, bb:Mobility, bb:Model, bb:ModelOfTheCurrentHIS, bb:ModelOfThePlannedHIS, bb:ModelingHospitalInformationSystems, bb:ModelingInformationSystems, bb:MonitorAndEvaluate, bb:Monitoring, bb:MonitoringOfNationalLegislation, bb:MonitoringOfNationalLocalPress, bb:MonitoringOfStandardizationAndCertificationOrganizations, bb:MonitoringOfStandardizationInitiatives, bb:MonitoringOfVitalSigns, bb:MonitoringTheProjectProgress, bb:MonolithicArchitecture, bb:Mpeg, bb:MriScanner, bb:MultifunctionalPhysicalDataProcessingSystem, bb:MultipleUsability, bb:MultipleUsabilityOfData, bb:Nanda, bb:Network, bb:NetworkManagement, bb:NetworkMonitoring, bb:NetworkStandard, bb:NetworkTopology, bb:Nic, bb:Noc, bb:Nomenclature, bb:NonComputerBasedApplicationComponent, bb:NonComputerBasedInformationProcessing, bb:NonComputerBasedInformationProcessingTool, bb:NonComputerBasedPhysicalDataProcessingSystem, bb:NonSignalBasedTransmittingMedium, bb:NonexperimentalStudyDesign, bb:Notification, bb:NuclearMedicineImaging, bb:Nurse, bb:NursingAdmission, bb:NursingAnamnesis, bb:NursingCarePlan, bb:NursingCarePlanning, bb:NursingCenter, bb:NursingClassification, bb:NursingDischargeAndNursingReportWriting, bb:NursingGoal, bb:NursingGuideline, bb:NursingHistory, bb:NursingManagement, bb:NursingManagementAndDocumentationSystem, bb:NursingProblem, bb:NursingProcedure, bb:NursingReport, bb:Nutrition, bb:OAIS3, bb:ObjectClass, bb:ObjectIdentity, bb:ObservationProtocol, bb:OfficesAndWritingServiceForReportWriting, bb:OncologyInformationSystem, bb:OpenEHR, bb:OpenEHRModelOfContent, bb:OpenEHRModelOfProcesses, bb:OpenEHROntology, bb:OpeningAPatientRecord, bb:Operation, bb:OperationManagementSystem, bb:OperationReport, bb:OperationRoom, bb:OperationalHISDirecting, bb:OperationalHISMonitoring, bb:OperationalHISPlanning, bb:OperationalInformationManagement, bb:OperationalInformationManagementGoal, bb:OperationalInformationManagementStaff, bb:OperationalManagementConcept, bb:OperationalizationOfMethodsAndDetailedStudyPlan, bb:OpticalFiber, bb:OpticalMedium, bb:OralAndDentalCare, bb:Order, bb:OrderCatalog, bb:OrderEntry, bb:OrderForm, bb:OrderingOfDrugs, bb:Organization, bb:OrganizationOfHealthCare, bb:OrganizationalInfrastructure, bb:OrganizationalMetamodel, bb:OrganizationalModel, bb:OrganizationalPerspective, bb:OrganizationalPlan, bb:OrganizationalSystem, bb:OrganizationalUnit, bb:OrganizationalUnitModelingElement, bb:OrganizationalUnitOfAHospital, bb:Orientation, bb:Orm, bb:OrthopedicsInformationSystem, bb:Oru, bb:Outpatient, bb:OutpatientCareInstitution, bb:OutpatientEHRCertification, bb:OutpatientManagementSystem, bb:OutpatientUnit, bb:PRINCE2, bb:Pager, bb:PaperBasedApplicationComponent, bb:PaperBasedPatientChart, bb:PaperBasedPatientRecord, bb:PaperBasedPhysicalDataProcessingSystem, bb:PastMedicalHistory, bb:Pathology, bb:PathologyInformationSystem, bb:PathologyReport, bb:Patient, bb:PatientActivityLevel, bb:PatientAdministration, bb:PatientAdministrationDepartment, bb:PatientAdministrationSystem, bb:PatientAdmission, bb:PatientAge, bb:PatientBilling, bb:PatientCare, bb:PatientCareEntityType, bb:PatientCenteredInformationProcessing, bb:PatientCentricStrategy, bb:PatientChartSystem, bb:PatientDataManagementSystem, bb:PatientDischargeAndTransferToOtherInstitutions, bb:PatientHistory, bb:PatientIdentification, bb:PatientIdentificationAndCheckingForRecurrent, bb:PatientIdentificationNumber, bb:PatientInsuranceData, bb:PatientLink, bb:PatientRecord, bb:PatientRecordArchive, bb:PatientRecordSystem, bb:PatientSatisfactionSurvey, bb:PatientState, bb:PatientTransfer, bb:PatientTransport, bb:PatientVisitInformation, bb:PatientsRelatives, bb:PayrollAccounting, bb:Pdfa, bb:Pencil, bb:Performance, bb:PerformanceOfApplicationComponents, bb:PerformanceOfLegalNotificationRequirements, bb:PerformanceOfTheApplicationComponent, bb:PerformantPhysicalDataProcessingSystem, bb:PerformantPhysicalDataProcessingSystems, bb:PerformantServer, bb:PermanentMonitoring, bb:PersonalComputer, bb:PersonalDigitalAssistant, bb:PersonalHealthRecord, bb:PersonalHygiene, bb:PertinentInformation, bb:PetriNet, bb:Pharmacy, bb:PharmacyDepartment, bb:PharmacyInformationSystem, bb:PhysicalDataProcessingSystem, bb:PhysicalIntegration, bb:PhysicalNetworkTopology, bb:PhysicalToolLayer, bb:Physician, bb:PictureArchivingAndCommunicationSystem, bb:PlanAndOrganize, bb:Planning, bb:PlanningOfBuildings, bb:PlanningOfFinances, bb:PlanningOfOrganizationalProcedures, bb:PlanningOfOrganizationalStructures, bb:PlanningOfRooms, bb:PlanningOfStaff, bb:Pmbok, bb:Portability, bb:PortfolioManagement, bb:PreliminaryOutlineOfAStudy, bb:PreparationOfAnOrder, bb:PreparationOfHealthStatistics, bb:PresentationIntegration, bb:PrintedForm, bb:PrinterServer, bb:ProblemManagement, bb:ProblemSolving, bb:Procedure, bb:ProcedureClass, bb:ProcessChain, bb:ProcessControlling, bb:ProcessIntegration, bb:Project, bb:ProjectCompletionPhase, bb:ProjectConflictManagement, bb:ProjectExecution, bb:ProjectExecutionModule, bb:ProjectInitiation, bb:ProjectInitiationPhase, bb:ProjectManagementBoard, bb:ProjectManagementMethod, bb:ProjectManager, bb:ProjectMonitoring, bb:ProjectPlan, bb:ProjectPlanning, bb:ProjectPlanningPhase, bb:ProjectPortfolio, bb:ProjectResourceAllocation, bb:ProjectResult, bb:ProjectTimeAllocation, bb:Projector, bb:ProvidingCustomerCenteredServices, bb:PublishingAndPresentation, bb:QualifiedElectronicSignature, bb:QualitativeContentAnalysis, bb:QualitativeEvaluationMethod, bb:QualitativeInterview, bb:QualitativeObservation, bb:Quality, bb:QualityAssessment, bb:QualityManagement, bb:QualityOfComputerBasedApplicationComponentsAndTheirIntegration, bb:QualityOfData, bb:QualityOfHISArchitecture, bb:QualityOfHISOutcome, bb:QualityOfHISProcesses, bb:QualityOfHISStructures, bb:QualityOfHealthCareOutcome, bb:QualityOfHealthCareProcesses, bb:QualityOfITServiceManagement, bb:QualityOfITSupport, bb:QualityOfITTraining, bb:QualityOfInformationManagement, bb:QualityOfOutcome, bb:QualityOfPatientCare, bb:QualityOfPhysicalDataProcessingSystems, bb:QualityOfProcesses, bb:QualityOfStructures, bb:QualityOfTacticalInformationManagement, bb:QualityReport, bb:QuantitativeEvaluationMethod, bb:QuantitativeQuestionnaire, bb:QuasiExperimentalStudyDesign, bb:QueueManager, bb:R01, bb:R01ORU, bb:RadiologicalExamination, bb:RadiologicalFinding, bb:RadiologyDepartment, bb:RadiologyInformationSystem, bb:RadiologyReport, bb:Radiotherapy, bb:RecommendationsForFurtherTreatment, bb:RecruitmentOfPatients, bb:RedundantComputingCenter, bb:RedundantServer, bb:ReferenceModel, bb:ReferenceModelForTheDomainLayerOfHospitalInformationSystems, bb:ReferentialIntegrity, bb:RehabilitationCenter, bb:Relative, bb:Relevancy, bb:Reliability, bb:ReliabilityOfData, bb:ReliabilityOfPhysicalDataProcesssingSystems, bb:ReliablePhysicalDataProcessingSystem, bb:ReliablePhysicalDataProcesssingSystem, bb:RemoteFunctionCall, bb:ReportAndPublicationOfStudy, bb:ReportToTheHospitalsBoardOfDirectors, bb:ReportWriting, bb:ReportingToTheCEO, bb:RepresentativeOfHospitalDepartment, bb:RequirementOfHISStakeholder, bb:ResearchAndEducation, bb:ResearchAndEducationEntityType, bb:ResearchDocument, bb:ResearchInstitution, bb:ResearchManagement, bb:Resource, bb:ReturnOnInvestmentStudy, bb:Ring, bb:RiskManagement, bb:RobotSystem, bb:RoleModelingElement, bb:Room, bb:RotaryPhone, bb:Router, bb:Sample, bb:Saps, bb:Saturation, bb:SchedulingAndResourceAllocation, bb:SchedulingAndResourcePlanningWithTheMedicalServiceUnit, bb:SchedulingAndResourcePlanningWithThePatientTransportService, bb:ScoringOfThePatient, bb:SecondLevelSupport, bb:SecurePhysicalDataProcessingSystem, bb:Security, bb:SecurityOfData, bb:SecurityOfPhysicalDataProcessingSystems, bb:SelfDescriptiveness, bb:SelfDevelopedSoftware, bb:SelfDevelopment, bb:SemanticIntegration, bb:SemistructuredInterview, bb:SeniorPhysician, bb:Server, bb:ServerCluster, bb:Service, bb:ServiceAssetManagement, bb:ServiceCatalog, bb:ServiceDesign, bb:ServiceDeskManagement, bb:ServiceDeskStaff, bb:ServiceOperation, bb:ServiceStrategy, bb:ServiceTransition, bb:Sgbv, bb:SheetOfPaper, bb:ShortTermHISPlanning, bb:SigG, bb:SignalBasedTransmittingMedium, bb:SingleSignOn, bb:SkinCare, bb:Snomed, bb:Soa, bb:SoaService, bb:SocialContact, bb:SocialHistory, bb:SocioTechnicalSystem, bb:SoftwareDevelopment, bb:SoftwareErgonomics, bb:SoftwareProduct, bb:SoftwareQuality, bb:SoftwareVendor, bb:Source, bb:Specialization, bb:Stability, bb:StabilityOfApplicationComponents, bb:StablePhysicalDataProcessingSystem, bb:StableServer, bb:StaffControlling, bb:StaffCost, bb:Standard, bb:StandardizationByCEN, bb:StandardizationOfComputerSystems, bb:StandardizationOfData, bb:StandardizationOfHISArchitecture, bb:StandardizationOfInterfaces, bb:StandardizedPhysicalDataProcessingSystem, bb:StandardizedPhysicalDataProcessingSystems, bb:Star, bb:StatisticalEvaluationOfPatientData, bb:StorageAreaNetwork, bb:StorageMedium, bb:StrategicAlignment, bb:StrategicAlignmentModel, bb:StrategicDecision, bb:StrategicGoalOfTheInstitution, bb:StrategicGoalOfTheNetwork, bb:StrategicHISDirecting, bb:StrategicHISMonitoring, bb:StrategicHISMonitoringResult, bb:StrategicHISPlanning, bb:StrategicHospitalGoal, bb:StrategicInformationManagement, bb:StrategicInformationManagementGoal, bb:StrategicInformationManagementPlan, bb:StructuralQualityAssessment, bb:Study, bb:StudyDesign, bb:StudyExploration, bb:StudyHypothesis, bb:StudyObjective, bb:StudyOutline, bb:StudyParticipant, bb:StudyPlan, bb:StudyReport, bb:StudyResult, bb:SubInformationSystem, bb:Subsystem, bb:SuitabilityForIndividualization, bb:SuitabilityForLearning, bb:SuitabilityForTheTask, bb:SupplyAndDisposalManagement, bb:SupportCost, bb:Surgeon, bb:Sustainability, bb:Switch, bb:SwotAnalysis, bb:SynchronousCommunication, bb:System, bb:SystemAnalysis, bb:SystemEvaluation, bb:SystemIntroduction, bb:SystemOfConcepts, bb:SystemSelection, bb:SystemSpecification, bb:SystematicInformationProcessing, bb:SystemsReview, bb:T3ApplicationServer, bb:T3DatabaseServer, bb:TabletPC, bb:TacticalHISDirecting, bb:TacticalHISMonitoring, bb:TacticalHISPlanning, bb:TacticalInformationManagement, bb:TansCriticalSuccessFactorApproach, bb:TechnicalMetamodel, bb:TechnicalModel, bb:TechnicalStaff, bb:Teleconsultation, bb:Telemicroscopy, bb:Teleradiology, bb:TeleradiologySystem, bb:Terminal, bb:TerminalServer, bb:TheProviderCentricStrategy, bb:TheRegionalOrNationalCentricStrategy, bb:TheStrategyOfIndependentHealthBanks, bb:TherapeuticDepartment, bb:TherapeuticProcedure, bb:TherapeuticService, bb:TherapeuticStandard, bb:ThirdLevelSupport, bb:ThirdPartyFund, bb:ThrombosisProphylaxis, bb:Tiff, bb:TimeMeasurement, bb:TimeMotionAnalysis, bb:Tiss, bb:TokenRing, bb:TopManagement, bb:TransactionManagementTechnology, bb:Transcription, bb:Transfer, bb:TransferDiagnosis, bb:TransinstitutionalHealthCareFunction, bb:TransinstitutionalHealthInformationSystem, bb:TransmittingMedium, bb:Transparency, bb:TreatmentText, bb:Tree, bb:TroubleShootingInItServiceManagement, bb:Typewriter, bb:Ultrasound, bb:UmlActivityDiagram, bb:UmlAssociation, bb:UmlAssociationClass, bb:UmlAttribute, bb:UmlClass, bb:UmlClassDiagram, bb:UmlMethod, bb:Umls, bb:UniversityMedicalCenter, bb:UnstructuredInterview, bb:UpToDateInformation, bb:UpToDatePhysicalDataProcessingSystem, bb:UpdatingTheStrategicInformationManagementPlan, bb:UsLaw, bb:Usability, bb:UsabilityOfPhysicalDataProcessingSystems, bb:UsabilityStudy, bb:UsablePhysicalDataProcessingSystem, bb:UsablePhysicalDataProcessingSystems, bb:UseOfStrategicInformationManagementPlan, bb:UserRequirementsAnalysis, bb:UserSatisfaction, bb:UserSurvey, bb:UserTraining, bb:UtilityAnalysis, bb:V1Style, bb:Vendor, bb:VendorStyle, bb:VideoConferencingSystem, bb:ViewPatientRelatedAppointments, bb:VirtualPrivateNetwork, bb:VirtualServer, bb:Virtualization, bb:VisitorAndInformationService, bb:VitalSign, bb:VnStyle, bb:Ward, bb:WardPhysician, bb:WebServer, bb:WorkOrganizationAndTimeManagement, bb:WorkSampling, bb:WorkingList, bb:Workstation, bb:WoundCare, bb:WoundTreatment, bb:WrittenAgreementOnTheStudyOutline, bb:Xml, bb:acceptance, bb:admittingPhysician, bb:careComprisedGroupsOfPatients, bb:careCoordinationOfCareProcess, bb:case, bb:chapter, bb:cin, bb:conceptDomain, bb:deadline, bb:degreeOfNormativity, bb:duration, bb:icdCode, bb:insurance, bb:isHeterogeneous, bb:isHomogeneous, bb:location, bb:managementFinancingForm, bb:managementLegalForm, bb:managementOpenness, bb:officialUserGroup, bb:page, bb:pin, bb:priority, bb:relative, bb:responsiblePerson, bb:structureConfiguration, bb:structureRange, bb:structureSize, bb:structureStability, bb:temporalDevelopmentStage, bb:temporalLifeSpan, bb:tripelRowNr, bb:upToDateness, bb:usageDescription ;
dc:creator <../de/Team> ;
dc:modified "2016-11-18"^^xsd:date ;
dc:publisher <../de/Team> ;
dc:source <../mapping> ;
vann:preferredNamespacePrefix "snik-bb" ;
vann:preferredNamespaceUri "http://www.snik.eu/ontology/bb/" ;
a owl:Ontology ;
rdfs:comment "Winter A, Haux R, Ammenwerth E, Brigl B, Hellrung N, Jahn F. Health Information Systems - Architectures and Strategies. London: Springer; 2011."@en ;
rdfs:label "BB", "Health Information Systems Ontology"@en, "bb" ;
owl:imports <http://www.w3.org/2000/01/rdf-schema#> ;
owl:versionInfo "0.3.0" ;
foaf:homepage <http://www.snik.eu> .
<bb/199993EG>
meta:chapter bb:chapter6-4-13 ;
meta:isAssociatedWith bb:DocumentArchivingSystem, bb:QualifiedElectronicSignature ;
a meta:EntityType ;
rdfs:label "1999/93/EG"@en, "1999/93/EG"@fa ;
rdfs:subClassOf bb:InformationManagementGuideline ;
skos:altLabel "European Guideline 1999/93"@en .
<bb/1TierArchitecture>
bb:page "173"^^xsd:positiveInteger ;
meta:chapter bb:chapter6-7-1-1 ;
a meta:EntityType ;
rdfs:label "1-tier Architecture"@en, "معماری سطح 1"@fa ;
rdfs:subClassOf bb:ArchitecturalStyleOfThePhysicalToolLayer ;
skos:definition "1-tier architectures are architectures with one centralized physical data processing system (denoted as “T 1 ”)."@en .
<bb/2PhaseCommitProtocol>
bb:page "156"^^xsd:positiveInteger ;
meta:chapter bb:chapter6-5 ;
a meta:EntityType ;
rdfs:label "2-Phase-Commit-Protocol"@en, "پروتکل دو مرحله ای"@fa ;
rdfs:subClassOf bb:CommunicationProtocol, bb:TransactionManagementTechnology ;
skos:definition "The “2-phase commit protocol” was developed for transaction management in DB n architectures. In the initial phase, this protocol checks if the transaction can be carried out by all affected database systems. Only if the changes are possible everywhere, they are actually carried out in a second phase in all database systems."@en .
<bb/2TierArchitecture>
bb:page "173"^^xsd:positiveInteger ;
meta:chapter bb:chapter6-7-1-1 ;
meta:entityTypeComponent bb:ApplicationServer, bb:DatabaseServer ;
a meta:EntityType ;
rdfs:label "2-tier Architecture"@en, "معماری 2 لایه"@fa ;
rdfs:subClassOf bb:ArchitecturalStyleOfThePhysicalToolLayer ;
skos:altLabel "T2"@en ;
skos:definition "In a 2-tier architecture, there is a server that serves both as application and database server. The program execution can partly or completely be given to the client PCs. We will refer to these architectures as “T 2.”"@en .
<bb/3LGM2>
bb:page "324"^^xsd:positiveInteger ;
meta:chapter bb:Thesaurus ;
meta:entityTypeComponent <bb/3LGM2DomainLayer>, <bb/3LGM2InterlayerRelationship>, <bb/3LGM2IntralayerRelationship>, <bb/3LGM2LogicalToolLayer>, <bb/3LGM2PhysicalToolLayer> ;
meta:isBasedOn bb:UmlClassDiagram ;
a meta:EntityType ;
rdfs:label "3LGMA2"@fa, "3LGM²"@en ;
rdfs:subClassOf bb:FunctionalMetamodel, bb:InformationSystemMetamodel, bb:OrganizationalMetamodel, bb:TechnicalMetamodel ;
skos:altLabel "Grafisches Drei-Ebenen-Metamodell"@de, "Three-Layer Graph-based Metamodel"@en ;
skos:definition "Metamodel for developing information system models of health information systems. It distinguishes three layers of information systems: domain layer, logical tool layer, and physical tool layer. It aims to support the systematic information management and especially the structural monitoring of information processing in health care institutions. 3LGM²-B consists of concepts describing basic elements of a HIS architecture. 3LGM²-M adds concepts for modeling message-based communication. 3LGM²-S provides additional concepts for modeling service-oriented architectures."@en .
<bb/3LGM2ApplicationComponent>
bb:page "58"^^xsd:positiveInteger ;
meta:chapter bb:chapter5-3 ;
meta:isAssociatedWith <bb/3LGM2CommunicationInterface> ;
meta:isAssociatedWith <bb/3LGM2EnterpriseFunction> ;
a meta:EntityType ;
rdfs:label "3LGM² Application Component"@en, "اجزای برنامه 3LGM2"@fa ;
skos:definition "An application component is a set of actually usable rules, which control data processing of certain physical data processing systems. Rules are considered to be actually usable, if they are implemented such that they are ready to support certain enterprise functions in a certain enterprise or support communication between application components. If the rules are implemented as executable software, the application component is called computer-based application component. Otherwise it is called non-computer-based."@en .
<bb/3LGM2B>
bb:page "52"^^xsd:positiveInteger ;
meta:chapter bb:chapter5-3 ;
a meta:EntityType ;
rdfs:label "3LGMA2-B"@fa, "3LGM²-B"@en ;
rdfs:subClassOf <bb/3LGM2> ;
skos:definition "3LGM²-B, which is the basis for 3LGM²-M and 3LGM²-S, consists of concepts describing b asic elements of a HIS architecture."@en .
<bb/3LGM2CommunicationInterface>
meta:chapter bb:chapter5-3 ;
meta:isAssociatedWith <bb/3LGM2EntityType> ;
a meta:EntityType ;
rdfs:label "3LGM² Communication Interface"@en, "رابط ارتباطی3LGM²"@fa .
<bb/3LGM2CommunicationLink>
meta:chapter bb:chapter5-3 ;
meta:isAssociatedWith <bb/3LGM2CommunicationInterface>, <bb/3LGM2EntityType> ;
a meta:EntityType ;
rdfs:label "3LGM² Communication Link"@en, "لینک ارتباط 3LGM ²"@fa ;
rdfs:subClassOf <bb/3LGM2IntralayerRelationship> .
<bb/3LGM2ComputerBasedApplicationComponent>
meta:chapter bb:chapter5-3 ;
a meta:EntityType, meta:ApplicationComponent, meta:ComputerBasedApplicationComponent ;
rdfs:label "3LGM² Computer-Based Application Component"@en, "ترکیب دهنده مبتنی بر رایانه 3LGM ²"@fa ;
rdfs:subClassOf <bb/3LGM2ApplicationComponent> .
<bb/3LGM2DataTransmissionConnection>
meta:chapter bb:chapter5-3 ;
meta:isAssociatedWith <bb/3LGM2TransmittingMedium> ;
a meta:EntityType ;
rdfs:label "3LGM² Data Transmission Connection"@en, "رابطه انتقال داده 3LGM²"@fa ;
rdfs:subClassOf <bb/3LGM2IntralayerRelationship>, bb:DataTransmissionConnection .
<bb/3LGM2DomainLayer>
bb:page "302"^^xsd:positiveInteger ;
meta:chapter bb:Thesaurus ;
meta:entityTypeComponent <bb/3LGM2EntityType>, <bb/3LGM2InformationProcess>, <bb/3LGM2OrganizationalUnit> ;
meta:isAssociatedWith <bb/3LGM2EnterpriseFunction> ;
a meta:EntityType ;
rdfs:label "3LGM² Domain Layer"@en, "Fachliche Ebene"@de, "لایه دامنه 3LGM²"@fa ;
skos:definition "In the 3LGM², the domain layer describes what kinds of activities in a health care institution are enabled by its information system and what kind of data should be stored and processed, independent of its implementation. Consequently, the domain layer describes enterprise functions and entity types."@en .
<bb/3LGM2EnterpriseFunction>
bb:page "55"^^xsd:positiveInteger ;
meta:chapter bb:chapter5-3 ;
meta:isAssociatedWith bb:UmlClass ;
meta:updates <bb/3LGM2EntityType> ;
meta:uses <bb/3LGM2EntityType> ;
a meta:Function ;
rdfs:label "3LGM² Enterprise Function"@en, "تابع سازمانی 3LGM2"@fa ;
skos:definition "The class of all activities interpreting the same set of entity types and updating the same set of entity types is called an information processing enterprise function (short: enterprise function). An enterprise function is a directive in an institution on how to interpret data about entity types and then update data about entity types as a consequence of this interpretation. The goal of data interpretation and updates is part of or contributes to (sub) goals of the institution. A function has no definitive beginning or end. Similar to an activity, an enterprise function is said to interpret entity types and update entity types."@en .
<bb/3LGM2EntityType>
bb:page "55"^^xsd:positiveInteger ;
meta:chapter bb:chapter5-3 ;
meta:isAssociatedWith bb:ObjectClass ;
a meta:EntityType ;
rdfs:label "3LGM² Entity Type"@en, "نوع عنصر 3LGM ²"@fa ;
rdfs:subClassOf bb:UmlClass ;
skos:definition "An entity type is a representation of 1. an object class and of 2. the data representing information concerning the objects of this object class, if these data are stored or could or should be stored in the information system."@en .
<bb/3LGM2InformationProcess>
bb:page "306"^^xsd:positiveInteger ;
meta:chapter bb:Thesaurus ;
meta:entityTypeComponent <bb/3LGM2EntityType> ;
meta:isAssociatedWith <bb/3LGM2EnterpriseFunction> ;
a meta:EntityType ;
rdfs:label "3LGM² Information Process"@en, "3LGM²-Informationprozess"@de, "فرآیند اطلاعات 3LGM²"@fa ;
skos:definition "Logical and chronological sequence of enterprise functions which interpret or update data about entities. Different from business processes, information processes do not contain the conditions under which enterprise functions are performed."@en .
<bb/3LGM2InterlayerRelationship>
bb:page "62"^^xsd:positiveInteger ;
meta:chapter bb:Thesaurus, bb:chapter5-3 ;
a meta:EntityType ;
rdfs:label "3LGM² Interlayer Relationship"@en, "3LGM²-Interebenenbeziehung"@de, "رابطه میان لایه 3LGM ² "@fa ;
rdfs:subClassOf bb:UmlAssociation ;
skos:definition "Dependencies among components of different layers in the 3LGM². Relationships exist between concepts at the domain layer and the logical tool layer and between concepts at the logical tool layer and the physical tool layer."@en .
<bb/3LGM2IntralayerRelationship>
meta:chapter bb:chapter5-3 ;
a meta:EntityType ;
rdfs:label "3LGM² Intralayer Relationship"@en, "رابطه میان لایه 3LGM ²"@fa .
<bb/3LGM2Location>
meta:chapter bb:chapter5-3 ;
a meta:EntityType ;
rdfs:label "3LGM ² مکان"@fa, "3LGM² Location"@en ;
rdfs:subClassOf bb:UmlClass .
<bb/3LGM2LogicalToolLayer>
bb:page "310"^^xsd:positiveInteger ;
meta:chapter bb:Thesaurus, bb:chapter8-5 ;
meta:entityTypeComponent <bb/3LGM2ApplicationComponent>, <bb/3LGM2CommunicationInterface>, <bb/3LGM2CommunicationLink>, <bb/3LGM2SoftwareProduct> ;
a meta:EntityType ;
rdfs:label "3LGM² Logical Tool Layer"@en, "Logische Werkzeugebene"@de, "لایه ابزار منطقی 3LGM²"@fa ;
skos:definition "In the 3LGM², the logical tool layer describes the set of application components used in a health care institution to support its enterprise functions. On this layer, application components communicate representations of entity types as messages via communication links and store them as data."@en .
<bb/3LGM2M>
bb:page "52"^^xsd:positiveInteger ;
meta:chapter bb:chapter5-3 ;
meta:entityTypeComponent <bb/3LGM2B>, <bb/3LGM2MCommunicationStandard>, <bb/3LGM2MMessageType> ;
a meta:EntityType ;
rdfs:label "3LGMA2-M"@fa, "3LGM²-M"@en ;
rdfs:subClassOf <bb/3LGM2> ;
skos:definition "3LGM²-M extends 3LGM²-B by concepts for modeling message- based communication."@en .
<bb/3LGM2MCommunicationStandard>
bb:page "66"^^xsd:positiveInteger ;
meta:chapter bb:chapter5-3 ;
a meta:EntityType ;
rdfs:label "3LGM²-M Communication Standard"@en, "استاندارد ارتباطات 3LGM²-M"@fa ;
rdfs:subClassOf bb:UmlClass ;
skos:definition "Communication standards describe how messages of a certain data format are communicated when a certain event occurs"@en .
<bb/3LGM2MMessageType>
bb:page "66"^^xsd:positiveInteger ;
meta:chapter bb:chapter5-3 ;
a meta:EntityType ;
rdfs:label "3LGM²-M Message Type"@en, "انواع پیام 3LGM ²-M"@fa ;
rdfs:subClassOf bb:UmlClass ;
skos:definition "A message type describes a class of uniform messages and determines which data about which entity types is communicated by a message belonging to this message type."@en .
<bb/3LGM2MessageType>
bb:page "67"^^xsd:positiveInteger ;
meta:chapter bb:chapter5-3 ;
meta:isAssociatedWith <bb/3LGM2EntityType>, bb:Message ;
a meta:EntityType ;
rdfs:label "3LGM² Message Type"@en, "نوع پیام 3LGM²"@fa ;
rdfs:subClassOf bb:UmlClass ;
skos:definition "A message type describes a class of uniform messages and determines which data about which entity types is communicated by a message belonging to this message type."@en .
<bb/3LGM2OrganizationalSystem>
meta:chapter bb:chapter5-3 ;
meta:isAssociatedWith bb:OrganizationalPlan ;
a meta:EntityType, meta:ApplicationComponent ;
rdfs:label "3LGM² Organizational System"@en, "سیستم سازمانی 3LGM²"@fa ;
rdfs:subClassOf <bb/3LGM2ApplicationComponent> .
<bb/3LGM2OrganizationalUnit>
bb:page "56"^^xsd:positiveInteger ;
meta:chapter bb:chapter5-3 ;
a meta:EntityType ;
rdfs:label "3LGM² Organizational Unit"@en, "واحد سازمانی 3LGM2"@fa ;
rdfs:subClassOf bb:UmlClass ;
skos:definition "An organizational unit is a part of an institution which can be defined by responsibilities."@en .
<bb/3LGM2PhysicalDataProcessingSystem>
bb:page "60"^^xsd:positiveInteger ;
meta:chapter bb:chapter5-3 ;
a meta:EntityType ;
rdfs:label "3LGM² Physical Data Processing System"@en, "3LGM² سیستم پردازش داده های فیزیکی"@fa ;
rdfs:subClassOf bb:UmlClass ;
skos:definition "A physical data processing system is a physically touchable object or a simulated physically touchable object being able to receive, store, forward, or purposefully manipulate data. We denote receiving, storing, forwarding and purposeful manipulation of data as data processing. This data processing is controlled by rules"@en .
<bb/3LGM2PhysicalToolLayer>
bb:page "60"^^xsd:positiveInteger ;
meta:chapter bb:chapter5-3 ;
meta:entityTypeComponent <bb/3LGM2DataTransmissionConnection>, <bb/3LGM2Location>, <bb/3LGM2PhysicalDataProcessingSystem>, <bb/3LGM2ToolClass>, <bb/3LGM2TransmittingMedium> ;
a meta:EntityType ;
rdfs:label "3LGM² Physical Tool Layer"@en, "لایه ابزار فیزیکی 3LGM2"@fa, "Physische Werkzeugebene"@de ;
skos:definition "The physical tool layer is a set of physical data processing systems."@en .
<bb/3LGM2ReceivingInterface>
meta:chapter bb:chapter5-3 ;
a meta:EntityType ;
rdfs:label " اینترفیس دریافت 3LGM2"@fa, "3LGM² Receiving Interface"@en ;
rdfs:subClassOf <bb/3LGM2CommunicationInterface> .
<bb/3LGM2S>
bb:page "52"^^xsd:positiveInteger ;
meta:chapter bb:chapter5-3 ;
meta:entityTypeComponent <bb/3LGM2SInvokingInterface>, <bb/3LGM2SProvidingInterface>, <bb/3LGM2SService>, <bb/3LGM2SServiceClass> ;
meta:isAssociatedWith bb:Soa ;
a meta:EntityType ;
rdfs:label "3LGM2-S"@fa, "3LGM²-S"@en ;
rdfs:subClassOf <bb/3LGM2> ;
skos:definition "For architectures in which computer-based application components provide s ervices to be used by other computer-based application components (so-called service-oriented architectures), the concepts of 3LGM²-S are useful for modeling."@en .
<bb/3LGM2SInvokingInterface>
bb:page "68"^^xsd:positiveInteger ;
meta:chapter bb:chapter5-3 ;
a meta:EntityType ;
rdfs:label "3LGM²-S Invoking Interface"@en, "رابط کاربری 3LGM2-S"@fa ;
rdfs:subClassOf <bb/3LGM2CommunicationInterface> ;
skos:definition "As their names imply, providing interfaces and invoking interfaces, each belonging to only one application component, are able to provide or to invoke services."@en .
<bb/3LGM2SProvidingInterface>
bb:page "68"^^xsd:positiveInteger ;
meta:chapter bb:chapter5-3 ;
a meta:EntityType ;
rdfs:label "3LGM²-S Providing Interface"@en, "ارائه رابط 3LGM2-S"@fa ;
rdfs:subClassOf <bb/3LGM2CommunicationInterface> ;
skos:definition "As their names imply, providing interfaces and invoking interfaces, each belonging to only one application component, are able to provide or to invoke services."@en .
<bb/3LGM2SService>
bb:page "68"^^xsd:positiveInteger ;
meta:chapter bb:chapter5-3 ;
a meta:EntityType ;
rdfs:label "3LGM²-S Service"@en, "3LGM²-S سرویس"@fa ;
rdfs:subClassOf bb:UmlClass ;
skos:definition "A service is a feature provided by an application component in order to be used by other application components."@en .
<bb/3LGM2SServiceClass>
bb:page "68"^^xsd:positiveInteger ;
meta:chapter bb:chapter5-3 ;
a meta:EntityType ;
rdfs:label "3LGM²-S Service Class"@en, "کلاس خدمات 3LGM2-S"@fa ;
rdfs:subClassOf bb:UmlClass ;
skos:definition "If we want to express that some services are of similar type, we can summarize them in a service class."@en .
<bb/3LGM2SendingInterface>
meta:chapter bb:chapter5-3 ;
a meta:EntityType ;
rdfs:label "3LGM ² ارسال رابط"@fa, "3LGM² Sending Interface"@en ;
rdfs:subClassOf <bb/3LGM2CommunicationInterface> .
<bb/3LGM2SoftwareProduct>
bb:page "58"^^xsd:positiveInteger ;
meta:chapter bb:chapter5-3 ;
meta:isAssociatedWith <bb/3LGM2ApplicationComponent> ;
a meta:EntityType ;
rdfs:label "3LGM² Software Product"@en, "3LGM² محصول نرم افزار"@fa ;
rdfs:subClassOf bb:UmlClass ;
skos:definition "A software product is a set of rules, represented by software being stored at a certain medium but not implemented and actually executable yet."@en .
<bb/3LGM2Support>
bb:page "52"^^xsd:positiveInteger ;
meta:chapter bb:chapter5-3 ;
a meta:EntityType ;
rdfs:label "3LGM² Support"@en, "پشتیبانی 3LGM2"@fa ;
rdfs:subClassOf bb:UmlAssociationClass ;
skos:definition "The computer-based application component connected with the class \"function\" only mediates the use of another computer-based application component which supports the enterprise function"@en .
<bb/3LGM2Tool>
meta:isBasedOn <bb/3LGM2> ;
meta:supports bb:InformationManagement, bb:StructuralQualityAssessment ;
a meta:ComputerBasedApplicationComponent, meta:ApplicationComponent, meta:EntityType ;
rdfs:label "3LGM² Tool"@en, "ابزار 3LGM ²"@fa ;
rdfs:subClassOf bb:ComputerBasedApplicationComponent .
<bb/3LGM2ToolClass>
meta:chapter bb:chapter5-3 ;
a meta:EntityType ;
rdfs:label "3LGM² Tool Class"@en, "کلاس ابزار 3LGM²"@fa ;
rdfs:subClassOf bb:UmlClass .
<bb/3LGM2TransmittingMedium>
meta:chapter bb:chapter5-3 ;
a meta:EntityType ;
rdfs:label "3LGM² Transmitting Medium"@en, "رسانه فرستنده 3LGM²"@fa ;
rdfs:subClassOf bb:UmlClass .
<bb/3LGM2Use>
bb:page "62"^^xsd:positiveInteger ;
meta:chapter bb:chapter5-3 ;
a meta:EntityType ;
rdfs:label "3LGM² Use"@en, "استفاده از 3LGM ²"@fa ;
rdfs:subClassOf <bb/3LGM2InterlayerRelationship> ;
skos:definition "The computer-based application component connected with a function over the class \"use\" is immediately used for supporting the activities regarding an enterprise function"@en .
<bb/3TierArchitecture>
bb:page "173"^^xsd:positiveInteger ;
meta:chapter bb:chapter6-7 ;
meta:entityTypeComponent bb:T3ApplicationServer, bb:T3DatabaseServer ;
a meta:EntityType ;
rdfs:label "3-tier Architecture"@en, "معماری سطح 3"@fa ;
rdfs:subClassOf bb:ArchitecturalStyleOfThePhysicalToolLayer ;
skos:altLabel "T3"@en ;
skos:definition "3-tier architecture, there is a separate application server and a separate database server. The database server is responsible for storing the data, and on the application server the application components are installed and executed."@en .
bb:A01
bb:conceptDomain "health care specific"^^xsd:string ;
bb:page "150"^^xsd:positiveInteger ;
meta:chapter bb:chapter6-5 ;
a meta:EntityType ;
rdfs:label "A01", "A01"@fa ;
rdfs:subClassOf bb:HL7EventType ;
skos:definition "A01 describes the event “admission of a patient"@en .
bb:A02
bb:conceptDomain "health care specific"^^xsd:string ;
bb:page "150"^^xsd:positiveInteger ;
meta:chapter bb:chapter6-5 ;
a meta:EntityType ;
rdfs:label "A02", "A02"@fa ;
rdfs:subClassOf bb:HL7EventType ;
skos:definition "A02 describes the “transfer to another organizational unit\"."@en .
bb:A03
bb:conceptDomain "health care specific"^^xsd:string ;
bb:page "150"^^xsd:positiveInteger ;
meta:chapter bb:chapter6-5 ;
a meta:EntityType ;
rdfs:label "A03", "A03"@fa ;
rdfs:subClassOf bb:HL7EventType ;
skos:definition "A03 describes “discharge of a patient."@en .
bb:AC1Style
bb:page "140"^^xsd:positiveInteger ;
meta:chapter bb:chapter6-5 ;
meta:isAssociatedWith bb:DB1Style ;
a meta:EntityType ;
rdfs:label "AC1 Style"@en, "روش AC1"@fa, "سبک AC1"@fa ;
rdfs:subClassOf bb:ApplicationComponentStyle ;
skos:altLabel "Monolithic Style"@en ;
skos:definition "In the simplest case, the overall HIS consists of only one computer-based application component, which supports most of the enterprise functions."@en .
bb:ACnStyle
bb:page "141"^^xsd:positiveInteger ;
meta:chapter bb:chapter6-5 ;
a meta:EntityType ;
rdfs:label "ACn Style"@en, "ACn سبک"@fa ;
rdfs:subClassOf bb:ApplicationComponentStyle ;
skos:altLabel "Modular Architecture"@en ;
skos:definition "architectures with a multiplicity of application components"@en .
bb:AccessControlManagement
a meta:Function ;
rdfs:label "Access Control Management"@en, "کنترل دسترسی"@fa .
bb:AccessControlSystem
meta:supports bb:AccessControlManagement ;
a meta:ComputerBasedApplicationComponent, meta:ApplicationComponent, meta:EntityType ;
rdfs:label "Access Control System"@en, "سیستم کنترل دسترسی"@fa ;
rdfs:subClassOf bb:ComputerBasedApplicationComponent .
bb:AccessIntegration
bb:page "147"^^xsd:positiveInteger ;
meta:chapter bb:Thesaurus, bb:chapter6-5 ;
a meta:EntityType ;
rdfs:label "Access Integration"@en, "Zugangsintegration"@de, "یکپارچه سازی دسترسی"@fa ;
rdfs:subClassOf bb:Integration, bb:QualityOfComputerBasedApplicationComponentsAndTheirIntegration ;
skos:definition "Access integration is guaranteed when the application components needed for the completion of a certain task can be used where they are needed."@en, "Condition of an information system where the application components needed for the completion of a certain task can be used where they are needed."@en .
bb:Accuracy
bb:page "202"^^xsd:positiveInteger ;
meta:chapter bb:chapter8-2 ;
a meta:EntityType ;
rdfs:label "Accuracy"@en, "دقت"@fa ;
rdfs:subClassOf bb:QualityOfData ;
skos:definition "Describes that data should be free from mistakes. For example, patient laboratory findings are free of measurement or transcription errors."@en .
bb:Acid
bb:page "156"^^xsd:positiveInteger ;
meta:chapter bb:chapter6-5 ;
meta:entityTypeComponent bb:Atomicity, bb:Consistency, bb:Durability, bb:Isolation ;
a meta:EntityType ;
rdfs:label "ACID"@en, "ACID"@fa ;
rdfs:subClassOf bb:TransactionManagementTechnology ;
skos:definition "Transaction management guarantees 'C'onsistency of data by 'A'tomicity, 'I'solation and 'D'urability of any transaction (ACID conditions)."@en .
bb:AcquireAndImplement
a meta:Function ;
rdfs:label "Acquire and Implement"@en, "به دست آوردن و پیاده سازی"@fa ;
rdfs:subClassOf bb:CobitProcess .
bb:Activity
bb:page "55"^^xsd:positiveInteger ;
meta:chapter bb:Thesaurus ;
meta:isAssociatedWith bb:EnterpriseFunction ;
a meta:EntityType ;
rdfs:label "Activity"@en, "Aktivität"@de, "فعالیت"@fa ;
rdfs:subClassOf bb:ResearchAndEducationEntityType ;
skos:definition "An activity interprets data about certain entity types and updates data of certain entity types. Instantiation of an enterprise function. Different from enterprise functions, activities have a definite beginning and end."@en .
bb:ActivityModelingElement
a meta:EntityType ;
rdfs:label "Activity Modeling Element"@en, "عنصر مدل سازی فعالیت"@fa ;
rdfs:subClassOf bb:ResearchAndEducationEntityType .
bb:AdHocMonitoring
bb:page "265"^^xsd:positiveInteger ;
meta:chapter bb:chapter9-5 ;
meta:updates bb:ItEvaluationStudy, bb:Project ;
meta:uses bb:HisComponent ;
a meta:Function ;
rdfs:label "Ad Hoc Monitoring"@en, "مانیتورینگ ویژه"@fa ;
rdfs:subClassOf bb:StrategicHISMonitoring ;
skos:definition "Ad Hoc Monitoring may be initiated when larger changes of a component are planned, or when sudden larger problems of HIS components have been observed. Ad hoc activities help to analyze a certain situation in detail, in order to better understand reasons and consequences of an observed or expected problem. The execution of those ad hoc activities entails systems evaluation studies which are planned and conducted by tactical information management."@en .
bb:Adaptability
bb:page "204"^^xsd:positiveInteger, "206"^^xsd:positiveInteger, "207"^^xsd:positiveInteger ;
meta:chapter bb:chapter8-2 ;
a meta:EntityType ;
rdfs:label "Adaptability"@en, "سازگاری"@fa ;
rdfs:subClassOf bb:SoftwareQuality ;
skos:definition "Can a software product be easily adapted to the working context? For example, functionality of a RIS software can be adapted to the particular workflow in a specific radiology."@en .
bb:AdaptabilityOfTheHIS
bb:page "206"^^xsd:positiveInteger ;
meta:chapter bb:chapter8-2 ;
a meta:EntityType ;
rdfs:label "Adaptability of the HIS"@en, "سازگاری HIS"@fa ;
rdfs:subClassOf bb:QualityOfHISArchitecture ;
skos:definition "In general, the hospital information system should be sufficiently flexible to adapt to the changing needs of the hospital. For example, it should be easy to add new computer-based application components to the information system, and application components should be easily replaceable by other (more advanced) application components. A star-based architecture (CP 1 architecture) with a communication server (see Sect. 6.5.1.3 ) supports exchanging or adding of new computer-based application components. Additionally, the available bandwidth of the network infrastructure should be easily extendable to match increasing volume of communication."@en .
bb:AdaptationCost
meta:chapter bb:chapter2-2 ;
a meta:EntityType ;
rdfs:label "Adaptation Cost"@en, "هزینه ادغام"@fa ;
rdfs:subClassOf bb:InformationManagementCost .
bb:Administration
a meta:Function ;
rdfs:label "Administrative Function"@en, "عملکرد اداری"@fa ;
rdfs:subClassOf bb:HospitalFunction .
bb:AdministrationAndAllocationOfPatientRecords
bb:conceptDomain "health care specific"^^xsd:string ;
meta:updates bb:PatientRecordArchive ;
meta:uses bb:PatientRecordArchive ;
a meta:Function ;
rdfs:label "Administration and Allocation of Patient Records"@en, "مدیریت و تخصیص پرونده های بیمار"@fa ;
rdfs:subClassOf bb:PatientAdministration .
bb:AdministrationManagement
bb:conceptDomain "health care specific"^^xsd:string ;
meta:chapter bb:chapter4-2 ;
a meta:EntityType ;
rdfs:label "Administration Management"@en, "مدیریت دولتی"@fa ;
rdfs:subClassOf bb:ManagementDepartment .
bb:AdministrationOfBusinessTripsAndFurtherTraining
meta:updates bb:HumanResource ;
meta:uses bb:HumanResource, bb:KeyPerformanceIndicator ;
a meta:Function ;
rdfs:label "Administration of Business Trips and Further Training"@en, "اداره سفرهای تجاری و آموزش بیشتر"@fa ;
rdfs:subClassOf bb:Administration .
bb:AdministrationOfHumanResourceMasterData
meta:updates bb:HumanResource, bb:KeyPerformanceIndicator ;
meta:uses bb:HumanResource ;
a meta:Function ;
rdfs:label "Administration of Human Resource Master Data"@en, "اداره منابع اصلی منابع انسانی"@fa ;
rdfs:subClassOf bb:Administration .
bb:AdministrativeAdmission
bb:conceptDomain "health care specific"^^xsd:string ;
bb:page "293"^^xsd:positiveInteger ;
meta:chapter bb:Thesaurus ;
meta:isAssociatedWith bb:HealthCareProfessional ;
meta:updates bb:AdministrativePatientData, bb:Bed, bb:Case, bb:PatientTransport ;
meta:uses bb:AdministrativePatientData, bb:Appointment, bb:Bed, bb:Case, bb:CostUnit, bb:PatientTransport ;
a meta:Function ;
rdfs:label "Administrative Admission"@en, "Administrative Aufnahme"@de, "پذیرش اداری"@fa ;
rdfs:subClassOf bb:PatientCare ;
skos:definition "Subfunction of patient admission. Comprises patient identification and documentation of main administrative data during the admission of a patient to an institution. Includes assignment of a patient identification number and of a visit number (case identifier)."@en .
bb:AdministrativeDischargeAndBilling
bb:conceptDomain "health care specific"^^xsd:string ;
meta:chapter bb:chapter5-2 ;
meta:updates bb:Bill, bb:Case, bb:Drg, bb:Notification ;
meta:uses bb:Case, bb:CostUnit, bb:PatientCareEntityType, bb:PatientHistory ;
a meta:Function ;
rdfs:label "Administrative Discharge and Billing"@en, "تخلف اداری و صورتحساب"@fa ;
rdfs:subClassOf bb:Administration ;
skos:altLabel "DRG"@en .
bb:AdministrativeEntityType
a meta:EntityType ;
rdfs:label "Administrative Entity Type"@en, "انواع موجودیت اداری"@fa .
bb:AdministrativeGuideline
meta:chapter bb:chapter6-3 ;
a meta:EntityType ;
rdfs:label " راهنما اداری"@fa, "Administrative Guideline"@en ;
rdfs:subClassOf bb:PatientCareEntityType .
bb:AdministrativePatientData
bb:conceptDomain "health care specific"^^xsd:string ;
meta:chapter bb:chapter2-4 ;
meta:entityTypeComponent bb:PatientInsuranceData, bb:PatientsRelatives, bb:TransferDiagnosis ;
a meta:EntityType ;
rdfs:label "Administrative Patient Data"@en, "داده های اداری بیمار"@fa ;
rdfs:subClassOf bb:PatientCareEntityType ;
skos:altLabel "Administrative Data"@en .
bb:AdministrativeStaff
bb:conceptDomain "health care specific"^^xsd:string ;
meta:chapter bb:chapter4-2 ;
a meta:Role ;
rdfs:label "Administrative Staff"@en, "کارکنان اداری"@fa ;
rdfs:subClassOf bb:HospitalStaff .
bb:AdministrativeSticker
meta:chapter bb:chapter5-3 ;
a meta:EntityType ;
rdfs:label "Administrative Sticker"@en, "برچسب اداری"@fa ;
rdfs:subClassOf bb:NonComputerBasedPhysicalDataProcessingSystem .
bb:AdministrativeSupport
a meta:EntityType ;
rdfs:comment "manuell hinzugefügt"@de ;
rdfs:label "Administrative Support"@en, "Administrativer Support"@de ;
rdfs:subClassOf bb:ItService ;
skos:definition "Administrativer Support umfasst die Beschaffung von Lizenzen und ggf. Begleitung der Installation (Zurverfügungstellung von Administrationsrechten)."@de .
bb:AdmissionDiagnosis
bb:conceptDomain "health care specific"^^xsd:string ;
meta:chapter bb:chapter6-3 ;
a meta:EntityType ;
rdfs:label "Admission Diagnosis"@en, "تشخیص پذیرش"@fa ;
rdfs:subClassOf bb:PatientCareEntityType .
bb:AdoptionOfProjectResult
meta:uses bb:ProjectResult ;
a meta:Function ;
rdfs:label "Adoption of Project Result"@en, "تصویب نتایج پروژه"@fa .
bb:Adt
bb:conceptDomain "health care specific"^^xsd:string ;
bb:page "150"^^xsd:positiveInteger, "294"^^xsd:positiveInteger, "314"^^xsd:positiveInteger ;
meta:chapter bb:Thesaurus ;
meta:entityTypeComponent bb:HL7EventDescription, bb:HL7MessageHeader, bb:HL7PatientIdentification, bb:HL7PatientVisitInformation ;
a meta:EntityType ;
rdfs:label "ADT"@en, "انتقال داده صورت حساب"@fa ;
rdfs:subClassOf bb:HL7MessageType ;
skos:definition "ADT stands for messages related to admission, discharge, and transfer of a patient. Admission, discharge, and transfer of a patient, as part of patient administration."@en .
bb:AnalysisAndAssessmentOfTheCurrentHISState
bb:conceptDomain "health care specific"^^xsd:string ;
meta:updates bb:DescriptionOfTheCurrentHISState ;
meta:uses bb:DescriptionOfTheCurrentHISState ;
a meta:Function ;
rdfs:label "Analysis and Assessment of the Current HIS State"@en, "تجزیه و تحلیل و ارزیابی چگونگی فعلی HIS"@fa ;
rdfs:subClassOf bb:LifeCycleManagementOfStrategicInformationManagementPlan .
bb:AnnualHospitalOperatingCost
bb:conceptDomain "health care specific"^^xsd:string ;
meta:entityTypeComponent bb:StaffCost ;
a meta:EntityType ;
rdfs:label "Annual Hospital Operating Cost"@en, "هزینه عملیاتی سالانه بیمارستان "@fa ;
rdfs:subClassOf bb:HospitalCost .
bb:AnnualITBudget
bb:conceptDomain "health care specific"^^xsd:string ;
meta:chapter bb:chapter2-2 ;
a meta:EntityType ;
rdfs:label "Annual IT Budget"@en, "بودجه سالانه IT"@fa ;
rdfs:subClassOf bb:HospitalBudget .
bb:ApplicationComponent
bb:page "333"^^xsd:positiveInteger ;
meta:chapter bb:Thesaurus ;
meta:isAssociatedWith bb:HeterogeneityOfTheHISArchitecture, bb:HomogeneityOfTheHISArchitecture, bb:PhysicalDataProcessingSystem ;
meta:supports bb:EnterpriseFunction, bb:HospitalFunction ;
a meta:ApplicationComponent, meta:EntityType ;
rdfs:label "Anwendungsbaustein"@de, "Application Component"@en, "عنصر نرم افزار"@fa ;
skos:closeMatch ob:ApplicationSystem ;
skos:definition "An application component is a set of actually usable rules, which control data processing of certain physical data processing systems. Rules are considered to be actually usable, if they are implemented such that they are ready to support certain enterprise functions in a certain enterprise or support communication between application components."@en .
bb:ApplicationComponentStyle
meta:chapter bb:chapter6-5 ;
a meta:EntityType ;
rdfs:label "Application Component Style"@en, "سبک کامپوننت کاربرد"@fa ;
rdfs:subClassOf bb:ArchitecturalStyleOfTheLogicalToolLayer .
bb:ApplicationHosting
a meta:EntityType ;
rdfs:comment "manuell hinzugefügt"@de ;
rdfs:label "Application Hosting"@en, "Applikation-Hosting"@de ;
rdfs:subClassOf bb:ItService ;
skos:definition "Applikation-Hosting umfasst Bereitstellung der Applikation auf einem (virtuellen) Server oder einer (virtuellen) Maschine in den Rechenzentren des Bereiches 1, Bereitstellung einer lokalen Installation auf Client-PCs und Sicherungsmaßnahmen im Rahmen des vereinbarten ServiceLevels."@de .
bb:ApplicationPortfolio
meta:chapter bb:chapter9-4 ;
a meta:EntityType ;
rdfs:label "Application Portfolio"@en, "نمونه کار برنامه"@fa .
bb:ApplicationServer
bb:page "169"^^xsd:positiveInteger, "173"^^xsd:positiveInteger, "47"^^xsd:positiveInteger ;
meta:chapter bb:chapter6-6 ;
a meta:EntityType ;
rdfs:label "Application Server"@en, "سروربرنامه "@fa ;
rdfs:subClassOf bb:Server ;
skos:definition "Server can run the back-end part of application software"@en .
bb:ApplicationSupport
a meta:EntityType ;
rdfs:comment "manuell hinzugefügt"@de ;
rdfs:label "Application Support"@en, "Applikationsbetreuung"@de ;
rdfs:subClassOf bb:ItService ;
skos:definition "Applikationsbetreuung umfasst den Betrieb in den Rechenzentren des Bereiches 1 (bei Client-Server-Systemen) bzw. auf den Client-PCs, Sicherstellung der Aktualität der Software (update-Service etc.), die Bereitstellung eines Ansprechpartners aus dem Bereich 1 (Administrator), die Möglichkeit, Fehler (incidents) und Anfragen (service requests) am IT ServiceDesk zu platzieren, die Möglichkeit, neue Anforderungen zur Umsetzung im Bereich 1 zu beantragen (IT Change Management-Verfahren)."@de .
bb:Appointment
bb:page "77"^^xsd:positiveInteger ;
meta:chapter bb:chapter6-2 ;
a meta:EntityType ;
rdfs:label "Appointment"@en, "Termin"@de, "وقت ملاقات"@fa ;
rdfs:subClassOf bb:Resource ;
skos:definition "Determines which persons have to be at a certain place at a given time. Examples are appointment for patient admission , examination, or surgery"@en .
bb:AppointmentScheduling
meta:chapter bb:chapter6-3 ;
meta:updates bb:MedicalProcedure, bb:Patient, bb:Resource ;
meta:uses bb:Case, bb:Order, bb:Patient, bb:Resource, bb:Transfer ;
a meta:Function ;
rdfs:label "Appointment Scheduling"@en, "زمان بندی قرار ملاقات"@fa ;
rdfs:subClassOf bb:Administration .
bb:AppropriatePhysicalDataProcessingSystem
bb:page "205"^^xsd:positiveInteger ;
meta:chapter bb:chapter8-2 ;
a meta:EntityType ;
rdfs:label "AppropriatePhysicalDataProcessingSystem"@en, "سیستم مناسب پردازش داده های فیزیکی"@fa ;
rdfs:subClassOf bb:PhysicalDataProcessingSystem ;
skos:definition "For example, the bedside computer does not dominate the physician-patient relationship."@en .
bb:ApprovalToAStudy
meta:isAssociatedWith bb:EducationResearch ;
a meta:EntityType ;
rdfs:label "Approval to a Study"@en, "تصویب برای مطالعه"@fa .
bb:ApprovalToStrategicInformationManagementPlan
meta:updates bb:StrategicInformationManagementPlan ;
a meta:Function ;
rdfs:label "Approval to Strategic Information Management Plan"@en, "تصویب طرح مدیریت اطلاعات استراتژیک"@fa ;
rdfs:subClassOf bb:LifeCycleManagementOfStrategicInformationManagementPlan .
bb:ArchitecturalStyle
bb:page "294"^^xsd:positiveInteger ;
meta:chapter bb:Thesaurus ;
a meta:EntityType ;
rdfs:label "Architectural Style"@en, "Architekturstil"@de, "سبک معماری"@fa ;
skos:definition "Combines architectures of information systems that are equivalent with regard to certain characteristics. On the logical tool layer, these characteristics comprise number of databases (DB 1 versus DB n ), number of application components (AC 1 versus AC n ), number of software products and vendors (V 1 versus V n ), and communication patterns (star versus spaghetti architecture and CP 1 versus CP n , respectively). On the physical tool layer, we can, for example, distinguish the mainframe architecture (1-tier architecture or T 1 ) and the client-server architectural style (2-tier architecture or T 2 , 3-tier architecture or T 3 )."@en .
bb:ArchitecturalStyleOfTheLogicalToolLayer
bb:page "138"^^xsd:positiveInteger ;
a meta:EntityType ;
rdfs:label "Architectural Style of the Logical Tool Layer"@en, "سبک معماری لایه ابزار منطقی"@fa ;
rdfs:subClassOf bb:ArchitecturalStyle ;
skos:altLabel "Taxononmy of Architecture at the Logical Tool Layer"@en ;
skos:definition "However, there are significant differences in hospital information systems architectures with respect to the types and relationships of information processing tools used and the way they are integrated."@en .
bb:ArchitecturalStyleOfThePhysicalToolLayer
a meta:EntityType ;
rdfs:label "Architectural Style of The Physical Tool Layer"@en, "سبک معماری لایه ابزار فیزیکی"@fa ;
rdfs:subClassOf bb:ArchitecturalStyle .
bb:ArchitectureOfAnInformationSystem
bb:page "294"^^xsd:positiveInteger ;
meta:chapter bb:Thesaurus ;
meta:isBasedOn bb:ArchitecturalStyle ;
a meta:EntityType ;
rdfs:label "Architecture of an Information System"@en, "Architektur eines Informationssystems"@de, "معماری یک سیستم اطلاعاتی"@fa ;
skos:definition "Fundamental organization of an information system, represented by its components, their relationships to each other and to the environment, and by the principles guiding its design and evolution. Architectures can be summarized into certain architectural styles."@en .
bb:Archiving
bb:page "294"^^xsd:positiveInteger ;
meta:chapter bb:Thesaurus ;
meta:updates bb:StorageMedium ;
a meta:Function ;
rdfs:label "Archivierung"@de, "Archiving"@en, "آرشیو"@fa, "بایگانی"@fa ;
rdfs:subClassOf bb:Administration ;
skos:definition "Long-time storing (e.g., for 10 or 30 years, depending on legal regulations) of documents and records, especially of patient records, after discharge of a patient."@en .
bb:ArchivingOfPatientInformation
bb:conceptDomain "health care specific"^^xsd:string ;
bb:page "97"^^xsd:positiveInteger ;
meta:chapter bb:chapter6-3 ;
meta:functionComponent bb:AdministrationAndAllocationOfPatientRecords, bb:LongTermArchiving, bb:OpeningAPatientRecord ;
meta:uses bb:PatientRecord ;
a meta:Function ;
rdfs:label "Archiving of Patient Information"@en, "بایگانی اطلاعات بیمار"@fa ;
rdfs:subClassOf bb:Archiving ;
skos:definition "Relevant data and documents containing patient information must be created, gathered, presented, and stored such that they are efficiently retrievable during the whole process of patient treatment. The storage of these data and documents is primarily done in patient records. Today, usually a mixture of paper-based and computer-based patient records is used. Certain legal requirements usually must be considered."@en .
bb:ArtificialSystem
a meta:EntityType ;
rdfs:label "Artificial System"@en, "سیستم مصنوعی"@fa .
bb:Ascii
meta:chapter bb:chapter6-4 ;
a meta:EntityType ;
rdfs:label "ASCII"@en, "اسکی"@fa ;
rdfs:subClassOf bb:DocumentStandard ;
skos:altLabel "American Standard Code for Information Interchange"@en .
bb:AssetAccounting
a meta:Function ;
rdfs:label "Asset Accounting"@en, "حسابداری دارایی "@fa ;
rdfs:subClassOf bb:Administration .
bb:AsynchronousCommunication
bb:page "157"^^xsd:positiveInteger ;
meta:chapter bb:Thesaurus ;
meta:isAssociatedWith bb:MasterApplicationComponent ;
a meta:EntityType;
rdfs:label " Asynchrone Kommunikation"@de, "Asynchronous Communication"@en, "ارتباط ناهمگام"@fa ;
rdfs:subClassOf bb:Communication ;
skos:definition "Form of communication where the application component sending a message will continue its tasks without interruption even when awaiting a response message from the communication partner."@en .
bb:Atc
bb:conceptDomain "health care specific"^^xsd:string ;
meta:chapter bb:chapter6-5 ;
a meta:EntityType ;
rdfs:label "ATC"@en, "ATC"@fa ;
rdfs:subClassOf bb:Classification ;
skos:altLabel "Anatomical Therapeutic Chemical Classification System"@en .
bb:Atomicity
bb:page "156"^^xsd:positiveInteger ;
meta:chapter bb:chapter6-5 ;
a meta:EntityType ;
rdfs:label "Atomicity"@en, "اتمی بودن"@fa ;
skos:definition "Atomicity guarantees that either all of the tasks of a transaction are performed or none of them are."@en .
bb:AuthenticityOfData
bb:page "203"^^xsd:positiveInteger ;
meta:chapter bb:chapter8-2 ;
a meta:EntityType ;
rdfs:label "Authenticity of Data"@en, "صحت داده ها"@fa ;
rdfs:subClassOf bb:QualityOfData ;
skos:definition "Describes that data have an established authorship. For example, the authorship of a discharge report is clear and indisputable."@en .
bb:AvailabilityOfApplicationComponents
bb:page "204"^^xsd:positiveInteger ;
meta:chapter bb:chapter8-2 ;
a meta:EntityType ;
rdfs:label "Availability of Application Components"@en, "در دسترس بودن اجزای برنامه"@fa ;
rdfs:subClassOf bb:SoftwareQuality ;
skos:definition "Is the application component made available at all places where it is needed? This means: Is access integration guaranteed (see Sect. 6.5.3.3 )? For example, is the RIS available in all treatment rooms of the outpatient unit?"@en .
bb:AvailabilityOfData
bb:page "131"^^xsd:positiveInteger, "203"^^xsd:positiveInteger, "229"^^xsd:positiveInteger ;
meta:chapter bb:chapter6-4 ;
a meta:EntityType ;
rdfs:label "Availability of Data"@en, "در دسترس بودن داده ها"@fa ;
rdfs:subClassOf bb:QualityOfData ;
skos:definition "Availability means that data must be retrievable and readable at any time throughout the archiving period"@en .
bb:AvailabilityOfTheApplicationComponent
bb:page "265"^^xsd:positiveInteger ;
meta:chapter bb:chapter9-5 ;
a meta:EntityType ;
rdfs:label "Availability of the Application Component"@en, "در دسترس بودن کامپوننت برنامه"@fa ;
rdfs:subClassOf bb:KeyPerformanceIndicator ;
skos:definition "down times per year"@en .
bb:AvailablePhysicalDataProcessingSystem
bb:page "205"^^xsd:positiveInteger ;
meta:chapter bb:chapter8-2 ;
a meta:EntityType ;
rdfs:label "available physical data processing system"@en, "سیستم پردازش داده های فیزیکی در دسترس"@fa ;
rdfs:subClassOf bb:PhysicalDataProcessingSystem ;
skos:definition "For example, computers are available both in the ward office and at the patient’s bedside."@en .
bb:AvailableServer
rdfs:label "available server"@en, "سرور دسترس"@fa .
bb:BPflV
bb:conceptDomain "health care specific"^^xsd:string ;
bb:page "215"^^xsd:positiveInteger ;
meta:chapter bb:chapter8-4 ;
a meta:EntityType ;
rdfs:label "BPflV"@en, "BPflv"@fa ;
rdfs:subClassOf bb:GermanLaw ;
skos:altLabel "Bundespflegesatzverordnung"@en ;
skos:definition "Verordnung zur Regelung der Krankenhauspflegesätze (Bundespflegesatzverordnung - BPflV); German law on financing health care. Contains sections about: Allgemeine Vorschriften, Vergütung der Krankenhausleistungen, Entgeltarten und Abrechnung, Vereinbarungsverfahren und Sonstige Vorschriften (Compare: http://www.buzer.de/gesetz/4772/index.htm)"@en .
bb:Backbone
meta:chapter bb:chapter9-2 ;
a meta:EntityType ;
rdfs:label "Backbone"@en, "پشتیبان"@fa .
bb:BalanceOfComputerBasedAndNonComputerBasedTools
bb:page "217"^^xsd:positiveInteger ;
meta:chapter bb:chapter8-5 ;
a meta:EntityType ;
rdfs:label "Balance of Computer-Based and Non-Computer-Based Tools"@en, "تعادل ابزارهای مبتنی بر کامپیوتر و غیر کامپیوتری"@fa ;
rdfs:subClassOf bb:QualityOfHISArchitecture ;
skos:definition "It is the task of information management to manage information processing in such a way that the goals of the hospital can be reached best. So, for a hospital whose goal is to provide very personal and humane treatment, it might be sensible, for example, to abstain from the use of technology and especially computers for all immediate physician-patient contact."@en .
bb:BalanceOfDataSecurityAndWorkingProcesses
bb:page "218"^^xsd:positiveInteger, "220"^^xsd:positiveInteger, "236"^^xsd:positiveInteger ;
meta:chapter bb:chapter8-5 ;
a meta:EntityType ;
rdfs:label "Balance of Data Security and Working Processes"@en, "تعادل امنیت اطلاعات و فرآیندهای کاری"@fa ;
rdfs:subClassOf bb:QualityOfHISArchitecture ;
skos:definition "A hospital information system should implement strict access control methods to ensure that unauthorized access is impossible. However, this can lead to hindrances in the daily work of the health care professionals."@en .
bb:BalanceOfDocumentationQualityAndDocumentationEfforts
bb:page "219"^^xsd:positiveInteger, "220"^^xsd:positiveInteger, "221"^^xsd:positiveInteger, "236"^^xsd:positiveInteger ;
meta:chapter bb:chapter8-5 ;
a meta:EntityType ;
rdfs:label "Balance of Documentation Quality and Documentation Efforts"@en, "تعادل کیفیت مستندات و تلاش های مستند سازی"@fa ;
rdfs:subClassOf bb:QualityOfHISArchitecture ;
skos:definition "Thus, information management carefully has to balance the amount of documentation that is really needed for the various purposes, and the effort that health care professionals have to invest."@en .
bb:BalanceOfFunctionalLeannessAndFunctionalRedundancy
bb:page "219"^^xsd:positiveInteger, "221"^^xsd:positiveInteger, "236"^^xsd:positiveInteger ;
meta:chapter bb:chapter8-5 ;
a meta:EntityType ;
rdfs:label "Balance of Functional Leanness and Functional Redundancy"@en, "تعادل اندکگری و افزونگری عملکردی"@fa ;
rdfs:subClassOf bb:QualityOfHISArchitecture ;
skos:definition "Functional leanness describes a situation where one hospital function is supported by one and only one application component; the opposite is functional redundancy (see also Sect. 8.7.4 ), which results in additional costs both for investment and maintenance."@en .
bb:BalanceOfHomegeneityAndHeterogeneity
bb:page "217"^^xsd:positiveInteger ;
meta:chapter bb:chapter8-5 ;
a meta:EntityType ;
rdfs:label "Balance of Homegeneity and Heterogeneity"@en, "تعادل یکنواختی و ناهمگونی"@fa ;
rdfs:subClassOf bb:QualityOfHISArchitecture ;
skos:definition "The collection of information processing tools (both on the logical and on the physical tool layer) should be as homogeneous (i.e., comparable in appearance and usability, for example, using tools from the same vendor) as possible and as heterogeneous as necessary. In general, a homogeneous set of information processing tools makes training and support of users easier and thus leads to reduced costs for the HIS."@en .
bb:BalancedNetwork
bb:conceptDomain "health care specific"^^xsd:string ;
bb:page "287"^^xsd:positiveInteger ;
meta:chapter bb:chapter10-4 ;
a meta:Role ;
rdfs:label "Balanced Network"@en, "شبکه متعادل"@fa ;
rdfs:subClassOf bb:HealthCareNetwork ;
skos:definition "Balanced networks show medium degrees of centrality and intensity."@en .
bb:Bar
bb:conceptDomain "health care specific"^^xsd:string ;
bb:page "150"^^xsd:positiveInteger, "178"^^xsd:positiveInteger ;
meta:chapter bb:chapter6-5 ;
a meta:EntityType ;
rdfs:label "BAR"@en, "BAR"@fa ;
rdfs:subClassOf bb:HL7MessageType ;
skos:definition "BAR stands for a patient accounting message"@en .
bb:Bdsg
meta:chapter bb:chapter8-4 ;
a meta:EntityType ;
rdfs:label "BDSG"@en, "قانون فدرال حفاظت از داده"@fa ;
rdfs:subClassOf bb:GermanLaw ;
skos:altLabel "Bundesdatenschutzgesetz"@de .
bb:Bed
bb:conceptDomain "health care specific"^^xsd:string ;
bb:page "77"^^xsd:positiveInteger ;
meta:chapter bb:chapter6-2 ;
a meta:EntityType ;
rdfs:label "Bed"@en, "تخت"@fa ;
rdfs:subClassOf bb:Resource ;
skos:definition "Must be managed according to its occupation"@en .
bb:BedOccupation
bb:conceptDomain "health care specific"^^xsd:string ;
bb:page "130"^^xsd:positiveInteger, "83"^^xsd:positiveInteger ;
meta:chapter bb:chapter6-3 ;
a meta:EntityType ;
rdfs:label "Bed Occupation"@en, "اشغال تخت"@fa ;
rdfs:subClassOf bb:KeyPerformanceIndicator ;
skos:definition "The hospital management must always have an overview of the recent bed occupation, i.e., about the patients’ staying at the hospital. This is, for example, important for the clerks at the information desk, who must be able to inform relatives and visitors correctly, and also for some general hospital management statistics (e.g. number of provided beds and beds actually used). [Anna Lörke according to Winter et al.]"@en .
bb:BehavioralPerspective
meta:chapter bb:chapter5-2 ;
a meta:EntityType ;
rdfs:label "Behavioral Perspective"@en, "دیدگاه رفتاری"@fa .
bb:Benchmarking
bb:page "295"^^xsd:positiveInteger ;
meta:chapter bb:Thesaurus ;
a meta:Function ;
rdfs:label "Benchmarking"@en, "معیار سنجش"@fa ;
skos:definition "Describes a process in which organizations evaluate various aspects of their performance and compare it to given standard or to the best organizations (“best-practice”). Typically, benchmarking comprises quantitative evaluation criteria (key performance indicators). Method of strategic monitoring of hospital information systems."@en .
bb:BestOfBreedArchitecture
bb:page "142"^^xsd:positiveInteger ;
meta:chapter bb:chapter6-5 ;
meta:isAssociatedWith bb:ACnStyle, bb:DBnStyle, bb:VnStyle ;
a meta:EntityType ;
rdfs:label "Best-of-Breed-Architecture"@en, "معماری بهترین نژاد"@fa ;
rdfs:subClassOf bb:ArchitecturalStyleOfTheLogicalToolLayer ;
skos:definition "An (AC n , V n ) architecture where the different application components are based on software from different vendors is commonly denoted as “best-of-breed,” pointing to the fact that the hospital combines the “best” software products from different vendors."@en .
bb:BestPracticeBenchmark
bb:conceptDomain "health care specific"^^xsd:string ;
a meta:EntityType ;
rdfs:label "Best-Practice-Benchmark"@en, "معیار بهترین شیوه"@fa .
bb:Bill
bb:page "78"^^xsd:positiveInteger ;
meta:chapter bb:chapter6-2 ;
a meta:EntityType ;
rdfs:label "Bill"@en, "صورتحساب"@fa ;
rdfs:subClassOf bb:AdministrativeEntityType .
bb:BillingOfAccountableServices
a meta:Function ;
rdfs:label "Billing of Accountable Services"@en, "صورتحساب خدمات قابل توضیح"@fa ;
rdfs:subClassOf bb:Administration .
bb:BloodBank
bb:conceptDomain "health care specific"^^xsd:string ;
meta:chapter bb:chapter4-2 ;
a meta:EntityType ;
rdfs:label "Blood Bank"@en, "بانک خون"@fa ;
rdfs:subClassOf bb:OrganizationalUnitOfAHospital .
bb:BloodBankManagementSystem
bb:page "134"^^xsd:positiveInteger ;
meta:chapter bb:chapter6-4 ;
a meta:ApplicationComponent, meta:ComputerBasedApplicationComponent, meta:EntityType ;
rdfs:label "Blood Bank Management System"@en, "سیستم مدیریت بانک خون"@fa ;
rdfs:subClassOf bb:ComputerBasedApplicationComponent ;
skos:definition "Supports blood donor services, blood analyses, administration of blood bottles"@en .
bb:BlueBook
dc:date "2011" ;
dc:publisher <http://dbpedia.org/resource/Springer_Science+Business_Media> ;
dc:title "Health Information Systems"@en ;
bibo:authorList bb:blank223753 ;
bibo:doi "10.1007/978-1-84996-441-8_4" ;
bibo:isbn "978-1-84996-440-1" ;
a bibo:Book .