You should: Sign up > Write articles > tell people about your articles > Monetize them > Earn money  > learn/do/earn more

2020 coronavirus pandemic in South Korea

From Wikiafripedia, the free afripedia (encyclopedia)
Jump to navigation Jump to search

2020 coronavirus pandemic in South Korea
COVID-19 Outbreak Cases in South Korea (Density).svg
Map of special cities & municipals with confirmed or suspected coronavirus cases (as of 13 April):
  Confirmed 1–9
  Confirmed 10–99
  Confirmed 100–499
  Confirmed 500–999
  Confirmed 1000–9999
  Confirmed ≥10000
Coronavirus Outbreak in South Korea over Time.gif
Coronavirus pandemic in South Korea over time (since January 20, 2020).
 
  Number of cases (logarithmically)
  Day not included in map
  Day included in map
  Last day included in map
DiseaseCOVID-19
Virus strainSARS-CoV-2
LocationSouth Korea
First caseIncheon International Airport
Arrival date20 January 2020
(9 months and 5 days)
OriginWuhan, Hubei, China
Confirmed cases10,537
Suspected cases13,391
Recovered7,447
Deaths
217
Official website
ncov.mohw.go.kr/en
Suspected cases have not been confirmed as being due to this strain by laboratory tests, although some other strains may have been ruled out.

The first confirmed case of the pandemic of coronavirus disease 2019 (COVID-19) in South Korea was announced on 20 January 2020.[1] The number of confirmed cases increased on 19 February by 20, and on 20 February by 58[2] or 70,[3] giving a total of 346 confirmed cases on 21 February 2020, according to the Centers for Disease Control and Prevention Korea (KCDC), with the sudden jump mostly attributed to "Patient 31" who participated in a gathering at a Shincheonji Church of Jesus the Temple of the Tabernacle of the Testimony church in Daegu.[3][4]

Amidst the fears of further contamination, mass gatherings in the affected cities were cancelled and a few hundred soldiers in Daegu are in isolation.[5][6] As of 4 February 2020, in order to help prevent the spread of COVID-19, South Korea is denying entry to foreigners traveling from Hubei Province.[7][8]

As of 9 April 2020, South Korea has about 10,423 cases and 204 deaths,[9] with over 494,711 people having been tested, a case fatality rate of 1.95%, which is lower than the WHO's global case fatality rate of 4.34%.[10]

South Korea introduced what was considered one of the largest and best-organised epidemic control programs in the world, along with Taiwan,[11] Vietnam,[12] and Singapore.[13] Different measures have been taken to screen the mass population for the virus, and isolate any infected people as well as trace and quarantine those who contacted them, without further lockdown.[14][15] The rapid and extensive tests taken by South Korea has been judged successful in limiting the spread of the outbreak despite not using the drastic measure of quarantining entire cities.[14][16][17]

In middle of March, South Korea successfully contained the Shincheonji cluster. However, excluding the Shincheonji cluster, the spreading trend has not diminished.[18]

Timeline[edit source | edit]

Map of special cities & municipals with confirmed or suspected coronavirus cases (as of 13 April):
  Confirmed cases reported
  Suspected cases reported
  14 days no confirmed cases
Confirmed cases per million residents by province or city
Number of confirmed coronavirus cases by provinces & special cities.

During the first four weeks, South Korea controlled the potential spread of COVID-19 by using high-tech resources like tracking the use of credit cards and checking CCTV footage of confirmed patients. However, since 18 February, the number of cases increased to more than 1,700 after discovery of the fact that patient No. 31 was a member of the Shincheonji Church of Jesus. Some media reported that was difficult for KCDC to screen the patient because Shincheonji teaches that illness is sin. Many members were uncooperative with KCDC and could not be contacted.[19] Shincheonji denied this, and other sources report that the sect did cooperate with the authorities.[20] About half of confirmed cases were linked to the Shincheonji Church as of 27 February; this was verified by health officials.[21] As of 10 March, the KCDC was able to contact and test most of the Shincheonji Church members, with the total number of tests nationally standing at around 200,000.[citation needed]

20 January – 17 February[edit source | edit]

Shincheonji Daegu Church
File:0222 코로나19 예방수칙 포스터 영문.jpg
Recommendations for preventing COVID-19 released by KCDC under the Ministry of Health and Welfare of South Korea.

On 20 January, the first confirmed case was identified as a 35-year-old Chinese woman. The first South Korean national to be infected occurred three days later was a 55-year-old man who worked in Wuhan and returned for a checkup with flu symptoms. The two infection reports were publicly released on 24 January.[1]

On 26 January, a third case as a 54-year-old South Korean man. He had used a rental car and visited three restaurants, a hotel, a convenience store and met his family before admitting himself to hospital. All these places were disinfected.[citation needed]

On 27 January, a fourth case was reported as a 55-year-old South Korean man who returned from Wuhan on 20 January. He first experienced flu symptoms on 21 January and suffered further complications four days later, eventually turning himself in. Both cases were tallied into formal records on 27 January.[22]

On 1 February, an update on the first four patients indicated that the first three patients were showing weaker symptoms and recovering well while the fourth patient was getting treatment from pneumonia. Rumours circulated that the fourth patient had died which health authorities denied.[23]

Two more confirmed cases were reported on 30 January with the fifth patient being a 32-year-old South Korean man who returned from his work at Wuhan on 24 January. The sixth patient was the first case in South Korea who had never visited Wuhan. The 56-year-old man caught the virus when visiting a restaurant with the third patient.[24]

On 31 January, a seventh patient was reported as a 28-year-old South Korean man returning from Wuhan on 23 January. He developed symptoms on 26 January, and was admitted to the hospital on 28 January.[25] On the same day, four more patients were admitted into the record as the eighth patient, 62-year-old South Korean woman, returned from Wuhan. The ninth patient caught the virus from the fifth patient through direct contact while the tenth and the eleventh patient were the wife and child who were infected while visiting the sixth patient.[26]

On 1 February, a 49-year-old Chinese national working in Japan as a tour guide was confirmed as the twelfth patient. He caught the virus while visiting a Japanese patient in Japan and entered South Korea through Gimpo International Airport on 19 January.[23] The KCDC confirmed an additional three cases on 2 February, bringing the total to fifteen.[27]

A woman, who had returned from Thailand after a five-day vacation, was tested positive and confirmed as the sixteenth case on 4 February.[28] Three more cases were confirmed on 5 February, bringing the total case count to 19. The seventeenth and nineteenth patients had attended a conference in Singapore and been in contact with an infected individual there.[29] The very same day the KCDC announced that the second patient had been released from hospital after being tested negative in consecutive tests, becoming the country's first coronavirus patient to fully recover.[30]

Details of the first 30 confirmed cases in South Korea (As of 17 February 2020)
Case Date Age Gender Nationality Place of stay Hospital of admission Visited Wuhan? Entry date Status Contacts of case Note Source
1 20 January 2020 35 Female Chinese Incheon Incheon Metropolitan City Medical Center, Incheon Yes 19 January 2020 Discharged (6 February 2020) 45 [31][32]
2 24 January 2020 55 Male Korean Seoul National Medical Center, Seoul Yes 22 January 2020 Discharged (5 February 2020) 75 [31][32]
3 26 January 2020 54 Male Korean Goyang Myongji Hospital, Goyang Yes 20 January 2020 Discharged (12 February 2020) 16 [31][32]
4 27 January 2020 55 Male Korean Pyeongtaek Seoul National University Bundang Hospital, Seongnam Yes 20 January 2020 Discharged (9 February 2020) 95 [31][32]
5 30 January 2020 33 Male Korean Seoul Seoul Metropolitan City Seoul Medical Center, Seoul Yes 24 January 2020 Discharged (March 2020) 31 [31][32]
6 30 January 2020 55 Male Korean Seoul Seoul National University Hospital, Seoul No (Infection in Domestic) Discharged (19 February 2020) 17 Friend of case 3 [31][32]
7 30 January 2020 28 Male Korean Seoul Seoul Metropolitan City Seoul Medical Center, Seoul Yes 23 January 2020 Discharged (15 February 2020) 9 [31][32]
8 31 January 2020 62 Female Korean Gunsan Wonkwang University Hospital, Iksan Yes 23 January 2020 Discharged (12 February 2020) 113 [31][32]
9 31 January 2020 28 Female Korean Seoul Seoul Metropolitan City Seoul Medical Center, Seoul No (Infection in Domestic) Discharged (24 February 2020) 2 Friend of case 5 [31][32]
10 31 January 2020 54 Female Korean Seoul Seoul National University Hospital, Seoul No (Infection in Domestic) Discharged (19 February 2020) 43 Wife of case 6 [31][32]
11 31 January 2020 25 Male Korean Seoul Seoul National University Hospital, Seoul No (Infection in Domestic) Discharged (10 February 2020) 43 Son of case 6 [31][32]
12 1 February 2020 48 Male Chinese Bucheon Seoul National University Bundang Hospital, Seongnam No 19 January 2020 (Japan) Discharged (18 February 2020) 422 Related to Japanese confirmed case [31][32]
13 2 February 2020 28 Male Korean Asan National Medical Center, Seoul Yes 31 January 2020 Discharged (24 February 2020) 0 Passenger on board the evacuation flights from Wuhan [31][32]
14 2 February 2020 40 Female Chinese Bucheon Seoul National University Bundang Hospital, Seongnam No (Infection in Domestic) Discharged (18 February 2020) 3 Wife of case 12 [31][32]
15 2 February 2020 43 Male Korean Suwon Korean Armed Forces Capital Hospital, Seongnam Yes 20 January 2020 Discharged (24 February 2020) 15 [31][32]
16 4 February 2020 42 Female Korean Gwangju Chonnam National University Hospital, Gwangju No 19 January 2020 (Thailand) Discharged (19 February 2020) 450 [31][32]
17 5 February 2020 37 Male Korean Guri Myongji Hospital, Goyang No 24 January 2020 (Singapore) Discharged (12 February 2020) 290 Related to cases at Grand Hyatt Singapore [31][32]
18 5 February 2020 20 Female Korean Gwangju Chonnam National University Hospital, Gwangju No 19 January 2020 (Thailand) Discharged (19 February 2020) 8 Daughter of case 16 [31][32]
19 5 February 2020 36 Male Korean Seoul Seoul Metropolitan City Seoul Medical Center, Seoul No 23 January 2020 (Singapore) Discharged (21 February 2020) 68 Related to cases at Grand Hyatt Singapore [31][32]
20 5 February 2020 41 Female Korean Suwon Korean Armed Forces Capital Hospital, Seongnam No (Infection in Domestic) Discharged (24 February 2020) 2 Sister-in-law of case 15 [31][32]
21 5 February 2020 59 Female Korean Seoul Seoul National University Hospital, Seoul No (Infection in Domestic) Discharged (29 February 2020) 6 Friend of case 6 [31][32]
22 6 February 2020 46 Male Korean Naju Chosun University Hospital, Gwangju No (Infection in Domestic) Discharged (15 February 2020) 1 Brother of case 16 [31][32]
23 6 February 2020 57 Female Chinese Seoul National Medical Center, Seoul Yes 23 January 2020 Discharged (29 February 2020) 23 [31][32]
24 6 February 2020 28 Male Korean Asan National Medical Center, Seoul Yes 31 January 2020 Discharged (27 February 2020) 0 Passenger on board the evacuation flights from Wuhan [31][32]
25 9 February 2020 73 Female Korean Siheung Seoul National University Bundang Hospital, Seongnam No (Infection in Domestic) Discharged (5 March 2020) 12 Mother of case 26 [31][32]
26 9 February 2020 51 Male Korean Siheung Gyeonggi Provincial Medical Center Anseong Hospital, Anseong No 31 January 2020 (Guangdong) Discharged (8 March 2020) 12 [31][32]
27 9 February 2020 37 Female Chinese Siheung Gyeonggi Provincial Medical Center Anseong Hospital, Anseong No 31 January 2020 (Guangdong) Discharged (7 March 2020) 38 Wife of case 26 [31][32]
28 10 February 2020 30 Female Chinese Goyang Myongji Hospital, Goyang Yes 20 January 2020 Discharged (17 February 2020) 1 Friend of case 3 [31][32]
29 16 February 2020 82 Male Korean Seoul Seoul National University Hospital, Seoul No (Infection in Domestic) Discharged (March 2020) 117 Friend of case 83 [31][32]
30 16 February 2020 68 Female Korean Seoul Seoul National University Hospital, Seoul No (Infection in Domestic) Discharged (March 2020) 27 Wife of case 29 [31][32]

18 February – 29 February[edit source | edit]

Epidemic curve of COVID-19 in South Korea

On 18 February, South Korea confirmed its 31st case in Daegu, a member of the Shincheonji religious organisation. The patient continued to go to gatherings of Shincheonji days after showing symptoms, which are typically held with people in very close proximity and include physical contact of the members. Many of the patient's close contacts would turn out to be infected, triggering a drastic escalation of the South Korean spread of confirmed cases of SARS-CoV-2 infection.[33][19]

On 19 February, the number of confirmed cases increased by 20. On 20 February 70[3] new cases were confirmed, giving a total of 104 confirmed cases, according to the KCDC. According to Reuters, KCDC attributed the sudden jump of 70 cases linked to "Patient No. 31", who had participated in a gathering in Daegu at the Shincheonji Church of Jesus the Temple of the Tabernacle of the Testimony.[3]

On 20 February, the streets of Daegu were empty in reaction to the Shincheonji outbreak. A resident described the reaction, stating "It's like someone dropped a bomb in the middle of the city. It looks like a zombie apocalypse."[3] The first death was reported[34] in a mental ward of Cheongdo Daenam Hospital in Cheongdo County. According to the mayor of Daegu, the number of suspected cases as of 21 February was 544 among 4,400 examined followers of the church.[35] The hospital was suspected as the source of the present outbreak after it was visited by a woman who became the second fatal case of South Korea on that day. Upon investigation, it was determined that the infection had spread to that hospital through a funeral ceremony attended by members of the church.[36][37]

All South Korean military bases were on lockdown after tests confirmed three soldiers to be positive for the virus.[36] Airlines cut connections and cultural schedules were being canceled due to fears of further spread.[38][39] United States Forces Korea raised the alert level from low to moderate and cut off non-essential travel to and from USFK Daegu.[40] USFK Daegu's school facilities were closed and non-essential personnel were ordered to stay at home while any visitors going there were not allowed to enter.[40] USFK announced that the widow of a retired soldier who was in Daegu was diagnosed to be positive for the virus on 24 February.[41] Camp Humphreys enacted virus detection protocols, including temperature checks and raised the alert level to high.[42] On 26 February, an American soldier based at Camp Carroll was diagnosed to be positive and was quarantined away from bases via off-base housing unit[43] with contact tracing done that showed his movements to Camp Walker.[44]

As of 22 February, among 9,336 followers of the church, 1,261 reported symptoms.[45] At the time, 169 confirmed cases involved the same church and another 111 came from the Cheongdo Daenam Hospital.[46] 23 February saw another 123 cases with 75 being from Shincheonji[47] and 24 February saw 161 additional cases with 129 being from the same religious group. Over 27,000 people have been tested for the virus with 19,127 negative results.[48]

On 24 February, 15 countries imposed travel restrictions to and from South Korea.[49] It was also reported that a senior health official overseeing the COVID-19 efforts in Daegu tested positive and was also a member of Shincheonji.[50][51] Within a few days, a petition to the nation's president urging for the disbandment of the church had over 750,000 signatures. Their headquarters in Gwacheon was raided by law enforcement and government officials said all 245,000 members of the religious group would be found and tested.[51]

On 28 February, over 2,000 confirmed cases were reported.[52]

March[edit source | edit]

On 2 March, there were over 4,200 confirmed cases.[53] With an additional 4,000 cases of COVID-19 within two weeks, and roughly 60% of the total infections nationwide having stemmed from the church, the Seoul city government asked prosecutors to press charges against the religious group's founder and senior members for murder, causing harm, and for violating the Infectious Disease and Control Act.[54] Interviews have occurred with all 230,000 members of the religious group and nearly 9,000 were said to be showing symptoms of the virus.[55] Due to the number of infections in the country, ninety-five countries have banned or limited entry for South Korean passport holders.[56] Testing is also conducted at drive-through testing sites where patients do not leave their vehicles, but are met by medical personnel in hazmat suits over several stations. The process is completed in a few minutes and results come in several days.[57] On 8 March, KCDC in South Korea announced that 79.4% of confirmed COVID-19 cases were related to group infection. KCDC also announced that outbreak associated with Shincheonji Church totaled 4,482 infections, accounting for 62.8% of the total confirmed cases.[58][59]

13 March was the first time since the outbreak on 20 January in which the number of recoveries, 177, was larger than the number of those who newly tested positive, 110.[60][61][62] However, with the recent cluster of cases in the Seoul Capital Area, there are new fears that infections may rise sharply.[63]

The controversy about Shincheonji also continued, and generated international interest. After the lawsuit started by the Mayor of Seoul, the police raided the church premises to check whether the list of members supplied by Shincheonji pursuant to a request by the authorities was, as the Mayor argued, not complete. The authorities checked the list seized during the raid with the one Shincheonji had supplied, and concluded that discrepancies were minor.[64]

The United States Commission on International Religious Freedom (USCIRF) expressed concern that religious freedom rights of Shincheonji members may be violated in South Korea by "exaggerating the church's role in the outbreak," and stated that, "USCIRF has received reports of individuals encountering discrimination at work and spousal abuse because of their affiliation with the church."[65] USCIRF reported that South Korean "Vice Minister of Health Kim Kang-lip has publicly stated that the Shincheonji church has cooperated with authorities."[65] The Belgian NGO Human Rights Without Frontiers and CESNUR released a "White Paper" claiming that, although it did make "mistakes" in its management of the crisis, Shincheonji had also been discriminated because of its status as an unpopular group in South Korea.[66][67]

On 17 March, around 79 church devotees were infected with the virus after attending the River of Grace Community Church. The infections were claimed to have been caused by spraying salt-water into followers' mouths, under the belief that this would protect them from the virus.[68][69] Nearly 140 churches in Gyeonggi Province, which surrounds Seoul and is part of the Greater Seoul Area, will be closed if they do not implement preventative measures, including temperature checks, two-meter separation, and the wearing of masks.[70] As more churches are holding services despite a government order for social distancing, on 30 March, the controversial Manmin Central Church in Guro, Seoul became a cluster with 22 infections linked to a gathering in early March in which the group was preparing stock footage to use for online worship services. Other church clusters have appears in the cities of Suwon, Busan, Geochang, and Bucheon.[71]

April – present outbreak[edit source | edit]

As infection rates have risen outside Korea leading to increases of sick arriving in the country (476 of 9,661 cases were imported as of 30 March), the KCDC will be implanting stronger infectious disease control measures for travelers coming from overseas as of 1 April. Additionally, new self-quarantine measures for travelers coming from Europe or the United States will be in effect from the same day. For example, those showing symptoms but test negative, and those who are without symptoms and are staying short-term in Korea, need to quarantine for two weeks in a government provided facility.[72] Costs for the stay at the facility are the responsibility of the individual and total 100,000 won (US$81) per day.[73] Afew days later, a Taiwanese woman was deported on 5 April for refusing to stay in a quarantine facility as she initially agreed and then later disagreed with paying for the cost of staying at the government designated facility, reportedly costing around 100,000 won per day.[74]

45 people are being investigated by the police for allegedly violating COVID-19 self-isolation. Under the revised anti-infectious disease law, violators can face up to a year in prison, a 10 million won fine, or in the case of foreign passport holders—deportation.[75]

Seeing the infodemic on COVID-19 information starting in China and spreading to Korea and the US, fake news researcher Cha Meeyoung of KAIST and the Institute for Basic Science, along with researchers from Ewha Womans University, started the multilingual Facts Before Rumors campaign to separate common claims seen online.[76][77][78][79]

A Canadian cast member with the touring The Phantom of the Opera stage play entered Korea on March 12, participated for roughly two weeks, and tested positive 2 April. An American colleague tested positive on 4 April, which shut down production of the musical until 14 April while the venue could be disinfected and contacts of the staff, those staying in the same hotel, and over 8,000 people who recently attended were contacted by health authorities who told them to stay indoors and contact a testing center if they develop symptoms.[80]

Statistics[edit source | edit]

Template:2019–20 coronavirus pandemic data/South Korea medical cases chart

Number of cases (blue) and number of deaths (red) on a logarithmic scale.

Template:2019–20 coronavirus pandemic data/South Korea medical cases

Containment[edit source | edit]

In its efforts to fight and contain the virus, South Korea has combined testing with contact tracing.[citation needed]

Infected South Koreans are required to go into isolation in government shelters. Their phones and credit card data are used to trace their prior movements and find their contacts. Those who are determined to have been near the infected individual receive phone alerts with information about their prior movements.[81]

According to Chun Byung-Chul, an epidemiologist at Korea University, high-risk patients who have underlying illnesses are prioritized for hospitalization. Patients with moderate symptoms are sent to "repurposed corporate training facilities and spaces provided by public institutions," where they receive observation and medical support. Patients who recover and test negative twice are released. Close contacts and infected individuals with minimal symptoms who can measure their own temperatures and whose family members are free of any chronic disease are required to self-quarantine for two weeks. Local monitoring teams calls the quarantined twice a day to make sure that they stay where they are and to ask about symptoms.[82]

Preventive measures[edit source | edit]

Those ordered to self-quarantine are required to download an app that alerts officials if the patient moves outside of the quarantine. Violators are fined up to $2,500.[83]

Impacts and reactions[edit source | edit]

At the drive-through test center the medical staff examines patients with suspected COVID-19 while in the vehicle.

The entire procedure of collecting a sample of secretions taking less than 10 minutes, and it's deployed to dozens of locations including Seoul,Daegu,Goyang, Incheon and Sejong.[84][85]

*Banner: Coronavirus-19 drive-thru screening clinic[86][87]
Sign in Daejeon pharmacy stating all masks are sold out
Line outside a pharmacy in Sejong City awaiting the store to open so they can buy masks

As of 18 March, South Korea's KOSPI stock index has dropped nearly 30% compared to a month ago. The drop precipitated on 23 February, when the country raised the coronavirus alert to 'highest level'.[88] As of 15 March, the KOSPI closed at 1,771.44 and the Kosdaq finished at 524 points, down 7%, prompting the Financial Supervisory Commission to impose a six-month ban on short-selling, the first such drastic action in nearly nine years. This was despite a markedly lower daily increase in cases. Automaker Hyundai Motor Company, having shut down its factories as the outbreak intensified, saw exports drop 21.4% in February from the same month last year.[89]

Social impact[edit source | edit]

Drive-through test center in Busan

As of 25 February, Daegu officials were aggressively warning residents to take precautions, while allowing private businesses such as restaurants to stay open. As a precautionary measure, many restaurants check the temperatures of their customers before accepting them. It is common for "offices, hotels, and other large buildings" to use thermal image cameras in order to identify people with fevers.[83] All Daegu's public libraries, museums, churches, day-care centers and courts had been closed.[90][needs update]

Apart from the city of Daegu and the church community involved, most of South Korea is operating close to normality, although nine planned festivals have been closed and tax-free retailers are closing.[91] The South Korean military manpower agency made an announcement that conscription from Daegu will temporarily be suspended.[92] The Daegu Office of Education decided to postpone the start of every school in the region by one week.[93]

Numerous educational institutes have temporarily shut down, including dozens of kindergartens in Daegu and several elementary schools in Seoul.[94] As of 18 February, most universities in South Korea had announced plans to postpone the start of the spring semester. This included 155 universities planning to delay the semester start by two weeks to 16 March, and 22 universities planning to delay the semester start by one week to 9 March.[95] Also, on 23 February 2020, all kindergartens, elementary schools, middle schools, and high schools were announced to delay the semester start from 2 to 9 March.[96][needs update]

The economy of South Korea is forecast to grow 1.9%, which is down from 2.1%. The government has provided 136.7 billion won for local governments as support.[91] The government has also organized the procurement of masks and other hygiene equipment.[91]

Entertainment agency SM Entertainment reportedly donated five hundred million won in efforts to fight the disease.[97][98][99]

In the K-POP industry, the rapid spread of the coronavirus within South Korea has led to the cancellations or postponing of concerts and other events for K-POP acts within and outside of South Korea, with example situations including the cancellation of the remaining Asia dates and the Europe leg for Seventeen’s Ode To You Tour on 9 February 2020 and the cancellation of all Seoul dates for BTS' Map of the Soul Tour.[100][101]

Travel restrictions[edit source | edit]

For further information, see Travel restrictions related to the 2019–2020 coronavirus pandemic
  South Korea
  Entrance refused to people from South Korea
  Entrance refused to people from some areas of South korea
  Imposed quarantine on people arriving from South Korea
  Other restrictions (self-quarantines, medical examination requirements, monitoring measures)

As of 20 March, a total of 171 countries and territories have issued entry bans and/or suspended visas for travelers from South Korea.[102]

On 16 March, USFK announced that travel restrictions for Cheonan city had been removed due to a decline in COVID-19 cases. Troops and Defense Department personnel residing in Cheonan were told to "contact their command prior to returning to work."[103]

Government reactions[edit source | edit]

Videotelephony of Central Disaster and Safety Countermeasure Headquarters

The number of inspections[edit source | edit]

The Blue House announced on 28 February the current status of coronavirus tests in Korea, comparing the testing situation in the United States and Japan. The number of inspections was 26 and 120 times higher than in those countries respectively as of 28 Feb. The cumulative number of inspections was about 53,000 by South Korea, while Japan was about 2,000, and in US about 440 cases were examined.[104]

Incorrect expression[edit source | edit]

On 20 February, one of the public reports by the South Korean government was titled "Pan-Governmental Special Aid Committee is assembled to handle Coronavirus 19 in Daegu" which can be also parsed as "...assembled to handle Daegu Coronavirus 19." After concerns were raised about potentially enabling discrimination, the government apologized on 22 February for using misleading expression and corrected the incorrect expression.[105]

Reactions from KMA[edit source | edit]

On 26 January, the Korean Medical Association (KMA) asked the government to temporarily bar entry to all travelers arriving from mainland China, but this recommendation was not followed.[106] On 27 January, KMA President Choi Dae-zip said: "The third confirmed case indicates that we have reached the point where we have to get rid of passive stance and actively prepare for the worsening of the situation, (and) the government should thoroughly monitor the trend of China's national outbreak of the virus and prepare administrative measures such as complete entry ban from China in case of the worst situation."[107] On 3 February, The KMA recommended halting all travel from China, rather than only from Hubei province.[108] After all, The KMA called for stronger government response in a total of six statements between 20 January, when the nation's first confirmed case occurred, and 18 February. A short time after that, cases spiked in Daegu and throughout the country.[109]

Public reactions[edit source | edit]

Presidential approval rating[edit source | edit]

Although there are many confirmed cases of COVID-19, President Moon Jae-in's approval rating rose by two percentage points to 44%. During the MERS crisis, the previous President Park Geun-hye's approval rating had fallen sharply to 29% due to inadequate management the MERS infection.[110]

In opinion poll conducted by Gallup Korea in the second week of March 2020, president Moon's approval rating has risen by 5% to 49%.[111]

Controversial petitions[edit source | edit]

There are two controversial petitions on the official Presidential Blue House website: one is for supporting President Moon for his handling of the coronavirus outbreak and another is for disapproval of President Moon's management of the coronavirus outbreak. The petitions of disapproval was completed by 1.46 million votes, and another petition of supporting President Moon reached more than 1.4 million votes, and it is planned to be completed by 27 March 2020.[112][113]

Anti-foreigner sentiment[edit source | edit]

In February 2020, an entrance to a South Korean restaurant in downtown Seoul reportedly had a sign in red Chinese characters stating: "No Chinese Allowed."[114] "No Chinese" signs have been cropping up throughout the country, and some businesses are simply banning all foreigners.[115] Some foreign residents have been excluded from the government mask distribution program as it is currently only allowed to 1.25 million foreigners who were subscribed to the public health insurance.[116] Concerning COVID-19, More than 760,000 South Korean citizens have signed a petition lobbying the government to ban Chinese tourists from entering the country.[117][118] The Daegu Lantern Festival mistakenly posted a notice in English that no foreigners are allowed to visit. However, the wrong sentence was removed and it was revealed a translation error by the PR agency regarding statement from a Daegu government official. The official in the Daegu city stated that the original message was the notification to foreign tourists about the delayed schedule of festival over COVID-19 concerns.[119] Jamaicans have reported widespread discrimination,[120] and foreigners were excluded from city wide stimulus funds, with the exception of Ansan city.[121] Supporters of Moon Jae In have been cyberbullied and accused of being "Chinese communists," while other writers have been accused of being Chinese.[122]

International response[edit source | edit]

On 24 February, the United States Centers for Disease Control and Prevention (CDC) upgraded the status of South Korea to level 3 (avoid non-essential travels due to widespread community transmission).[123]

On 28 February, Charles Schwab Corporation advised employees who had travelled to China and South Korea to self-quarantine for 14 days.[124] Multiple companies such as Amazon, Google, TD Bank Group, Bank of Nova Scotia, London Stock Exchange Group, and Cargill, Inc. deferred all non-essential travels to areas affected by the outbreak.[125]

As of 8 March, US military has suspended all travels to and from South Korea for all military personnel and their family over the concern of the virus.[126]

As of 10 March, 109 countries or regions restrict entry of visitors from South Korea.[127]

View of foreign media on COVID-19 in Korea[edit source | edit]

The Washington Post has praised the South Korean government's handling of coronavirus outbreak and stated that South Korea is a model for the U.S. response instead of Iran.[128] The Washington Post also appreciated South Korea's response as a successful model for democratic countries.[129]

Agence France-Presse has compared South Korea's handling of coronavirus outbreak with China. The newspaper stated that "While China locked down cities, Seoul embraced widespread testing and public notice of movements of those infected, raising some privacy concerns". Also, AFP analyzed that the South Korean government handled the crisis using a model of open information, public participation, and widespread testing.[130] Additionally, according to the paper, Masahiro Kami, a chairperson of the Tokyo-based Medical Governance Research Institute stated that South Korea is a good model for every country for handling the coronavirus outbreak.[131]

WSJ analyzed the aggressive Coronavirus Test Program in South Korea. The government contacted the citizens proactively to test the coronavirus in various ways including a home visit, a quick 10 minutes drop off drive-through COVID-19 testing center free of charge. Although South Korea not yet defeated the outbreak, experts credit the emphasis on energetic COVID-19 test program with reducing case numbers and fatalities.[132][133]

UPI has analyzed that South Korea's model has worked on handling coronavirus outbreak without any further harder restrictions on foreigners.[134] The paper also observed that Health authorities have aggressively promoted hygiene and social distancing.[135] Additionally, according to the paper Kim Jong-hwan, an administrator at Seoul Metropolitan Eunpyeong Hospital positively evaluated the government's deal with coronavirus outbreak by stating that "The government's response has been so well-organized. I'm proud of it."[136]

Time magazine and BBC News concluded that the reason for the high number of confirmed cases of the coronavirus in South Korea is thanks to the relative "openness" and "transparency" in the Korean society.[137] As for the rapid spread of the virus, the reason was the religious group Shincheonji Church.[138] The Blue House announced on 28 February the current status of coronavirus tests in three countries: Korea, the United States, and Japan, and analyzed statistically the reasons why there were so many confirmed cases in South Korea: the number of inspections was 26 or 120 times higher than other countries. The cumulative number of inspections was about 53,000 in South Korea, with only 2,000 in Japan and 440 cases examined in the United States. After the tests, the rate of confirmed cases was highest in Japan (9.04%), followed by Korea (3.3%) and the United States (3.15%).[104]

Bloomberg L.P. analyzed the reason for the low death rate in South Korea. South Korea experienced serious difficulties during the outbreak of MERS in 2015 due to a lack of test kits. Afterwards, the country approved rapid deployment of COVID-19 test kits, and now they are able to test more than 10,000 people a day. In neighboring Japan, only about 2,700 people in total have been tested for COVID-19 as of 3 March. Officials in Seoul operate "drive-thru" testing stations for quick testing. Diagnostics company Seegene Inc. is also exporting its test kits to other countries including China, Europe and the US.[139][140]

AFP attributed the factors behind the low death rate of South Korea to the rigorous testing and the infected population profile. South Korea's widespread testing leads mild or asymptomatic cases to be identified so the proportion of dying goes down. Moreover, the infected population in the South Korea has a unique profile. Most of the country's infections are linked to the Shincheonji Church of Jesus and most of its members are young women. Statistics show that the virus is most deadly among older generations and men. So the death rate in South Korea is lower than other countries.[141]

CNN reported the innovative drive-through testing for COVID-19 in the northern city of Goyang, which was inspired by the drive-through counters at Starbucks.[57] Reuters detailed the new testing facilities in South Korea. Several drive-through coronavirus screening centres were built, including roadside testing facilities. Their purpose is to diagnose patients quickly, while preventing the infection of others in, e.g., a hospital waiting room or a community health center. The entire testing procedure takes several minutes.[84] William Schaffner, a professor of preventive medicine and infectious diseases at Vanderbilt University School of Medicine, stressed the importance of the broad testing efforts in South Korea. It would provide us with an unclouded picture of the COVID-19 illness.[142] Victoria’s Chief Health Officer, Brett Sutton has recommended the drive-thru coronavirus testing in Australia.[143] On 10 March, Australia opened the first drive-through testing station in Adelaide.[144][144]

Business Insider analyzed the difference of coverage of patient testing patients for COVID-19, comparing the USA to South Korea. Per million citizens, South Korea tested 700 times more than the USA.[19] Fortune explained South Korea's efforts of setting up several "drive-thru" coronavirus screening facilities as contributing to testing thousands of samples a day.[145]

CNN had an interview with South Korea health minister Park Neung-hoo. Park expressed cautiously his desire that the coronavirus outbreak is 'passed the peak' as per the result regarding the number of new daily infections has declined in recent days.[146] The S. Korean government has the ability operate about 15,000 diagnostic test per day and has conducted over 190,000 tests by 10 March nationwide. Park also answered the inquiry from CNN about practicable tips for controlling COVID-19. Park believes that dealing with outbreaks by focusing efforts on early testing and global cooperation would be crucial instead of the lockdown option, as the virus could still spread quickly without testing.[146] S. Korean authorities have arranged the two types of facilities, one for about 10% of coronavirus patients who required hospitalization and another for the patients who were only suffering from mild symptoms.[146]

See also[edit source | edit]

Notes and references[edit source | edit]

  1. 1.0 1.1 Lua error in ...ribunto/includes/engines/LuaCommon/lualib/mwInit.lua at line 23: bad argument #1 to 'old_ipairs' (table expected, got nil).
  2. Lua error in ...ribunto/includes/engines/LuaCommon/lualib/mwInit.lua at line 23: bad argument #1 to 'old_ipairs' (table expected, got nil).
  3. 3.0 3.1 3.2 3.3 3.4 Lua error in ...ribunto/includes/engines/LuaCommon/lualib/mwInit.lua at line 23: bad argument #1 to 'old_ipairs' (table expected, got nil).
  4. Lua error in ...ribunto/includes/engines/LuaCommon/lualib/mwInit.lua at line 23: bad argument #1 to 'old_ipairs' (table expected, got nil).
  5. Lua error in ...ribunto/includes/engines/LuaCommon/lualib/mwInit.lua at line 23: bad argument #1 to 'old_ipairs' (table expected, got nil).
  6. Lua error in ...ribunto/includes/engines/LuaCommon/lualib/mwInit.lua at line 23: bad argument #1 to 'old_ipairs' (table expected, got nil).
  7. Lua error in ...ribunto/includes/engines/LuaCommon/lualib/mwInit.lua at line 23: bad argument #1 to 'old_ipairs' (table expected, got nil).
  8. Lua error in ...ribunto/includes/engines/LuaCommon/lualib/mwInit.lua at line 23: bad argument #1 to 'old_ipairs' (table expected, got nil).
  9. Lua error in ...ribunto/includes/engines/LuaCommon/lualib/mwInit.lua at line 23: bad argument #1 to 'old_ipairs' (table expected, got nil).
  10. Lua error in ...ribunto/includes/engines/LuaCommon/lualib/mwInit.lua at line 23: bad argument #1 to 'old_ipairs' (table expected, got nil).
  11. Lua error in ...ribunto/includes/engines/LuaCommon/lualib/mwInit.lua at line 23: bad argument #1 to 'old_ipairs' (table expected, got nil).
  12. Lua error in ...ribunto/includes/engines/LuaCommon/lualib/mwInit.lua at line 23: bad argument #1 to 'old_ipairs' (table expected, got nil).
  13. Lua error in ...ribunto/includes/engines/LuaCommon/lualib/mwInit.lua at line 23: bad argument #1 to 'old_ipairs' (table expected, got nil).
  14. 14.0 14.1 Lua error in ...ribunto/includes/engines/LuaCommon/lualib/mwInit.lua at line 23: bad argument #1 to 'old_ipairs' (table expected, got nil).
  15. Lua error in ...ribunto/includes/engines/LuaCommon/lualib/mwInit.lua at line 23: bad argument #1 to 'old_ipairs' (table expected, got nil).
  16. Lua error in ...ribunto/includes/engines/LuaCommon/lualib/mwInit.lua at line 23: bad argument #1 to 'old_ipairs' (table expected, got nil).
  17. Lua error in ...ribunto/includes/engines/LuaCommon/lualib/mwInit.lua at line 23: bad argument #1 to 'old_ipairs' (table expected, got nil).
  18. Lua error in ...ribunto/includes/engines/LuaCommon/lualib/mwInit.lua at line 23: bad argument #1 to 'old_ipairs' (table expected, got nil).
  19. 19.0 19.1 19.2 Lua error in ...ribunto/includes/engines/LuaCommon/lualib/mwInit.lua at line 23: bad argument #1 to 'old_ipairs' (table expected, got nil).
  20. Lua error in ...ribunto/includes/engines/LuaCommon/lualib/mwInit.lua at line 23: bad argument #1 to 'old_ipairs' (table expected, got nil).
  21. Lua error in ...ribunto/includes/engines/LuaCommon/lualib/mwInit.lua at line 23: bad argument #1 to 'old_ipairs' (table expected, got nil).
  22. Lua error in ...ribunto/includes/engines/LuaCommon/lualib/mwInit.lua at line 23: bad argument #1 to 'old_ipairs' (table expected, got nil).
  23. 23.0 23.1 Lua error in ...ribunto/includes/engines/LuaCommon/lualib/mwInit.lua at line 23: bad argument #1 to 'old_ipairs' (table expected, got nil).
  24. Lua error in ...ribunto/includes/engines/LuaCommon/lualib/mwInit.lua at line 23: bad argument #1 to 'old_ipairs' (table expected, got nil).
  25. Lua error in ...ribunto/includes/engines/LuaCommon/lualib/mwInit.lua at line 23: bad argument #1 to 'old_ipairs' (table expected, got nil).
  26. Lua error in ...ribunto/includes/engines/LuaCommon/lualib/mwInit.lua at line 23: bad argument #1 to 'old_ipairs' (table expected, got nil).
  27. Lua error in ...ribunto/includes/engines/LuaCommon/lualib/mwInit.lua at line 23: bad argument #1 to 'old_ipairs' (table expected, got nil).
  28. Lua error in ...ribunto/includes/engines/LuaCommon/lualib/mwInit.lua at line 23: bad argument #1 to 'old_ipairs' (table expected, got nil).
  29. Lua error in ...ribunto/includes/engines/LuaCommon/lualib/mwInit.lua at line 23: bad argument #1 to 'old_ipairs' (table expected, got nil).
  30. Lua error in ...ribunto/includes/engines/LuaCommon/lualib/mwInit.lua at line 23: bad argument #1 to 'old_ipairs' (table expected, got nil).
  31. 31.00 31.01 31.02 31.03 31.04 31.05 31.06 31.07 31.08 31.09 31.10 31.11 31.12 31.13 31.14 31.15 31.16 31.17 31.18 31.19 31.20 31.21 31.22 31.23 31.24 31.25 31.26 31.27 31.28 31.29 Cite error: The named reference YNA was invoked but never defined (see the help page).
  32. 32.00 32.01 32.02 32.03 32.04 32.05 32.06 32.07 32.08 32.09 32.10 32.11 32.12 32.13 32.14 32.15 32.16 32.17 32.18 32.19 32.20 32.21 32.22 32.23 32.24 32.25 32.26 32.27 32.28 32.29 Lua error in ...ribunto/includes/engines/LuaCommon/lualib/mwInit.lua at line 23: bad argument #1 to 'old_ipairs' (table expected, got nil).
  33. Lua error in ...ribunto/includes/engines/LuaCommon/lualib/mwInit.lua at line 23: bad argument #1 to 'old_ipairs' (table expected, got nil).
  34. Lua error in ...ribunto/includes/engines/LuaCommon/lualib/mwInit.lua at line 23: bad argument #1 to 'old_ipairs' (table expected, got nil).
  35. Lua error in ...ribunto/includes/engines/LuaCommon/lualib/mwInit.lua at line 23: bad argument #1 to 'old_ipairs' (table expected, got nil).
  36. 36.0 36.1 Lua error in ...ribunto/includes/engines/LuaCommon/lualib/mwInit.lua at line 23: bad argument #1 to 'old_ipairs' (table expected, got nil).
  37. Lua error in ...ribunto/includes/engines/LuaCommon/lualib/mwInit.lua at line 23: bad argument #1 to 'old_ipairs' (table expected, got nil).
  38. Lua error in ...ribunto/includes/engines/LuaCommon/lualib/mwInit.lua at line 23: bad argument #1 to 'old_ipairs' (table expected, got nil).
  39. Lua error in ...ribunto/includes/engines/LuaCommon/lualib/mwInit.lua at line 23: bad argument #1 to 'old_ipairs' (table expected, got nil).
  40. 40.0 40.1 Lua error in ...ribunto/includes/engines/LuaCommon/lualib/mwInit.lua at line 23: bad argument #1 to 'old_ipairs' (table expected, got nil).
  41. Lua error in ...ribunto/includes/engines/LuaCommon/lualib/mwInit.lua at line 23: bad argument #1 to 'old_ipairs' (table expected, got nil).
  42. Lua error in ...ribunto/includes/engines/LuaCommon/lualib/mwInit.lua at line 23: bad argument #1 to 'old_ipairs' (table expected, got nil).
  43. Lua error in ...ribunto/includes/engines/LuaCommon/lualib/mwInit.lua at line 23: bad argument #1 to 'old_ipairs' (table expected, got nil).
  44. Lua error in ...ribunto/includes/engines/LuaCommon/lualib/mwInit.lua at line 23: bad argument #1 to 'old_ipairs' (table expected, got nil).
  45. Lua error in ...ribunto/includes/engines/LuaCommon/lualib/mwInit.lua at line 23: bad argument #1 to 'old_ipairs' (table expected, got nil).
  46. Lua error in ...ribunto/includes/engines/LuaCommon/lualib/mwInit.lua at line 23: bad argument #1 to 'old_ipairs' (table expected, got nil).
  47. Lua error in ...ribunto/includes/engines/LuaCommon/lualib/mwInit.lua at line 23: bad argument #1 to 'old_ipairs' (table expected, got nil).
  48. Lua error in ...ribunto/includes/engines/LuaCommon/lualib/mwInit.lua at line 23: bad argument #1 to 'old_ipairs' (table expected, got nil).
  49. Lua error in ...ribunto/includes/engines/LuaCommon/lualib/mwInit.lua at line 23: bad argument #1 to 'old_ipairs' (table expected, got nil).
  50. Lua error in ...ribunto/includes/engines/LuaCommon/lualib/mwInit.lua at line 23: bad argument #1 to 'old_ipairs' (table expected, got nil).
  51. 51.0 51.1 Lua error in ...ribunto/includes/engines/LuaCommon/lualib/mwInit.lua at line 23: bad argument #1 to 'old_ipairs' (table expected, got nil).
  52. Lua error in ...ribunto/includes/engines/LuaCommon/lualib/mwInit.lua at line 23: bad argument #1 to 'old_ipairs' (table expected, got nil).
  53. Lua error in ...ribunto/includes/engines/LuaCommon/lualib/mwInit.lua at line 23: bad argument #1 to 'old_ipairs' (table expected, got nil).
  54. Lua error in ...ribunto/includes/engines/LuaCommon/lualib/mwInit.lua at line 23: bad argument #1 to 'old_ipairs' (table expected, got nil).
  55. Lua error in ...ribunto/includes/engines/LuaCommon/lualib/mwInit.lua at line 23: bad argument #1 to 'old_ipairs' (table expected, got nil).
  56. Lua error in ...ribunto/includes/engines/LuaCommon/lualib/mwInit.lua at line 23: bad argument #1 to 'old_ipairs' (table expected, got nil).
  57. 57.0 57.1 Lua error in ...ribunto/includes/engines/LuaCommon/lualib/mwInit.lua at line 23: bad argument #1 to 'old_ipairs' (table expected, got nil).
  58. Lua error in ...ribunto/includes/engines/LuaCommon/lualib/mwInit.lua at line 23: bad argument #1 to 'old_ipairs' (table expected, got nil).
  59. Lua error in ...ribunto/includes/engines/LuaCommon/lualib/mwInit.lua at line 23: bad argument #1 to 'old_ipairs' (table expected, got nil).
  60. Lua error in ...ribunto/includes/engines/LuaCommon/lualib/mwInit.lua at line 23: bad argument #1 to 'old_ipairs' (table expected, got nil).
  61. Lua error in ...ribunto/includes/engines/LuaCommon/lualib/mwInit.lua at line 23: bad argument #1 to 'old_ipairs' (table expected, got nil).
  62. Lua error in ...ribunto/includes/engines/LuaCommon/lualib/mwInit.lua at line 23: bad argument #1 to 'old_ipairs' (table expected, got nil).
  63. Lua error in ...ribunto/includes/engines/LuaCommon/lualib/mwInit.lua at line 23: bad argument #1 to 'old_ipairs' (table expected, got nil).
  64. Lua error in ...ribunto/includes/engines/LuaCommon/lualib/mwInit.lua at line 23: bad argument #1 to 'old_ipairs' (table expected, got nil).
  65. 65.0 65.1 Lua error in ...ribunto/includes/engines/LuaCommon/lualib/mwInit.lua at line 23: bad argument #1 to 'old_ipairs' (table expected, got nil).
  66. Lua error in ...ribunto/includes/engines/LuaCommon/lualib/mwInit.lua at line 23: bad argument #1 to 'old_ipairs' (table expected, got nil).
  67. Lua error in ...ribunto/includes/engines/LuaCommon/lualib/mwInit.lua at line 23: bad argument #1 to 'old_ipairs' (table expected, got nil).
  68. Lua error in ...ribunto/includes/engines/LuaCommon/lualib/mwInit.lua at line 23: bad argument #1 to 'old_ipairs' (table expected, got nil).
  69. Lua error in ...ribunto/includes/engines/LuaCommon/lualib/mwInit.lua at line 23: bad argument #1 to 'old_ipairs' (table expected, got nil).
  70. Lua error in ...ribunto/includes/engines/LuaCommon/lualib/mwInit.lua at line 23: bad argument #1 to 'old_ipairs' (table expected, got nil).
  71. Lua error in ...ribunto/includes/engines/LuaCommon/lualib/mwInit.lua at line 23: bad argument #1 to 'old_ipairs' (table expected, got nil).
  72. Lua error in ...ribunto/includes/engines/LuaCommon/lualib/mwInit.lua at line 23: bad argument #1 to 'old_ipairs' (table expected, got nil).
  73. Lua error in ...ribunto/includes/engines/LuaCommon/lualib/mwInit.lua at line 23: bad argument #1 to 'old_ipairs' (table expected, got nil).
  74. Lua error in ...ribunto/includes/engines/LuaCommon/lualib/mwInit.lua at line 23: bad argument #1 to 'old_ipairs' (table expected, got nil).
  75. Lua error in ...ribunto/includes/engines/LuaCommon/lualib/mwInit.lua at line 23: bad argument #1 to 'old_ipairs' (table expected, got nil).
  76. Lua error in ...ribunto/includes/engines/LuaCommon/lualib/mwInit.lua at line 23: bad argument #1 to 'old_ipairs' (table expected, got nil).
  77. Lua error in ...ribunto/includes/engines/LuaCommon/lualib/mwInit.lua at line 23: bad argument #1 to 'old_ipairs' (table expected, got nil).
  78. Lua error in ...ribunto/includes/engines/LuaCommon/lualib/mwInit.lua at line 23: bad argument #1 to 'old_ipairs' (table expected, got nil).
  79. Lua error in ...ribunto/includes/engines/LuaCommon/lualib/mwInit.lua at line 23: bad argument #1 to 'old_ipairs' (table expected, got nil).
  80. Lua error in ...ribunto/includes/engines/LuaCommon/lualib/mwInit.lua at line 23: bad argument #1 to 'old_ipairs' (table expected, got nil).
  81. Lua error in ...ribunto/includes/engines/LuaCommon/lualib/mwInit.lua at line 23: bad argument #1 to 'old_ipairs' (table expected, got nil).
  82. Lua error in ...ribunto/includes/engines/LuaCommon/lualib/mwInit.lua at line 23: bad argument #1 to 'old_ipairs' (table expected, got nil).
  83. 83.0 83.1 Lua error in ...ribunto/includes/engines/LuaCommon/lualib/mwInit.lua at line 23: bad argument #1 to 'old_ipairs' (table expected, got nil).
  84. 84.0 84.1 Lua error in ...ribunto/includes/engines/LuaCommon/lualib/mwInit.lua at line 23: bad argument #1 to 'old_ipairs' (table expected, got nil).
  85. Coronavirus in South Korea: How 'trace, test and treat' may be saving lives Archived 12 March 2020 at the Wayback Machine
  86. Lua error in ...ribunto/includes/engines/LuaCommon/lualib/mwInit.lua at line 23: bad argument #1 to 'old_ipairs' (table expected, got nil).
  87. South Korea has 'passed the peak' of the coronavirus outbreak, health minister hopes Archived 10 March 2020 at the Wayback Machine
  88. Lua error in ...ribunto/includes/engines/LuaCommon/lualib/mwInit.lua at line 23: bad argument #1 to 'old_ipairs' (table expected, got nil).
  89. Lua error in ...ribunto/includes/engines/LuaCommon/lualib/mwInit.lua at line 23: bad argument #1 to 'old_ipairs' (table expected, got nil).
  90. Lua error in ...ribunto/includes/engines/LuaCommon/lualib/mwInit.lua at line 23: bad argument #1 to 'old_ipairs' (table expected, got nil).
  91. 91.0 91.1 91.2 Lua error in ...ribunto/includes/engines/LuaCommon/lualib/mwInit.lua at line 23: bad argument #1 to 'old_ipairs' (table expected, got nil).
  92. Lua error in ...ribunto/includes/engines/LuaCommon/lualib/mwInit.lua at line 23: bad argument #1 to 'old_ipairs' (table expected, got nil).
  93. Lua error in ...ribunto/includes/engines/LuaCommon/lualib/mwInit.lua at line 23: bad argument #1 to 'old_ipairs' (table expected, got nil).
  94. Lua error in ...ribunto/includes/engines/LuaCommon/lualib/mwInit.lua at line 23: bad argument #1 to 'old_ipairs' (table expected, got nil).
  95. Lua error in ...ribunto/includes/engines/LuaCommon/lualib/mwInit.lua at line 23: bad argument #1 to 'old_ipairs' (table expected, got nil).
  96. Lua error in ...ribunto/includes/engines/LuaCommon/lualib/mwInit.lua at line 23: bad argument #1 to 'old_ipairs' (table expected, got nil).
  97. Lua error in ...ribunto/includes/engines/LuaCommon/lualib/mwInit.lua at line 23: bad argument #1 to 'old_ipairs' (table expected, got nil).
  98. Lua error in ...ribunto/includes/engines/LuaCommon/lualib/mwInit.lua at line 23: bad argument #1 to 'old_ipairs' (table expected, got nil).
  99. Lua error in ...ribunto/includes/engines/LuaCommon/lualib/mwInit.lua at line 23: bad argument #1 to 'old_ipairs' (table expected, got nil).
  100. Lua error in ...ribunto/includes/engines/LuaCommon/lualib/mwInit.lua at line 23: bad argument #1 to 'old_ipairs' (table expected, got nil).
  101. Lua error in ...ribunto/includes/engines/LuaCommon/lualib/mwInit.lua at line 23: bad argument #1 to 'old_ipairs' (table expected, got nil).
  102. Lua error in ...ribunto/includes/engines/LuaCommon/lualib/mwInit.lua at line 23: bad argument #1 to 'old_ipairs' (table expected, got nil).
  103. Lua error in ...ribunto/includes/engines/LuaCommon/lualib/mwInit.lua at line 23: bad argument #1 to 'old_ipairs' (table expected, got nil).
  104. 104.0 104.1 Lua error in ...ribunto/includes/engines/LuaCommon/lualib/mwInit.lua at line 23: bad argument #1 to 'old_ipairs' (table expected, got nil).
  105. Lua error in ...ribunto/includes/engines/LuaCommon/lualib/mwInit.lua at line 23: bad argument #1 to 'old_ipairs' (table expected, got nil).
  106. Lua error in ...ribunto/includes/engines/LuaCommon/lualib/mwInit.lua at line 23: bad argument #1 to 'old_ipairs' (table expected, got nil).
  107. Lua error in ...ribunto/includes/engines/LuaCommon/lualib/mwInit.lua at line 23: bad argument #1 to 'old_ipairs' (table expected, got nil).
  108. Lua error in ...ribunto/includes/engines/LuaCommon/lualib/mwInit.lua at line 23: bad argument #1 to 'old_ipairs' (table expected, got nil).
  109. Lua error in ...ribunto/includes/engines/LuaCommon/lualib/mwInit.lua at line 23: bad argument #1 to 'old_ipairs' (table expected, got nil).
  110. Lua error in ...ribunto/includes/engines/LuaCommon/lualib/mwInit.lua at line 23: bad argument #1 to 'old_ipairs' (table expected, got nil).
  111. Lua error in ...ribunto/includes/engines/LuaCommon/lualib/mwInit.lua at line 23: bad argument #1 to 'old_ipairs' (table expected, got nil).
  112. Lua error in ...ribunto/includes/engines/LuaCommon/lualib/mwInit.lua at line 23: bad argument #1 to 'old_ipairs' (table expected, got nil).
  113. Lua error in ...ribunto/includes/engines/LuaCommon/lualib/mwInit.lua at line 23: bad argument #1 to 'old_ipairs' (table expected, got nil).
  114. Lua error in ...ribunto/includes/engines/LuaCommon/lualib/mwInit.lua at line 23: bad argument #1 to 'old_ipairs' (table expected, got nil).
  115. Lua error in ...ribunto/includes/engines/LuaCommon/lualib/mwInit.lua at line 23: bad argument #1 to 'old_ipairs' (table expected, got nil).
  116. [Exclusive Expats sidelined in Seoul’s mask-rationing Archived 14 March 2020 at the Wayback Machine
  117. Lua error in ...ribunto/includes/engines/LuaCommon/lualib/mwInit.lua at line 23: bad argument #1 to 'old_ipairs' (table expected, got nil).
  118. Lua error in ...ribunto/includes/engines/LuaCommon/lualib/mwInit.lua at line 23: bad argument #1 to 'old_ipairs' (table expected, got nil).
  119. Lua error in ...ribunto/includes/engines/LuaCommon/lualib/mwInit.lua at line 23: bad argument #1 to 'old_ipairs' (table expected, got nil).
  120. Lua error in ...ribunto/includes/engines/LuaCommon/lualib/mwInit.lua at line 23: bad argument #1 to 'old_ipairs' (table expected, got nil).
  121. Lua error in ...ribunto/includes/engines/LuaCommon/lualib/mwInit.lua at line 23: bad argument #1 to 'old_ipairs' (table expected, got nil).
  122. https://thediplomat.com/2020/04/south-korea-cyberbullying-amid-coronavirus/
  123. Lua error in ...ribunto/includes/engines/LuaCommon/lualib/mwInit.lua at line 23: bad argument #1 to 'old_ipairs' (table expected, got nil).
  124. Lua error in ...ribunto/includes/engines/LuaCommon/lualib/mwInit.lua at line 23: bad argument #1 to 'old_ipairs' (table expected, got nil).
  125. Lua error in ...ribunto/includes/engines/LuaCommon/lualib/mwInit.lua at line 23: bad argument #1 to 'old_ipairs' (table expected, got nil).
  126. Lua error in ...ribunto/includes/engines/LuaCommon/lualib/mwInit.lua at line 23: bad argument #1 to 'old_ipairs' (table expected, got nil).
  127. Lua error in ...ribunto/includes/engines/LuaCommon/lualib/mwInit.lua at line 23: bad argument #1 to 'old_ipairs' (table expected, got nil).
  128. Lua error in ...ribunto/includes/engines/LuaCommon/lualib/mwInit.lua at line 23: bad argument #1 to 'old_ipairs' (table expected, got nil).
  129. Lua error in ...ribunto/includes/engines/LuaCommon/lualib/mwInit.lua at line 23: bad argument #1 to 'old_ipairs' (table expected, got nil).
  130. Lua error in ...ribunto/includes/engines/LuaCommon/lualib/mwInit.lua at line 23: bad argument #1 to 'old_ipairs' (table expected, got nil).
  131. Lua error in ...ribunto/includes/engines/LuaCommon/lualib/mwInit.lua at line 23: bad argument #1 to 'old_ipairs' (table expected, got nil).
  132. How South Korea Put Into Place the World’s Most Aggressive Coronavirus Test ProgramArchived 17 March 2020 at the Wayback Machine
  133. South Korea's Drive-Through Testing For Coronavirus Is Fast — And Free Archived 17 March 2020 at the Wayback Machine
  134. Lua error in ...ribunto/includes/engines/LuaCommon/lualib/mwInit.lua at line 23: bad argument #1 to 'old_ipairs' (table expected, got nil).
  135. Lua error in ...ribunto/includes/engines/LuaCommon/lualib/mwInit.lua at line 23: bad argument #1 to 'old_ipairs' (table expected, got nil).
  136. Lua error in ...ribunto/includes/engines/LuaCommon/lualib/mwInit.lua at line 23: bad argument #1 to 'old_ipairs' (table expected, got nil).
  137. Lua error in ...ribunto/includes/engines/LuaCommon/lualib/mwInit.lua at line 23: bad argument #1 to 'old_ipairs' (table expected, got nil).
  138. Lua error in ...ribunto/includes/engines/LuaCommon/lualib/mwInit.lua at line 23: bad argument #1 to 'old_ipairs' (table expected, got nil).
  139. Virus Testing Blitz Appears to Keep Korea Death Rate Low Archived 9 March 2020 at the Wayback Machine
  140. Seegene launches KFDA Approved COVID-19 AssayArchived 19 February 2020 at the Wayback Machine
  141. Lua error in ...ribunto/includes/engines/LuaCommon/lualib/mwInit.lua at line 23: bad argument #1 to 'old_ipairs' (table expected, got nil).
  142. Coronavirus: South Korea’s aggressive testing gives clues to true fatality rate Archived 10 March 2020 at the Wayback Machine
  143. Lua error in ...ribunto/includes/engines/LuaCommon/lualib/mwInit.lua at line 23: bad argument #1 to 'old_ipairs' (table expected, got nil).
  144. 144.0 144.1 First 'drive-thru' coronavirus testing station opens in South Australia Archived 10 March 2020 at the Wayback Machine
  145. Other countries are testing patients for coronavirus by the tens of thousands. Why the U.S. is so far behind Archived 4 March 2020 at the Wayback Machine
  146. 146.0 146.1 146.2 CNN NEWS- 10 March 2020:South Korea has 'passed the peak' of the coronavirus outbreak, health minister hopes Archived 10 March 2020 at the Wayback Machine

External links[edit source | edit]

Media related to 2020 coronavirus pandemic in South Korea at Wikimedia Commons
Media related to Press releases about the COVID-19 pandemic by Ministry of Health and Welfare (South Korea) at Wikimedia Commons