HL及其在公共卫生信息系统

1、2022-4-301 HL7 HL7概况概况 HL7 V2.X HL7 V2.X HL7 V3.0HL7 V3.0 HL7HL7在在PHINPHIN的应用的应用主 要 内 容2022-4-302 Health Level Seven Health Level Seven ( (HL7) HL7) 19871987年成立年成立 美国国家标准局（美国国家标准局（ANSIANSI）授权授权的从事医疗服务信息传输协议及标的从事医疗服务信息传输协议及标准研究和开发的机构准研究和开发的机构HL7 概况2022-4-303HL7HL7的目的的目的 开发和研制医疗数据信息传输协开发和研制医疗数据信息传输协议及

2、标准议及标准 优化临床及其管理数据信息的程优化临床及其管理数据信息的程序序 降低卫生信息系统互连的成本降低卫生信息系统互连的成本 提高卫生信息系统之间数据信息提高卫生信息系统之间数据信息共享的程度共享的程度HL7 概况2022-4-304* * 全美国约有全美国约有9 95%5%的医院，的医院，9 95%5%的医疗相关设备及信息系统应用的医疗相关设备及信息系统应用HL7HL7作为其标准。作为其标准。 * * HL7 HL7 现有会员现有会员22002200多名，代多名，代表着世界上主要国家和主流技术表着世界上主要国家和主流技术的发展趋势。的发展趋势。HL7的影响力 2022-4-305 21

3、International HL7 Affiliates: Argentina Australia Brazil Canada China Croatia Czech Republic Denmark Finland Germany India Japan Korea Lithuania New Zealand Southern Africa Switzerland Taiwan Turkey The Netherlands United KingdomHL7 is International!26 USA2022-4-306 PAYERSPAYERS GENERAL INTERESTGENE

4、RAL INTEREST PROVIDERSPROVIDERS CONSULTANTSCONSULTANTS VENDORSVENDORSHL7HL7会员2022-4-307PAYERSPAYERSBlue Cross & Blue Shied, United Blue Cross & Blue Shied, United Health Group, Vytra Health Plans, Health Group, Vytra Health Plans, etc.etc.GENERAL INTERESTGENERAL INTERESTAMA, AHA, JCAHO, CDC, NCHS, P

5、an AMA, AHA, JCAHO, CDC, NCHS, Pan Am. Health Organization/WHO, U.S. Am. Health Organization/WHO, U.S. Dept. of DefenseDept. of DefenseHealth Affairs, Health Affairs, U.S. Dept. of Health & Human U.S. Dept. of Health & Human Service.Service.HL7HL7会员2022-4-308PROVIDERSPROVIDERSJohn Hopkins Hospital,

6、Baptist John Hopkins Hospital, Baptist Health System, U.S. Dept. of Health System, U.S. Dept. of Veterans Affairs, etc.Veterans Affairs, etc.CONSULTANTSCONSULTANTSErnst & Young LLP, GartnerGroup, Ernst & Young LLP, GartnerGroup, etc. etc. VENDORSVENDORSIBM, SUN, IDX, HP, NEC, Microsoft, IBM, SUN, ID

7、X, HP, NEC, Microsoft, 3M, SMS, etc.3M, SMS, etc. HL7HL7会员2022-4-309HL7HL7的应用的应用Get your health informationAny-time,Any-where,Any-device.2022-4-30101. HL71. HL7s SIGs SIG成员提议成员提议 2. 2. SIGSIG磋商、讨论、投票磋商、讨论、投票(90%)(90%)3. SIG3. SIG成员如有反对意见须注明理由，成员如有反对意见须注明理由， 组长负责解决组长负责解决4. SIG4. SIG通过的标准提案须提交通过的标准提案须

8、提交HL7HL7技技术术 委员会通过委员会通过5. 5. HL7HL7技术委员会通过的标准报技术委员会通过的标准报ANSIANSI 审批审批HL7HL7制定标准的程序2022-4-30111. HL71. HL7s Messaging Standard s Messaging Standard 2. Arden Syntax for Medical 2. Arden Syntax for Medical LogicLogic Systems Systems3. Clinical Context Object3. Clinical Context Object Workgroup(CCOW) W

9、orkgroup(CCOW)4. Clinical Document 4. Clinical Document ArchitectureArchitecture (CDA) (CDA)HL7HL7研究的标准2022-4-3012 HL7HL7s Messaging Standards Messaging Standard： 2.2 1994 2.2 1994年年2 2月颁布月颁布 ( (ANSI) ANSI) 2.3 1997 2.3 1997年年5 5月颁布月颁布 ( (ANSI)ANSI) 2.3.1 19992.3.1 1999年年4 4月颁布月颁布 ( (ANSI)ANSI) 2.4

10、2000 2.4 2000年年1010月颁布月颁布 ( (ANSI)ANSI) 2.5 2.5 20032003年年8 8月颁布月颁布 (ANSI)(ANSI) 2.6 2.6 研制中研制中 3.0 3.0 20042004年年3 3月部分月部分 (ANSI)(ANSI)HL7HL7研究的标准及其进展2022-4-3013与相关标准的合作与相关标准的合作DICOM、XML、IEEE(X12N)、ASTM(E31) SNOMED、ICD、LOINC、CPT、NDCCEN TC251、 ISO 2152022-4-3014 1 物理 Physical 2 链路 Data Link 3 网络 Net

11、work 4 传输 Transport 5 会话 Session 6 表示 Presentation 7 应用 Application HL7与网络体系结构及协议的关系与网络体系结构及协议的关系2022-4-3015HL7 HL7 与与 OSI OSI 的关系的关系链路 Data Link物理 Physical传输 Transport网络 Network表示 Presentation会话 Session应用 ApplicationFTPHTTPPOP3.TCPUDPIPLLC; MACSMTP实体线路实体线路Health Level Seven (HL7)2022-4-3016 HL7 HL7

12、概况概况 HL7 V2.X HL7 V2.X HL7 V3.0HL7 V3.0 HL7HL7在在PHINPHIN的应用的应用主 要 内 容2022-4-3017An HL7 Version 2.X SpecCommon SpecsChapter-Specific SpecsChapter-Specific SpecsChapter-Specific SpecsChapters2 and 8Chapters 3, 4, 6, .Trigger Event and MessagesSegments and Fields2022-4-3018HL7HL7标准涵盖的内容标准涵盖的内容 General

13、Introduction (Chapter 1) Message Infrastructure (Ch. 2) General conventions Data Types Message Construction Rules Patient Administration (Ch. 3) 62 Patient Administration transactions 238 patient-related data items2022-4-3019 Orders & Observations (Ch. 4 & 7) Diagnostic Services (Lab, Radiology, etc

14、.) Medications and Drugs Treatments Clinical trials Dietary Supply Queries (Ch. 5) Queries & ResponsesHL7HL7标准涵盖的内容标准涵盖的内容2022-4-3020 Financial Management (Ch. 6) basic service billing messages e-claims Management of Master Files/Tables (Ch. 8) Patients Providers Locations Clinical Document Manageme

15、nt (Ch. 9)HL7HL7标准涵盖的内容标准涵盖的内容2022-4-3021 Scheduling of Medical Services (Ch. 10) Patient Referral/Discharge (Ch. 11) Patient Care (Ch. 12) Laboratory Automation (Ch. 13) Application Management (Ch. 14) Personnel Management (Ch. 16) Appendices .HL7HL7标准涵盖的内容标准涵盖的内容2022-4-3022HL7HL7消息模型消息模型Converts a

16、nd sends in HL7Receives in HL72022-4-3023HL7HL7消息传输格式消息传输格式MessageSegmentField2022-4-3024消息（消息（MessageMessage）：）： 消息是数据在系统之间交换的基本单元，消息是数据在系统之间交换的基本单元，每条消息都有各自的消息类型（每条消息都有各自的消息类型（Message Message type V2.4type V2.4共有共有112112种种）用于定义消息目的用于定义消息目的 消息类型中有触发事件消息类型中有触发事件( (Trigger Trigger Event) Event) 如如ADT

17、 ADT 消息由若干个消息段组成。消息由若干个消息段组成。HL7HL7消息传输格式2022-4-3025V2.4 Message - ADTMSHMessage HeaderEVNEvent TypePIDPatient Identification PD1Additional Demographics NK1 Next of Kin /Associated PartiesPV1Patient Visit PV2 Patient Visit - Additional Info. GT1 Guarantor IN1Insurance IN2 Insurance Additional Info.

18、IN3 Insurance Addl Info - Cert. optional may repeat2022-4-3026A HL7 V2.4 Admit MessageMSH|&|PATH|GP123|200108261705+1100|A04|101|P|2.4|34567|AL|NE|AU|enEVN|A01|200108261645+1100|PID|KNEE123|KneesNobbyJMr|19331215|M|23 Shady LaneLIGHTNING RIDGENSW2392|219171803NK1|1|KneesBarbaraK|Wife|CPContact perso

19、n|PV1|1|I|2000201201|E|004777GetwellSaraJ|TRMA|ADM|A0|2022-4-3027消息段（消息段（SegmentSegment）：）： 由一组数据字段（由一组数据字段（Data fieldData field）按一按一定顺序和规则组成，每一消息段都有相应定顺序和规则组成，每一消息段都有相应的名称，用于界定其内容或功能的名称，用于界定其内容或功能 V2.4V2.4共有共有138138种消息段种消息段。Message Message Header (MSH), Event Type (EVN), Header (MSH), Event Type (E

20、VN), Patient ID (PID), and Patient Patient ID (PID), and Patient Visit (PV1)Visit (PV1) 消息段分为：必须、可选、可重复三种消息段分为：必须、可选、可重复三种类型类型HL7HL7消息传输格式2022-4-3028A HL7 V2.4 SegmentMSH|&|PATH|GP123|200108261705+1100|A04|101|P|2.4|34567|AL|NE|AU|enEVN|A01|200108261645+1100|PID|KNEE123|KneesNobbyJMr|19331215|M|23 S

21、hady LaneLIGHTNING RIDGENSW2392|219171803NK1|1|KneesBarbaraK|Wife|CPContact person|PV1|1|I|2000201201|E|004777GetwellSaraJ|TRMA|ADM|A0|2022-4-3029HL7 V2.4 MSH Segment 定义定义SEQLENDTOPTRP/#TBL#ITEM #ELEMENT NAME11STR00001 Field Separator24STR00002 Encoding Characters3180HDO00003 Sending Application4180

22、HDO00004 Sending Facility5180HDO00005 Receiving Application6180HDO00006 Receiving Facility726TSO00007 Date/Time Of Message840STO00008 Security97CMR00009 Message Type1020STR00010 Message Control ID113PTR00011 Processing ID128IDR010400012 Version ID1315NMO00013 Sequence Number14180STO00014 Continuatio

23、n Pointer152IDO015500015 Accept Acknowledgment Type162IDO015500016 Application Ack. Type172IDO00017 Country Code186IDOY/3021100692 Character Set1960CEO00693 Principal Language Of MessageSEQ - position within segmentLEN - length of fieldDT - data type for fieldOPT - optionality for fieldRP/# - repeat

24、abilityTBL# - table number for codesITEM# - HL7 field numberELEMENT NAME - name2022-4-3030Segments .MSH|&|PATH|GP123|20000826|ORU|101|P|2.4|34567|AL|NE|AU|enPID|KNEE123|KneesNobbyJMr|19331215|M|23 Shady LaneLIGHTNING RIDGENSW2392|219171803OBR|1|PMS66666|956635.9|LFTLIVER FUNCTION TESTN2270OBX|1|NM|1

25、751-7S AlbuminLN|38|g/L|35-45|FOBX|2|NM|1779-8S Alkaline PhosphataseLN|52|U/L|30-120|F2022-4-3031Segments .MSH|&|PATH|GP123|20000826|ORU|101|P|2.4|34567|AL|NE|AU|enPID|KNEE123|KneesNobbyJMr|19331215|M|23 Shady LaneLIGHTNING RIDGENSW2392|219171803OBR|1|PMS66666|956635.9|LFTLIVER FUNCTION TESTN2270OBX

26、|1|NM|1751-7S AlbuminLN|38|g/L|35-45|FOBX|2|NM|1779-8S Alkaline PhosphataseLN|52|U/L|30-120|F2022-4-3032Segments .MSH|&|PATH|GP123|20000826|ORU|101|P|2.4|34567|AL|NE|AU|enPID|KNEE123|KneesNobbyJMr|19331215|M|23 Shady LaneLIGHTNING RIDGENSW2392|219171803OBR|1|PMS66666|956635.9|LFTLIVER FUNCTION TESTN

27、2270OBX|1|NM|1751-7S AlbuminLN|38|g/L|35-45|FOBX|2|NM|1779-8S Alkaline PhosphataseLN|52|U/L|30-120|F2022-4-3033Segments .MSH|&|PATH|GP123|20000826|ORU|101|P|2.4|34567|AL|NE|AU|enPID|KNEE123|KneesNobbyJMr|19331215|M|23 Shady LaneLIGHTNING RIDGENSW2392|219171803OBR|1|PMS66666|956635.9|LFTLIVER FUNCTIO

28、N TESTN2270OBX|1|NM|1751-7S AlbuminLN|38|g/L|35-45|FOBX|2|NM|1779-8S Alkaline PhosphataseLN|52|U/L|30-120|F2022-4-3034Segments .MSH|&|PATH|GP123|20000826|ORU|101|P|2.4|34567|AL|NE|AU|enPID|KNEE123|KneesNobbyJMr|19331215|M|23 Shady LaneLIGHTNING RIDGENSW2392|219171803OBR|1|PMS66666|956635.9|LFTLIVER

29、FUNCTION TESTN2270OBX|1|NM|1751-7S AlbuminLN|38|g/L|35-45|FOBX|2|NM|1779-8S Alkaline PhosphataseLN|52|U/L|30-120|F2022-4-3035MSH|&|PATH|GP123|20000826|ORU|101|P|2.4|34567|AL|NE|AU|enPID|KNEE123|KneesNobbyJMr|19331215|M|23 Shady LaneLIGHTNING RIDGENSW2392|219171803OBR|1|PMS66666|956635.9|LFTLIVER FUN

30、CTION TESTN2270OBX|1|NM|1751-7S AlbuminLN|38|g/L|35-45|FOBX|2|NM|1779-8S Alkaline PhosphataseLN|52|U/L|30-120|FRepeated Segments .2022-4-3036MSH|&|PATH|GP123|20000826|ORU|101|P|2.4|34567|AL|NE|AU|enPID|KNEE123|KneesNobbyJMr|19331215|M|23 Shady LaneLIGHTNING RIDGENSW2392|219171803OBR|1|PMS66666|95663

31、5.9|LFTLIVER FUNCTION TESTN2270OBX|1|NM|1751-7S AlbuminLN|38|g/L|35-45|FOBX|2|NM|1779-8S Alkaline PhosphataseLN|52|U/L|30-120|FRepeated Segments .2022-4-3037字段（字段（FieldsFields）：）： 是一个字符串。字段必须定义其是一个字符串。字段必须定义其在消息段中的位置、长度、数据类型在消息段中的位置、长度、数据类型(55(55种种) )、选择类型、重复性、选择类型、重复性HL7HL7消息传输格式2022-4-3038NK1|1|Kn

32、eesBarbaraK|Wife|CPContact person|PV1|1|I|2000201201|E|004777GetwellSaraJ|TRMA|ADM|A0|Lets look at “Fields” .IDNameSexStreet AddressTown/SuburbDOBMSH|&|PATH|GP123|20000826|ORU|101|P|2.4|34567|AL|NE|AU|enPID|KNEE123|KneesNobbyJMr|19331215|M|23 Shady LaneLIGHTNING RIDGENSW2392|2191718032022-4-3039表（表（

33、TableTable）：）： V2.4 V2.4共有共有470470余个表，分为余个表，分为HL7HL7标标准表和用户自定义表以及外部表三类准表和用户自定义表以及外部表三类HL7HL7消息传输格式2022-4-30400100DOn discharge0100OOn receipt of order0100RAt time service is completed0100SAt time service is started0100TAt a designated date/time表表0100 HL7 When to Charge2022-4-3041表表0116 User Bed Stat

34、us0116CClosed0116HHousekeeping0116IIsolated0116KContaminated0116OOccupied0116UUnoccupied2022-4-3042HL7-enabled systemReceiverDataHow does HL7 Messaging work?NetworkHL7-enabled systemSenderDataHL7MessageCreationEncodingHL7MessageParsingEncodingHL7 V2.xStandardHL7 V2.xStandard2022-4-3043接收系统发送系统HL7HL7

35、消息传输消息传输( (初始模式初始模式) )生成生成HL7Message，发给应答系统发给应答系统校验，如错误，校验，如错误，返回拒绝消息返回拒绝消息应用程序生成确应用程序生成确认、出错、拒绝认、出错、拒绝消息消息2022-4-3044HL7HL7消息传输消息传输( (增强模式增强模式) )生成生成HL7Message，发给应答系统发给应答系统接收，检查接收，检查MSH，确认发送端是否确认发送端是否需要成功接收、需要成功接收、安全存储的确认安全存储的确认发送系统接收系统2022-4-3045 HL7 HL7概况概况 HL7 V2.X HL7 V2.X HL7 V3.0HL7 V3.0 HL7H

36、L7在在PHINPHIN的应用的应用主 要 内 容2022-4-3046 HL7 Version 3HL7 Version 3 is a family Reference Information Model (RIM) Vocabulary Specifications Defined Methodology2022-4-3047An HL7 Version 3.X SpecCommon SpecsChapter-Specific Specs2-nd Order 1 choice of 0-n Drug 0-1 Nursing*Future ConsiderationHL7 Reference

37、 Model2022-4-3048ClassAttribute : DatatypeAttribute : DatatypeAttribute : DatatypeAttribute : DatatypeClassAttribute : DatatypeAttribute : DatatypeAttribute : DatatypeAttribute : DatatypeRelationshipInformation Model Components2022-4-3049RoleEntityParticipationActsNormative RIM Class Diagram2022-4-3

38、050 Core concepts of the RIM Every happening is an Act Procedures, observations, medications, supply, registration, etc. Acts are related through an Act_relationship composition, preconditions, revisions, support, etc. Participation defines the context for an Act author, performer, subject, location

39、, etc. The participants are Roles patient, provider, practitioner, specimen, employee etc. Roles are played by Entities persons, organizations, material, places, devices, etc.2022-4-305110.*plays10.*scopes0.*10.*1RIM Core Classes0.*0.*11110.*0.*ProcedureObservationPatient EncntrSubstance AdmSupplyRe

40、ferralFinancial actWorking listContractOrganizationLiving SubjectPersonMaterialPlacePatientEmployeeAssigned EntityCertified EntityGuarantorAccess2022-4-3052EntityClass_CD : CSCD : CVDeterminer_CD : CSStatus_CD : CSRoleClass_CD : CSCD : CVEffective_TMR : IVLParticipationType_CD : CSTMR : IVLStatus_CD

41、 : CSActClass_CD : CSCD : CDMood_CD : CSStatus_CD : CSActivity_Time : GTS10.*10.*10.*RIM Core Attribute Value SetsEntityClass CodeRoleClass CodeParticipationType CodeActMood CodeActClassCodeEntityDeterminerCode10.*playsvalidates2022-4-3053Vocabulary Domains and Codes Every coded attributes in the RI

42、M must be associated with one and only one Vocabulary Domain prior to being used in a message. A vocabulary is a defined set of coded concepts, which may be: specified as an enumerated list of coded concepts (HL7 defined) a reference to external concepts (e.g., SNOMED, LOINC, CPT, .).2022-4-3054Refi

43、nement from RIM to Message2022-4-3055Demo ExampleOrderPhysicianPerformerLaboratorySubjectSpecimenRecord targetPatientDefinitionOrdered TestAuthor2022-4-3056Demo ExampleOrderDefinitionPerformerAuthorRecord targetPatientLaboratoryPhysicianOrdered testSubjectSpecimen2022-4-3057PersonPractitionerclass_c

44、d : CSdeterminer_cd : CSid : SETnm : BAGtelecom : BAGCertifiedEntityclass_cd : CSid : SETtelecom : BAG0.1.subjectPerson0.certificate1.Authortype_cd : CSsignature_cd : CSsignature_txt : ED1.0.origination1.certifiedEntity0.Organizationclass_cd : CSdeterminer_cd : CSid : SETnm : BAGHealthCareProvidercl

45、ass_cd : CSid : SETtelecom : BAG0.1.healthCareOrganization0.healthCareProviderLicense1.Performertype_cd : CS1.0.performance1.healthCareProvider0.ObservationOrderclass_cd : CSmood_cd : CSid : SETcd : CDactivity_time : GTS0.0.observationOrder0.author0.0.1.performer0.observationOrder1.Personclass_cd :

46、CSdeterminer_cd : CSid : SETnm : BAGtelecom : BAGadministrative_gender_cd : CEbirth_time : TSPatientclass_cd : CSid : SETaddr : BAG1.0.healthCareProvider1.patient0.Subjecttype_cd : CS1.0.observationOrder1.subject0.1.0.subjectOf1.patient0.Message structure from RMIM123489105672022-4-3058Information M

47、odel MappingNestingRelationshipNameCardinality/Rep Allowed?Optional?Data TypeRow NumberNestingStructureSegment Slot Type/ Tag ValueShared Type?Slot NameSlotData Field Domain Spec.NoteConditional PresenceRequired ValueInclusionRepetitionsNote1rootPatient_encounter111ENCENC1M1encounter_classification_

48、cdnyCE2encounter_classification_cd112M1end_dttmnyVTS3end_dttm2M1expected_insurance_plan_qtynyNM 4expected_insurance_plan_qty3M1first_similar_illness_dtnyVTS5first_similar_illness_dt4M1patient_classification_cdnyCE6patient_classification_cd513M1start_dttmnyVTS7start_dttm6M1status_cdnyCE8status_cd722M

49、191ChoiceIPChoiceM110TagN22specializationnone1112TagI22specializationInpatient_encounter1132IPEIPE1M13is_preceded_byPatient_admission1162PADMPADM2M124End Choice2involvesPatient1251PTPPTP3M13is_a_role_ofPerson Pt132generalizeStakeholder42is_assignedStakeholder_identifier443has_a_primary_ provider Ind

50、ividual_HC_provider Prim care phys0,1461PCPPCP4M0,14is_a_role_of Person Prim care phys147531ListListPTBAAccountList5R0,M3hasPatient_billing_account0,M542PTBAPTBA1M159End List601ListListEPEncPracList6M61GroupEncPracEncPracObject ViewObject Views and AttributesSegmentAttribSegment or Data FieldMessage

51、 ElementsMessage Structure A01Union U1Hierarchical Message DescriptionInformation Model MappingMessageStructureMessage ElementsTies every element of a message directly to a class, attribute or association in the Reference Information ModelProvides the message profile specifications for the data elem

52、ents in the messageEquivalent to populating a V2.x Abstract Message Definition with each of the relevant Segment tablesAND thenadding the message profile specification for which segments to use and/or repeat, and which code domains to use. 2022-4-3059How do models to messages?HL7-ConformantApplicati

53、onHL7-ConformantApplicationDataHL7MessageCreationHL7MessageParsingDataMessageInstanceITSImplementationTechnology SpecificationsHierarchicalMessageDefinitionDiscontinuepharmacy orderSend as ASCIIstring in XMLformat2022-4-3060Our example schema2022-4-3061Implementation Technology Specification V3 goal

54、 is to support different ITS layers Character based interfaces: ER7 XML Object Broker Technology CORBA Active-X/DCOM Others EDIFACT is a possibility2022-4-3062 HL7 HL7概况概况 HL7 V2.X HL7 V2.X HL7 V3.0HL7 V3.0 HL7HL7在在PHINPHIN的应用的应用主 要 内 容2022-4-3063 Cases, contacts and exposure groups Laboratory order

55、s and results Syndromic and health indicator data Interventions Environmental data Spatial data Health alerts Recommendations PHIN的功能2022-4-3064Clinical Case Detection and ResponseState and LocalPublic HealthDepartmentsCenters ForDisease Controland Prevention(CDC)PersonPublic Health LabClinical Site

56、HospitalClinicPositive result returned to clinical site and forwarded to state and CDCSpecimen sent to Laboratory Response Network lab for confirmationCase data sent to State Health Dept. and forwarded to CDC with request for assistanceLaw enforcementLaw enforcement notifiedPatient presents with Ant

57、hrax symptoms at clinical siteFederal response entitiesFederal response entities notifiedResponse teams identify source of exposureField Investigation TeamEnvironmental specimens sent to lab with report back to field team and stateField team reports findings back to state or local health dept. and C

58、DCExposed individuals identified2022-4-3065PHINFood SafetyUSDA, FDAClinical SectorLabs, Care deliveryLaw EnforcementFBI, LocalLaboratory ResponseUSDA, FDA, DOD, Public Health LabsSurveillanceCDC, State HD,Local HDResponseCDC, State HD,Local HD,Federal AgenciesPHIN与其他系统的关系2022-4-3066 Detection and Mo

59、nitoring Syndromic surveillance Health Indicators Existing surveillance for specific agents Laboratory Response Network (LRN)PHIN的功能2022-4-3067 Response Outbreak management systemsDynamic information requirementsConfigurableIntegrate with existing activities Laboratory Response Network Clinical care

60、 dataPHIN的功能2022-4-3068HL7在在PHIN的应用的应用Class: PublicHealthCase (CASE)A public health case is an Observation representing a condition or event that has a specific significance for public health. It involves an instance or instances of a reportable infectious disease or other condition. 2022-4-3069Clas