OpenMRS 객체 간 관계
각 encounter type을 환자에게 제공되는 서비스 유형으로 간주합니다. 이와 같은 관계가 더 필요할 수 있습니다. 데이터 양이 적으므로 관계 유형마다 별도 테이블을 만드는 대신 하나의 테이블로 모델링할 수 있는지 검토해야 합니다. 이 데이터를 대상으로 아래 설명과 같은 질문에 답할 수 있는 서비스도 제공되어야 합니다.
| Object | Object | Name | Description |
|---|---|---|---|
| Location | Program (m) | Program Departments | On user login to a location, narrow down the programs which are serviced from that location |
| Program | Encounter Type (m) | Program Services | Each program could have a list of encounter types and when saving an encounter the type is derived from it |
| Location | Encounter Type (m) | Department Services | Each location could have a list of encounter types, if no program is used then encounter type is picked based on the location |
| Program | Form (m) | Program Forms | In the context of a program, provide only the choice of forms associated to it. If it is less that 7 forms then we can display all of them instead of expecting user to favourite it |
| Location | Order Type (m) | Order Points | Each location may be responsible for fulfilling certain orders. On login to a location, order fulfilment application should be presented to the user. |
Location, Program, ET, VT, Obs Forms, Order Type, Order Class, Provider
원문 정보
원문 보기 ↗Bahmni Wiki · CC BY-SA 4.0