其實我們可以把Resource當作是物件(本來就是),Data Type是參考型別,也是物件。
就物件導向的概念自然就會衍生出抽象物件,在FHIR中稱為Logical Models。下圖是這些抽象物件的架構。
現在就是比照所有物件導向程式的物件架構,都有個最原始的物件。這邊叫Base。他就是一個空物件提供繼承。
回去看Resource已經改了,其型態為Base,自身為Interface。(其他雷同就不加演示)
Structure
| Name | Flags | Card. | Type | Description & Constraints | 
|---|---|---|---|---|
![]()  | «I»N | Base | Base Resource Elements defined in Ancestors:  | |
![]() ![]()  | Σ | 0..1 | id | Logical id of this artifact | 
![]() ![]()  | Σ | 0..1 | Meta | Metadata about the resource | 
![]() ![]()  | ?!Σ | 0..1 | uri | A set of rules under which this content was created | 
![]() ![]()  | 0..1 | code | Language of the resource content Common Languages (Preferred but limited to AllLanguages)  | |
然後呢?隨著Resource的制定,發現好多Resource都有一些規範URL的需求。簡單講就是Resource的詳細應用規範所需的元素。這下子就用CanonicalResource來描述。MetadataResource也是相同的概念。
原本Resource中,改繼承自MetadataResource者有:(這些當然也有CanonicalResource)
原本Resource中,改繼承自MetadataResource者有:(這些當然也有CanonicalResource)
- ActivityDefinition
 - CapabilityStatement
 - CapabilityStatement2
 - ChargeItemDefinition
 - CodeSystem
 - CompartmentDefinition
 - ConceptMap
 - ConditionDefinition
 - EventDefinition
 - Evidence
 - EvidenceVariable
 - ExampleScenario
 - GraphDefinition
 - ImplementationGuide
 - Library
 - Measure
 - MessageDefinition
 - NamingSystem
 - OperationDefinition
 - PlanDefinition
 - Questionnaire
 - SearchParameter
 - StructureDefinition
 - StructureMap
 - TerminologyCapabilities
 - TestScript
 - ValueSet
 




沒有留言:
張貼留言